Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.groff.bug > #1950

[bug #58796] preconv: want option to write traditional [g|t]roff special characters where possible

Path csiph.com!goblin3!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From Ingo Schwarze <INVALID.NOREPLY@gnu.org>
Newsgroups gnu.groff.bug
Subject [bug #58796] preconv: want option to write traditional [g|t]roff special characters where possible
Date Wed, 5 Aug 2020 09:50:29 -0400 (EDT)
Lines 40
Approved bug-groff@gnu.org
Message-ID <mailman.889.1596635431.2739.bug-groff@gnu.org> (permalink)
References <20200721-112756.sv108747.43680@savannah.gnu.org> <20200725-150219.sv93119.61886@savannah.gnu.org> <20200725-204112.sv97361.22511@savannah.gnu.org> <20200730-121108.sv93119.91224@savannah.gnu.org> <20200805-135029.sv97361.28717@savannah.gnu.org>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain;charset=UTF-8
X-Trace usenet.stanford.edu 1596635431 10106 209.51.188.17 (5 Aug 2020 13:50:31 GMT)
X-Complaints-To action@cs.stanford.edu
To "G. Branden Robinson" <g.branden.robinson@gmail.com>, Dave <saint.snit@gmail.com>, Ingo Schwarze <schwarze@usta.de>, bug-groff@gnu.org
Envelope-to bug-groff@gnu.org
X-PHP-Originating-Script 1001:sendmail.php
X-Savane-Server savannah.gnu.org:443 [209.51.188.72]
X-Savane-Project groff
X-Savane-Tracker bugs
X-Savane-Item-ID 58796
User-Agent Mozilla/5.0 (X11; OpenBSD amd64; rv:77.0) Gecko/20100101 Firefox/77.0
X-Apparently-From 87.173.125.204 (Savane authenticated user schwarze)
In-Reply-To <20200730-121108.sv93119.91224@savannah.gnu.org>
X-BeenThere bug-groff@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id "Bug reports for the GNU version of nroff, troff et al" <bug-groff.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-groff>, <mailto:bug-groff-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-groff>
List-Post <mailto:bug-groff@gnu.org>
List-Help <mailto:bug-groff-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-groff>, <mailto:bug-groff-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <20200805-135029.sv97361.28717@savannah.gnu.org>
X-Mailman-Original-References <20200721-112756.sv108747.43680@savannah.gnu.org> <20200725-150219.sv93119.61886@savannah.gnu.org> <20200725-204112.sv97361.22511@savannah.gnu.org> <20200730-121108.sv93119.91224@savannah.gnu.org>
Xref csiph.com gnu.groff.bug:1950

Show key headers only | View raw


Follow-up Comment #4, bug #58796 (project groff):

Regarding note #3 (it's all a bit tangential to this ticket):

I meant requiring iconv(3) at compile time, not iconv(1) at run-time.  The
former would be horrible, the latter almost harmless.

I neither think that groff is really C++, it is more like C with some aspects
of classes, nor am i aware of features in C++ to handle Unicode.  When you
handle Unicode in C++, you just use C library features.  And Unicode handling
in Perl and C is totally different, so much so that i can hardly think of any
commonalities, so talking about Perl is really pointless here.

C features for handling Unicode are so bad that even for a new program, i
would seriously consider making it ASCII only even today rather than using
them.  When Kristaps started mandoc ten years ago, he made exactly that
decision, and i'm very grateful to him for that, is was a very wise decision. 
Even though internally, it uses practically no C-library Unicode-handling
features and no other Unicode-handling library, it has practically perfect and
in particular extremely robust and simple Unicode support.  I very much doubt
that converting an existing program like groff would be a good idea, even if
you had time to waste for a purely make-work project, in particular since
groff already has a way for handling Unicode that works reasonably well and is
simpler and more robust than anything you could do with the native C library
features.

Of course, all this turns out to argue slightly in favour of Branden's idea,
but i still think this ticket isn't high priority.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58796>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/

Back to gnu.groff.bug | Previous | Next | Find similar


Thread

[bug #58796] preconv: want option to write traditional [g|t]roff special characters where possible Ingo Schwarze <INVALID.NOREPLY@gnu.org> - 2020-08-05 09:50 -0400

csiph-web