good evening,
I would like to ask you how to proceed if I would like to translate Ultimaker Cura into Czech.
I never translated programs, translated movies and dramas, documentaries, I would like to try. I have already found some information on the Internet, and I would therefore like to make sure that this is the right procedure. I found in the c: \ Program Files \ Ultimaker Cura \ resources \ i18n template folder to accurately translate 4 templates that can be opened and translated in poedit. I don't know how to proceed please
adekarem
All 6 comments
It would be good if we were to provide a proper guide for it... But here you go.
We have 4 files. You seem to already have found them: cura.pot (texts from the Cura interface), uranium.pot (texts from the Uranium GUI framework), fdmprinter.def.json.pot (setting names and descriptions) and fdmextruder.def.json.pot (more setting names and descriptions). These files contain the English texts and empty fields that can be filled in. The files can be opened with PoEdit and translated with that application.
Do not underestimate the work for translating Cura. It's quite a lot of work! I also write subtitles as a hobby, and I'd say that translating Cura is probably about as much work as ~6 hours of film (more and more difficult text in total but you don't need to timestamp or line break it so it'll go faster).
Specifics for translating applications
When translating an application, you'll sometimes encounter texts that have words that need to be filled in, like "Successfully loaded %1!" or "Could not connect to {printer_ip}. Please check your connection." This is not something you'll have seen when you only did movies/series/documentaries. In place of the cryptic text, there will be something filled in by the application. You should not translate or change the cryptic parts, but you can move them around as they fit in your phrasing! Luckily, PoEdit will warn you if you do it wrong. They come in 3 different flavours in Cura:
%1or%2or%sor something, a%with one symbol after it.{something_in_brackets}.<xml_tags>, sometimes with an extra</slash>.
To know what the cryptic part means, refer to the entry's context. Don't translate text in brackets or in angle brackets.
You will also encounter plural forms now. Some texts are describing something with a dynamic count. For instance: "Copied 2 models." where the "2" could be any number. For those forms, PoEdit will allow you to fill in multiple plural forms. For English, this would be two forms: "Copied {count} model." for 1, and "Copied {count} models." for 0 or more than 1. However different languages have all sorts of plural forms. According to this page, Czech has a singular form for N=1, a plural form for 2<=N<=4, and another plural form for N>=5. So for the couple of plural phrases that Cura has you'll probably need to fill in 3 translations.
Sometimes you'll see a text with an ampersand in a word, usually towards the beginning, like &Open File or P&references. This ampersand marks the underlined letter that signifies which Alt-key is the hotkey for that menu entry. We don't put a lot of effort in making these completely unique for every language, but if you see a couple of those entries close together, you could optionally take care to make the letters unique keys on the keyboard.
Guide lines specific to Cura
- Almost all entries have a context, but it doesn't usually tell much other than that the text is used on a button or something. However for some texts the context will explain what to pay attention to, what names/things are filled in for the
%1, etc. We normally fill those in if previous translators made a mistake there. - We don't translate industry terms (to a degree) unless you're adamant that no Czech person would ever use the English version. For instance some terms that should not be translated: FDM, slicing, nozzle, extruder, priming. Some terms that should probably be translated: infill pattern, build plate, walls, ooze shield. If the language allows, you can inflect the English industry terms according to your grammar. For instance in Dutch we could use "primen" as a verb with our
-ensuffix. If you have been using Cura for a while, these industry terms should not be a problem for you. - Usually you won't really need to pay attention to text length. It's best to keep it within reason though. Especially with the settings list it's quite annoying to see everything abbreviated.
- When the English text is missing punctuation or capital letters, try to copy that into your translated text. It's probably on purpose, and something follows after it or it's done to be consistent with some neighbouring interface element. If you think it's really wrong though you can always let us know and we may correct the English text in the next version. There can be exceptions though if your language has specific grammar rules different from English. For instance, German writes all nouns with a capital letter so the German phrase may still start with a capital letter even if the English phrase didn't, if the phrase starts with a noun.
- Our .po(t) files contain translations for old texts. You probably won't see them in PoEdit, but they are there if you use a text editor, starting with a pound sign and tilde
#~. You don't need to translate those. You can, but it's 95% sure those phrases will never get used any more.
Our workflow
When you're done, it's nice for your attribution if you'd submit a pull request here on Github. If that is too technical, you can also e-mail the .po files to me. My e-mail address is in the header of the .pot files as the maintainer.
For the initial translation, I'd think you need a couple of weeks to translate everything if you're doing this in your spare time. Right now we've just started our translation round for Cura 4.3, but I don't think you can make it before its release. So by the time you finish, we'll have continued to add new things for the 4.4 release. But once the 4.4 beta is out, we can ask you to translate the new texts as well.
We release every 2 months with like ~100-150 new phrases every release. This should be doable in an hour or two to update. We can e-mail you every release as a reminder, provided you committed with your e-mail address in to make the pull request or if you e-mailed us the .po files. Translating every time is completely voluntary of course. If you're ever late or otherwise obstructed, we'll typically remove the language option from the drop-down in the preferences, but existing users won't switch away from the language. This is because we don't like new users to get the feeling of a broken program when they see incomplete translations. We will leave the (incompletely) translated files in our source code though, so that someone (or yourself) could later pick up where you left off.
After submitting your translations, we will check them manually for common mistakes. We don't speak Czech though so we won't be able to make any real corrections to your language. But we have some tools to automatically check translations for broken %1s and such. If there is a serious error that we can't correct, we may contact you again for a clarification.
Ghostkeeper
on 12 Sep 2019
good evening,
I would like to ask you how to proceed if I would like to translate Ultimaker Cura into Czech.
I never translated programs, translated movies and dramas, documentaries, I would like to try. I have already found some information on the Internet, and I would therefore like to make sure that this is the right procedure. I found in the c: \ Program Files \ Ultimaker Cura \ resources \ i18n template folder to accurately translate 4 templates that can be opened and translated in poedit. I don't know how to proceed please
Postoupila si nejak? Pripadne nabizim pomocnou ruku s prekladem!
S474N
on 23 Dec 2019
Omlouv谩m se za pozdn铆 odpov臎膹 n臎co p艡elo啪en茅ho m谩m, ale moment谩ln臎 z d暖vodu
nemoc铆 jsem p艡eklad pozastavila, mohu se zeptat zda v铆te jak to d谩t do kupy
poslala bych v谩m co m谩m a pop艡铆pad臎 bych n臎co i p艡elo啪ila nav铆c d臎kuji za
odpov臎膹
adekarem
on 28 Dec 2019
Sorry for the late reply I have something translated, but for the moment
of diseases I have paused the translation, I can ask if you know how to put it into a cluster
I would send you what I have and possibly I translated something extra thank you for
answer
The most common way to share translation files is via .po files, if that's what you're asking. Google Translate is borking on your sentence a bit.
Ghostkeeper
on 31 Dec 2019
Someone else has recently translated the Cura repository to Czech. It just needs to also translate Uranium now before we can add it.
Ghostkeeper
on 28 Feb 2020
This is merged for Cura 4.6.
Ghostkeeper
on 7 May 2020
Related issues
rudowinger
路
3Comments
StanislavJochman
路
3Comments
wi1k1n
路
3Comments
jornada812
路
3Comments
tomoinn
路
3Comments
Most helpful comment
It would be good if we were to provide a proper guide for it... But here you go.
We have 4 files. You seem to already have found them: cura.pot (texts from the Cura interface), uranium.pot (texts from the Uranium GUI framework), fdmprinter.def.json.pot (setting names and descriptions) and fdmextruder.def.json.pot (more setting names and descriptions). These files contain the English texts and empty fields that can be filled in. The files can be opened with PoEdit and translated with that application.
Do not underestimate the work for translating Cura. It's quite a lot of work! I also write subtitles as a hobby, and I'd say that translating Cura is probably about as much work as ~6 hours of film (more and more difficult text in total but you don't need to timestamp or line break it so it'll go faster).
Specifics for translating applications
When translating an application, you'll sometimes encounter texts that have words that need to be filled in, like "Successfully loaded %1!" or "Could not connect to {printer_ip}. Please check your connection." This is not something you'll have seen when you only did movies/series/documentaries. In place of the cryptic text, there will be something filled in by the application. You should not translate or change the cryptic parts, but you can move them around as they fit in your phrasing! Luckily, PoEdit will warn you if you do it wrong. They come in 3 different flavours in Cura:
%1or%2or%sor something, a%with one symbol after it.{something_in_brackets}.<xml_tags>, sometimes with an extra</slash>.To know what the cryptic part means, refer to the entry's context. Don't translate text in brackets or in angle brackets.
You will also encounter plural forms now. Some texts are describing something with a dynamic count. For instance: "Copied 2 models." where the "2" could be any number. For those forms, PoEdit will allow you to fill in multiple plural forms. For English, this would be two forms: "Copied {count} model." for 1, and "Copied {count} models." for 0 or more than 1. However different languages have all sorts of plural forms. According to this page, Czech has a singular form for N=1, a plural form for 2<=N<=4, and another plural form for N>=5. So for the couple of plural phrases that Cura has you'll probably need to fill in 3 translations.
Sometimes you'll see a text with an ampersand in a word, usually towards the beginning, like
&Open FileorP&references. This ampersand marks the underlined letter that signifies which Alt-key is the hotkey for that menu entry. We don't put a lot of effort in making these completely unique for every language, but if you see a couple of those entries close together, you could optionally take care to make the letters unique keys on the keyboard.Guide lines specific to Cura
%1, etc. We normally fill those in if previous translators made a mistake there.-ensuffix. If you have been using Cura for a while, these industry terms should not be a problem for you.#~. You don't need to translate those. You can, but it's 95% sure those phrases will never get used any more.Our workflow
When you're done, it's nice for your attribution if you'd submit a pull request here on Github. If that is too technical, you can also e-mail the .po files to me. My e-mail address is in the header of the .pot files as the maintainer.
For the initial translation, I'd think you need a couple of weeks to translate everything if you're doing this in your spare time. Right now we've just started our translation round for Cura 4.3, but I don't think you can make it before its release. So by the time you finish, we'll have continued to add new things for the 4.4 release. But once the 4.4 beta is out, we can ask you to translate the new texts as well.
We release every 2 months with like ~100-150 new phrases every release. This should be doable in an hour or two to update. We can e-mail you every release as a reminder, provided you committed with your e-mail address in to make the pull request or if you e-mailed us the .po files. Translating every time is completely voluntary of course. If you're ever late or otherwise obstructed, we'll typically remove the language option from the drop-down in the preferences, but existing users won't switch away from the language. This is because we don't like new users to get the feeling of a broken program when they see incomplete translations. We will leave the (incompletely) translated files in our source code though, so that someone (or yourself) could later pick up where you left off.
After submitting your translations, we will check them manually for common mistakes. We don't speak Czech though so we won't be able to make any real corrections to your language. But we have some tools to automatically check translations for broken
%1s and such. If there is a serious error that we can't correct, we may contact you again for a clarification.