multiMAN - multiLINGUAL - Translated in 31 Languages

[deank]

Confirmed. I finished translating 209 lines and tested on the update for translators. Letters ı, ş, ğ, İ, Ş, Ğ are not shown with the current fonts.

Ok, I checked and it works with User font #0 (and some other fonts). I added an additional parameter in multiMAN to use different fonts for different localizations if required.

Seems that all looks okay now:



***

This is the current language list:

	{ 0,	2,	 "EN",	"English",		"English"		},
	{ 1,	2,	 "BG",	"Bulgarian",		"Български"		},
	{ 2,	2,	 "RU",	"Russian",		"Русский"		},
	{ 3,	2,	 "RO",	"Romanian",		"Română"		},
	{ 4,	5,	 "TR",	"Turkish",		"Türkçe"		},
	{ 5,	2,	 "ES",	"Spanish",		"Español"		},
	{ 6,	2,	 "DE",	"German",		"Deutsch"		},
	{ 7,	2,	 "FR",	"French",		"Français"		},
	{ 8,	2,	 "IT",	"Italian",		"Italiano"		},
	{ 9,	2,	 "BR",	"Brazilian",		"Português BR"		},
	{ 10,	2,	 "PR",	"Portuguese",		"Português"		},
	{ 11,	2,	 "NL",	"Dutch",		"Nederlands"		},
	{ 12,	2,	 "PL",	"Polish",		"Polski"		},
	{ 13,	2,	 "UA",	"Ukrainian",		"Українська"		},
	{ 14,	2,	 "HU",	"Hungarian",		"Magyar"		},
	{ 15,	2,	 "DK",	"Danish",		"Dansk"			},
	{ 16,	2,	 "FI",	"Finnish",		"Suomi"			},
	{ 17,	2,	 "SE",	"Swedish",		"Svenska"		},
	{ 18,	2,	 "MY",	"Malaysian",		"Melayu"		},
	{ 19,	2,	 "XX",	"Other",		"Other"			}

[NuclearAqua]

So, I finished my Portuguese translation and updated multiMAN with the previous page's update and added LANG_PR.TXT (European Portuguese) to USRDIR/lang, but when I change the language in XMMB nothing happens. What am I doing wrong here?

I figured it out. I renamed it to LANG_XX and selected "Other" in the language menu. Now most options already appear in Portuguese, but in game selecting menus Load, Exit, Game Settings, etc. still appear in English. I translated everything in the .txt, but those options still appear in English. Is this meant to happen?

Also, I noticed that some of the words in Portuguese are longer than in English, which causes wording to override the space meant for the next button and the text appears on top of the other text. Can you change your code so that buttons will be automatically spaced to prevent this?

[deank]

In game display modes what you see is LEGEND2.PNG, which is not a part of the translation, sorry. It is up to theme makers.

Also, I noticed that some of the words in Portuguese are longer than in English, which causes wording to override the space meant for the next button and the text appears on top of the other text. Can you change your code so that buttons will be automatically spaced to prevent this?

No. If you did translations before you would know that it is not that easy to fit everything. When I'm ready with all texts/labels I'll see if I can rearange some of them to make more space.

[NuclearAqua]

In game display modes what you see is LEGEND2.PNG, which is not a part of the translation, sorry. It is up to theme makers.



No. If you did translations before you would know that it is not that easy to fit everything.

Who makes the default theme for multiMAN? If that's it, I'm afraid some translations will be broken because of this. It's a shame if theme makers don't add support for other languages.

[dlanor]

In game display modes what you see is LEGEND2.PNG, which is not a part of the translation, sorry. It is up to theme makers.

True, since that is a picture rather than text, and it needs to fit in graphically with the rest of the theme graphics.

But in XMMB mode there is lots of normal text that doesn't seem to be covered by any current translation strings (as yet).
I'm here referring to the XMMB column headers as well as all commands and command clarification texts in the XMMB columns.

So at present it is only alternate/popup menus (including File Manager) and other popup texts (like command button hints) that are translated.
All text of the XMMB menu remains in the original English.

For some things the reason is obvious (the word 'Retro' does not exist in the LANG_DEFAULT.TXT, for example), but for other things it is not so clear.
I assume that it is only due to lack of time that you have not yet added the XMMB texts into the translation string collection.

----- re: text space restrictions in button 'hints' and submenus

No. If you did translations before you would know that it is not that easy to fit everything.

I agree, and it is very much the responsibility of the translator to try to find sufficiently brief ways to translate the original texts.

But even so, we also have to face the fact that English is a fairly terse language compared to many others, so in many cases the length of strings and phrases will tend to grow in the translation into more verbose languages.

Best regards: dlanor

[dlanor]

Who makes the default theme for multiMAN? If that's it, I'm afraid some translations will be broken because of this. It's a shame if theme makers don't add support for other languages.

Are you assuming that all theme makers are fluent in all existing languages ?

That will of course not be the case, and a theme maker can't very well add support for all the languages he doesn't even understand.

Best regards: dlanor

[deank]

Modifying multiMAN to support external translation files is not a speedy and easy task. I'm working on it when I can (I have a lot of night shifts this week until July 4th so time is scarce).

I committed a new version to googlecode, which includes the genres, retro groups and xmmb column names. There are still some dialogs from the main interface to be added and then I'll get to XMMB columns.

Currently there are about 240 labels (lines in the lang files) and I expect this to grow up to probably 400 by the time I finish with XMMB columns (multiMAN/Home column, Settings column with all these Yes/No/Auto/Enabled/Disabled/Never/Always/etc/etc/etc. It is A LOT OF WORK and I test it each time when I get back home in the morning for the last 20-30 labels I add each night.

D

[kgb]

Dude, im portuguese and my translation works flawlessly, you cant make literal translations check my examples below:

http://i70.photobucket.com/albums/i118/manl/mossad/multiMAN_3.png
http://i70.photobucket.com/albums/i118/manl/mossad/multiMAN_2-1.png

examples: instead of making a literal translation of "Group Titles by Genre" - "Agrupar Títulos por Género" or "Back" (in Game Settings) that would be "Voltar Atrás" you must addapt, the litteral translation would be too long but you can still choose other words and retain the original meaning - "Agrupar por Género" and "Anterior"

Another thing, i guess you must be doing something wrong, i simply chose Portugues from the language list and it worked, no need to choose "Other"


@ Dean, one suggestion, you could change the language code of Portugal from 'PR' to 'PT' - thats the correct language code for portuguese language and also the country code (ISO Country Code, 2 Digit: PT; ISO Country Code, 3 Digit: PRT)

Also, with this test version we already have more than one version of language translations made by various persons for the same language, maybe you could set up some kind of team or group for each language or something like that, not just because of these various versions but i think it would also be easier to translators - it would take less time finding bugs in the translations and due to the staggering amount of updates you so kindly offer us it would speed up the official releases, just a thought

regards

regards

[NuclearAqua]

Are you assuming that all theme makers are fluent in all existing languages ?

Of course not. All I'm saying is that theme makers should also accept translations to the text that is currently in image format and work in conjuction with dean to change its text when the user selects a different language.

And please realise that I'm not pressuring anyone to doing this. It will be done at it's own pace, and then it's done it's done.

I find it exciting to be part of such a big community project as this

@ Dean, one suggestion, you could change the language code of Portugal from 'PR' to 'PT' - thats the correct language code for portuguese language and also the country code (ISO Country Code, 2 Digit: PT; ISO Country Code, 3 Digit: PRT)

Yeah, I was also going to suggest this.

Also, with this test version we already have more than one version of language translations made by various persons for the same language, maybe you could set up some kind of team or group for each language or something like that, not just because of these various versions but i think it would also be easier to translators - it would take less time finding bugs in the translations and due to the staggering amount of updates you so kindly offer us it would speed up the official releases, just a thought

That's quite a good idea. Looking forward to working with you. /Fico feliz por trabalhar contigo

[deank]

@ Dean, with this test version we already have more than one version of language translations made by various persons for the same language, maybe you could set up some kind of team or group for each language or something like that, not just because of these various versions but i think it would also be easier to translators - it would take less time finding bugs in the translations and due to the staggering amount of updates you so kindly offer us it would speed up the official releases, just a thought

I'm sorry but I don't have time to organize you in groups, check the quality of your translations (not that I can) and all that stuff. I have no idea who-is-who (except 3-4 people here) so it is up to the translators to communicate with each other somehow and decide what will be the official translation for certain language.

Either communicate via PM, or Skype or IRC and get back to me.