bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints


From: G. Branden Robinson
Subject: [bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints
Date: Wed, 21 Oct 2020 02:54:43 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Update of bug #42233 (project groff):

                  Status:                    None => Invalid                
             Assigned to:                    None => gbranden               
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #2:

Steffen has withdrawn most/all of his other patches and even after reading
this report a few times I'm not clear on what exactly the problem is supposed
to be.

The "solution", "drop gnulib", is not likely, especially not during an RC
cycle.

This could be reopened if we had a simple, reproducible case of groff actually
misbehaving.

> I think currently groff makes false use of wcwidth(3): if it finds the
`unicode' property in a `DESC' file it uses wcwidth(3) to determine the visual
width, not taking into account the current locale, but which wcwidth(3)
depends upon.

I don't understand why the width of a Unicode character would be
locale-dependent.  As I understand it, the width property (half-width,
full-width, undefined) is determined on a per-codepoint basis and while it
might vary, there's no reason to expect it to vary based on the _locale_. 
More likely, I think, it would vary due to choices taken by a font vendor, and
people using the font would be forced to adapt.

Closing.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]