Follow-up Comment #9, bug #59402 (group groff):

[comment #7 comment #7:]
> Preconv has not used NFD it has just 'passed on' the characters
> which have been already decomposed (NFD) by uconv.

That's my intended point: preconv is NF-agnostic.  It merely reflects its
input, whether that be uconv output or some UTF-8 file a user has encoded in
either NFC or NFD.  Preconv itself never makes those decisions.

> if someone has gone to the great trouble of decomposing
> a character before passing it to groff/preconv they must
> really, really want the output to be 'built' from 2 separate
> glyphs rather than the composed glyph which would normally
> be used. Who are we to argue!!

To play quasi-devil's advocate: "we" are typesetters, who are in a decent
position to know what will look best on the page.  What we _don't_ know is
whether someone has indeed gone to great trouble of decomposing a character
because they want want the output to be composed of two glyphs, or whether
they're using NFD for reasons wholly unrelated to troff, not knowing (nor,
ideally, needing to care) which form typesets the best.  Such users may
reasonably expect troff, a typesetting program, to give them the best possible
typeset output from their input.

But until libc provides a read_users_mind() module, groff has no way to
distinguish the above two cases.  So I reckon we'll have to settle for
prominently documenting the hazards of feeding NFD to groff.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to