Path: csiph.com!news.uzoreto.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Dave Newsgroups: gnu.groff.bug Subject: [bug #58930] take baby steps toward Unicode Date: Sat, 15 Aug 2020 20:53:18 -0400 (EDT) Lines: 57 Approved: bug-groff@gnu.org Message-ID: References: <20200810-095606.sv93119.42780@savannah.gnu.org> <20200814-100002.sv108747.62919@savannah.gnu.org> <20200814-220415.sv93119.59625@savannah.gnu.org> <20200814-222905.sv93119.21750@savannah.gnu.org> <20200815-040539.sv108747.29165@savannah.gnu.org> <20200815-123802.sv93119.34881@savannah.gnu.org> <20200815-174643.sv108747.91177@savannah.gnu.org> <20200815-195318.sv93119.97497@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 1597539200 25343 209.51.188.17 (16 Aug 2020 00:53:20 GMT) X-Complaints-To: action@cs.stanford.edu To: "G. Branden Robinson" , Dave , bug-groff@gnu.org Envelope-to: bug-groff@gnu.org X-PHP-Originating-Script: 1001:sendmail.php X-Savane-Server: savannah.gnu.org:443 [2001:470:142::72] X-Savane-Project: groff X-Savane-Tracker: bugs X-Savane-Item-ID: 58930 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 X-Apparently-From: 2605:a601:ab42:5b00:d79a:70a3:b6a4:34bf (Savane authenticated user barx) In-Reply-To: <20200815-174643.sv108747.91177@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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20200815-195318.sv93119.97497@savannah.gnu.org> X-Mailman-Original-References: <20200810-095606.sv93119.42780@savannah.gnu.org> <20200814-100002.sv108747.62919@savannah.gnu.org> <20200814-220415.sv93119.59625@savannah.gnu.org> <20200814-222905.sv93119.21750@savannah.gnu.org> <20200815-040539.sv108747.29165@savannah.gnu.org> <20200815-123802.sv93119.34881@savannah.gnu.org> <20200815-174643.sv108747.91177@savannah.gnu.org> Xref: csiph.com gnu.groff.bug:1982 Follow-up Comment #7, bug #58930 (project groff): [comment #4 comment #4:] > just lamenting the total disjunctivity of the set. That two of the three, intended to serve different purposes, are disjunct seems more laudable than lamentable. But I'm not here to police your feelings. > I can't think of a more appropriate mapping for it. Well, if there were a more appropriate mapping for \[u00A0], that mapping should also apply to the Latin-1 A0. They're the same character, just with different input representations. Speaking more generally, for a Latin-1 input file, "groff latin1.txt" and "groff -Klatin1 latin1.txt" should produce identical output. Presently, for this character they do not. > Might as well sweep that one into this report, then. As long as it doesn't change the billing, I won't complain about you doing more work than I asked for. > tmac/pdf.tmac sources tmac/ps.tmac so the fix only has to be made in one place. I should have said "notably but not limited to -Tps and -Tpdf." Fixing this in the device-specific tmac file then requires duplicating that fix for at least -Tascii, -Tlatin1, and the various -TX* devices, and I couldn't even begin to guess about the more obscure legacy devices. On the one hand, I get that \[u2011] is a character, and characters are mapped to glyphs, and glyphs reside in fonts, and fonts are device-specific, so some device-specific code seems a reasonable place to handle it. But zooming out, the semantics of U+2011 NON-BREAKING HYPHEN are not device-specific; as an output glyph, it is always identical (as you note) to \[hy], or \[u2010]. What separates them is its behavior--and this should be the same across all devices, suggesting it should be handled in a device-independent section of the code. I mean, I don't want to back-seat drive, and tell you your very simple solution, which covers most output formats most people care about, isn't good enough--except I guess I do, because that's kind of what I'm doing. _______________________________________________________ Reply to this item at: _______________________________________________ Message sent via Savannah https://savannah.gnu.org/