Update of bug #65710 (group groff):
Status: Need Info => None
_______________________________________________________
Follow-up Comment #3:
[comment #2 comment #2:]
> [comment #0 original submission:]
> > In my opinion preconv should either:
> >
> > 1. Fail and force the user to edit the input to make a real
> > choice, eliminating U+00A0 in the input.
>
> This option seems materially the same as the rejected bug #65654, except
with that bug's proposed warning upgraded to a fatal error. (Granted, #65654
was rejected a few days before bug #65693 (the current ticket's inciting
report) was opened.)
Yes.
Bjarni's prescription was much too strong.
Subject: preconv.cpp: Issue a warning if code '0xA0' is used in
the input and thus changed to '\~'
File: "src/preproc/preconv/preconv.cpp"
Subroutine: unicode_entity(int u)
The code '0xA0' is displayed as a normal space, and is thus
visually the same as it.
So authors better use '\~' directly in their files.
No, authors has better not, necessarily, use `\~` directly in their files.
_Maybe_ they mean `\ ` (an unadjustable space). It's impossible to know,
which is why they should disambiguate it.
And if there are multiple U+00A0 characters in sequence, the author might be
better off supplying a `\h` sequence to express what it is they want,
precisely.
A ticket grounded on sound principles often meets a better fate than one
grounded on poor ones.
One could of course accuse me of authorial ("submittorial"?) bias...
At this point I'm leaning toward solution 1 from comment #0.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65710>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
