From: Gabriel Diaz <gdiaz@9grid.es>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] localization
Date: Wed, 27 Apr 2011 19:08:27 +0200 [thread overview]
Message-ID: <BANLkTimCOwdjQa-zbuV8KY9xG7CdRJp-8A@mail.gmail.com> (raw)
In-Reply-To: <39dfebd1c4a2b418969b09c701998fc3@ladd.quanstro.net>
Hello
We install operating systems in English. Spanish / Catalan localized
systems are a source of problems like:
* error messages do not reflect was going on in Spanish but it does in
English, and in some cases it can mislead the user, jumping to a
wrong conclusion
* translations are often outdated, referring to things not present in
the system anymore
* applications do not always use the localization engine of the
system, so you end with multiple languages and localization
implementations, grep-ing though a localized log file is painfull if
you must deal with more than one language (and can lead you to use
error codes)
* jargon is usually translated and used in strange way at best, also
the 'false friends' words are difficult to handle in an automated way
I would prefer to have a system completely in English but polished,
instead of a badly or half translated system.
"La memoria no se puede 'written'" is a common windows error, which
shows the kind of problems they found.
slds.
gabi
On Wed, Apr 27, 2011 at 6:14 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> !/bin/upas/marshal -s 'Re: [9fans] localization' -R /mail/fs/mbox/3100 9fans@9fans.net
> On Wed Apr 27 12:04:56 EDT 2011, dexen.devries@gmail.com 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?
>
> it's not the implementation that bothers me so much as the
> theory of operation. command-line utilities are localized s.t.
> it becomes necessary to fiddle with the locale if you want to
> parse the output. but then you can't present this as localized
> output yourself easily. localization can go as far as changing the set
> of digits, or even the default numbering base! they also don't
> choose a character set. shell scripting becomes impossible.
>
> i realize no localization makes life difficult for folks who speak greek.
> it would be interesting to hear from a non-native english speaker
> on if they think dealing with the computer in english is something
> that can be done once and then forgotten, and if this is less work
> than dealing with the tower of locale.
>
> it would be interesting to hear ideas on this. it's a hard problem.
>
> - erik
>
>
next prev parent reply other threads:[~2011-04-27 17:08 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 [this message]
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
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=BANLkTimCOwdjQa-zbuV8KY9xG7CdRJp-8A@mail.gmail.com \
--to=gdiaz@9grid.es \
--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).