Re: Docs String Freeze Exception: Update keyboard shortcuts
Al 03/04/12 05:22, En/na Jeremy Bicha ha escrit: Design has requested window management keyboard shortcuts to be changed to use Ctrl+Super instead of just Super. Full details are available at https://bugs.launchpad.net/ayatana-design/+bug/969235 Hi Jeremy, Ack, and +1 from translations. If the actual shortcut in the code changes, documentation and translations need to reflect that change to be correct. At the same time, I want to refer to the Windows key as the Super key instead of as the Meta key. Meta is confusing as it also refers to the Alt key. Since Unity's new keyboard shortcut overlay uses Super, anything else would be confusing. I've submitted a merge with these changes at https://code.launchpad.net/~jbicha/ubuntu-docs/lp969235-ctrl-super-keyboard-shortcuts/+merge/100546 Sounds sensible too. However, that will break quite a lot of existing translations. In order to avoid it, if you apply this change, could you please: 1. Apply the s/Meta/Super substitution to the .pot file and all the .po files in the precise-translations docs branch (both in the msgid and msgstr fields) 2. Merge the precise-translations branch with trunk, so that Launchpad can import the new translations (*) Let me know if we can help with any of this. Cheers, David. (*) I've noticed Launchpad changes the directory layout on the precise-translations branch to be a flat listing of PO files, which means the merge probably won't work. Then I'd simply suggest fetching the files from the branch, putting them in the right place in the trunk branch and committing. -- David Planella Ubuntu Translations Coordinator www.ubuntu.com / www.davidplanella.wordpress.com www.identi.ca/dplanella / www.twitter.com/dplanella signature.asc Description: OpenPGP digital signature -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translation status for ubuntu-docs
Hi, On 26 March 2012 11:09, David Planella david.plane...@ubuntu.com wrote: You're probably aware of the feature, but you can also alternatively export translations to a separate branch, which you can choose to merge to trunk at your convenience. In whichever way you use it, branch exports and imports are recommended over manual exports and imports. Yes, I was aware of it, but I don't really see any benefit in using it over and above a simple export of po files from Launchpad. What are the reasons why a branch export is recommended over a manual export? -- Matthew East http://www.mdke.org gnupg pub 1024D/0E6B06FF -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translation status for ubuntu-docs
Al 03/04/12 08:49, En/na Matthew East ha escrit: Hi, On 26 March 2012 11:09, David Planella david.plane...@ubuntu.com wrote: You're probably aware of the feature, but you can also alternatively export translations to a separate branch, which you can choose to merge to trunk at your convenience. In whichever way you use it, branch exports and imports are recommended over manual exports and imports. Yes, I was aware of it, but I don't really see any benefit in using it over and above a simple export of po files from Launchpad. What are the reasons why a branch export is recommended over a manual export? In general, - Correct paths: Paths and PO file names of branch exports are correct, unlike many manual exports - More automation: no need to manually go to the web UI, request an export, wait for Launchpad to reply, get download URL from Launchpad's e-mail. Changes are committed daily to the branch, which can then be merged to trunk with one bzr command, instantly, without having to wait for Launchpad. - Latest data availability: expanding on the previous point, having the latest data available without the need of manual intervention, makes it possible to provide infrastructure to help community work around that data. I've not announced it widely as it is not more than an experiment for now, but I've been working on such a tool as a helper to documentation translation work, and getting feedback from translators (see below). Last week I had a chat on #ubuntu-doc with jbicha and he set the exports branch for me, which is what I'm using to generate a daily HTML build of translated documentation to help translators [1]. This has been very helpful, so I think this point is already covered, thanks Jeremy! Cheers, David. [1] http://91.189.93.101/ (currently down for maintenance) -- David Planella Ubuntu Translations Coordinator www.ubuntu.com / www.davidplanella.wordpress.com www.identi.ca/dplanella / www.twitter.com/dplanella signature.asc Description: OpenPGP digital signature -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translation status for ubuntu-docs
On 3 April 2012 07:57, David Planella david.plane...@ubuntu.com wrote: Al 03/04/12 08:49, En/na Matthew East ha escrit: On 26 March 2012 11:09, David Planella david.plane...@ubuntu.com wrote: You're probably aware of the feature, but you can also alternatively export translations to a separate branch, which you can choose to merge to trunk at your convenience. In whichever way you use it, branch exports and imports are recommended over manual exports and imports. Yes, I was aware of it, but I don't really see any benefit in using it over and above a simple export of po files from Launchpad. What are the reasons why a branch export is recommended over a manual export? In general, - Correct paths: Paths and PO file names of branch exports are correct, unlike many manual exports I think that, as you noted at the bottom of your email here [1], that this isn't the case! [1] https://lists.ubuntu.com/archives/ubuntu-doc/2012-April/016482.html - More automation: no need to manually go to the web UI, request an export, wait for Launchpad to reply, get download URL from Launchpad's e-mail. Changes are committed daily to the branch, which can then be merged to trunk with one bzr command, instantly, without having to wait for Launchpad. That might be true if the correct paths were maintained, but if they aren't, the po files have to be added manually anyway, and I don't think it makes much difference. I'm not 100% up to speed on how bzr merge works, but won't the bzr merge command add the revision history from the translations branch to the main branch? If so, and given the massive number of daily changes to the translations branch, I think that this could dramatically increase the size of the revision history in the main branch, increasing download time for contributors. - Latest data availability: expanding on the previous point, having the latest data available without the need of manual intervention, makes it possible to provide infrastructure to help community work around that data. I've not announced it widely as it is not more than an experiment for now, but I've been working on such a tool as a helper to documentation translation work, and getting feedback from translators (see below). I agree that this could be an advantage, although if there is the path issue noted above, wouldn't it require manual intervention in any event? -- Matthew East http://www.mdke.org gnupg pub 1024D/0E6B06FF -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translation status for ubuntu-docs
Al 03/04/12 10:10, En/na Matthew East ha escrit: On 3 April 2012 07:57, David Planella david.plane...@ubuntu.com wrote: Al 03/04/12 08:49, En/na Matthew East ha escrit: On 26 March 2012 11:09, David Planella david.plane...@ubuntu.com wrote: You're probably aware of the feature, but you can also alternatively export translations to a separate branch, which you can choose to merge to trunk at your convenience. In whichever way you use it, branch exports and imports are recommended over manual exports and imports. Yes, I was aware of it, but I don't really see any benefit in using it over and above a simple export of po files from Launchpad. What are the reasons why a branch export is recommended over a manual export? In general, - Correct paths: Paths and PO file names of branch exports are correct, unlike many manual exports I think that, as you noted at the bottom of your email here [1], that this isn't the case! [1] https://lists.ubuntu.com/archives/ubuntu-doc/2012-April/016482.html You're absolutely correct, which is why I think the current set up is already the best we can have: - Automatic imports - Automatic exports (exporting to a separate branch). Sorry I didn't include the info about the exports layout on my previous reply. It was meant to be a generic list of advantages of manual vs. automatic exports, and what I meant by that point is that in automatic ones the files are named correctly (e.g. languagecode.po) and are placed in the right location, which is something that often does not happen with manual exports. Now in the particular case of Ubuntu docs we've got the following layout: ubuntu-help/ubuntu-help.pot ubuntu-help/ca/ca.po ubuntu-help/zh_CN/zh_CN.po ... But Launchpad expects the common gettext layout, i.e. flat, with all .po files and .pot file in one same folder: ubuntu-help/ubuntu-help.pot ubuntu-help/ca.po ubuntu-help/zh_CN.po ... Which in turn means the ubuntu-docs layout is not directly supported. I only realised that after I had initially suggested to use automatic exports to trunk, so I apologise for suggesting a non-working option. I think it would still work if we were to set symlinks linking to the right paths, but unless someone would like to volunteer for investigating this approach, I'd suggest leaving trunk exports for now. In summary, though, I'd still recommend the current setup (automatic imports, automatic exports to separate branch) for this and future releases. - More automation: no need to manually go to the web UI, request an export, wait for Launchpad to reply, get download URL from Launchpad's e-mail. Changes are committed daily to the branch, which can then be merged to trunk with one bzr command, instantly, without having to wait for Launchpad. That might be true if the correct paths were maintained, but if they aren't, the po files have to be added manually anyway, and I don't think it makes much difference. It still offers advantages. Compare (manual export): 1. Go to the docs project Launchpad URL 2. Request the full translations download (only project maintainers can do this) 3. Wait for Launchpad to request (it might take from minutes, to hours to days, depending on Launchpad's load) 4. Check your e-mail, retrieve the download link 5. Fetch translations from the download link, wait for download to complete 6. Uncompress tarball, fix filenames and paths if necessary 7. Put translations in the ubuntu-docs tree 8. Commit translations: bzr commit -mUpdated translations from Launchpad Vs (automatic export to separate branch): 1. Checkout latest translations: bzr checkout --lightweight lp:~ubuntu-core-doc/ubuntu-docs/$RELEASE-translations 2. Put the translations in the ubuntu-docs tree. E.g. (where PODIR is the checkout location of the previous command, and DOCSDIR where the ubuntu-docs tree lives) #!/bin/env bash for f in $PODIR/ubuntu-help/*.po do LANG=`basename $f .po` echo Copying $f to $DOCSDIR/ubuntu-help/$LANG cp $f $DOCSDIR/ubuntu-help/$LANG done 3. Commit translations: bzr commit -mUpdated translations from Launchpad The second option (automatic export to separate branch) you can do in a matter of a few minutes in a synchronous manner, while the first option might take hours and you'll be depending on Launchpad and you'll have to finish your work asynchronously. I'm not 100% up to speed on how bzr merge works, but won't the bzr merge command add the revision history from the translations branch to the main branch? If so, and given the massive number of daily changes to the translations branch, I think that this could dramatically increase the size of the revision history in the main branch, increasing download time for contributors. I'm not a bzr expert either, so I'm not in the position to provide an authoritative answer. In any case, I'll just add a few points to the discussion: - With the 3-step approach above, you would not be merging revisions
Re: Translation status for ubuntu-docs
Al 26/03/12 17:10, En/na Ask Hjorth Larsen ha escrit: Dear translators and documentation people On Mon, 26 Mar 2012, Timo Jyrinki wrote: 2012/3/26 Jeremy Bicha jbi...@ubuntu.com: I uploaded the potfile for ubuntu-docs tonight and opened up translations on Launchpad for the precise branch. What about the ubuntu-docs under /ubuntu/precise/+source/ubuntu-docs - it'll be updated at the time of actual upload? For future, do you think that ubuntu-docs under the Ubuntu translations should simply be not visible until the final template is uploaded? Or this current system still better? I think one of the biggest invisible problems in Ubuntu translations making people go away (if they notice it) is the fact that work is wasted. Most of the people translating do not know that probably a lot of their translations will not be used if they've been translating ubuntu-docs in the last month or so, or even this coming week. This would not be such a big problem it is today without being combined with the lack of supporting fuzzy strings in LP. Then when the docs team do a cleanup of commas, articles or word orders (I'd assume there is always a bunch of those in addition to total rewrites), quality translations that would still have a lot value (either 100% match or something easily fixed to match the new form) are being lost. This is especially big problem in ubuntu-docs, since it has long strings, and a single small change anywhere will always reset a big amount of translated text compared to application UI texts that are usually much shorter. With the new precise ubuntu-docs template, I see that while the total number of strings have stayed roughly the same (+100 strings), the number of untranslated strings have raised from 358 to 1086. What I personally will do is: - now very quickly save the current Ubuntu precise's ubuntu-docs PO file - when the new ubuntu-docs gets to precise proper, fuzzy match the downloaded PO file to the new template manually with gettext tools - in case of simple word order / punctuation / etc changes simply unfuzzy or make a little fix in the translation - upload the new PO with saved translations back to Launchpad But I'd estimate that not many of the languages have the luck of someone doing this work. In the other language teams, there might be frustrated people noticing that the hard work they've done (translating ubuntu-docs is really hard work since there is so much of it) has for a part disappeared. Not that this would be a new problem of course, but what do you think about the template hiding idea or do you have any other ideas to help this problem (other than contributing to LP code)? -Timo Hi Ask, I apologise for the delay in replying. I apologize in advance for the considerable amount of grumbling below. But I think we have big problems. No need to apologise on your side. As long as the conversation is civil, we should encourage everyone to speak their mind to highlight problems and how to fix them. So thank you for your direct and honest feedback. I think Launchpad should be entirely disabled for docs translations. The lack of fuzzy matching makes Launchpad almost useless for anything but UI translations. The alternative is to use e.g. a bzr archive to maintain the translations. This requires more technical knowledge, but we (translations coordinators) can help individual translators with it, and actually get the job done. We are qualified to use tools like bzr, msgmerge and other things to make sure that work is not lost. But right now I (as a coordinator) am quite powerless to stop the waste of time. The only thing I can do is to not recommend that people work on certain things. I cannot even put a big red sticker on the ubuntu docs page on Launchpad saying don't translate this. I have only indirect means of communication (e-mails) around Launchpad. This makes everything very complicated and not something I look forward to dealing with. I acknowledge the problems with fuzzy translations, and as it's been discussed several times in the mailing list, for now and the foreseeing future, we've only got workarounds to deal with it. However, and despite these issues, I'm personally against disabling translations in Launchpad. While in your team or on others there might be contributors with experience with bzr or other version control systems, I'd encourage you to consider the wider translation community, where most translators don't possess those technical skills. The approach in Ubuntu has always been to lower the approach to contribution, and that would go on the opposite direction. Shutting down translations in Launchpad and allowing only VCS contributions would not only radically increase the barrier to translation contribution, limiting it to a few translators with technical skills, but it would also increase the amount of work from the docs team to merge and commit all merge proposals coming
Re: Translation status for ubuntu-docs
Al 27/03/12 11:44, En/na Hannie Dumoleyn ha escrit: Op 26-03-12 17:10, Ask Hjorth Larsen schreef: Dear translators and documentation people On Mon, 26 Mar 2012, Timo Jyrinki wrote: 2012/3/26 Jeremy Bicha jbi...@ubuntu.com: I uploaded the potfile for ubuntu-docs tonight and opened up translations on Launchpad for the precise branch. What about the ubuntu-docs under /ubuntu/precise/+source/ubuntu-docs - it'll be updated at the time of actual upload? For future, do you think that ubuntu-docs under the Ubuntu translations should simply be not visible until the final template is uploaded? Or this current system still better? I think one of the biggest invisible problems in Ubuntu translations making people go away (if they notice it) is the fact that work is wasted. Most of the people translating do not know that probably a lot of their translations will not be used if they've been translating ubuntu-docs in the last month or so, or even this coming week. This would not be such a big problem it is today without being combined with the lack of supporting fuzzy strings in LP. Then when the docs team do a cleanup of commas, articles or word orders (I'd assume there is always a bunch of those in addition to total rewrites), quality translations that would still have a lot value (either 100% match or something easily fixed to match the new form) are being lost. This is especially big problem in ubuntu-docs, since it has long strings, and a single small change anywhere will always reset a big amount of translated text compared to application UI texts that are usually much shorter. With the new precise ubuntu-docs template, I see that while the total number of strings have stayed roughly the same (+100 strings), the number of untranslated strings have raised from 358 to 1086. What I personally will do is: - now very quickly save the current Ubuntu precise's ubuntu-docs PO file - when the new ubuntu-docs gets to precise proper, fuzzy match the downloaded PO file to the new template manually with gettext tools - in case of simple word order / punctuation / etc changes simply unfuzzy or make a little fix in the translation - upload the new PO with saved translations back to Launchpad But I'd estimate that not many of the languages have the luck of someone doing this work. In the other language teams, there might be frustrated people noticing that the hard work they've done (translating ubuntu-docs is really hard work since there is so much of it) has for a part disappeared. Not that this would be a new problem of course, but what do you think about the template hiding idea or do you have any other ideas to help this problem (other than contributing to LP code)? -Timo I apologize in advance for the considerable amount of grumbling below. But I think we have big problems. I think Launchpad should be entirely disabled for docs translations. The lack of fuzzy matching makes Launchpad almost useless for anything but UI translations. The alternative is to use e.g. a bzr archive to maintain the translations. This requires more technical knowledge, but we (translations coordinators) can help individual translators with it, and actually get the job done. We are qualified to use tools like bzr, msgmerge and other things to make sure that work is not lost. But right now I (as a coordinator) am quite powerless to stop the waste of time. The only thing I can do is to not recommend that people work on certain things. I cannot even put a big red sticker on the ubuntu docs page on Launchpad saying don't translate this. I have only indirect means of communication (e-mails) around Launchpad. This makes everything very complicated and not something I look forward to dealing with. There is only one thing which is worse than not getting a voluntary contribution due to it being too difficult, and that is to get the contribution and then throw it away. Because that contributor will not come back. I and others have previously requested fuzzy matching and some other IMHO essential features on Launchpad, but there seems to be no plans to implement any of it or even recognize the importance. So please disable ubuntu docs in Launchpad. Best regards Ask Hello Ask, I fully understand your grumbling, but for the moment we have to make do with what we have. Because I firmly believe in the translation of Ubuntu Desktop Guide, I translated most of the Oneiric version on LP. And when I click F1 on my desktop (Oneiric), I am so proud to see that almost everything is in Dutch now. Regards, Hannie Thanks Hannie for your feedback and your awesome work translating the guide, that's the spirit! Cheers, David. -- David Planella Ubuntu Translations Coordinator www.ubuntu.com / www.davidplanella.wordpress.com www.identi.ca/dplanella / www.twitter.com/dplanella signature.asc Description: OpenPGP digital signature -- ubuntu-translators mailing list
Translations deadline approaching: useful translation resources
Hi all, Just a quick announcement of a couple of resources that should help you in translating 12.04. I've been mentioning some of them, but not too widely in the last few weeks, as they are still experimental. So if you see any bug, downtime or anything worth reporting, please let me know. I hope you find them useful! Translations stats -- The translations stats site is a resource that should help translation teams focus their precious time on the most important translations and track and showcase their progress: http://91.189.93.77/stats/precise What I also personally like about this is that you can see message sharing at work: notice the Italian translation of Oneiric benefiting from translations that have been done in Precise: http://91.189.93.77/stats/oneiric/it I've created a Launchpad project for it, where anyone can report bugs, ask questions, (soon) translate and contribute to code: https://bugs.launchpad.net/ubuntu-translations-stats Ubuntu docs translations I'm hosting the translated HTML version of the Ubuntu docs and updating it daily with Launchpad translations here: http://91.189.93.101/ The site should serve you the right pages according to your browser preferences. If you've got any issue seeing the localised pages (I know there is one with the Danish pages), just let me know. I can also do additional updates if you've got a PO file you'd like to have online before the next daily update. Just send me the Launchpad export link to the PO file and I can update the translated html with it. Regards, David. -- David Planella Ubuntu Translations Coordinator www.ubuntu.com / www.davidplanella.wordpress.com www.identi.ca/dplanella / www.twitter.com/dplanella signature.asc Description: OpenPGP digital signature -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translation status for ubuntu-docs
Al 03/04/12 12:59, En/na Hannie Dumoleyn ha escrit: As I said, I'm not particularly in favour of disabling them, but I'd like to hear what other translators have got to say on this, and if they've got any further ideas. Thanks again for the honest feedback and for raising this issue. Cheers, David. Here is a reaction from a frustrated translator ): Hi Hannie, Thanks for your e-mail. I think at this point we all have realized changes in documentation strings are an issue for translations. In terms of feedback, rather than more examples that this is an issue, I was thinking rather of ideas on how we could minimize it. That said, let me reply to the points below: It is a hell of a job to get previous translations back, but since fuzzies are not supported in Launchpad the only way to get them back is by copying and pasting. As from the comments I understand this translator knows how to use the gettext tools, here's a suggestion to get back fuzzy strings quickly: 1. Download the PO file for your language from Launchpad (nl.po) 2. Download the POT file from Launchpad (ubuntu-help.pot) 3. Run the following command: msgmerge nl.po ubuntu-help.pot nl-fuzzies.po That should then give you a file with fuzzy matches. I use a merged file, which I open in Lokalize (more than 600 fuzzies!). While working online in LP on the Precise version, I look in Lokalize to see if there is a fuzzy and when that is the case I copy and paste the fuzzy to LP and make the changes. Often they are minor, such as: top panel becomes menu bar, '.' becomes key.key/, item becomes file, and so on. The amount of *extra* work cannot be expressed in hours, but in weeks I'm afraid. Hannie Right, apart from the fact that Launchpad hides fuzzy strings, what you are describing here is something that is outside of Launchpad and any other translations tool's control. This is due to minor changes being done to documentation and the original translations becoming obsolete. The only thing I can think of is that whenever such a trivial change is done in the original docs is done, the replacement is done on the translations (the .po files) and the template (the .pot file). That is also not without its drawbacks: - It increases the amount of work for the docs team (they'd be doing the replacements in the .po and .pot files) - String replacement in translations is very tricky, and should probably be left to translators except for the most trivial cases. Cheers, David. -- David Planella Ubuntu Translations Coordinator www.ubuntu.com / www.davidplanella.wordpress.com www.identi.ca/dplanella / www.twitter.com/dplanella signature.asc Description: OpenPGP digital signature -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Small string changes to gnome-settings-daemon and gnome-control-center
Hey The email is a bit late but recently we changed those strings * gnome-settings-daemon To fix https://launchpad.net/bugs/964178 [UIFe] Make keyboard layout indicator more consistent https://wiki.ubuntu.com/KeyboardSettings?action=diffrev2=10rev1=8 In the keyboard indicator: - Keyboard Preferences got renamed Keyboard Layout Settings... - Show Current Layout got renamed Show Layout Chart * gnome-control-center to fix https://launchpad.net/bugs/968290 System settings - Appearance - Theme entries don't appear translated - the string default (displayed in the theme selector combo) got marked translatable -- Sebastien Bacher -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translation status for ubuntu-docs
Hello Ask, I fully understand your grumbling, but for the moment we have to make do with what we have. Because I firmly believe in the translation of Ubuntu Desktop Guide, I translated most of the Oneiric version on LP. And when I click F1 on my desktop (Oneiric), I am so proud to see that almost everything is in Dutch now. Regards, Hannie Thanks Hannie for your feedback and your awesome work translating the guide, that's the spirit! Cheers, David. Sorry for my grumbling in the other mail I sent earlier today to the list on this subject. I know everyone is doing his best and if it is technically too complicated, or we lack manpower, then it is just too bad. I still enjoy translating the docs, and I hope our work will not be in vain. But yes, I am frustrated about all the extra work and I hope one day it will be possible in LP the fuzzies can be transferred to a new version. Thanks for your kind words. It does keep the spirit high :) Hannie -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
serverguide now translatable
Dear all, I've activated the Ubuntu Server Guide for translations and it can be translated here: https://translations.launchpad.net/serverguide/precise/+translations This document isn't published in Ubuntu as a package but it is displayed on help.ubuntu.com. Translating it is a large and complex job but some teams have translated it in the past so I think that it's worth having translations enabled. -- Matthew East http://www.mdke.org gnupg pub 1024D/0E6B06FF -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
UIFe: Update keyboard shortcut overlay with more consistent wording
Hi, Unity 3D's new keyboard shortcut overlay (when you press and hold the Super/Windows key) has rather inconsistent grammar and wording. I've submitted a branch proposal to improve this. https://bugs.launchpad.net/ubuntu-translations/+bug/964673 I apologize for the late notice and I realize this changes several strings. Is this something that can happen for Precise? Thanks, Jeremy Bicha -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translations deadline approaching: useful translation resources
Hello David, On 03-Apr-12 6:21 PM, David Planella wrote: Hi all, Just a quick announcement of a couple of resources that should help you in translating 12.04. I've been mentioning some of them, but not too widely in the last few weeks, as they are still experimental. So if you see any bug, downtime or anything worth reporting, please let me know. I hope you find them useful! Translations stats -- The translations stats site is a resource that should help translation teams focus their precious time on the most important translations and track and showcase their progress: http://91.189.93.77/stats/precise I looked at the link and saw that Khmer translation is 35%, Does this mean that Khmer will not include in the release or 12.04? Today I download Beta 2 release and try to install but unfortunately I did not see Khmer language in Ubuntu Installer. I have finished translating debian-installer and most of the files in: https://translations.launchpad.net/ubuntu/precise/+lang/km What is the different translations between https://translations.launchpad.net/ubuntu/precise/+lang/km and http://91.189.93.77/stats/precise/km for Khmer? Regards, Sokhem -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translations deadline approaching: useful translation resources
On 3 April 2012 07:21, David Planella david.plane...@ubuntu.com wrote: Ubuntu docs translations I'm hosting the translated HTML version of the Ubuntu docs and updating it daily with Launchpad translations here: http://91.189.93.101/ That website isn't working right. In both Firefox and Chromium, my browser tries to download pages to my Downloads folder, instead of just displaying them like normal webpages. Thanks, Jeremy -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
