All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: localization of Grub
Date: Mon, 29 Sep 2008 23:47:33 +0200	[thread overview]
Message-ID: <1222724853.25662.2.camel@localhost> (raw)
In-Reply-To: <48E122E7.5060004@nic.fi>

[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]

El lun, 29-09-2008 a las 21:48 +0300, Vesa Jääskeläinen escribió:
> Robert Millan wrote:
> > On Sun, Sep 28, 2008 at 11:49:54PM +0200, Carles Pina i Estany wrote:
> >>>   - gettextise the util tools, so they can be translated as normal
> >>>   programs.
> >> ok! (I guess/hope that will be more "burocratic" work than new work)
> > 
> > It _is_ technical work I think, but less fun than the other part :-/
> > 
> >> I don't expect to have time until 22th October (aprox.). I have more
> >> interest in the second part (it's "newer") than first part, but first
> >> part has a practical and fast effects with (I think) less investment.
> > 
> > The second part also builds on the first, to some extent.  I.e. if you want
> > to test gettext support in GRUB itself, you need some strings to translate,
> > and these are provided by the .mo files which are only built if the build
> > system supports that, etc.
> 
> Before you guy's go too deep in detail I would like to remind special
> requirements for graphical user interface related to localization.
> 
> You can't just printf stuff to screen in there. There has to be some
> changes in logic how information is presented to user. Currently there
> is lot of printf's in the code to display information and that is not
> going to be too pretty for graphical menu as we need to display some
> kind of console on event when there is something to be displayed.
> 
> Also try to think how different languages differentiate for displaying
> certain types of information. Here is some simple example. (Bear in mind
> if there are grammatical errors or typos or so :))
> 
> (eng) "See Figure 2 in page 14 for more details.' -> (fin) "Sivulla 14
> olevassa kuvassa 2 on enemmän tietoa asiasta.'
> 
> Please notice difference in order of arguments in the languages.
> 
> Also there are some weird scripts that change order of characters. In
> example for some right-to-left scripts seem to have this feature. On
> example that I think belongs to this group is hebrew where they normally
> write from right-to-left, but for English (or foreign) texts are still
> visually correct.
> 
> In example:
> "<native>This is native 1</native><english>2and this is
> English3</english><native>4, so weird.</native>"
> 
> Would be something like:
> ".rdiew os ,42and this is English31 evitan si sihT"
> 
> So this subject really has more details than meets the eye in first sight :)
> 
Well, no one proposed a full implementation of the Unicode bi-di
algorithm, and I think such a complex feat goes way beyond the
development power behind GRUB right now. However, gettext does allow for
the changes in the argument order you are worried about. Thus, there
should be no problem translating the interface to LTR languages for the
time being.

-Habbit

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2008-09-29 21:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26  8:16 localization of Grub Carles Pina i Estany
2008-09-26  8:34 ` Carles Pina i Estany
2008-09-26 11:13   ` Felix Zielcke
2008-09-26 12:19     ` Carles Pina i Estany
2008-09-28 13:39       ` Robert Millan
2008-09-28 21:49         ` Carles Pina i Estany
2008-09-29 14:59           ` Robert Millan
2008-09-29 18:48             ` Vesa Jääskeläinen
2008-09-29 21:47               ` Javier Martín [this message]
2008-09-29 23:14               ` Carles Pina i Estany
2008-09-29 22:55             ` Carles Pina i Estany
2008-12-07 23:33         ` Carles Pina i Estany
2008-12-08 14:33           ` Carles Pina i Estany
2008-12-14  1:03             ` Robert Millan
2009-01-04 11:36               ` Carles Pina i Estany
2008-12-14  1:02           ` Robert Millan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1222724853.25662.2.camel@localhost \
    --to=lordhabbit@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.