The above video goes away if you are a member and logged in, so log in now!
LANG_BR.TXT - Portuguese BRAZIL
Last edited by apc16; 07-02-2011 at 05:57 PM.
thanks for this feature. Can you the same be done for the pop-up bottom right of the menu or expand pop-up window, because the word is not fit in space ? Instead english "Group ROMs by Emulator" russian "Группировать ROMы по эмуляторам" or shortly "Группировать по эмуляторам" cut off the last letters.
Originally Posted by deank
Translation has been completed 100%
pvc1 the same here with greek.....
I see the problem and agree that it can sometimes be difficult to keep a translation short enough, without serious violations of grammar or normal phrase structures. I've had the same problem with some of my Swedish translation. But at the same time we don't want to force all text to use microscopic characters, just so that those critical phrases can be displayed in full.
Originally Posted by pvc1
Perhaps it is possible for Dean to use adaptible font width scaling for some cases, so that extra horizontal 'compression' is only used where and when it is needed...
This way the readability would not be worsened for any sentences kept short enough to fit within the intended spacing at original size, while still allowing those troublesome phrases that require too many characters to still be displayed in full with a reduced character width.
Best regards: dlanor
Originally Posted by SK47
You seem to have missed the fact that Dean released another version of the LANG_DEFAULT.TXT file earlier today, containing several new strings to be translated.
You can download that file, together with the new multiMAN version update that uses it, from post #2 in this thread.
And you should also be aware that even this new version is not the final one, as there are lots more strings that need to be added in order to cover all the commands of the XMMB menu. So we are still probably several days from any final translation versions, and the time to start submitting our translations here (except for things Dean may want to test, of course). We should all hold back on doing so until Dean specifically asks for it.
Best regards: dlanor
Yeah, but the newest version doesn't contain any new labels. It was "only" an update for multiMAN itself.
Originally Posted by dlanor
Just checked his (SK47) file. You're right..it's missing several labels. The latest two updates both contain 295.
i translate language to polish, i check three times, and consult with other polish scene member, this is perfect translation, please add me to credit or something, i wand to be proud from add something to your extraordinary application
Last edited by djtom; 07-03-2011 at 04:40 PM.
Deank do have an estimate how many strings there will be when your finished? BTW finnish translation has now been updated to 295 strings.
I've installed the new multiMAN update you released earlier today, for using 295 translation string entries.
The first time I started multiMAN after that update I still had (intentionally) my older LANG_SE.TXT installed, containing only 239 string entries.
This obviously resulted in an error message in using the new version, just as should happen, but the odd thing is that the program claimed that the faulty language file was for the Finnish language (Suomi) rather than the Swedish language (Svenska). I suspect that this is simply an indexing offset error, as these languages are next to each other in the list used for selection.
However, when I later used the XMMB menu to again try enabling that old language file, the error message I then got from that attempt (as expected) correctly claimed that the faulty language file was for the Swedish language, so that instance of the validity testing was not affected by the same indexing error as did affect the initial test.
That initial test malfunction is not a very serious bug, as it will be invisible when language files are complete.
But I thought you might still want to fix it.
Another oddity worth mentioning is that in the language selection list there seemed to be a blank entry between Polish and Ukrainian, though I guess that might be a placeholder for something you've not yet finished or decided on.
Edit: Apparently that 'blank' entry should have been Greek language, so this must be related to the font problem for Greek letters...
I also have a question to make about one translation entry that I did not quite understand the meaning of. I do understand all the words and phrases of course, but I still don't understand the context in which they fit together, so I need to ask you about this. The entry in question was this one in line #260:
It seems to me that this refers to a different payload usage than I am aware of, as the payload should not normally be involved in the creation of a 'default backup folder'. That should be done through perfectly normal filesystem calls, without using any payload functions, as I see it.
Originally Posted by LANG_DEFAULT.TXT
Obviously I am missing something of basic importance here, which is why I need to ask you about it.
So exactly when and how is a payload used to create a backup folder ?
I have made a translation of that entry anyway, just so as to complete the work (as far as current LANG_DEFAULT.TXT goes anyway), but I won't feel confident in my translation until I understand the full context of it.
Best regards: dlanor