Translating a software program with only the original language strings available will result in crappy translations.
When you translate software the most important factor is the context, and you can't know the context if you don't have the working program at your disposal.
eg: string 26 "times"... what 'times', is that plural for 'time'? do you mean "multiply by"? Is it the name of a Magazine? etc...
You can't translate stuff in that way. People need the program to know what the strings are used for (not to mention to know how long they can be).
blahblahblah... I didn't realize you posted a link to the program... I'm very slow today
I'll update this post with Dutch translation to make it up
---------------------------------------------------------------
UPDATE (Dutch):
langSettings[0] = "_Live Mediageschiedenis";
langSettings[1] = "Over...";
langSettings[2] = "Opslaan als HTML";
langSettings[3] = "OK";
langSettings[4] = " speelde: ";
langSettings[5] = " door: ";
langSettings[6] = "Aantal";
langSettings[7] = "Titel";
langSettings[8] = "Artiest";
langSettings[9] = "Voorkeuren:";
langSettings[10] = "Taal veranderen >>";
langSettings[11] = "Mediageschiedenis >>";
langSettings[12] = "Wissen";
langSettings[13] = "Gemaakt door:";
langSettings[14] = "Meer informatie:" ;
langSettings[15] = "Website";
langSettings[16] = "Speciale dank aan:";
langSettings[17] = "Mediageschiedenis: ";
langSettings[18] = "door ";
langSettings[19] = "Pagina automatisch gegenereerd door ";
langSettings[20] = "Je favorieten ";
langSettings[21] = " meest gespeelde liedjes zijn: ";
langSettings[22] = "Opgeslagen door ";
langSettings[23] = "Er is een nieuwe versie beschikbaar van "
langSettings[24] = "Er is momenteel geen mediageschiedenis voor deze contactpersoon!";
langSettings[25] = " - ";
langSettings[26] = " keren afgespeeld";
langSettings[27] = "Opgeslagen als: ";
langSettings[28] = "<geen data>";
langSettings[29] = "Klik hier om je mediageschiedenis te wissen."
but, all the stuff said below makes it that it is impossible to make a proper Dutch translation for this script...
--------------------------------------------------------------------------
EDIT 1:
- Your script is very buggy. Things don't work like they are supposed to concearning the interface (the logging itself is fine).
- There are things which aren't translatable (eg: "version:")
- There are things which are translatable but not updated when the language changes (eg: "thanks to")
- There are things which revert back to English (eg: /xsonghist)
- Extremely many translated lines will not fit in your interface.
- Your script detects media changes, these can be things other than songs. Thus don't use 'songs' in your texts. Or: make a clear destinction between media and songs (also in the translation).
- Many code in your script can be optimized or be done with a plus function (eg: instead of grabbing the registry key for the script path, why not use
MsgPlus.ScriptFilesPath)
EDIT 2:
This goes in general, thus for everybody who wants to translate their scripts:- Make sure you have enough space for the translations! English is a very very very short language and most other languages need far more space.
- Take in account different syntaxis in other languages. Not all languages have the same grammar syntax as English.
eg: not in all languages the syntax is:
"played x times"
in some languages the verb must come after the count number (eg: in dutch: "x keren afgespeeld")
In other words, try to keep to be translated words/sentences as a whole, do not split them up in seperate things to translate. Use tags if you need to. eg:
instead of:
langSettings[25] = " - played";
langSettings[26] = " times";
do:
langSettings[25] = " - played %s times";
In dutch this could be solved by using:
langSettings[25] = " - ";
langSettings[26] = " keren afgespeeld";
but this wont be possible in every language
Making a script (or any program for that matter) translatable is far from strait forward and is actually not that easy to do properly...