[bug #58930] take baby steps toward Unicode

[Dave]

Follow-up Comment #11, bug #58930 (project groff):

It's a judgement call, certainly.  Is a change that allows groff to handle
U+2011 on some output devices but incorrectly kerns it better or worse than
having groff emit a warning and discard the character?  In the latter case,
the user has a clear sign that his input is not understood.  In the former,
the input is accepted for PostScript/PDF but produces subpar typography and
gives the user no sign that anything is amiss (though it would at least not be
the only miskerned character in Unicode's General Punctuation block: see bug
#58897).

My perfectionist tendencies argue for either implementing a solution that is
100% correct (as far as testing can demonstrate anyway) or bluntly telling the
user "sorry, don't know how to do that."  But an 80%-correct solution is not
without merit.

    _______________________________________________________

Reply to this item at:

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

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