Guix System installer text direction wrong for RTL languages

  • Open
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • pelzflorian (Florian Pelz)
Owner
unassigned
Submitted by
pelzflorian (Florian Pelz)
Severity
important

Debbugs page

P
P
pelzflorian (Florian Pelz) wrote on 19 Apr 2019 03:05
(address . bug-guix@gnu.org)
20190419100534.u264vkx5cwcmkby4@pelzflorian.localdomain
On Wed, Apr 17, 2019 at 12:06:31PM +0200, Ludovic Courtès wrote:
Toggle quote (5 lines)
> I made changes to the installer so it’s almost ready as far as I’m
> concerned. It now displays language and territory names in the right
> language.
>

Language names for Arabic, Farsi, Hebrew are shown Left-to-Right (LTR)
instead of Right-to-Left, e.g. العربية is displayed wrongly as ‭العربية‬.

Regards,
Florian
L
L
Ludovic Courtès wrote on 19 Apr 2019 08:26
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . 35319@debbugs.gnu.org)
87h8auaudw.fsf@gnu.org
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

Toggle quote (9 lines)
> On Wed, Apr 17, 2019 at 12:06:31PM +0200, Ludovic Courtès wrote:
>> I made changes to the installer so it’s almost ready as far as I’m
>> concerned. It now displays language and territory names in the right
>> language.
>>
>
> Language names for Arabic, Farsi, Hebrew are shown Left-to-Right (LTR)
> instead of Right-to-Left, e.g. العربية is displayed wrongly as ‭العربية‬.

Ouch, good point! I have no idea what it takes to display RTL languages
properly. AFAIK ‘gettext’ simply returns a string, so I guess it’s up
to the UI toolkit (Newt?) to do the right thing?

Ludo’.
P
P
pelzflorian (Florian Pelz) wrote on 19 Apr 2019 11:11
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 35319@debbugs.gnu.org)
20190419181149.xdxscrfz3d2kxi3a@pelzflorian.localdomain
On Fri, Apr 19, 2019 at 05:26:35PM +0200, Ludovic Courtès wrote:
Toggle quote (16 lines)
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>
> > On Wed, Apr 17, 2019 at 12:06:31PM +0200, Ludovic Courtès wrote:
> >> I made changes to the installer so it’s almost ready as far as I’m
> >> concerned. It now displays language and territory names in the right
> >> language.
> >>
> >
> > Language names for Arabic, Farsi, Hebrew are shown Left-to-Right (LTR)
> > instead of Right-to-Left, e.g. العربية is displayed wrongly as ‭العربية‬.
>
> Ouch, good point! I have no idea what it takes to display RTL languages
> properly. AFAIK ‘gettext’ simply returns a string, so I guess it’s up
> to the UI toolkit (Newt?) to do the right thing?
>

Debian has a similar bug:


The


says:

Debian's version of newt include Bidirectional text support not yet present
upstream, including an API addition "newtCheckboxSetWidth". Please only use
this within Debian until it is supported upstream.

There is a


However, I do not know how to use this.

Regards,
Florian
L
L
Ludovic Courtès wrote on 19 Apr 2019 16:00
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . 35319@debbugs.gnu.org)
878sw5bnxm.fsf@gnu.org
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

Toggle quote (14 lines)
> The
>
> https://salsa.debian.org/mckinstry/newt/blob/debian/master/debian/README.Debian
>
> says:
>
> Debian's version of newt include Bidirectional text support not yet present
> upstream, including an API addition "newtCheckboxSetWidth". Please only use
> this within Debian until it is supported upstream.
>
> There is a
>
> https://salsa.debian.org/mckinstry/newt/blob/debian/master/debian/patches/bidi.patch

Thanks for researching it. We may be unable to fix it for 1.0 but we
should definitely address it.

Ludo’.
L
L
Ludovic Courtès wrote on 9 Apr 2020 00:38
control message for bug #35319
(address . control@debbugs.gnu.org)
875ze95ctb.fsf@gnu.org
severity 35319 important
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 35319@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 35319
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch