Re: [Rosegarden-devel] Notation Strings update

[Hans K. <hki...@ma...>]

I do know the KDE i18n mailing list has spoken out several times on "all KDE apps must start with en_US" and then be translated.  I don't know specifically that this means "all apps that use KDE" and not just "all apps in the KDE foundation", but I can't seem to get the "translated" en_US strings to appear on my machine, so that's my bet.

However, as an American, I can't say I'd really miss having an en_US version.  It might be absolutely fine to have English (British) as the "base" language as long as the option to have either style of note-naming was there.

Then the only problem would be dealing with bug reports telling you your spelling "behavior" is "internationalized" incorrectly.

and you should just need to install kdebase, kde-i18n-en_GB, and maybe locales-i18n-en_GB.

----- Original Message -----
From: Chris Cannam <ca...@al...>
Date: Wed, 5 Feb 2003 21:33:43 +0000 
To: "Hans Kieserman" <hki...@ma...>, ros...@li...
Subject: Re: [Rosegarden-devel] Notation Strings update

> On Wednesday 05 February 2003 21:01, Hans Kieserman wrote:
> > Do you think it would be useful to directly translate American
> > names into another language- does anyone do that?
> >
> > Also, the original scheme as you mentioned worked for English users
> > who wanted American note names, but not vice-versa.  I'm afraid it
> > might be therefore only really useful in one language (i.e. in that
> > situation)
> 
> Well, the motivation really is that some people learn note names from 
> software than uses terse names like "1/16" rather than from music 
> teachers, so regardless of what the "proper" name for that note may 
> be in their own language, the concept of a sixteenth note may be more 
> familiar (even when written in full and translated, rather than 
> written briefly as 1/16).  Bownie is an example of one such person in 
> English, I think, and I'm sure there must be numerous people whose 
> native languages are not English but who are nevertheless more 
> familiar with American names than "their own".
> 
> In that sense I guess it's an admission that the American names are a 
> sort of common language, which answers your second paragraph: if an 
> American user wants British names, that's frankly their problem and 
> there's no reason the software should make it as simple as the 
> British user who only really knows American names because they're 
> what's used everywhere else.  Cultural imperialism blah blah blah.
> 
> As for whether we actually would want to translate the American names, 
> I really don't know.
> 
> But impossible to translate to en-US!  That's not just obnoxious, it 
> seems counter-productive too: it means the strings hardcoded into the 
> file would have to be the final word on how they'll appear to 
> American users, which means not only would it be harder to modify 
> them after the fact, but that Americans would be likely to get a 
> substandard GUI if the program wasn't actually written by Americans.  
> Can it really be true?
> 
> Anyway, if US becomes the default, I'd have to make an en-GB 
> translation forthwith.  Then all I'd have to do is work out how to 
> get it to use that translation on machines on which I'm not running 
> KDE.
> 
> 
> Chris
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Rosegarden-devel mailing list
> Ros...@li...
> https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup