[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #9, bug #62300 (group groff): [comment #7 comment #7:] > if the above is in fact the case, one of us should open a new bug report. Bug #65693 ___ Reply to this item at:

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #8, bug #62300 (group groff): The glyph 'u00A0' is defined in "groff/build/font/devpdf/U-*" except in U-ZD: U-AB:u00A0 280,0 0 690 uni00A0 -- U-ABI:u00A0 280,0,0,0,500 690 uni00A0 -- U-AI:u00A0 277,0,0,0,500 690

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #7, bug #62300 (group groff): [comment #6 comment #6:] > the font defines operators for the glyph, which results in a > space of a certain width. This is a fixed width? If so, such fonts provide an undocumented exception to this statement in groff_char(7): "a no-break space...

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #6, bug #62300 (group groff): \[u00A0] is meaningful if you are using a font which defines the glyph. (I appear to have about 67 fonts which define the glyph, some even define kern pairs for the glyph, and one tibetan font defines composites using it). Groff does not convert it

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #5, bug #62300 (group groff): [comment #2 comment #2:] > The input sequence '\[u00A0]' is _syntactically_ valid...but > like '\[u]' and '\[u]', it's not _meaningful_ Dear future me: next time you run across this comment and think "I responded to this somewhere" but

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #4, bug #62300 (project groff): > Convert input U+00A0 to \~ as troff would, not to \[u00A0]. ...or as troff _should_, were it not for bug #58962. ___ Reply to this item at:

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Update of bug #62300 (project groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.23.0

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #2, bug #62300 (project groff): Hi Bjarni, [comment #1 comment #1:] > commit f47b7dd139525bf3b8b4fbe767c3a45816c8445a > Author: Bjarni Ingi Gislason > Date: Sat Nov 17 15:59:09 2018 + > > The character \[u00A0] is not recognized > > The input character

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

Follow-up Comment #1, bug #62300 (project groff): commit f47b7dd139525bf3b8b4fbe767c3a45816c8445a Author: Bjarni Ingi Gislason Date: Sat Nov 17 15:59:09 2018 + The character \[u00A0] is not recognized The input character "no-break space" (' ', 0xA0) is mapped by "groff"

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

URL: Summary: [preconv] does not handle U+00A0 (NBSP) as it should Project: GNU troff Submitted by: gbranden Submitted on: Tue 12 Apr 2022 03:14:52 AM UTC Category: Preprocessor