9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] localization
Date: Wed, 27 Apr 2011 20:04:09 +0200	[thread overview]
Message-ID: <20110427180409.GA427@polynum.com> (raw)
In-Reply-To: <201104271759.08417.dexen.devries@gmail.com>

Hello,

On Wed, Apr 27, 2011 at 05:59:08PM +0200, dexen deVries wrote:
> browsing through uriel's slides from fosdem 2006 [1], i see him mention Plan 9
> lacks localization. what are this lists feelings on localization (both
> translation of strings and formatting of numbers, time etc.) of user-facing
> applications?
>
> the only model i know right now is gettext() and related from GNU; there's
> gotta be a better way; perhaps an fs for it? ;-)

As an example of the joy of the localization, switching recently KerGIS
servers from NetBSD 3.x to NetBSD 5.x, the same code recompiled would
give errors, with cryptic messages, until I happen to pin the problem to
the formating of numbers... I use, as a backup version of files, a text
(mainly ASCII) transcription of the data, and use 'd.d' for example. But
since users had LC_ALL set to french, NetBSD 3.x didn't support nor time
neither number localization so no problem, but 5.x now does. Result :
"french" 'd,d' was expected for input; and 'd,d' sent for output. Joy!

For another mean instead of gettext(), you have what has done Donald E.
Knuth with TeX and al: : all the strings are extracted in a "pool"
file---a text file---, so as long as one sticks to the index (the
position), one can provide a translated pool file to localize.

Furthermore, IMHO, there are 3 levels:

- 0: firmware/kernel: LANG C (a restricted faulty subset of english)
- 1: system libraries and utils, directly used by programmers, not
really users: LANG C (idem)
- 2: user level scripts or programs; since they are adapted for higher
level manipulation, the levels 0 and 1 messages have no meaning for the
user, so it is useless to translate. And since level 2 shall match the
user (here is the business!), this is not a problem.

So, for me at least, the best solution to this difficult problem is the
one provided for Plan9 by Rob Pile and Ken Thompson (I cite the authors
of the "Hello World or...", i.e. UTF8.

More is too much.
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C




  parent reply	other threads:[~2011-04-27 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 15:59 dexen deVries
2011-04-27 16:14 ` erik quanstrom
2011-04-27 17:08   ` Gabriel Diaz
2011-04-27 17:20     ` Lluís Batlle i Rossell
2011-04-27 18:17       ` erik quanstrom
2011-04-27 20:45         ` Lluís Batlle i Rossell
2011-04-27 20:51           ` dexen deVries
2011-04-27 21:00           ` erik quanstrom
2011-04-27 21:52           ` smiley
2011-04-27 18:04 ` tlaronde [this message]
2011-04-27 21:29   ` Iruatã Souza
  -- strict thread matches above, loose matches on Subject: below --
2005-02-05 12:52 Sergey Reva
2005-02-05 14:51 ` Steve Simon

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=20110427180409.GA427@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).