I18N progress

[Update: This ticket is closed, any further discussion goes to its successor ticket:2018]

This ticket is intended for two purposes:

Submit new translation source files by attaching them to this ticket.

Report about performing synchronization of existing translation source files in the SVN repository.

Step 1 is done by contributors willing to add support for a new language to the VirtualBox product. An accepted translation file appears in the SVN repository and becomes available in the binary builds. Even after that, contributors remain responsible for updating translation files to keep them in sync with updates to the VirtualBox UI.

Step 2 is performed by the GUI maintainer at innotek before a new release (or after a major UI change) to inform contributors that translation files need to be updated.

bluebat, VirtualBox_zh_TW.ts should appear in SVN shortly. Please zip it next time (there is no UI to download an attachment in raw format here yet; making it binary will force raw format automatically).

What about uploading the partially translated files to the wiki?
So in that way it would be easier to coordinate translations.
Furthermore, the partially made translations wouldn't be lost. (supposing the translator abandon for some reason)

Just submit your translation files on a regular base to this record. We will add them to the source tree, even when they're not done yet.

There it goes!

It should be good to give some guidelines about the acceleration keys on the wiki article.
Is there a way to check acceleration keys overlapping on qt3-linguist?
How does the translator know the limits of the acceleration keys context?
I mean there are same accel keys between same <context></context>.

Just submit your translation files on a regular base to this record. We will add them to the source tree, even when they're not done yet.

There it goes!

It should be good to give some guidelines about the acceleration keys on the wiki article.
Is there a way to check acceleration keys overlapping on qt3-linguist?
How does the translator know the limits of the acceleration keys context?
I mean there are same accel keys between same <context></context>.

Hi I'd like to help at the translation in Spanish. This is my native language and I start to translate.

Hi, I know that this isn't the right place to ask that, but I cannot test my translation. I'm using VirtualBox 1.3.8, Qtlinguist3, I've got the .qm, placed into <path_VB..>/nls/ folder, changed locale to ro_RO (on ubuntu 6.10), but still got nothing. The only language I see is English.
Any help would be appreciated.

Hi, I know that this isn't the right place to ask that, but I cannot test my translation. I'm using VirtualBox 1.3.8, Qtlinguist3, I've got the .qm, placed into <path_VB..>/nls/ folder, changed locale to ro_RO (on ubuntu 6.10), but still got nothing. The only language I see is English.
Any help would be appreciated.

The translation is for the upcoming version of vbox. You should test it from svn (dont know its state)

Thanks to everyone for his/her contribution! I want to clarify the requirements you must meet in order to let us legally include your translation to the VirtualBox product.

Each of you must explicitly state here that you allow InnoTek to use your translation under the terms of the MIT license. Alternatively, you can fill, sign and send us a copy of the InnoTek Contributor's Agreement (ICA).

Those who haven't already done so, must send an e-mail to info {at} innotek.de that contains the name of the language you are translating to.

NOTE. These steps are a must for ALL translators, even for those whose translation files are already in SVN! If we don't get your explicit permission as described above, we will have to remove your translations from the product. And please don't forget that you must specify your full name in your licensing statement (as well as in the Authors section of the translation file), not a nick name.

I've added all new languages and synchronized them with the current code base. They will soon appear in the SVN so please be patient and don't send updates until then.

General note to everybody
Please look through the table of current translators. Languages that contain columns with the bold text are not legally clean and WILL BE REMOVED from the product before the next release if we don't get the required information from the authors. Bold text in the Authors column means that we don't have the full name of the author and don't have his/her e-mail address. Bold in License status means we don't have a legal permission from the author.

jean-jacques,
I've renamed VirtualBox_fr_FR.ts to VirtualBox_fr.ts to have French French for all territories if there is no territory-specific translation (like fr_BE for example). And please don't forget about

lestat,
I've done the same to VirtualBox_it_IT for the same reason (there is unlikely to be a separate translation to it_CH).

jean-jacques, you are not listening to me for some reason. I asked to not update the translation before the one you have attached here earlier appears in SVN... I will try to merge the latest one from you once more but I cannot guarantee it will be clean (so you will have to carefully check it). And, once again, please zip the .ts file next time before attaching.

All, just in case. Please no translation updates until the current ones are in SVN so that you can download them and use to continue your work.

The wizard dialog are not OK concerning the internationalization. I have foubd the following which is not included within the ts files:
Next, Back, Finish, Cancel, Other/Unknown (OS type combo box), E&xisting (new image file)

I've found a problem with whatsthis balloons in settings dialogs (shown from the context menu or after clicking on the ? button on the window title bar on Win32). Qt couldn't always properly recognize rich text used for some items and therefore would display HTML tags and would break lines instead of formatting them as desired. I had to resynchronize all language files again so that some items became outdated. You will have to download the files again from SVN, merge with what you've already done and re-translate those unlucky items. Sorry for inconvenienve.

Also, I've decided that VirtualBox will ship translation files for built-in Qt dialogs and other resources (see comment:37) instead of relying that they are installed on the user machine together with the Qt library. There are lots of reasons to do so, the most important are 1) we ship our own Qt build on Win32 and 2) not all languages are present in the set of Qt translation files supplied by Trolltech.

Therefore, you can now find qt_xx_YY.ts files in the nls in this directory. Part of them are already fully translated, the other part are totally untranslated. Here are the untranslated ones:

qt_es.ts

qt_it.ts

qt_ro.ts

qt_zh_CN.ts

qt_zh_TW.ts

People maintaining the corresponding VirtualBox_*.ts files should translate these qt_*.ts files as well, in order to get their language in built-in Qt dialogs.

What's the best practices for several independent developers working together ?
Say, one can start from the beginning and the other from the end, and we combine results somehow (maybe SVN) ?

Documentation translation proposal:

To make the product really translated, the documentation must be translated as well. However now, it's too professional, very-long & complex to be translatable.

One idea to make documentation more translatable, is to devide current Innotek's documentation "User Manual" into 2 parts: "Start-up guide" (for newbies) and "Reference guide" (for advanced users).

This will allow translators to translate just the first guide.

So small team/1-man can translate the start-up guide, so it will be available in 40+ languages shortly (weeks, and cover basic user needs), while the "Reference guide" can only be translated by large teams - which will result in, say, 5-8 languages after a long period of time (many months/1 year).

Updates to Russian, Romanian and French translations are merged to SVN.

igorbounov, there is no need to create multiple attachments of the same language -- you can overwrite the existing one. Also, I couldn't send a reply to your last e-mail, because <mailer daemon e-mail address> told that your work e-mail (igorbounov...) is Unrouteable address.

Therefore, you can now find qt_xx_YY.ts files in the nls in this directory. Part of them are already fully translated, the other part are totally untranslated. Here are the untranslated ones:

qt_es.ts

I dont get it :)
I downloaded the qt_es.ts (qt 3.3.8) from trolltech and it is translated.
Which is the difference between this two versions?

The difference is that I took these .ts files from Qt 3.3.3, because this is the version we are currently bound to on Win32. So, you can just compare the one from 3.3.8 and the untranslated one from SVN and send me the first one if there are no incompatible changes (you will have to fix them first if there are).

All language files have been synchronized with the current sources and merged to SVN. There was one important change: "Global Settings" is renamed to "Preferences" everywhere. Your old translations will still work but are marked as untranslated, because the translation will be different for many languages. Please review.

<source>Failed to discard the snapshot <b>%1</b>of the virtual machine <b>%1</b>.</source>

There are two "%1".

Is this correct?

No, it was not correct. Thank you for noticing! The source and all language files have been corrected and merged to SVN. All translations are kept, so no re-translation is necessary unless your language is Chinese (where I simply don't know what means "snapshot" and what means "machine" -- so please check; items are marked as "unfinished").

Also, I've made one more harmless correction to all translation files because of this (recorded as a Translation hint #4 here):

Don't translate items starting with the # (hash) sign in contexts VBoxGlobalSettingsDlg and VBoxVMSettingsDlg, such as #general, #input and so on. They are responsible for the settings category hyper-link feature on the VM Details page and translating them will break this feature.

toshi3_tanaka, thank you a lot for these corrections! You have a hawk eye, please keep going :)

medber and adrian5632, thank you for providing translations! Now please license them properly to let us include your translations to the prodict (details are here. Medber, this also relates to you because in your previous license statement you didn't mention your full name (it must match the translator name in the .ts file!) and we don't have your e-mail (either put it here in the encrypted form or send to info{at}innotek.de if you want to keep privacy).

All language files have been transparently updated to correct English typos found by toshi3_tanaka, a couple of phrases with corrected English spelling have been marked "untranslated" (to make sure you check them). Arabic and Polish languages have been added to SVN.

The Japanese language (VirtualBox_ja_JP.ts) translation attached here by Toshimitsu Tanaka is published under the terms of the MIT license.

I have a small question: should the language code be ja_JP but not just ja? The difference is simple: the latter (generic) form will be used as a fall-back for ja_XX locales in case if there is no exact ja_XX translation; the former (specific) will only be used for the ja_JP locale. So the actual question is: can your translation be used as a fall-back for Japanese speaking territories other than Japan?

"If you want your translation to be included with VirtualBox, then you have to license it under the MIT license or alternatively sign the innotek Contributor Agreement."
OK, as U wish :P Now the translation is MIT licensed :P

All latest updates have been incorporated and resynchronized with sources. A few new translatable items has added due to slight UI changes. You can update them now or wait for some more upcoming UI updates.

I've noticed that some recently attached translations were outdated (did not include the latest changes from SVN). PLEASE remember to take a latest SVN copy and merge it with your recent translation before attaching the latter here. Solving conflicts in all translations on my side is a) unsafe because I can read only two languages and b) very time consuming. So, please review the current translations for mistakes (again, by comparing your local copies with current SVN versions).

adrian5632, please remove the _PL suffix from file names you attach here, since we decided not to use the country code for Polish (as you may have noticed, files in SVN already end with _pl, not with pl_PL). Not a big problem of course, but will save me a bit of time I spend renaming your files :)

lestat, yes, as long as you don't want to keep the old phrasing for further reference, you can remove "obsolete" items while translating. Keep in mind that there is no UI for doing that in Qt Designer -- you can manually edit the .ts file and delete all <message> elements that contain <translation type="obsolete"> elements. No need to do it right now because I will remove obsolete translations from all files before the 1.4.0 release.

Xeph, you are welcome! http://virtualbox.org/wiki/Translating should describe everything you need to know . If you have questions, feel free to ask here. Please pay special attention to this section to not forget about licensing your translation when it is done.

Sorry about this mistake I've made, my latest upload was VirtualBox_ro.zip (35.4 kB) - added by alexef on 05/03/07 17:36:09. 100% Up to date, with wrong file name (missing .ts[.zip])) and it seems like it wasn't commited to SVN.

VirtualBox_ro.zip must be removed from this page, I shall update the current translation from SVN and upload it right here.

After downloading the last sources, I have seen that some textes are no more translated. This concern mainly the main menu of the VM.

What texts exactly do you mean?

on the rigth side of the main menue the short cute are english (eg. Host+F).

You must have forgotten. It has always been like that -- Host+<Letter> shortcuts in the VM menu are not translatable in the current version (for technical reasons).

Within the status bar, the "host key" is printed out as "Rigth Ctrl", for previous version this was correct.

I think "Right Ctrl" is more correct than the previous "Control_R" (this is our attempt to workaround broken keysym names in Xlib). Anyway, you will be able to translate these key names now according to typical keyboard caps in your country (for X11 only; in Win32 key names are properly translated by the system).

Please hold on with any translations, language updates are being gathered to.

Some textes are not present into the language files:
After creating a VM and while starting it for the first time, a wizard is launched. All textes for the first and following windows are not contained within the *.ts files

For the upcoming 1.4.0 release, a couple of new UIs have been added and a couple of UIs have been updated. You are welcome to update your translations. All the translation files have been resynchronized with the sources and merged to SVN.

If you want to have your translation updated in 1.4.0, please keep in mind that the release of 1.4.0 is scheduled for the beginning of the next week.

Congrats for the 1.4.0 release!
I just have uploaded my latest update to the Romanian translation and I'm wondering if it would get into the downloadable 1.4 packages or any update from now on applies only to the next (1.4.2?) version.
Thanks

Xeph, you are welcome! http://virtualbox.org/wiki/Translating should describe everything you need to know . If you have questions, feel free to ask here. Please pay special attention to this section to not forget about licensing your translation when it is done.

The Swedish translation is progressing fast and is ready to be committed.
It is not 100% complete but I hope to get some time soon to finish it.

Yeager, thank you very much for your contribution! The .zip file you attached here looks OK but you haven't licensed your work for us so I cannot include it into the code base. Please do it as described here. Don't forget that we need your full name and a valid e-mail (you can send it privately if you don't want to publish it).

kangmin, peremen and Xeph,
Thank you a lot for your efforts, but could you please coordinate your work? For now, I only have .qm files from kangmin, which is not acceptable because we need the .ts sources. I also know that Xeph started working on the translation several weeks ago and probably made some progress. There is no need to do the same work twice, so please contact each other (you can do it right here) to join your efforts and give us a single translation in the .ts format.

kangmin, peremen and Xeph,
Thank you a lot for your efforts, but could you please coordinate your work? For now, I only have .qm files from kangmin, which is not acceptable because we need the .ts sources. I also know that Xeph started working on the translation several weeks ago and probably made some progress. There is no need to do the same work twice, so please contact each other (you can do it right here) to join your efforts and give us a single translation in the .ts format.

I met Xeph on IRC a week ago, and he said that he lost all his works by accident, and he wants me to maintain the translation.(I have a log for that time) I made ts file and it is undergoing tests for several Korean users. It will go soon. Btw, is there any method to contact with kangmin except this space?

but I did not konw all about this!!
there is is only reason, when i visit first time this place
there is any tranclated korean souces
and I start translate this work and complet. that's it!!

Well, I reviewed through your translation, but I think your translation is immature. Although you claimed that you completed the translation, lots of part of .ts file is remaining as '?', which means untranslated. I will post my .ts file, please compare it with yours.

oh, I know that! when it open wiht Qt Linguist have a lots of ? marks.
but it translated complet. right
beacuse I translate with Qt Linguist and text editor[editplus] to easy translate!
I don't konw why it remain ? mark.
if you see all of contats my .ts file wiht Qt Linguist or editplus,
you can see it tranlated complet.
It is impotant only to use Qt Linguist? or my .ts file is correct.
thanks...

as you can see there is no erro When it apply to Virtualbox.
any other place thanks for your attention

Well, I mentioned not only error, but also quality. I reviewed your translation, but quality wasn't so good :( By the way, can you talk me with email? Your English is hard to read, so I want to talk with you in Korean. Mine is <removed>.

oh, I know that! when it open wiht Qt Linguist have a lots of ? marks.
but it translated complet. right
beacuse I translate with Qt Linguist and text editor[editplus] to easy translate!
I don't konw why it remain ? mark.
<snip>

Just a tip: you need to press CTRL+ENTER on each translated string to mark it as translated, or else it will remain with a question mark. Also, try to use Qt Linguist's features to check the assigned key accelerators and punctuation marks. These features help maintain the consistency of your translation quite a bit.

Dear kangmin and peremen. Great, now I have two different Korean translations :) To be serious, I don't have any knowledge of Korean at all in order to choose a better one. So, please give me a single version. I suggest you that peremen will take the kangmin's .ts files, check and make necessary corrections when it is essential. And yes, you can now contact each other directly by e-mail, so please continue the Korean translation related discussion in private. Thank you.

Dear kangmin and peremen. Great, now I have two different Korean translations :) To be serious, I don't have any knowledge of Korean at all in order to choose a better one. So, please give me a single version. I suggest you that peremen will take the kangmin's .ts files, check and make necessary corrections when it is essential. And yes, you can now contact each other directly by e-mail, so please continue the Korean translation related discussion in private. Thank you.

Finally, kangmin said that he will give up and let me to maintain translation. Also I finished Korean translation file, which is my own work. File will go soon.

hron84 and JJK, thank you very much for your work. However, I have a few remarks on your translations.

To both hron84 and JJK: you took too old translation templates, so your translations are slightly outdated -- you will have to download your .ts files directly from SVN once they appear there and re-translate outdated translation items.

To horn84: please use Qt Linguist 3.x if possible -- I'm not completely sure that Qt Linguist 4 generates 100% backward compatible .ts files, so something may theoretically not work. Also, I stripped off the _HU suffix from file names and removed the country name because it seemed to me that Hungarian language is the same everywhere and doesn't vary depending on the country of usage. If you disagree, please object here. Also, the translation file you've attached contains "Garami Gábor" as the author which doesn't match George Hron. I cannot accept your translation until I've got some reasonable explanation.

To JJK: It looks like you used some text editor to translate the .ts file directly instead of Qt Linguist -- that is possible but makes your life harder. And as a result, there are some errors in your translation like incorrect escaping of special HTML characters (e.g. line #116 in VirtualBox_fi.ts) that results into English text being used instead of the tranlsated one for those items. My suggestion is that you start from the beginning: take a fresh copy of VirtualBox_xx_YY.ts, open it in the Qt Designer and copy-paste there all translations you've already made from the old VirtualBox_fi.ts. Taking into account that you've just started your translation this should be the easiest way to fix all those incorrect escaping errors. Agree?

hron84 and JJK, thank you very much for your work. However, I have a few remarks on your translations.

To both hron84 and JJK: you took too old translation templates, so your translations are slightly outdated -- you will have to download your .ts files directly from SVN once they appear there and re-translate outdated translation items.

Also, I stripped off the _HU suffix from file names and removed the country name because it seemed to me that Hungarian language is the same everywhere and doesn't vary depending on the country of usage. If you disagree, please object here.

It's true. But i choose to use the hu_HU form in two cause:

In the world, everybody uses the hu_HU form to describe a hungarian language, such as locales.

In the wiki, you wrote the my_MY form, and i followed the description.

Also, I stripped off the _HU suffix from file names and removed the country name because it seemed to me that Hungarian language is the same everywhere and doesn't vary depending on the country of usage. If you disagree, please object here.

It's true. But i choose to use the hu_HU form in two cause:

In the world, everybody uses the hu_HU form to describe a hungarian language, such as locales.

In the wiki, you wrote the my_MY form, and i followed the description.

Yes, but it's just a general template. Anyway what stands behind using "hu" instead of "hu_HU": VirtualBox_hu.ts is more generic, it will be chosen for (possibly custom) locales like hu_EN, hu_WHATEVER etc. while !Virtualhu_hu_HU will be used only when the locale is hu_HU exactly.

OK, we are working together, and i forgotten update the header. I'm really sorry, it's my mistake.

Then, specify both names there (comma separated). And I will also need a license statement from Garami Gábor here as well (in the same way you did it here).

So, I'm waiting for an updated translation in Qt 3.x format from you. Please merge the current SVN version of VirtualBox_xx_YY.ts with your translation after you convert it to Qt 3.x (using some standalone file merge tool) -- it will show you all places you need to correct.

To JJK: It looks like you used some text editor to translate the .ts file directly instead of Qt Linguist -- that is possible but makes your life harder. And as a result, there are some errors in your translation like incorrect escaping of special HTML characters (e.g. line #116 in VirtualBox_fi.ts) that results into English text being used instead of the tranlsated one for those items. My suggestion is that you start from the beginning: take a fresh copy of VirtualBox_xx_YY.ts, open it in the Qt Designer and copy-paste there all translations you've already made from the old VirtualBox_fi.ts. Taking into account that you've just started your translation this should be the easiest way to fix all those incorrect escaping errors. Agree?

Also, I stripped off the _HU suffix from file names and removed the country name because it seemed to me that Hungarian language is the same everywhere and doesn't vary depending on the country of usage. If you disagree, please object here.

It's true. But i choose to use the hu_HU form in two cause:

In the world, everybody uses the hu_HU form to describe a hungarian language, such as locales.

In the wiki, you wrote the my_MY form, and i followed the description.

Yes, but it's just a general template. Anyway what stands behind using "hu" instead of "hu_HU": VirtualBox_hu.ts is more generic, it will be chosen for (possibly custom) locales like hu_EN, hu_WHATEVER etc. while !Virtualhu_hu_HU will be used only when the locale is hu_HU exactly.

OK, we are working together, and i forgotten update the header. I'm really sorry, it's my mistake.

Then, specify both names there (comma separated). And I will also need a license statement from Garami Gábor here as well (in the same way you did it here).

He hasn't a internet connection now, but i think he accept the license, because we are in a group. We read the how-to.

So, I'm waiting for an updated translation in Qt 3.x format from you. Please merge the current SVN version of VirtualBox_xx_YY.ts with your translation after you convert it to Qt 3.x (using some standalone file merge tool) -- it will show you all places you need to correct.

dmik, i have a one question:
can you tell me any good merge tool? I don't know which merge tool is a best. And i worry about a version-copatibility too.
Thankss

hron84, I also see a message from qzy dated 06/10/07 18:19:37 here where he/she states he/she has already started to translate. Are you aware of that?

I saw it, but i'mn't sure, he/she is working on this really. I sent it, but if he/she send a translation sometime, i cancel my translation, and I accept his/her precedence.

Well, asking me first at least would have made it possible to avoid working line-by-line. Anyway, yes, I've done a part of it and was willing to finish it this weekend. However the only thing that counts is to get a good translation. I'll look at yours and if there's anything I can add, I will.

The Hungarian and Finnish translations are added to SVN. Updates to the Swedish translation are merged to SVN.

Well done, JJK and hron84! Please keep in mind that in order to continue/update your translations, you need to download the SVN copies of your translation files from this site and continue on them, not on your local copies you attached here!

hron84, I resynchronized your translation with the current sources before adding it, so you don't have to merge manually which added some new translation items and rendered some old ones 'obsolete' (you will see it in the Qt Linguist). From now on you can use any subversion GUI client as a merge tool (to merge your local changes with the current SVN version of the .ts file before attaching a new version here), but just in case here is a good standalone merge tool: http://www.guiffy.com.

yeager, I've found that your translation is also not made in the Qt Linguist 3. Accidentally I've run it through the Qt Linguist myself (so it's now correct) but please use only the Qt Linguist 3 application to update the .ts file in the future to make sure it conforms to the format expected by Qt 3.

In general, it's not recommended to translate Ctrl+<latin_letter> shortcuts (for example, Ctrl+S used to open the VM Settings Dialog) because they are intended to be language neutral and should have the same action regardless of the selected UI language. Translate them only if there is a very special reason to do so in your language; otherwise simply leave the original. Note that the action name starting with a different letter or having a different underscored (Alt+<any_letter>) accelerator in your language is not a valid reason to translate the corresponding Ctrl+<latin_letter> shortcut.

So, it is recommended to revert Ctrl+<latin_letter> shortcuts to original values (from VirtualBox_xx_YY.ts) for those who have translated them.

hron84, I also see a message from qzy dated 06/10/07 18:19:37 here where he/she states he/she has already started to translate. Are you aware of that?

I saw it, but i'mn't sure, he/she is working on this really. I sent it, but if he/she send a translation sometime, i cancel my translation, and I accept his/her precedence.

Well, asking me first at least would have made it possible to avoid working line-by-line. Anyway, yes, I've done a part of it and was willing to finish it this weekend. However the only thing that counts is to get a good translation. I'll look at yours and if there's anything I can add, I will.

lxndr, thank you for joining the translation team! Please note that your file should have a _nl suffix, not nl_NL -- unless there are various flavors of Dutch that may not be used one in place of another.

cromo, thanks for your report, but I don't see the problem: "Show Log" and "Release" actions are placed in different top-level windows so their shortcuts cannot interfere with each other. About Ctrl+S vs Ctrl-P: the latter is commonly used for the Print action I'd say (and I prefer to have it reserved for that purpose). I also don't see a big need to assign Ctrl+S to the "Start VM" action because when you want to start a VM, the VM list is normally in focus, where the Enter key will act as a "shortcut".

lxndr, thank you for joining the translation team! Please note that your file should have a _nl suffix, not nl_NL -- unless there are various flavors of Dutch that may not be used one in place of another.

cromo, thanks for your report, but I don't see the problem: "Show Log" and "Release" actions are placed in different top-level windows so their shortcuts cannot interfere with each other. About Ctrl+S vs Ctrl-P: the latter is commonly used for the Print action I'd say (and I prefer to have it reserved for that purpose). I also don't see a big need to assign Ctrl+S to the "Start VM" action because when you want to start a VM, the VM list is normally in focus, where the Enter key will act as a "shortcut".

Hi dmik my e-mail address you can publish, I used nl_NL since ispell and the like use it like that as well, I can change to _nl if that would better correspond to your needs. A sort of dutch is also spoken in Belgium in which case nl_BE is used but most of the time this division is ommitted. Your call!

dmik, I noticed the Enter way of lunching VMs after posting. Anyway it would be nice to put 'Enter' string next to the 'Start' entry in Machine menu, so the user can see which key is used to start the machine.
Also, there is no translation string available for "Other/Unknown" Guest OS type.

The last paragraph at the last page of the New VM wizzard gets cut here. My translation of this paragraph is a bit longer than the original string but is cut quite a bit more, so I guess that english translation is cut, too.

cromo, the last paragraph thing is a known issue (will be fixed soon). The Ctrl-Alt-D shortcut has been already replaced in the SVN tree. Putting Enter to the Start action title is not actually correct, because it's not a true shortcut (and cannot be such) -- it acts only when the VM list is in focus.

cromo, thank you very much! However, I cannot use your translation right now because I need a confirmation from Adrian Łubik (adrian5632) that he agrees and your translation is a real improvement over his one. Also, I need your full name mentioned in the licensing statement you made above and your e-mail (privately to info/innotek.de if you don't want to publish it here).

I already tried to contact Adrian before, but he's probably out for his holidays or sth as he didn't reply yet. I'll ask him to comment it here whenever he's back.
Regarding the licensing statement: I, Dawid Wrobel (<e-mail removed>) hereby agree for this translation to be used by Innotek GmbH under the terms of MIT license.

Ok, we've been waiting for quite some time now; moreover your translation looks more like a serious update than a complete rewrite to me (changeset:4139), so Adrian should have no reason to complain. I've merged your version to SVN.

P.S. You may want to use pure Latin spelling for your names in the .ts file since there still can be systems that only have ASCII + the national character set (which will make your names hardly readable there).

Yeah, a serious update is a better description indeed.
Regarding the names, the 'ó' sign should be present in any charset regardless its coding, but 'Ł' will only be readable in UTF or ISO8859-2, so I'll change that into 'L' in next update of the translation, which is actually on its way.

Also, I was wondering about if the debug strings should be translated at all. These are only useful for either advanced users or developers, and while the former will understand the 'callee', 'return code' etc. strings, the latter owill struggle with understanding what do these localized strings mean if they were posted to a mailing list or something. Some of such users would probably want to translate them back into english and it would confuse the devs even more. So what I'd do is to use only english for these rarely shown debug strings.

There is no 'ó' in the ASCII character set (characters 32-127) and I may assure you that there are 8-bit code pages that don't contain it in the upper part (128-255) -- for example, all Russian code pages. Anyway, I don't insist of course, it's just a suggestion.

About the "debug" strings: it's up to you to decide. Your logic makes sense (posting to mailing lists), however it will not be difficult to guess because the format of the error message is always the same. Most translators translate these strings as well.

I want to ask a question: What is a state of hungarian translation? qzy has sent a final translation? Because he told him, he can be done in a week, when i mailing with him. If not, i will continue translation and i send a finally, but i want a response. What do you want, what i do?

hron84, the state of the translation corresponds to what you see at the top -- i.e. the SVN repo contains the last version you attached here. You are free to finish your translation, I got nothing from qzy so far.

hron84, the state of the translation corresponds to what you see at the top -- i.e. the SVN repo contains the last version you attached here. You are free to finish your translation, I got nothing from qzy so far.

dmik, thanks a reply. OK, then I start finish the translation (i'm in 759/851 state). I merged it with the SVN VirtualBox_xx_YY.ts file. I need circa a week to complete the translation and view over it.

Expecting the new release of VirtualBox, all language files have been resynchronized with the current sources and merged to SVN. This gives quite a bit of new strings to translate. The new release is planned next week, so please try to update your translations ASAP. Thank you very much.

P.S. Note that you must download (checkout) a .ts file for your language from SVN and continue your work on it, not on your local copy!

"<p>You didn't attach a hard disk to the new virtual machine. The machine will not be able to boot unless you attach a hard disk with a guest operating system or some other bootable media to it later using the machine settings dialog or the First Run Wizard.</p><p>Do you want to continue?</p>"
This is a new string and I don't think it's correct to say that the machine will not boot without the hard disk attached, as you can also boot from network, cd and floppy. Or am I wrong?

Also, the "Please note that debugging requires special knowledge and tools, so it is recommended to press <b>OK</b> now." sentence sounds kinda... insulting. Wouldn't it be better if the message said: "However, if you are not going to debug the machine it is recommended to press <b>OK</b> now."?

cromo, Dmitry (our GUI expert) is currently in vacation. He will answer your comments when he is back. My two cents:

You are right that the user can boot from other medium even if no harddisk is attachaed, most notably from network. Perhaps the string could be refined but the string also mentions that the user should attach some other bootable medium using the settings dialog or the first run wizard. Setting up a server for network requires some more effort and is therefore not used by beginners.

I fully agree to your remark about the debugging message.

The values for ports are indeed integer values. The input field will accept decimal values as well. But yes, hexadecimal values are normally used for port numbers and this could be stated in the string.

The New VM Wizard always sets the primary master hard disk as a boot device, therefore if you don't attach a hard disk in this wizard then the machine won't boot unless you go to the settings and manually select a different boot device.

95% of users a) use the release version of the product (where the built-in debugging tool is not available) and b) really don't know how to debug a VM. I don't think that not knowing something (especially if you don't need/want it to know, as many users do) may be called "insulting".

Frank already answered: both decimal and hexadecimal integers are accepted, and even octal AFAIR. However, there is not much space in the instant help box so we cannot put every single detail in there.

About shortcuts: good idea but you can already do it: press Host-Home to activate the menu, then press the underscored letter (M or D in this case). Probably the information about Host-Home should appear in the message box at first run to let users know about this feature.

I was actually thinking that the message is wrong because it is possibile to choose the boot device by pressing the F11 key after booting up the machine no matter how the boot order is set up in VM's settings. But in general you're right, if we don't tell the average user that he didn't attach any drive, most of the time he will only get confused about hte the machine not booting.

I still think it's rather unpolite and not assertive to say that "Hey, I am pretty sure you don't know how to do it because you'd need a lot of knowledge which most likely you don't have, so you better press that OK button and don't even try to mess around with the machine anymore'. It's up to you, I just have a feeling that majority of the users reading such message will feel a bit awkward. But it could be just me ;-)

I asked because for the other similar help box message regarding USB vendor ID filter that only accepts hexadecimal values. However I had no idea that the serial port address field can also accept decimals and even octals. But why would one need to use theses for the serial port address which is always represented with hexadecimal value? Or did I forget about something? Anyway, it doesn't really matter.

Regarding the shortcuts - indeed, I for one had no idea about that Host-Home key combination.

chromo, the F11 key is for advanced users who will normally ignore/suppress warning messages like that (targeted at new users in the first place). Again: when the Guru Meditation condition happens, there is nothing a regular user can do if he selects Ignore instead of OK -- this is what this message is about. USB fields are different: you can only use hex there and w/o the 0x prefix, which needs to be mentioned.

Updates to the Korean, Czech, Italian, Polish, Brazilian Portuguese and Swedish translations are merged to SVN (will appear within half an hour or so). Thank you guys! We're still waiting for other translators to update their languages.

Updates to the Romanian and Korean translations are merged to SVN (will appear within some time). Thank you guys!

cromo -- thanks, you are right, but since accelerators will be removed from Cancel keys in all dialogs (since Esc is always a hard-coded shortcut for them), it's no more an issue.

khiav, thank you very much for your help. However, we cannot accept your translation right now because
a) there is already a translation by OSS Integral Institute Co, Ltd. in the repository, and your translation doesn't look like an update of this translation. Please contact OSSII and collaborate with them. I can give you their e-mail if you give me yours or contact me at dmik/innotek.de.
b) you didn't license your work properly (see below).

helix84, piarres, Pau, thank you for joining the team of translators, but bear in mind that we cannot use your translations (in particular, include them in the release builds) until they are properly licensed. See http://www.virtualbox.org/wiki/Translating for details.

Piarres, your translation is temporarily added to SVN (for your convenience), but once again, it's illegal to use it w/o your public permission. I also ask you to use the Qt Linguist tool for translating instead of a third-party XML editor (I've already explained why somewhere above or on the Translating page). I've corrected some issues manually this time, so please use the version from our SVN (http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/nls/VirtualBox_eu.ts) for further translation.

The Slovak transkation is added to SVN. helix84, thank you. However, please relicense by mentioning your full name since it's the one shown in the Author field of the translation file. Otherwise it's hard to associate the person who makes the license statement with the one who is the author of the translation. Also, please use Qt Linguist version 3 instead of version 4, since the latter generates excessive content that the former may not understand.

piarres and Pau, same to both of you. Please relicense by mentioning your full name. And also give use your e-mail address (here or privately to dmik/innotek.de).

I've corrected *all* language files so that the Cancel push button doesn't have an associated accelerator any more -- pressing ESC will act like a Cancel action in any dialog anyway. You should pick a fresh version of the .ts file for your language from SVN. Note that you don't need to retranslate the text for the Cancel button (but you are advised to check this button to make sure I didn't break anything).

Updates to the Korean translation are merged to SVN. peremen, please note that I removed the Alt+C shortcut from all Cancel buttons since ESC always acts like a shortcut for the Cancel action. If you disagree, please argument here.

victor, thank you for the update, but could you please attach a source .ts file instead of the compiled .qm file? We can't accept binary files -- there is data loss when they are compressed (by default).

Updates to the Chinese translation are merged to SVN. victor, thank you for finally providing a 100% translation and please note too that I removed the Alt+C shortcut from all Cancel buttons since ESC always acts like a shortcut for the Cancel action.

victor, thank you very much for this "last minute" observation! I have updated all translation files in the SVN so that they include this change now.

All who already attached here the newest 1.5.2 translations. I didn't process and merge your files to the SVN yet! You need to perform a simple patch to your existing translation files (see below) and reattach them again. Sorry for inconvenience, but it will be the fastest route.

The below also applies to those who already checked out .ts files earlier, before changeset:5243, and already started to translate them. In order to add the missing item to your existing .ts file, please do the following:

Open the .ts file in a simple text editor.

Search for "<name>VBoxAddSFDialog</name>" to find the proper <context> element.

Add the following to the end of this context (insert the given text just before the closing </context> tag of the VBoxAddSFDialog context):

Open the .ts file in Qt Designer and translate the newly inserted item.

(Re-)attach the .ts file here.

That's all.

peremen, you are right about killing the attachment description, but please repeat your licensing statement in the ticket comment once more -- and this time mention your full name please, in the same form it is specified in the .ts file. It's a formality, but we need it. Thank you!

Updates to the Czech, French, Japanese, Korean, Portuguese (Brazil), Romanian and Swedish translation are merged to SVN. Thank you guys, that was fast! :)

victor, what you mention in comment:227 is correct, however it's not GUI, it's the VirtualBox core for which the translation framework isn't fully functioning yet. Once it's done, we will inform all translators.

The new Serbian translation has been added to SVN (no qt_sr.ts yet). Updates to the Korean translation are merged to SVN.

ozzii, thank you very much! Though you didn't provide the translation file for built-in Qt strings (qt_sr.ts). Please do it, otherwise we won't be able to include your translation into the release. Also, I assume that "ozzi" is your full name. If it's not, you will have to change it both in the .ts file and in your licensing statement you posted in comment:234.

Anybody can share me the QT Linguist 3? Cos I cant access the download page.
All i can download is the qt-win-opensource-4.3.2-mingw.

I believe I saw a separate free distribution of Qt Linguist for Win32. Let me check. Alternatively, you can install one of the popular Linux distributions (inside a VirtualBox VM for example) where you will find an installable package of Qt Linguist.

Cant I just translate the QT files directly by changing the unfinished text?

It's not recommended because you may accidentally break the syntax and your translation won't work properly.

Updates to the French, Spanish and Serbian translations are merged to SVN. The Serbian translation is now approved.

jean-jacques, when you want to separate ! and ? from the preceding word, please use the &amp;nbsp; seqennce instead of the raw space char when it takes place in RichText items (i.e. items that are enclosed with <p>, <qt> and so on). This is necessary to make sure the ! or ? char doesn't get moved alone to the next line when the text is rewrapped after changing the container size. Note that in simple items (like Dialog and UI element titles) you must use the raw space char because HTML markup isn't understood there.

ozzii, please consider to write your name in Latin in the Comma-separated list of translators field because some systems may not have fonts with Cyrillic and your name will be completely unreadable in this case.

jd, please note that your translation had some syntax errors which I corrected (one translatable item was missing, a few others contained garbage in the <translation> field). Please compare your last attached .ts file with the current SVN version to see what has changed.

Almost finish the translation for Indonesian but want to test them first...
Want to ask, how to convert the *.ts into *.qm?

Are you sure you have read http://www.virtualbox.org/wiki/Translating? Anyway, you need the QLinguist tool to do this. If you are not on Linux (where this tool is usually available in your distribution's package pool) then you will have to create a Linux VM and install the QLinguist package there.

jd, please note that your translation had some syntax errors which I corrected (one translatable item was missing, a few others contained garbage in the <translation> field). Please compare your last attached .ts file with the current SVN version to see what has changed.

Sorry I have missed this message. I will check it. I think the last file i sent has this error

The Catalan translation is addwd to SVN and approved. Updates to French and Spanish translations are merged to SVN.

Pau, thank you very much for the translation! Everything seems to be OK except that I noticed that you didn't translate the main text of the registration dialog. Please feel free to update your work with this translation once you've got time. But if you want to have it appear in 1.5.4, then please hurry up.

The Dutch translation is added to SVN, but not yet approved (must reach the 50% barrier). lxndr, thank you very much for your initial contribution! Please note that I've changed the language code from nl_NL to just nl (and thus removed the country name from the .ts file) because we came to a conclusion that the differences between nl_NL and e.g. nl_BE would be minimal or no at all in the context of VirtualBox and it's quite acceptable to use the same translation for all nl_* locales.

cartman, thanks for your interest. However, you didn't provide a translated version of built-in Qt library strings (qt_tr.ts) so we cannot accept your VirtualBox_tr.ts so far. Please prepare qt_tr.ts and please attach them as normal files zipped into VirtualBox_tr.zip next time.

david_yacobus, the same requirement (qt_id.ts) is applied to you too. When I get this file, I will put both to the SVN. Also, you still have not licensed your translation. Please do it as described in http://www.virtualbox.org/wiki/Translating.

I attached a patch to the current Finnish translations, making the language more proper Finnish etc. Earlier sent to vbox-dev mailing list, from where I got pointed to here. The translation patch is against the current SVN version and I license my changes for it under the MIT license (http://www.virtualbox.org/wiki/MIT%20license). Also the previous Finnish translation so far licensed under MIT license (comment:137).

I suggest to create page for translators instead of keep using this ticket. It is hard to track the comment, I could miss some important notices. Also, all the messages, like new translation, translation update, notices are mixed, so it is too hard to separate them. Because this ticket will grow bigger and bigger, I think this is the time to create several pages for translators.

Replying to peremen:
It's hard to track because e-mail notifications are still broken, not because of the number of comments. But yes, the latter will eventually make loading of this page really slow :) Trac sometimes is just a disaster (doesn't support e-mail management, doesn't support paging for ticket comments). Maybe I will create a dedicated thread on http://forums.virtualbox.org.

You might have noted that we released VirtualBox 1.5.6 yesterday. Unfortunately, this release does not contain any i18n updates posted here. We apologize for that. The reason is that not all GUI changes were backported from the trunk to the 1.5 branch resulting in different i18n strings. We will notify you when we are about to release the next major version, VirtualBox 1.6, so you will have time to complete the translations. Thank you for your understanding.

As we had to update all our packages due to a last-minute regression we backported some of the i18n strings from SVN trunk to 1.5. You might want to update your package from our website if you already downloaded a package during the first hours after the release of 1.5.6.

I'm not sure if you read the last comments of this report. As I already stated we did not update all of the i18n strings as there was just not enough time for this. Keep in mind that 1.5.6 is part of a branch while the i18n files posted here are usually define i18n strings for the trunk version. The next release will be 1.6 and we will give the translators time to update their respective i18n files.

I'm a little bit confused, for the next release of VBox, is there going to be a major changes on the UI?
How to update the language?
Should we start from scratch or is there any files to download so that we can "continue" previous translation?

BTW, to everyone who doesn't get automatic notifications about new comments to this ticket. Please log in to www.virtualbox.org using your name, then go to http://www.virtualbox.org/settings and set a preferred e-mail address there and you will start getting them.

I have resynchronized the .ts files once again before 1.6 because we had to add one more message box (appears when the new hard disk attachment is added but there is no unused hard disks for it) and one more error message. Please feel free to update the translation files but please remember that the 1.6 deadline is tomorrow morning, 30.04, 10:00 CET.

Please note that if you are unable to update these few new items by that time, they will not go to the 1.6 release, but they will for sure appear in the next 1.6.x update.

Pau, I noticed that your translation is seriously broken because you don't use Qt Linguist 3 for translation. Look at #1840 for example -- you attempted to translate the <comment> text there (and in other places around) which is wrong. Your translation will look ugly if you don't fix it. The deadline is the same.

Pau, I noticed that your translation is seriously broken because you don't use Qt Linguist 3 for translation. Look at #1840 for example -- you attempted to translate the <comment> text there (and in other places around) which is wrong. Your translation will look ugly if you don't fix it. The deadline is the same.

Ok, thanks... I didn't realize when I turned to Gentoo. Well, I think Catalan traslation has to wait for the next release to be published (today I don't think it could be possible to fix it, I don't have a lot of time). Ups...

Updates to the Polish, Swedish, Chinese and Spanish translations are merged to SVN.

wwl81er, sorry but we cannot accept your translation:

You based your work on the existing work of OSSII (OSS Integral Institute Co. Ltd. cotributed by bluebat and simply overwritten the Autors: field there w/o any explanation.

You took the too old version of the VirtualBox_zh_TW.ts file and your translation doesn't merge cleanly.

In order to fix 1 please contact OSSII, discuss the matter with them and provide the feedback of this discussion here. To fix 2, simply take the current version of the file from the public SVN and use it for translating.

Note to all translators. The GUI is currently in the unstable state of transitioning from Qt3 to Qt4. No NLS updates are accepted at the present time. Please be patient and wait until a further notice. Thank you for your continued interest to our product!

mmodem, please note that VirtualBox_pt.ts from your last Portuguese.tar.bz2 attachment was not updated in the SVN because it differs too much (you've picked up a too old version). Please take the fresh one from the current SVN, re-translate/merge it and then attach back.

Keep in mind that all these updates are for the Qt3 frontend; the Qt4 frontend currently used on the trunk is not yet ready, so please don't translate the .ts files from src/VBox/Frontends/VirtualBox4/nls yet.

The Slovak (sk_SK) translation attached here by Jozef Riha is published under the terms of the MIT license.

Thank you very much, Jozef! However, the .ts file you attached is outdated and doesn't merge cleanly. Please take a new copy of VirtualBox_sk.ts from the SVN and merge your changes yourself, and then re-attach the file.

The Slovak (sk_SK) translation attached here by Jozef Riha is published under the terms of the MIT license.

Thank you very much, Jozef! However, the .ts file you attached is outdated and doesn't merge cleanly. Please take a new copy of VirtualBox_sk.ts from the SVN and merge your changes yourself, and then re-attach the file.

please, what is the best way to do it? is it ok just to pull sources from svn, rewrite ts file with the one i modified (and attached here), run lupdate ../vbox/src/VBox/Frontends/ -ts VirtualBox_sk.ts and review/edit the ts file? i haven't found any merging tool for linguist files.

please, what is the best way to do it? is it ok just to pull sources from svn, rewrite ts file with the one i modified (and attached here), run lupdate ../vbox/src/VBox/Frontends/ -ts VirtualBox_sk.ts and review/edit the ts file? i haven't found any merging tool for linguist files.

No, you must not run lupdate. A possible solution is to compare your attached .ts file with the fresh one from SVN side by side and transfer the translated strings from the former to the latter w/o breaking its structure.

In the future, the easiest way to keep it in sync is to go to some directory and type (this implies subversion is installed):

This will download the nls/ subdirectory from our public SVN to the ./VirtualBox_nls/ directory on your local drive where you will find your .ts file. You may translate it there "in place". Whenever you want to attach an updated version of your .ts file, you simply go to ./VirtualBox_nls/ and do:

svn update

This will pull out recent changes from our public SVN (if any) and merge them with your last version (which as I said above you keep right there). In some rare cases there may be conflicts between the latest SVN version and your local version which you will have to resolve manually (see the subversion documentation on the official project site).

This will pull out recent changes from our public SVN (if any) and merge them with your last version (which as I said above you keep right there). In some rare cases there may be conflicts between the latest SVN version and your local version which you will have to resolve manually (see the subversion documentation on the official project site).

The new 2.0 release is expected next week. Please note that VirtualBox 2.0 and following versions will ship the VirtualBox GUI that uses Qt version 4 and therefore you need to update the Qt4 NLS files, not the Qt4 ones. See comment:1 and also make sure you have read the Translating document once more since there are some important updates.

To make it clear and avoid any possible confusion, a new ticket:2018 has been created. Please read the first three comments carefully and direct all further translation activity to that defect.

This defect is closed from now on. Please don't comment on it and don't attach any new files here.

I would appreciate a comment from Mr Victor Wang on ticket #2018 to say whether he is still interested in maintaining the Chinese translation or whether someone new can take over. If you don't answer I will assume you are happy with that.