bugGNU roff - Bugs: bug #65693, exceptions to NBSP statement in...

 
 

bug #65693: exceptions to NBSP statement in groff_char(7) should be documented

Submitter:  Dave <barx>
Submitted:  Mon 06 May 2024 07:06:11 AM UTC
   
 
Category:  Core Severity:  2 - Minor
Item Group:  Documentation Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 09 May 2024 06:45:47 AM UTC, comment #2: 

Given the arguments in favor of the U+00A0 to \~ mapping presented in bug #58962 and bug #65710, I now wonder if groff might be better off doing something heretical like ignoring the u00A0 glyph in a font and applying its own mapping to that character.  That is, rather than documenting the exception to the cited groff_char(7) sentence, make that sentence universally true.

Dave <barx>
Group Member
Tue 07 May 2024 11:51:15 AM UTC, comment #1: 

Related: bug #65710.

G. Branden Robinson <gbranden>
Group administrator
Mon 06 May 2024 07:06:11 AM UTC, original submission:  

groff_char(7) states, "a no-break space... is mapped to \~, the adjustable non-breaking space escape sequence."

But as Deri and Bjarni point out in bug #62300, some fonts (including many URW fonts groff installs for devpdf) include a u00A0 glyph, which is necessarily of a fixed width.

Demonstration (when using -Tpdf):

.ft U-TR
a b c
.brp
a b\~c
.brp
a b\[u00A0]c
.brp

The results are the same if "\[u00A0]" is replaced with the corresponding Latin-1 character.

Dave <barx>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by gbranden (Posted a comment)
  • -email is unavailable- added by barx (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code