• Status Closed
  • Percent Complete
  • Task Type Feature Requests
  • Category User Interface → Language
  • Assigned To No-one
  • Operating System All players
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 1
  • Private
Attached to Project: Rockbox
Opened by bookshare - 2007-08-21

FS#7637 - localise language names

I wish that some more language names could be localised. Some names include:
czech: ceski
chinese-simp: jeantsi
chinese-trad: jongtong
japanese: nihongo
finnish: suomi
korean: hangugoru
russian: paruski
hebrew: hevreete

Closed by  zagor

Reason for closing:  Fixed
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

Closing all feature requests.

nls commented on 2007-08-21 16:32

This should be as simple as a file-rename, any objections?

yes, it should.

Are users of all these languages more likely to know the romanized versions of their language names, rather than the English?

Ideally we’d have the filenames be something like “Ελληνικά (Greek).lng”, but that’s probably not feasible I suppose (not now, anyway).

I used manderin chinese (the 1 of 2 used in taiwan and the most common in china). For japanese I used the one universal dialect spoken everywhere in japan, and I used south korean.

rasher: why is unicode filenames not feasable? it would only annoy people who dont use a unicode font, which wouldnt matter seen as they wouldnt be using a unicode-requiring lang.

and hebrew should be Ivrit

jdgordon: I’m thinking mainly of the build system, SVN, people’s environment etc. In Rockbox itself, it could probably work, though putting the English name first would probably be better (to let everyone see *something*).

bookshare: If that was directed at me, I think you missed my point, which is that people might know the English name better than the romanized name (I don’t know if this is the case - this is why I asked it).

I don’t think so. And, by the way czech is actualy cesky. I typed wrong.

And russian correctly should be “Русский”

Мы написания названия с латинские символы.

Ох, и, кстати, русский нуждается в обновлении.

@harry tu: I don’t use russian, but you’re right: there are many things to be done in the translation. I don’t think, I could do it on my own, as I don’t know how to translate many technical terms. If you want to help me, I might try to update the language file.
And please, write your comments only in english!! Others might also want to read what you write.

I wrote onpurposefully in russian since you don’t seem to have understood the earlier comments. And no, I don’t use russian. I used google translate because I had the understanding that you didn’t understand what was happening in the previous comments which were written in English. And, I wish you would translate what you know. That is what I am doing (I am working on an update to the japanese file).

Obviosly I was distracted by some earlier comments, as some spoke of writing the localised language names with original signs in Unicode.
Imho, the only alternatives for lang names are english language names or the original names in unicode. Romanized language names would look very strange and would be more difficult to read for most users.
I’ll try and update russian, when I have time.

How about “Русский (Russian)”?

I personally think that would be the best solution, though I don’t know if the build system would be able to handle it (filenames with both unicode and spaces).

With a few small fixes to (using GNU extensions though - don’t know if that’s a no-no or not), it’s possible to build with filenames like I just mentioned.

The ‘release’ script will probably require tweaks as well.

How about fashioning latin chars so they look like the lang name in its original language?

As a follow-up to my latest comment, it won’t work as long as we rely on using zip as the archive format since it doesn’t have any notion of filename encodings. Using 7zip would solve this problem as it stores filenames as unicode - I suspect a modern tar does this as well, but haven’t tested it - does anyone know?

Does linux do 7zip though?

Certainly. It’s an open file format, and a Free extractor exists for Linux. Going 7-zip has downsides as well, of course. Primarily in not being as ubiquitous as pkzip.

But why don’t we simply make roman chars look like the original languages’ writing?

And we can rename japanese.lang to nihongo.lang. I know that japanese people will be able to understand it.

I think the consensus is that renaming languages is not worth the trouble of changing distribution format to 7zip. If we happen to change for other reasons, this is an obvious thing to do.

Romanising languages is at best a half solution, and at worst it breaks things for people not used to the romanisation of their language name - not to mention that it’ll break upgrades.

Finnish should be renamed though.

I suggest closing this task.


Available keyboard shortcuts


Task Details

Task Editing