== Open Week -- Get started translating Ubuntu -- andrejz and TLE -- Tue, Oct 12 == {{{#!IRC [15:01] (... having some problems with a missing person stand by!) [15:01] Logs for this session will be available at http://irclogs.ubuntu.com/2010/10/12/%23ubuntu-classroom.html following the conclusion of the session. [15:04] hello! [15:05] Ok, andrejz is going to step in and help us out [15:05] my name is andrejz and i am a slovenain launchpad group translation coordinator [15:05] we kind of put him on the spot so he's volunteered to take over, thanks andrejz! [15:05] i have been just told dpm is not here so i haven't really prepared [15:05] so if things seem a bit strange, just ask me and i will try to answer them as best as i can [15:07] QUESTION: can you explain how a new contributor finds out what and how to translate Ubuntu? [15:08] Ubuntu (and many other projects) are being translated through a web interface found on www.launchpad.net [15:08] So the first thing you need to do is get an account there [15:08] Then it's good to get in contact with your translation team - a list can be found here [15:08] https://translations.launchpad.net/+groups/ubuntu-translators [15:09] Different groups have different workflows (do things in a different way) according to the number of active members and they find suits them best [15:10] So i guess it's best to ask the team leader where is the best area to contribute [15:10] QUESTION: Do different translation teams work in different ways? Are there different workflows and "rules"? [15:10] Yes they do [15:11] andrejz: just let me know when you are ready for new questions [15:11] ok [15:11] Maybe the people who asked them can say whether they were happy with the reply [15:11] So back to the question.. [15:12] for example some teams only translate the strings, while others thorouglhy review them to ensure better quality. Of course this depends on how strong the team is [15:12] Additionally a lot of translations get imported from upstream (for ubuntu two most important are gnome and debian) [15:13] in some languages translation groups in upstream exist, in others they don't [15:14] this can affect how the teams are going to cope with the workload. That's why it's best to get in contact with the team leader who is probably aware of what needs the most attention [15:14] next question please [15:14] bilalakhtar> QUESTION: Translation strings in Ubuntu keep changing very frequently early in the cycle. Hence, would you recommend new translators to work only after UI Freeze? [15:15] That's a double edged sword. My opinion it's good to translate even before UI freeze [15:15] the level of changes depends on the packages [15:16] You mind if I elaborate [15:16] for example if we take evolution - it's a really stable program, so one can translate it and be certain only a few strings will change on the other hand unity has been developed during this cycle, so strings changed a lot [15:17] so my advice is: do translate, but the projects for which the strings seem more "stable". Again translator coordinator should have a good grasp of which projects should be translated [15:17] TLE, please elaborate [15:17] It can also depend a lot on the resources of your team [15:17] To translate early you accept that some of your work may be lost because the strings change [15:18] but you also help with development by spotting errors in the strings, at least if you report them as bugs [15:18] this is very helpful for developers [15:19] but if you are a very small team you may not have reources to spend on that [15:19] Next question [15:19] dholbach> QUESTION: What is upstream? How can one work together with upstream? [15:19] Upstream are the projects from which ubuntu is built [15:20] There are a lot of them, but the most important are Gnome, KDE and Debian [15:20] Some of these projects (including the ones i mentioned below) also have their translation projects [15:21] so one can translate packages within Gnome, KDE, Debian, etc .. [15:21] Now again, it depends from team to team [15:21] For big languages (like spanish for example) there is a gnome translation team, debian translation team, etc.. [15:21] for some smaller there is no upstream translation team [15:22] you should visit sites of these projects to check whether they exist [15:22] translations are automatically imported into launchpad, after the release of upstream packages [15:23] so for example, translation will be imported in gnome the next time when gnome 2.32.1 is released [15:23] that's why there is usually some lag between the time when translations are translated in upstream and until they appear in launchpad [15:23] translations are currently not exported out of launchpad back to upstream [15:24] so by working together with upstream i am primarily referring to : making sure that you don't translated the same packages (duplication of work) [15:24] if you fix a bug in launchpad send notify the upstream, so they can fix it as well [15:25] it's also good if you maintain some vocabulary standards, etc.. [15:25] again it depends on the specific teams (whether they exist and how strong in manpower they are) [15:25] next question [15:26] Kottravai> QUESTION: Are there any specific rules to follow while translating? [15:26] You mean technical or grammar rules ? [15:27] andrejz: lets take the next one [15:27] Again it depends from team to team. For example in some teams it's required one enters the name of the package they intend to translate on a wiki [15:27] ok, sure TLE [15:27] while he elaborate [15:27] genupulas> QUESTION: what is meant by UI freeze [15:27] maybe expand to stings freeze as well [15:28] UI freeze means USer interface freeze. This means UI won't change anymore, so the translation strings are not going to change anymore. So UI freeze= string freeze [15:29] This in theory means that the strings, which you translate won't be changed (and hence lost) before release of next ubuntu version [15:29] usually this is about 1 month before the final release, actual date can be found in the release schedule [15:29] But there can always be some string freeze exceptions if there is a good reasons and translators agree with it [15:30] so it's good to be on ubuntu-translators mailing list in order to stay up to date with last minute strings changes [15:30] next question please [15:30] we'll go back to Kottravai question [15:30] Kottravai> I'm asking about any rules that are unique to ubuntu - terminology you should not use, etc. [15:31] No, there is no such thing. Of course different languages have different rules about foreign words, comas, voacabulary, etc. Some teams are more strict and others more loose. But there is nothing unique to ubuntu [15:32] next question [15:32] dholbach> QUESTION: Do you know of LoCo teams that come together locally to translate together? This way they could also show new contributors how to do it. [15:32] well, we do :) [15:33] we had this translations evenings this cycle, where people gathered (online) and translated /reviewed strings together. We really did a lot of work, and it's much easier to get motivated once you see others are motivated as well [15:34] I believe it's better if events for new contributors are seperate, because otherwise they suddenly appear in translation frenzy and they might not be able to get their questions answered as detailed as they would like [15:35] we also did that but earlier in this cycle (in august). In total we managed to get 3 regular new contributors, which is significant for a team of our size [15:35] I am sure some of the other teams do similar things as well [15:35] next question [15:35] QUESTION: How do I find a translating team for my language? [15:35] https://translations.launchpad.net/+groups/ubuntu-translators [15:36] next question [15:36] QUESTION: Are translations re-done every cycle? If not completely, how much % of it can be re-used? [15:36] If the strings remain the same, then no additional work needs to be done [15:37] But a number of strings changes during a release cycle, either to improve their clarity or strings get added, because the program gets more functions. [15:37] these need to be translated [15:38] with the new message translation sharing it is now possible to translate a string in 10.10 and the string is then automatically translated in all previous supported ubuntu versions (if the string exist there) [15:38] so even if you are translating 10.10 you are still helping out with 10.04 [15:39] next and final question please, because i need to go (i jumped in at the last moment, so i couldn't allocate the time, sorry) [15:39] I can share a few approximate numbers [15:39] before the next question [15:39] ok [15:39] The Gnome desktop which is a group of modules that are quite central to Ubuntu [15:40] it consist of roughly 40000-45000 string [15:40] and of those ~10 - 15% have to be translated or updated in each 6 month cycle [15:40] very roughly [15:40] ;) [15:40] dholbach> QUESTION: What is the most difficult thing for a new translator? What should new translators be particular careful about? [15:41] In my experience it's the language. because we usually talk differently than we translate, so one needs to get accustomed to that. [15:42] also most translators are "power users" so they are quite familiar with english vocabulary and hence they tend to use englishisms a lot [15:43] but if you are active and have a good mentor (someone who reviews your strings and gives you advice) you can improve to a quality translator in a month or so it's not that hard. one just needs to be persistent [15:44] i need to leave, hope i answered your questions ok [15:44] thank you very much andrejz [15:44] I will answer the last question on my list [15:44] if you have any additional questions you can always post on ubuntu-translators mailing list or on IRC [15:44] regards [15:44] and then talk a little but quality [15:45] andrejz: have fun [15:45] Kottravai> QUESTION:What exactly are "Big" languages? === Rodemires is now known as Rodemire [15:45] Big languages are the ones spoken by lots of people [15:46] or rather langueges used to a large extend by computer userss [15:46] so something like spanish, english, chinese and so on [15:46] dholbach> QUESTION: Are there strings that are harder to translate than others? What about things like plurals or strings that include some kind of "code"? How can I test that I didn't break stuff when I translated? [15:47] Yes there are definitely strings that are harder than others [15:47] the first class of hard strings are single word ones e.g. "Load" [15:48] because english is quite ambigous, there is no way to know whether it refers to the noun or the verb [15:48] here you have to hope that the developers though of it and included a string that explains it [15:48] and if not you need to make a bugreport, because if you have that problem, then most likely other translators will to [15:49] you languaes team can help you determine the meaning or report a bug [15:49] second is something like strings with markup [15:49] "Hallo world" [15:50] we are seing fewer and fewer if such string, but for these it is important to not change the markup, i.e. the stuff between < .. > [15:50] lastly there is something like plural strings [15:51] There are 10 minutes remaining in the current session. [15:51] e.g. if you want a string that says "You have ??? unsaved changes" [15:51] and you want ??? to be any number [15:51] or I should say if developers want ;) [15:52] then they will so called plural strings, they have one version for each plural state in english and you then need to make one translation for each plural state in your language [15:53] but this a quite an advanced topic and is much easier to grasp with an example, so ask you team or other translators when you run into it [15:53] I don't see any more questions, so lastly I will mention just a few quick words about quality [15:54] Strings that we translate are often very visible [15:54] therefore it is desireable to aim for as high quality in out translations as possible [15:54] However quality are a few different things [15:55] The obvious ones are grammar and spelling [15:55] take whatever help you can get and need to get it right, as many other people will see the strings you write [15:55] There are 5 minutes remaining in the current session. [15:56] this is not meant to discourage anyone, you do not need to be a grammar superhero, just as throrough as you can be [15:57] another thing concerning quality is the quality of the stuff that you are writing in your own language [15:57] in my case Danish [15:57] When you are transating you have the english string riiiiight next to the one you are writing === Fifthmarch is now known as anneboleyn [15:58] which makes it very easy to fall accidentally adopt the english sentence structure [15:58] which might not be the most elegant in your own language [15:59] so try and let go of the actual english sentence, focus on its contents and the formulate it in your own language [15:59] Well I could talk about translaion quality all day [15:59] but I think that was the last we had time for [16:00] if you have any more questions please drop by #ubuntu-translators and ask them there }}}