Re: Translation of program names

["Andrew W. Nosenko" <awn bcs zp ua>]

Mariano Suarez-Alvarez wrote:
: Hi,
: 
: On Thu, 2003-10-30 at 15:48, Christian Rose wrote:
: 
: > To sum my points up:
: > 1) Translate descriptive names.
: > 2) Do *not* translate branding names.
: 
: This leaves the problem that people using scripts other than those
: derived from latin will get to see the names written in a script they
: are not necessarily familiar with in branding names.

The "people unable to see us-ascii" charset is imagined problem only.
Do you see any software/hardware pair where this is impossible?

Please note: I'm say about us-ascii charset, which used indeed in the
default .desktop entries and in the "C" locale, not about some generic
latin-based script.

If Mariano (or anyone who have similar things) whant to support hardware
and peoples unable to see us-ascii charset, then his need to redesign
GNOME entirelly (fallbacks to the us-ascii), redesign hardware entirelly
(hardcoding of some charsets and removing of us-ascii that exist always
if not removed especially), redesign OS entirelly (how you want to
exeute e.g. `cat' commаnd if you unable to enter this command and see
name of this command and to stare name of the program that impliments
this command?

I can to say more, but IMO previos paragraph is enough (may be).

GNOME should to support charsets another than us-ascii and latin1.  And
GNOME do it.  Not in all casesm, but in many.  But requesting to support
cases when us-ascii is inaccessible...  Or force users to work when
*real* information (as contrast to the imaginied, like to translated
program names) is inaccessible...


-- 
Andrew W. Nosenko    (awn bcs zp ua)