Update of bug #65654 (group groff):
Status: Need Info => Rejected
Assigned to: None => gbranden
Summary: preconv.cpp: Issue a warning if code '0xA0' is used
in the input and thus changed to '\~' => [preconv] want a warning if code
'0xA0' is used in the input
_______________________________________________________
Follow-up Comment #3:
Dave has convinced me.
If the input code point U+00A0, which is valid as _groff_ input, is not
desired in a source file, write a Makefile/shell script to detect it.
Same as if you wanted to compose a document without using, say, an asterisk.
(Good luck with string interpolations, though.)
Closing as rejected.
[comment #2 comment #2:]
> ...there is no reason for preconv to warn about this. The same issue exists
no matter what Unix tool processes input containing both characters. Users
may choose to avoid U+00A0 in their input files for this reason, or they may
use other strategies to deal with it. It is not preconv's job to police this
usage. Users who desire such warnings can write a simple preprocessor (using
grep or sed, perhaps) to emit them.
>
> Once you start down the rabbit hole of "warn the user about characters that
are hard to visually tell apart," where do you stop? In the monospace fonts
used in most terminals, you'd be hard-pressed to distinguish U+2012 FIGURE
DASH from U+2013 EN DASH. Unicode has a plethora of space-like and dash-like
characters. Should preconv warn about all of these? That seems absurd.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65654>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
