[l10n-dev] Re: IMPORTANT: pls fix double names
Op Vr, 2011-04-15 om 14:24 +0200 skryf Eike Rathke: Hi Dwayne, On Friday, 2011-04-15 12:43:45 +0200, Dwayne Bailey wrote: Instead of reinventing the wheel. Why not use poconflicts? http://translate.sourceforge.net/wiki/toolkit/poconflicts - which detects these kinds of different translations. That's a solution for a different problem. We don't want to detect different translations of a term, but identical translations of different terms within a given set. For example Calc function names, if both SEARCH and FIND are translated identical it breaks functionality. Poconflict checks for both. Dwayne has been doing these checks on our translations for something like 6 years, and I think has demonstrated them at OOo conferences. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/better-lies-about-gnome-localisation -- - To unsubscribe send email to dev-unsubscr...@l10n.openoffice.org For additional commands send email to sy...@l10n.openoffice.org with Subject: help
Re: [l10n-dev] Scottish Gaelic (gd) localisation
Op Do, 2011-01-13 om 17:37 + skryf Michael Bauer: Is there a specific reason you mention them in this order? I usually try to sort alphabetically or in order of frequency if it is obvious (for example I usually list the capitals last). Where shall we position the Tironian ampersand (when we decide which one to use :-)? Errr, no, sorry, they just group that way phonologically in Gaelic, alphabetically is fine. As a total outsider it seems as if 204A could hold some advantages, but in terms of the practicalities I can't cast a judgement. The ideal would be if we gradually do things better, but it is hard to convince people to improve font support for small languages. It is a common problem in Africa for languages needing extra diacritics. Now if you could get some government to mandate language support for imported products, it might just get fixed quite quickly :-) Ya that would be the thing. I did a test page and a straw poll on my Facebook account. Last time I ran a test, virtually everyone had boxes but this time, only about half reported probles and then usually linked to Google Chrome; interestingly cross-OS support has improved. What worries me is that mobile devices can't handle 204A at all by the looks of it, whereas most seem to do the other one fine. So I think we'll go with the second-best option for now; I'll monitor development and when I can see a majority of platforms supporting 204A, we can make the change. For now, it's more important that it displays, rather than encoding purity. If it improved quickly, I guess it will get even better. Chrome has some font issues; I'm guessing it will just disappear one of these days. The releases of Pootle we make now, only affect people installing this in future, targeting even later usage. I just had a new idea: adding both. This way people can make the choice per application they are translating. It seems that only mobile applications might need the wrong character. What do you think about that idea? Similar things to what would help improving OpenOffice.org. We can use a spell checker and autocorrect data exactly as they are used in OpenOffice.org. I guess Kevin Scannel is the best person to talk to with regards to spell checkers. I can help you build the necessary autocorrect files - we have some scripts to take a spreadsheet of incorrect - correct columns and generate the file needed for Virtaal and OpenOffice.org. There already is one: http://extensions.services.openoffice.org/en/project/faclair-afb (though the server seems to be down just now). Is there some way we can utilise that? Perfect. I can upload it soon. Just say - do you feel it is ready for general use for localisers? The beta warning is very bold here :-) Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/versions-dependencies-different-distributions - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Scottish Gaelic (gd) localisation
Op Di, 2011-01-11 om 13:50 + skryf Michael Bauer: Friedel, Easy. The rules on Launchpad are wrong. I hadn't seen those as I tend not to use Launchpad but prefer to handle gd localisations at each project's source and localising and OS is not high on the list of priorities right now. But thanks for pointing those out, I'll see if I can get those amended. Irish has a similar problem. Kevin Scannell once explained that in the early days of the web some enthusiastic person put out a bad plural ruleset for Irish and he's been chasing it around cyberspace ever since. I'm also trying to get the right rules onto Unicode but those guys make the Siachen Glacier look like a MiG. Thanks for the headsup again! Michael Ok, I suspected something like that was possible. I'm adding support to both Pootle, Virtaal and the Translate Toolkit. What is the preferred name for your language? I see the ISO codes package refers to it as Gaelic; Scottish Gaelic - we try to find a way of fixing these names, at least for English. Should I prefer Gaelic or Scottish Gaelic? I guess Scottish Gaelic is better since some people refer to Irish as Gaelic as well. Any special characters that localisers might not be able to type easily? We can add those in Pootle as clickable links by default if you think it is useful enough. Furthermore, we can now look into our quality checks to see if any customisations can be done to ensure they serve your language well. If you are interested in customising Virtaal for some of its language specific features, we can look down that path as well (not necessarily a big task). Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/versions-dependencies-different-distributions - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Scottish Gaelic (gd) localisation
Op Do, 2011-01-13 om 12:35 + skryf Michael Bauer: The preferred name is Scottish Gaelic (Gaelic is ambiguous as you say, referring to Scots, Irish and Manx Gaelic). I committed initial support for Scottish Gaelic including the plural form to our software, and it will form part of our next release. Special characters would be the vowels with grave Àà Òò Ùù Èè Ìì ... Is there a specific reason you mention them in this order? I usually try to sort alphabetically or in order of frequency if it is obvious (for example I usually list the capitals last). Where shall we position the Tironian ampersand (when we decide which one to use :-)? ... and the Tironian ampersand. Now technically that's ⁊ at U+204A but practically speaking, people often use ┐ at U+2510 because it's visually usually the same but is more commonly represented in fonts. 204A would be better but I can live with 2510. What do you think? I can't speak for the font coverage. On my system U+204A is displayed with DejaVu Sans just fine, which is the font used as the main UI font on most Linux distributions, I think. It is also packaged with OpenOffice.org as far as I know, so it isn't totally unsupported. In tools that use a Monospace font by default (like Virtaal or text editors) it might be more of an issue, since I see it isn't present in DejaVu Sans Mono, although I still have it in the FreeMono font on my system. Most such editors allow setting a custom font anyway. The more important issue might be that the Unicode properties for these two characters are different. The one is classified as punctuation (204A) and the other as a symbol (2510). This won't make a difference in many situations, but can only make things go wrong. I guess it might affect advanced searches, line breaking and maybe more. I can't say for sure. As a total outsider it seems as if 204A could hold some advantages, but in terms of the practicalities I can't cast a judgement. The ideal would be if we gradually do things better, but it is hard to convince people to improve font support for small languages. It is a common problem in Africa for languages needing extra diacritics. Now if you could get some government to mandate language support for imported products, it might just get fixed quite quickly :-) What sort of customisations for Virtaal are you talking about? I've not used it much so not sure what's possible etc. Similar things to what would help improving OpenOffice.org. We can use a spell checker and autocorrect data exactly as they are used in OpenOffice.org. I guess Kevin Scannel is the best person to talk to with regards to spell checkers. I can help you build the necessary autocorrect files - we have some scripts to take a spreadsheet of incorrect - correct columns and generate the file needed for Virtaal and OpenOffice.org. Another interesting feature of Virtaal is Autoterm, where translators can automatically obtain the common FOSS glossary. Read more here: http://translate.sourceforge.net/wiki/virtaal/autoterm Further customisations to the quality checks might benefit users if there are common false positives or cases where the accuracy of the tests can be improved with knowledge of Scottish Gaelic. This is not important or urgent. I guess if you use the quality checks you might eventually know if there are things you want to see improved. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/versions-dependencies-different-distributions - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] Draft of the ANLoc FOSS localisation manual
Hallo everybody I've been working on a book about the localisation of Free and Open Source Software. The first version of the book is almost finished, and I would love to get more feedback. Download it here: http://www.africanlocalisation.net/foss-localisation-manual It is available under the Creative Commons license “Attribution Non-Commercial Share Alike”. I explain a bit more about the why and how on my blog: http://translate.org.za/blogs/friedel/en/content/draft-anloc-foss-localisation-manual Thank you for any help or feedback. Regards Friedel -- Translate with Virtaal! http://virtaal.org/ - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Pootle is down
Op Do, 2010-08-05 om 19:08 -0300 skryf Santiago Bosio: ... Santiago PS: someone has a hint on the timeframe for the new server to be up? Hi Santiago We've already starting testing the server and things are looking good so far. I guess after the current round of translations there might be good news. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/communities-have-power-and-speed - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Op Do, 2010-06-24 om 10:50 +0200 skryf Goran Rakic: У чет, 24. 06 2010. у 08:13 +0200, André Schnabel пише: Did anybody try to build a tmx from old translations using po2tmx and then pretranslate? If I clear all duplicates in my compendium I have 100% fuzzy match with PO too. Fuzzy match is not the same as moving the exact translation string. Moving translation string does not require any review. I completely agree that matching strings by identifier is more valuable than a 100% string match. = Contexts everywhere = oo2xliff gives you the full context ;) This is a missing feature in oo2po. Context is passed and visible in a comment, not in a gettext msgctxt field where other tools expects it. The msgctxt field was always meant to be used to disambiguate otherwise identical messages. It isn't meant to be an identifier for the string, because the source text (msgid) is the unique identifier (when combined with the optional msgctxt). When we added support for msgctxt in the converters, the support for it in many PO software was very minimal, so we obviously wanted to only use it where it was necessary (and we continued to give alternatives, such as KDE comments, merging, etc.) Recent releases of the toolkit (since version 1.3.0) only support merge and msgctxt, however. Maybe we should add an option to always add msgctxt based on the identifier, similar to the old msgid_comment_all style we used to have: http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle using tmx gives you what you want. Iv you use xliff as format for translation files, you could even correctly mark how the segment was translated and decide later hwo to deal with such segments (auto-approve, review ...) I can do the same with PO file. Maybe the semantics is not standardized like in xliff but xliff is overcomplicated. I want to be able to grep and sed my translations, I can not do that with xliff. Just in case some people weren't aware: pogrep from the Translate Toolkit can search in XLIFF, PO and TMX files (and even .mo files as well :-) http://translate.sourceforge.net/wiki/toolkit/pogrep Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OOo svn
Op So, 2010-06-27 om 22:30 +0700 skryf Nguyen Vu Hung: Hello, 2010/6/27 Goran Rakic gra...@devbase.net Dana Ned, 27 Jun, 2010 15:04 , Nguyen Vu Hung je napisao/la 1. What is the best tool for po file offline translation? I use plain old text editor with PO syntax coloring. Poedit and Virtaal[1] are some of the tools I see others use. Lokalize is also good option if you can run KDE applications on your OS. [1] http://translate.sourceforge.net/wiki/virtaal/index [2] http://userbase.kde.org/Lokalize Thanks, we use Poedit and sometimes pootle for translating. Obviously I would also recommend Virtaal, but I'm not exactly objective :-) Of course, it has many interesting features over something like poedit, and is available on Windows very easily (unlike Lokalize as far as I know). Read about some of the features here: http://translate.sourceforge.net/wiki/virtaal/features 2. (With pootle and other tools), how can I track how many strings, words that my vi members have translated? You can always count translated messages. If you want to know how many were translated in the past, you need to do before and after count. If you manage your PO file in version control system you can run the pocount tool on the latest and previous revision. The need raises when we need to make a report on who and how many strings has been translated by that person. It seems that pootle doesn't provide this feature. # Hello, I know that some people at translate.sf.net is reading this mailing list. (I don't follow all mail, so please use the Pootle mailing list for such purposes, or maybe point our attention to a specific thread you want us to look at.) Pootle 2.0 provides some statistics at different levels about how many strings were suggested, reviewed and translated. You can look at our server to see an example: http://pootle.locamotion.org/ As you click into more detail, you will see how the statistics apply to that language or project. 3. Can I access po files via svn? - http://wiki.services.openoffice.org/wiki/OOo_and_Subversion If your team is using Pootle at sunvirtuallab.com for translating, OpenOffice.org release engineers would merge your translations with new templates and (luckily) you do not get to worry about it. You should make backups as mistakes happens. I would seriously recommend that people make backups, and that we look at putting all the PO files in some version control system as well. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Op Di, 2010-06-22 om 14:42 +0200 skryf Rafaella Braconi: Hi Olivier, Hi everybody On 22.06.10 11:59, Olivier Hallot wrote: Hi Rafaella It is (so far) in the UI. Please take a look, for instance, at the CUI folder as it contains all strings for the options, the dialogs, tab pages and customization. This is something ready from the begining of the project. Other folders seems to have the same problem, and I have no way to easily point what went wrong. the problem is always that whenever there is a resource shifting it's very difficult to keep the translations... I wonder if 3.2 tmx files would help to recover old translations. They can be found at: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx32/ In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. On a side note, I really think we need a version control on the po files... I think that a more powerful translation memory in Pootle would help... I am surprised to hear that the PO files aren't in version control - it has many advantages, so I would strongly recommend it. Translation memory in Pootle will solve some of the issues we are talking about, but I still believe we need a way to find specific versions of the translations reliably. The upcoming version of Pootle has made good progress towards giving translation memory in the online translation interface. Although the final bits aren't implemented yet, I hope we can have it reasonably soon. I'd really appreciate it if people can get involved - at least for working towards a user interface for it. For the case of OOo (especially if stuff moved around), I think using TMX files during the upgrade and/or pomigrate2 is still the better solution anyway, since a cleaner migration to a new version means less review work, whereas translation memory would mean more information for translators, but requiring lots of review. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Op Wo, 2010-06-23 om 07:55 +0200 skryf André Schnabel: Hi, Hallo Goran, André, everybody. Am 22.06.2010 21:39, schrieb Goran Rakic: У уто, 22. 06 2010. у 16:10 -0300, Olivier Hallot пише: Hi Rafaella dev's I would like to express my deep disapointment with this situation. I will second that, but for what I know the problem here is in our PO toolkit, not in the process how developers work. Things can easily improve by creating a new tool for merging POTs created from SDF file with old PO files that could cope up with code moving from one module into another. If there are no voices against it I can work on this during July so we can test and improve it later and make it ready for next release cycle. Hmm .. I'm not really keen of having yet another tool. If we are working on something, this should be done within translate toolkit. The pretranslate tool from translate toolkit is supposed to do exactly what we need - unfortunately it doesn't work the way we need it. The tool that Goran mentions, pomigrate2 is supposed to handle this to some extent. Goran, can you maybe help us see what is currently missing in pomigrate2 to handle this situation? We should file a bug for the Translate Toolkit to ensure that we can prioritise this and try to fix this for everyone's benefit. At least not for xliff - did anybody try with .po? I also did not check, how successfull pretranslate works with translation memories. Unfortunately pretranslate manpage gives no information, what format to use as translation memory file. In fact - for my own workflow (using xliff files, OLTE and built in translation memory which is based on the translations I did so far) gives ~ 60% automatic transaltions for the moved strings. My translatoin memory does not contain all the previus translations, therefore the rather low rate. Unfortunately there is no german tmx file at ooo.services :( So for me - before starting a new tool I'd recommend: - to provide .tmx files based on previous translations for all languages - try to improve translate toolkit - teach developers about the workload some acitivities cause here, that seem to be very simple for developers and find some way to move l10n strings along with the original english strings I agree with all of this. Several tools, such as our own Virtaal, can use the TMX file to provide speedup to translators when working. We shouldn't underestimate the difference in value between identifier matched TM, and source text matched TM - matching perfectly on identifier and source text is the first prise, and would mean that no review of the string would be necessary (in principle). Matching on source text only (as you would with TMX files) would need review, in my opinion (at least for anything shorter). So please, let us work together to fix whatever we need on the tools side (including for teams using XLIFF :-) - We need to migrate translations well if source code moves, without translators needing to do a lot of work. I believe pomigrate2 is at least a step in the right direction, maybe with some outstanding work. - We need to ensure that up-to-date translation memories are available for people to use (regardless of whether source code moves or not). Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenCTI use?
Op Do, 2010-06-17 om 14:49 +0200 skryf Rafaella Braconi: Hi Sophie, Is it planed to migrate OpenOffice.org glossaries from SunGloss to OpenCTI? no. There are no plans to migrate OOo glossaries from SunGloss to OpenCTI. If yes, do you have a time frame of when it'll be done? I would like to maintain the French glossary and I have already several terms to add from the former versions. You are raising a very good topic - terminology management for OOo. I think that this is a good time to start gathering the requirements. What would you expect from a terminology tool? What are the key functions? Is this something that is already covered by the Pootle Terminology function? Is this something that can be set up in the OOo wiki system? Hi everybody We keep on talking about the coming Pootle server. So to build your excitement: the upcoming version of Pootle will still have all of the terminology features, but also support terminology extraction, and some abilities to do terminology management, such as editing the source text of the term, adding and removing terms, etc. I hope it will help more teams to do good terminology work along with their translations. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/translation-saturday - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Danish language on Pootle - please
Op Ma, 2010-05-10 om 18:32 +0200 skryf leif: ... Yes. The current translation is clearly from babelfish or google translate. More entertaining than useful ;-) It would be relevant for us to get translation privileges for this as well. Hi I just want to emphasise again: please don't translate Pootle there. As soon as the new version of Pootle is installed for OpenOffice.org, these change will disappear (probably soon, from what I understand). Please contribute it here to the official Pootle translations so that all Pootle users can benefit from your improvement. Maybe the Danish translation on the OOo Pootle can just be removed as a temporary measure? Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/virtaal-060-released - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Danish language on Pootle - please
Op Di, 2010-05-11 om 16:21 +0200 skryf Kristoffer Rath Hansen: Hi, I'm lakridserne from OOo Denmark (leif can verify that). Could you please post a link to the official Pootle site, where we can translate Pootle into better Danish? You can find it here: http://pootle.locamotion.org/da/ You will need to log in to be able to translate. Feel free to contact me if you have any questions. You are also free to join the Pootle mailing list if you want: https://lists.sourceforge.net/lists/listinfo/translate-pootle Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/virtaal-060-released - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Danish language on Pootle - please
Op Di, 2010-05-11 om 16:53 +0200 skryf Rafaella Braconi: Hi Friedel, On 11.05.10 15:44, F Wolff wrote: Op Ma, 2010-05-10 om 18:32 +0200 skryf leif: ... So you recommend to translate the Pootle resources at: http://pootle.locamotion.org/projects/pootle/ just to make sure the changes get integrated into next Pootle release, right? Exactly. I guess any work on the old version live for a very short while until the new server is deployed, so it doesn't feel worth while. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/virtaal-060-released - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Danish language on Pootle - please
Op So, 2010-05-09 om 16:01 +0200 skryf leif: Another thing is, that Pootle itself has been translated into Danish. We can only suggest changes to the Danish language. We have made a few suggestions and we will probably come with further suggestions in the future, now that we begin to use Pootle. You can contribute to the Danish translation of Pootle here: http://pootle.locamotion.org/da/ Let me know if you have any questions or issues there. The translations of Pootle there is for a newer version of Pootle that will hopefully be deployed soon for OpenOffice.org translation as well. Also, feel free to ask any questions about Pootle on the mailing list: https://lists.sourceforge.net/lists/listinfo/translate-pootle Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/virtaal-060-released - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Localization/Translation of OpenOffice.org
Op Do, 2010-05-06 om 10:36 +0200 skryf Ivo Hinkelmann: Hi, Hi everybody! On 05.05.2010 10:41, Frank Mau wrote: Hi, after the outage of one of our pootle-instances and the limitation of the other two ones, we see a pressing need to buy new hardware with a new version of Pootle 2.x. a fast and new machine combined with the new pootle version would be really helpfull! The current state of the pootle services is bad. Pootle 2.0 will work much better than the current version. We developed it with the scale of OOo in mind. In our mind is a quad-core machine (x86) with 2.x GHz and 8 or 16 GB RAM. To host all languages on one big machine, the disk space should be 1 TB for each of the two harddisks. that disk also fit well for hosting the latest l10n builds in all variants! I'm sure everyone is excited about these possibilities! We will work with Ivo and Frank to get the best performance for Pootle out of the hardware. Pootle 2.0 is really much improved. This solution should fit into our future l10n-scenario: Short update-times for the pootle-service, early localized builds, continuous localization. Hope this fits for pootle and our requirements for OOo-localizations. Any suggestions? Let's improve our OpenOffice.org for a larger community :-) Cheers, Frank and hopefully we can switch back to file merge instead of file upload! This would improve the security and I don't have to delete any misplaced l10n zips ;) Cheers, Ivo I think we'll be able to go back to merging, yes. But even if we don't: language administrators can do some of their own file management with Pootle 2, so hopefully this will already mean less work for you :-) Pootle 2.0 also allows a complete file to be uploaded as suggestions for teams that prefer that as part of their workflow. Pootle 2.0 brings a lot of improvements, not only to performance and scalability, but also things like the quality checks, easier permissions and account management, and useful information in news feeds. We are already working on Pootle 2.1 with several improvements to the online translation and review interface. We also want to make it easier for teams to manage their terminology work. Stay tuned! Thank you Ivo and Frank for your hard work on improving Pootle at OOo! Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/virtaal-060-released - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Using a Bafia dictionary in OO 3.1 (ksf_Cm)
Op Sa, 2010-02-27 om 20:54 +0100 skryf Uwe Jung: Hello, I hope I am on the right place here. I'm working on a Hunspell dictionary for the Bafia language which is situated in Central Cameroon. The ISO-Code is ksf. The dictionary is starting to work fine using Hunspell stand alone inside Ubuntu 9.10. How can I incorporate the dictionary to Open Office 3.1 ? Currently it seems not to know that this language exist? If there is a project to start on this matter, how should I start it? Best regards Uwe Jung Yaounde Hallo Uwe You will need to create a locale for OpenOffice.org to have some basic information about the language. There is currently a project under way to do this for some African languages here: http://www.it46.se/afrigen/ which is probably the easiest way to do this. I am not sure when they will contribute to OpenOffice.org again - be sure to ask. This is part of the African Network for Localisation: http://www.africanlocalisation.net/ Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/hunspell-osx-106 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Some errors in po/pot files
Op Wo, 2010-02-10 om 15:54 + skryf Sveinn í Felli: In helpcontent2/shared/guide.po on lines 3858-3864: #: digital_signatures.xhp#par_id3204443.help.text msgctxt digital_signatures.xhp#par_id3204443.help.text msgid link href=\http://wiki.services.openoffice.org/wiki/How_to_use_digital_Signatures\; \\English Wiki page on digital signatures/link msgstr msgfmt and kbabel give me error on this. Maybe there are too many slashes? Best regards, Sveinn í Felli P.S. This message is repeated several times. Hallo The correct layout would be like this: #: digitalsign_receive.xhp#par_id3204443.help.text msgctxt digitalsign_receive.xhp#par_id3204443.help.text msgid link href=\http://wiki.services.openoffice.org/wiki/How_to_use_digital_Signatures\; English Wiki page on digital signatures/link msgstr or even #: digitalsign_receive.xhp#par_id3204443.help.text msgctxt digitalsign_receive.xhp#par_id3204443.help.text msgid link href=\http://wiki.services.openoffice.org/wiki/How_to_use_digital_Signatures; \English Wiki page on digital signatures/link msgstr Do you know how this error was introduced? Which tools were used during the lifetime of this file? I remember that the Translate Toolkit used to have a small issue which could be related, but that was already some time ago if I remember correctly. If you can fix it by hand and upload it by overwriting, that should solve it. Unfortunately it seems that Pootle accepts that, so the error is only discovered later with another tool. I hope that helps. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/it-seems-my-web-browser-unique - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Regarding : Duplicated files on Pootle
Op Ma, 2010-02-08 om 17:21 +0100 skryf Ivo Hinkelmann: Hi Friedel, as you might have more knowlege about those po / pot tool chain, it looks like that a: pot2po -t $IN_DIR/$lang -i $POT_DIR -o $OUT_DIR/$lang don't remove old and no longer used files, like in our case reportdesign/registry/* that have been moved to reportbuilder/registry/*. But now I have both there in $OUT_DIR/$lang How can I avoid this? Cheers, Ivo Hi Ivo As far as I know, the output in OUT_DIR should directly reflect your POT_DIR - if not I'll be surprised. Did you not perhaps generate the pot files in a directory already containing files? If you have files moving around, the best would be to look at pomigrate2: http://translate.sourceforge.net/wiki/toolkit/pomigrate2 This way you won't have the moved file be seen as a new and empty file. It can do a few things more than pot2po does on its own, even though it uses pot2po internally (be sure to use --pot2po). I hope that can be a start to solving this. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/it-seems-my-web-browser-unique - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Regarding : Duplicated files on Pootle
Op Do, 2010-02-04 om 18:23 +0100 skryf Dick Groskamp: As SANTIAGO stated http://l10n.openoffice.org/servlets/ReadMsg?list=devmsgNo=11887 : I've also problems generating a new SDF from the po-files with po2oo. po2oo is skipping the directory reportdesign in total. That is the only problem, but now I am not able to deliver a new sdf wihcih includes the changes I've made to POOTLE to be refelcted in 3.2. Could someone give some advice on how to proceed from here ? I think this means that you have the wrong SDF file that you are using as template (-t). I'm not aware of where the correct one would be, but I think that is the issue here. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/it-seems-my-web-browser-unique - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Glossary: summary of your feedback and wishes
Op So, 2009-10-11 om 19:09 +0200 skryf Sophie: Concerning the terminology files, I'm reluctant to add more things to our Pootle servers because of their instability and slowness. Also, I may be wrong but I've seen that it is not possible to add context to the word. The upcoming version should address several of the performance issues that we have seen until now. In fact, a big focus for this release was scalability for the sake of the OOo community. At least for Pootle, it will ignore context given in this way: view (verb) The same methods of providing terminology help is used in Virtaal at the moment. This might not be perfect in all regards, as the PO format has a msgctxt field that should be used, but not all formats has something similar. Pootle will also display the comments for the term in the tooltip. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/pseudolocalisation-podebug-3-interview-rail-aliev - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] xmltags error
Op Di, 2009-10-13 om 13:14 +0200 skryf F Wolff: Op Do, 2009-10-08 om 04:35 -0700 skryf Belayneh Melka: Hi all, The sentence structure of the language(Oromo Language) for which we are doing the translation is different from English. Hence, when we translate the help files the order of the tags will be different from that for English. For example, English: Press item type=keycodeF6/item until the emphDrawing/emph toolbar is selected. Oromo: Hanga kamshaan emphFakkasaa/emph filatamutti item type=keycodeF6/item dhiibi. But, when we run pofilter command of translate toolkit on this translation file, the out put shows the following error: (pofilter) xmltags: checks that XML/HTML tags have not been translated. Does this have effect on the build? i.e. does the build crash due to this error? Thanks in advance, Dawit You should be able to reorder things as needed for your translation. BUT: please also report these issues to the Translate Toolkit team in future. I just happened to see this topic by accident, and would have entirely missed it otherwise. We want to continue to improve our quality checks so that they are as useful as possible to translators. Those of you who are interested in keeping track of progress on this issue can put themselves in CC for this bug: http://bugs.locamotion.org/show_bug.cgi?id=1160 Is anybody able to look into fixing this? Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/pseudolocalisation-podebug-3-interview-rail-aliev - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Glossary, how do you handle it?
Op Ma, 2009-09-28 om 22:11 +0200 skryf Sophie: Hi all, I would like to know how you handle your glossary for your language. As for now I use SunGloss [1]. But it seems that it is no more updated for English language and it's difficult for us to maintain our own language (this is not a criticism, it has been really helpful for me). I know several languages are missing on SunGloss and I would like to have a more accessible tool to maintain our glossaries. They are important for us of course, but also for other (sometime the same) localization teams who are working on other product. We may want to be consistent with Gnome, KDE, Firefox, the Gimp, Gnumeric, etc... Could we have a discussion on this and see if we need a tool that allow us to build and maintain our glossaries, with an easy search through languages, able to handle comments or definitions and with some revision Hallo Sophie, everybody Rafaella pointed me to this thread by private mail, so I'll write a few notes a bit late in the thread. Pootle can assist translators with terminology (created yourself, downloaded from our Pootle server, exported from something like SunGloss, anything really). The only issue is that it only supports PO and XLIFF files at the moment. If we have TBX files or some other format, let us know, we can try to quickly write a simple converter with the Translate Toolkit which should be quite easy if we already support the format in another converter. The way in which Pootle works with terminology is explained here: http://translate.sourceforge.net/wiki/pootle/terminology_matching (can somebody perhaps add a screenshot to this wiki page?) André already mentioned poterminology. This tool can help to extract frequently occurring terms (even multi-word terms) from your existing files to give you a great start when creating a new glossary, or to survey your existing translations: http://translate.sourceforge.net/wiki/toolkit/poterminology For people translating offline, our translation tool Virtaal offers very similar terminology help, although it is aimed even more at productivity. Here is a screenshot: http://translate.sourceforge.net/wiki/virtaal/screenshots#terminology_assistance I definitely have more ideas on how to improve this in future, so I hope the OOo translators will help with ideas and features to improve this even more. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/pseudolocalisation-podebug-3-interview-rail-aliev - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Entire Vietnamese translation cross review
Op Vr, 2009-02-13 om 02:16 +0900 skryf Nguyen Vu Hung: Vietnamese, and probably Japanese, Korean and Chinese as well have a big problem in word segmentation that prevents pootle from making a good terminology. At least in Vietnamese, the feature suggested terminology in pootle is quite useless. We have to use an external dictionary. I am sorry that it is not working well for you, and disappointed that this is the first time we hear about this. What is needed to improve it? What does segmentation have to do with it? Surely you are translating from English so the segmentation of the Vietnamese is not required, or is it? The only feedback I have gotten so far about the terminology feature is that it is extremely useful. So if your experience is different, please help us to understand how your expectations are different and how we can improve it. Perhaps we can help you tune the terminology list with knowledge of how Pootle makes the suggestions. For those interested, the terminology feature is explained here: http://translate.sourceforge.net/wiki/pootle/terminology_matching Pootle is developed as an open source project. We really need contributors to get involved and help us to improve it. Obviously I can't promise that somebody will fix everything in 10 minutes, but over the years volunteers to the project have tried to improve things in many areas for many languages - especially Vietnamese. Most recently a volunteer from the One Laptop Per Child project contributed some improvements to the quality checks for Spanish. We would welcome your contributions. Last year there was a Google Summer of Code project suggested to improve the handling of terminology. Perhaps it will be proposed again this year and you can help to work out how things should work and help to test it. Thank you for the feedback. Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/language-and-dialect-codes - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Entire Vietnamese translation cross review
Op Do, 2009-02-12 om 14:23 +0900 skryf Nguyen Vu Hung: Hello all, 12 of our Vietnamese team members will do a cross review against the entire Vietnamese translation which is available on pootle. The target is 3.1 so we have one month until the deadline. The review process is simple: Every members go through every po files, suggest a better translation if one think it may need and mark it as fuzzy. Then another will go through all the fuzzy messages and do really the fixes. The main purpose of this task is maintain the consistency in our translation. We also update vi.wiktionary.org - which is an open dictionary - to make sure every members referring the same source. This is a huge and heavy task. Please let us know if you have any ideas or suggestions. We also need pootle to be up and running because the review is proccessed with pootle Aijin Kim. :D This sounds like a big but worthwhile project. A few ideas that came to mind when I read your message: * You might want to review your terminology in Pootle before you start. That way all translators will see the suggested terminology while they review the existing translations. Remember that a person with enough rights can upload a newer file or newer files in the terminology project to add more terms that you might have standardised later. * If you can download the ZIP file with all PO files, you can perhaps have a look at poconflicts in the Translate Toolkit http://translate.sourceforge.net/wiki/toolkit/poconflicts Poconflicts reads all translations in multiple files and look for conflicting translations (same English but different translations). You can also reverse the testing to see if different English strings were translated with the same text (in other words, if some ambiguous translations were used). Just some ideas Good luck! Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/language-and-dialect-codes - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] pootle suggestions:
On Vr, 2008-08-01 at 12:22 +0900, Hung Nguyen Vu wrote: Hi all, I think it will be nice if we have the following features in pootle( sunvirtual.com ) 1. When translating online with pootle, after finishing a msgstr, we usually want to submit it and go to the next msgstr. So, by pressing the Tab key in the msgstr textbox, they Submit button should be focused. http://www.flickr.com/photos/vuhung/2721657230/sizes/o/ 2. Find and go to the first fuzzy in a file 3. Find and go to the first untranslated msgstr in a file 4. Free keyword search( regex search will be nice too ) under a folder. Happy translating. Hallo I'm moving this discussion to the tools mailing list - the preferred place for discussion localisation tools. Really, since these are just Pootle issues, it could even be better suited on the Pootle mailing list: https://lists.sourceforge.net/lists/listinfo/translate-pootle Luckily, it seems that all your wishes are already granted :-) 1) - You can use the accesskey 's' in your browser. The exact way to activate them are different between browsers. This way you don't need to use Tab at all. 2)+3) If you click on Show Editing Functions (Hiện các chức năng dịch) - Quick Translate (Dịch nhanh). This takes you to all the fuzzy and untranslated entries. If you really want to look at _only_ the fuzzy entries, click on Show Checks (Hiện kết quả kiểm tra) and search for either isfuzzy or untranslated. 4) The current searching functionality is being discussed on the Pootle mailing list. I suggest you join the conversation there. Currently we can't yet do regular expressions inside Pootle, but it is planned. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] [Fwd: [Translate-devel] Introducing CorpusCatcher 0.1]
Hallo everybody I think this announcement can be quite interesting for some people on the list, so I'm forwarding this here. Translate.org.za developed CorpusCatcher to help in building web corpora specifically for applications in spell checker building. The idea is that this is something that can easily be extended for specific applications. For any comments or to contribute improvements, please join the translate-devel mailing list here: https://lists.sourceforge.net/lists/listinfo/translate-devel Keep well Friedel Forwarded Message From: Walter Leibbrandt To: [EMAIL PROTECTED] Subject: [Translate-devel] Introducing CorpusCatcher 0.1 Date: Thu, 17 Jul 2008 16:24:49 +0200 The first version of CorpusCatcher was released recently. CorpusCatcher is a toolset for creating language corpora by crawling the Web. It was based on BootCaT (http://sslmit.unibo.it/~baroni/tools_and_resources.html), but evolved into a stand-alone project. Thanks to Kevin Scannell for his advice in this regard. Its main features are: - Querying Yahoo! for pages containing specific seed words. - Crawling the web for relevant pages. - Extracting the text from found pages. - Filtering results based on positive and/or negative word lists. The release is available for download at https://sourceforge.net/project/showfiles.php?group_id=91920package_id=284333 The live documentation is available on the wiki at http://translate.sourceforge.net/wiki/corpuscatcher/index Dependecies to use CorpusCatcher: - Python = 2.4 - mechanize 0.1.7b - pYsearch 3.0 See http://translate.sourceforge.net/wiki/corpuscatcher/readme#installation for installation details. Please report any bugs found at http://bugs.locamotion.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] [Fwd: [Translate-devel] Introducing CorpusCatcher 0.1]
On Do, 2008-07-17 at 16:48 +0200, F Wolff wrote: Hallo everybody I think this announcement can be quite interesting for some people on the list, so I'm forwarding this here. Translate.org.za developed CorpusCatcher to help in building web corpora specifically for applications in spell checker building. The idea is that this is something that can easily be extended for specific applications. My apologies - I meant to write to [EMAIL PROTECTED] *subscribed to too many lists*. Still, hopefully it was interesting to some of you. Sorry for the mistake. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] new version of gsicheck available for download
On Ma, 2008-06-30 at 15:15 +0200, Gregor Hartmann wrote: Hi Friedel, the sourcecode is available in the module transex3 gsicheck.cxx and tagtest.cxx unfortunately up to now only in the CWS newkeyid1 which has status approved by QA. Regards Gregor Thank you, Gregor. Unfortunately I haven't worked with the OOo sources in a few years, and have never worked with the CWSs. Can you perhaps aid me with a CVS URL or even a web based browser? I found this: http://lxr.go-oo.org/source/l10n/transex3/source/gsicheck.cxx but I assume that this is not the newkeyid1 CWS that you are referring to. Thank you again. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] new version of gsicheck available for download
On Di, 2008-06-17 at 14:45 +0200, Gregor Hartmann wrote: Hi, I have now uploaded archives for windows, linux, solaris sparc, solaris intel and MAC intel. All based on DEV300_m13 (plus CWS:newkeyid1). Version 1.9.0 features - Checking and removing (switch -f -ff ) of new KeyIDs - relaxing GID/LID length to 250 chars each You can download them at http://ooo.services.openoffice.org/gsicheck/ Hallo Gregor Is the source code also available? Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Creating linebreaks or non-breaking spaces in the installation wizard
On Wo, 2008-06-11 at 14:52 +0200, Eike Rathke wrote: Hi Clytie, On Monday, 2008-06-09 22:36:32 +0930, Clytie Siddall wrote: How should we insert a line-break, or a non-breaking space in the Installation Wizard? Did you try using U+00A0 NO-BREAK SPACE, respectively U+202F NARROW NO-BREAK SPACE for a maybe nicer visual result? Eike (assuming we are discussing translating through Pootle) We'll need to see if these things work. Last time I checked, at least some browsers did not actually allow submitting these through web forms, and would convert it to normal spaces instead. So it might be necessary to try it, and download the file to confirm that it worked. If the browsers still mess this up, doing this offline and uploading might be the only resort. I'd like to hear of any feedback on this, since I haven't checked this recently. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Op Maandag 2008-04-07 skryf André Schnabel: Hi, F Wolff schrieb: I don't know if I am stating the obvious, but just wanted to remind people that Pootle exposes many quality checks, which should stop gsierrors from entering the translations. The checks called 'variables', 'xmltags' and 'escapes' are the important ones. Not all of them might necessarily be problems, but should help you to avoid problems with gsicheck. This view is available with: Show editing functions - Show checks. thanks for the hint. I never tried this function, as the translation in the German UI of pootle is missleading. Thanks for the feedback, André. The translations of the Pootle interface is maintained at http://pootle.locamotion.org - perhaps you can contribute there, since you understand the context of that message better. Also feel free to help us add good comments to the translation to help translators understand it better. But anyway - i tried it now, but the errors found within pootle do not match the errors reported by gsicheck. So it seems nice that the checks are there, but it does not ensure, that gsichek will be passed. André I would really like to know these details, since it is definitely our intention to report at least all the errors that gsicheck reports. Please help us if there are any errors that we missed - perhaps they were added to gsicheck more recently, or there is a bug in our error detection around this. I believe the quality checks is a powerful way for translators to review possibly problematic strings. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Op Maandag 2008-04-07 skryf Aijin Kim: Hi Pootle translation lead, All the Pootle translation was submitted via IssueTracker. You can add yourself as cc to the issue to track the progress. However, several languages still have gsicheck errors to be fixed and the strings have format errors won't be imported to the database. So please **check the issue of your language and have the strings fixed ASAP**. You can find the link of the result file of gsicheck in the issue description. Here is the list of the issue # for each language: Arabic http://www.openoffice.org/issues/show_bug.cgi?id=87973 Bengali http://www.openoffice.org/issues/show_bug.cgi?id=87975 ... Thanks, Aijin I don't know if I am stating the obvious, but just wanted to remind people that Pootle exposes many quality checks, which should stop gsierrors from entering the translations. Check this URL for example: http://www.sunvirtuallab.com:32300/bn/openoffice_org/index.html?editing=1showchecks=1 I picked Bengali (bn) as the first language in the list with gsicheck errors mentioned in the bug. The checks called 'variables', 'xmltags' and 'escapes' are the important ones. Not all of them might necessarily be problems, but should help you to avoid problems with gsicheck. This view is available with: Show editing functions - Show checks. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Translatable contents extraction ?
Op Maandag 2008-02-25 skryf Aijin Kim: Hi Friedel, F Wolff 쓴 글: Op Maandag 2008-02-25 skryf Jean-Christophe Helary: Is it possible to only have the PO parts that need translation/ updating and not the whole set ? All the already translated parts are irrelevant to the translation itself (except when used as translation memories). Is there a simple tool that can extract the translation data and later merge the translated data ? pofilter and pomerge will help you do this. In fact, if you send your translations right back to Pootle, you can just upload the translated subsets when you upload (as long as you don't choose overwrite when you download. The default behaviour should be merge, which is what you want. I could see the 'merge' processing takes very long time and most of the resource of the server machine. It is serious if the uploaded file is large because the server is frozen until the processing is completed. Is it possible to merge off-line and upload the merged file with 'overwrite' option? Thanks, Aijin I identified a possible area of speed improvement in the upload merging code. If anybody is interested in a small programming project, I can point them to the code in question. It will need quite a bit of testing to which I can't quite devote enough time right now. One can use pomerge offline to do the merging. This will of course blindly overwrite existing translations in the template (old) translations files. Pootle does more by checking for conflicts, changing things conflicts into suggestions, etc. This is partly why it also takes longer. If people know what they do, of course there are some shortcuts that can be taken. But please, make sure that people understand that overwrite really means overwrite - the previous file is gone (unless we start using some underlying version control system for the PO files on the server). Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] How to upload ?
Op Vrydag 2008-03-07 skryf Aijin Kim: Hi Reiko, Let me confirm... To upload the files correctly, I have to create the zip file with the same name as I donload them ? You only can upload with file-based, i.e. one file at one time. zip of files can't be uploaded correctly. I've just uploaded Pootle user guide accordingly: http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Translating_off-line If you have several files to upload and they can overwrite the existing ones in Pootle, please send me the zip file. I could copy them directly on the server machine. You should upload a ZIP file in the same folder that you downloaded it from. This should work, and both merge and overwrite mode should be supported. Note that with ZIP files, overwrite mode is still done file per file. It shouldn't touch other files in the project that didn't occur in the ZIP file. If you are downloading the ZIP from http://www.sunvirtuallab.com:32300/ja/helpcontent2/swriter/ you will get the files with no directories in the ZIP file. Your ZIP file should then look the same if you upload it to the same place, or you could put everything in to a folder called 'swriter' and upload it from here http://www.sunvirtuallab.com:32300/ja/helpcontent2/ For large uploads, sending them to Aijin might be better for several reasons anyway, but I thought I'll just explain how it works. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: problem strings in OmegaT
Op Vrydag 2008-02-29 skryf Aijin Kim: Hi JC, Thanks a lot for your kind explanation. So you mean that you manually delete the msgid_comment part from each target string? If so, it should be better that source string doesn't include the msgid_comment line in source string to avoid additional work, right? Now, I'm thinking if we need to use msgctxt style. Ain has confirmed that poedit supports it. I'm not sure about OmegaT. If OmegaT also supports msgctxt, it'd be good to change the format of po files from next update. What do you think? Aijin I think msgctxt might be the best way to go, except if some team really wants to support some tool that doesn't yet support it well. From my understanding, the current versions of OmegaT will already work better with the msgctxt-type files, simply because the msgid will now always just contain the text for translation. This should enable the normal translation workflow of PO files in OmegaT, and should mean that the TM, etc. should work properly. (Of course, there might still be issues more generally about PO support, but at least it should be better than with the msgid comments). Unless anybody objects, I think going with msgctxt should be a good goal for just about everybody. I understand that Ain (not Aijin:-) has also already migrated that way. I think it is also worthwhile noting that the msgid comment was introduced by KDE before msgctxt existed, and now even the KDE project does not use it anymore. Although the Translate Toolkit and Pootle support it quite well, I think, most other tools that don't support it yet, probably never will, as these type of files will probably gradually disappear :-) Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Translatable contents extraction ?
Op Maandag 2008-02-25 skryf Jean-Christophe Helary: Is it possible to only have the PO parts that need translation/ updating and not the whole set ? All the already translated parts are irrelevant to the translation itself (except when used as translation memories). Is there a simple tool that can extract the translation data and later merge the translated data ? pofilter and pomerge will help you do this. In fact, if you send your translations right back to Pootle, you can just upload the translated subsets when you upload (as long as you don't choose overwrite when you download. The default behaviour should be merge, which is what you want. http://translate.sourceforge.net/wiki/toolkit/pofilter http://translate.sourceforge.net/wiki/toolkit/pomerge You can download a ZIP file of all the PO files in the project/directory where you want to do this. You are interested in pofilter --test=untranslated, but the page above will give more information on the command line use. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Ja project human relation
Op Dinsdag 2008-02-12 skryf Maho NAKATA: From: F Wolff [EMAIL PROTECTED] Subject: Re: [l10n-dev] Ja project human relation Date: Sat, 09 Feb 2008 12:41:26 +0200 Op Saterdag 2008-02-09 skryf Maho NAKATA: I tried to verify at home and at Lab (via VNC) but the server is down at the moment. http://www.sunvirtuallab.com:32300/register.html Thanks, -- Nakata Maho ([EMAIL PROTECTED]) Please retry now. I believe I fixed it. Hi F Wolff and Aijin thanks, now it has been fixed. I accessed http://www.sunvirtuallab.com:32300/home/ . However, I see `Quick link' and 'Change Options', (or something similar written in Japanese) but not privilege information. Could you please verify? thanks, -- Nakata Maho ([EMAIL PROTECTED]) Does the server not give instructions to select the languages and projects that you want to work on? Please click on Change Options and configure your information there. This will allow an administrator for your projects to configure your permissions there. Please confirm: There should be a message saying: 「オプション変更」をクリックし、言語とプロジェクトを選択してください Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Ja project human relation
Op Saterdag 2008-02-09 skryf Maho NAKATA: Hello Aijin, From: Aijin Kim [EMAIL PROTECTED] Subject: Re: [l10n-dev] Ja project human relation (was Re: OpenOffice.org 3.0 Translation) Date: Thu, 07 Feb 2008 20:51:26 +0800 Thanks a lot for your information. I could see the accounts of Reiko and you on the server. Could you please configure your language and project in 'My account' page so that I can set the admin privilege for you? I already gave Reiko the privilege. And I'll also set the right for Hirano-san after he register and set configuration. I tried to verify at home and at Lab (via VNC) but the server is down at the moment. http://www.sunvirtuallab.com:32300/register.html Thanks, -- Nakata Maho ([EMAIL PROTECTED]) Please retry now. I believe I fixed it. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] changing sdf fileformat
Op Donderdag 2008-02-07 skryf Gregor Hartmann: Hi, I am planing to change the sdf fileformat slightly. there is the 3. filed in every line which seems to be unused. I would like to use it to store information like the new KeyID and other things which will help to identify strings which will have to be retranslated after the sourcestring has changed, but that is still to come. Anyways tzhe change would be to have a formated string in the 3. field of the sdf file (right after the filename) It should look like this: fieldname:fieldcontent;filed2:data2;field3:data3 and so on, as required. Would that break anybodys processes? If noone objects I would like to go on next week. Comments as always welcome. Thanks for your attention Gregor From what it sounds like, the Translate Toolkit will be unaffected. Will this become a compulsory field in the format? In other words, can we count on having this unique identifier? It might be worthwhile to then rather start using this identifier in our conversion process than the one we currently construct. We'll obviously need the community to help us test this so that we can continue with self confidence after the change. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] TMs for 3.0
Op Donderdag 2008-02-07 skryf Rafaella Braconi: Dear All, please find the latest tmx (based on the 2.4 release) at : http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx24/ Great thanks to Frank and Ivo! Rafaella I had a _very_ quick look at some of them, and it seems that the Help file for zh-CN and the Vietnamese UI and help file has some encoding problems. All the others that I tried (mostly UI files) seemed ok. (I didn't try all of them.) Can you perhaps have a look at these files at least? Perhaps some validation against the others would be a good idea to make sure they are ok? I simply ran pocount over the files to see how big they are, and the parser complained because of incorrect UTF-8 data in the Vietnamese files. The zh-CN file just _looks_ wrong. For example: tu tuid=282032 tuv xml:lang=en-US segExample:/seg /tuv tuv xml:lang=zh-CN seg示0x00E4��：/seg /tuv /tu (the two characters before the colon is U+FFFD REPLACEMENT CHARACTER with notes: used to replace an incoming character whose value is unknown or unrepresentable in Unicode So I guess something went wrong somewhere. Furthermore, I think it is important to note that these TMX files does not follow the same unescaping rules of the new conversions done by Translate Toolkit 1.1. Of course, TMX files corresponding to the new unescaping rules can be generated from the set of PO files with po2tmx from the Translate Toolkit: http://translate.sourceforge.net/wiki/toolkit/po2tmx Hopefully there are solutions for all preferred working methods. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Ja project human relation (was Re: OpenOffice.org 3.0 Translation)
Op Donderdag 2008-02-07 skryf Kazunari Hirano: Hi Aijin, I have registerd and set the configuration. Thanks, khirano And I updated your access permissions. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OpenOffice.org 3.0 - Translation Schedule
Op Dinsdag 2008-02-05 skryf Reiko Saito: Hi Aijin, Thank you so much for your information and update to the user guide. I realized you added the section Localized Documents for me. -- I had added link JapaneseTranslation for JA community :-) Let me translate the additional part and ask you if I have any question. Regards, -Reiko Hallo Reiko, and thank you for your contribution to the documentation. I wanted to suggest a different name for the article though, since the name doesn't suggest that it has something to do with the Pootle user guide :-) Perhaps something like [[Pootle User Guide/ja]] or [[あてもなくユーザー ガイド]] (from Google machine translation :-) Or is there already a policy on the wiki for handling translations? The translations linked to from the front page does not seem to use a consistent way of naming the translated articles, but I guess the native name is good. If it is moved, I'll also link to it from the Pootle wiki site, for the benefit of all Japanese Pootle users. http://translate.sourceforge.net/wiki/pootle/index Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: Make wiki information more accessible
Op Woensdag 2008-02-06 skryf Vikram Vincent: Hello again, Is there any info on which files could be translated first in order to get some quick results? Thanks again. Regards There are a few tricks that you can try. When you have your tree of PO files, you can prioritise the modules/directories. Remember that you can use pocount to give you a good idea of the number of words and units in a set of files. http://translate.sourceforge.net/wiki/toolkit/pocount As a start, you probably want to skip the help files (helpcontent2) entirely at the start. Identify some programs in OpenOffice.org that you want to do first. You might (for example) prioritise Writer over the other programs. Things like the macro editor is probably the last priority. With some help from people in the know, you should be able to compile a list of modules/directories that are necessary for the translation of your chosen tool(s). You might also want to do the short strings first: http://translate.sourceforge.net/wiki/guide/short_strings_first You also want to make sure you gain as much as possible from translation memory to reuse the things that you have done in the project (or other previous projects). This can save some time, but also helps with consistency. Another time saver is terminology like Pootle does during translation. It makes it easier for inexperienced people to contribute without knowing all terminology before they start. I hope this is of some help. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle: generating SDF files for build
Op Saterdag 2008-02-02 skryf Clytie Siddall: On 02/02/2008, at 7:02 PM, Pavel Janík wrote: Hi, On 2.2.2008, at 9:23, Clytie Siddall wrote: Thanks, Pavel. So we need something to notify us of milestone release, so we can generate an updated SDF file for you to use. no. You have to keep your SDF file as up-to-date as possible. Or you can track http://planet.go-oo.org/ for e.g. EIS — OOH680_m6 ready for use. etc. BUT: I won't wait for you to update it. I simply get the latest GSI file you have at the provided URL. I do not care if it is or it is not updated at all because that would slow me and other teams considerably. I can understand that. I'm not asking you to do anything else: I'm trying to work out how we (my team) can adjust our workflow, using Pootle, to continue to provide the file regularly to you. Currently, I do all that manually. As soon as I have a reasonable number of new/changed strings, I convert from PO to SDF, gsicheck and upload the new file to that same URL. (In periods of change, I do that quite often.) Now our translation is on Pootle, I'm trying to work out a way to factor Pootle into our workflow, possibly by suggesting new features to the Pootle devs, so Pootle can be used to create SDF files manually/ automatically to the desired URL. I asked if there was any specific build schedule, because that would be a constant in the equation. But it looks like it's a variable. ;) from Clytie Ideally we could periodically (say daily) generate the SDF files for all languages and provide them for download somewhere. Then Pavel could either pull from here, or you could download the file, hold back or do extra testing if you want, and then publish on another URL for Pavel. We are considering some architectural changes on the Pootle server that would make downloads possible (at least in principle). My guess is that Aijin won't be able to attend to that soon, but I think this is doable. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle response time
Op Saterdag 2008-02-02 skryf Olivier Hallot: Hi, Am I the only one who gets 15 seconds average time for pootle response? With such response times it becomes very hard to keep a transation pace comfortable directly on the server. Just doing a simple math, I have 1570 string to translate in HC2/scal/01.po, at this pace it will take me no less than 7 hours waiting for Pootle... Sad... This is obviously not the way it should be, and Aijin and I will look into this. I have a few ideas that Aijin will hopefully be able to investigate soon. So I tried to download the file to work on Kbabel, but KBabel shows weird things with msgids ... for example: _: 04060103.xhp#par_id3148558.407.help.text\n emphMaturity/emph is the date on which the security matures (expires). The HC/scalc/01.po file I downloaded has this in it: #: 04060103.xhp#par_id3148558.407.help.text msgid _: 04060103.xhp#par_id3148558.407.help.text\n emphMaturity/emph is the date on which the security matures (expires). msgstr Pootle does not get bothered with the spurious string _: 04060103.xhp#par_id3148558.407.help.text\n but Kbabel does. Am I missing something on Kbabel and/or is there another fine tunning for Pootle needed? Thank you Olivier The text marked with _: \n is the old KDE style of marking context to disambiguate messages that would otherwise be identical. The PO files for OpenOffice.org translation can be formed with different options for handling duplicates, KDE style comments being one of them. More information is available here: http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] search function in Pootle
Op Vrydag 2008-02-01 skryf Olivier Hallot: Thank you Friedel for you patience. Yes I'm still exploring the tool so I went finally to the verifications. I have some questions more since then: - some verifications are affected by the location of the keyboard shortcut symbol (~). Is there a way to make verifications with this symbol ignored or hidden? Yes. The project needs to be classified as an OpenOffice.org project, then many of the tests are adapted accordingly. Aijin, can you please update the project configuration? - A way to skin or color-configure some special conditions: approximate translations, begin or end whitespace. Those are in pale gray, hard to find. You can force your browser to use different styling for certain sites, but perhaps this is not the most attractive option to you. We will be finalising the release of Pootle 1.1.0 soon, and if you want to give more specific ideas of what you have in mind and help us test them, we might be able to incorporate that to the release. At the moment these colours are not configurable inside Pootle, if that is what you wanted to know. The choice of colour is simply to ensure that it doesn't distract too much during normal work, but that there is way to see the suspicious whitespace. That is it (for the time being, I plan to attend next tuesday irc meeting...) Thank you. Olivier Thank you for the feedback. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] L10n Meeting on IRC - 31-01-2008
Op Woensdag 2008-01-30 skryf Rafaella Braconi: This is a friendly l10n meeting reminder :-) Date/Time: January 31st at 9:00 am UTC (10:00 am Paris/Berlin time) - Channel: IRC network FreeNode, #ooonlc. Agenda: ... In the meeting I made a mistake. The IRC channel for Pootle is of course #pootle on irc.freenode.net. (#zaf that I mentioned is where we discuss South African localisation issues - of course people are welcome there as well :-) I'm often in #pootle, as well as other people using our tools. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] search function in Pootle
Op Donderdag 2008-01-31 skryf Olivier Hallot: Hi Rafaella, That is exactly what it does, although I thought initially that the search function should return all ocurrences in one page. Actually I know I have one Gallery string left untranslated in the UI, but the question was where in the file tree?. I'm still exploring this interesting tool. Regards, Olivier Hallo Olivier Since the project is so big, it can take some effort to find this, of course. Plain searching should eventually get you there (unless this perhaps is a string that isn't available for translation!) If you have a good idea in which component of OOo the message could be, you might want to first navigate into that directory and start the search from there. This will limit the search to the files in this directory. Another thing to consider, is to make use of the checks (Verificações) to find unchanged strings (you might also want to review other checks for possible areas of improvement): http://www.sunvirtuallab.com:32300/pt_BR/openoffice_org/index.html?editing=1showchecks=1 Unchanged and untranslated strings could possibly be where you need to look, although everything seems 100% translated at the moment for pt_BR. Even for the checks, you can choose to only review the unchanged checks for a specific directory (or file) in the tree of files. If you know where to look, this could perhaps also cut down on searching through results in the other areas of OOo. I hope this helps. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] search function in Pootle
Op Woensdag 2008-01-30 skryf Olivier Hallot: Hi I want to locate a specific string (say Gallery) in the po files tree, but I only get the first occurence and it seems that there is no other way to find the others. Any hint? Thanks. If you skip or submit that occurrence, it takes you to the next one in the project / directory / file that you started the search from. You can of course also download and search offline. The Pootle interface just makes it easy to search across a whole project / directory. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] put files in goals
Op Woensdag 2008-01-30 skryf Olivier Hallot: Hi I went thru the pootle user guide for admin, and I set a test goal. Now I am supposed to place po files into the test goal by using a dropdown list which I can't find anywhere in the page... Am I missing something? Thanks in advance. Hallo Olivier Just to be sure, are you following the documentation here: http://wiki.services.openoffice.org/wiki/Pootle_User_Guide ? I would just like to check that the instructions you are following is the same as what I'm comparing against. When you start out, all directories are Not in a goal - the name of the default goal in your project. If you click on it, (not in a goal) you can see the directories (and files) that are not yet moved to a specific goal by selecting the appropriate goal from the list. Initially all directories (and files) will be in the goal with the name Not in a goal. I hope this helps. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle : name of goals and .po files
Op Dinsdag 2008-01-29 skryf sophie: Hi all, My first contact with Pootle ;) I've understand that I have to define goals, but what name could I give. Can I name them 3.0 or is it better like March or April ? What importance have this name ? The name doesn't really matter that much. You can choose something that makes sense to you. Most of our work will take place of line or on other tools than Pootle, so I've download the zip file for French, but the .po files seems to be corrupted, for example : #: main.xhp#tit.help.text msgid _: main.xhp#tit.help.text\n Welcome to the $[officename] Impress Help msgstr Bienvenue dans l'aide de $[officename] Impress In this case the first part _: main.xhp#tit.help.text\n is a context marker which should not be translated. Perhaps in future we can use the msgctxt markers in the PO files which makes this distinction clearer. Tools are becoming better at supporting these. or others have no .xhp file references like that and are commented : #~ msgid #~ link href=\text/simpress/02/1323.xhp\ name=\Line Contour Only #~ \Line Contour Only/link #~ msgstr #~ link href=\text/simpress/02/1323.xhp\ name=\Afficher uniquement #~ les lignes fines\Afficher uniquement les lignes fines/link #~ msgid #~ link href=\text/simpress/02/1321.xhp\ name=\Contour Mode #~ \Contour Mode/link #~ msgstr #~ link href=\text/simpress/02/1321.xhp\ name=\Sans remplissage #~ \Sans remplissage/link Is it an issue or not ? Thanks in advance for your help Kind regards Sophie These are usually called obsolete entries. It means they were translatable before, but were removed from the file. They are kept in case they are restored, or in case they can be useful for fuzzy matching on the next update. You can just ignore them. Any PO editor should ignore it and only display the others. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Preparing 3.0 in Pootle
Op Vrydag 2008-01-25 skryf Aijin Kim: Hi all, I'm starting to prepare the contents for 3.0 in Pootle. The languages which are scheduled as end of Jan. will be uploaded first. Works during the preparation period are possibly missed, so please don't update the contents in Pootle during the period. Once the upload is finished, I'll get back to you soon. Thanks, Aijin Hallo Aijin I just wanted to ask - are you using the new toolkit (1.1) for the file conversion? Are you happy with the conversion process documented here? http://translate.sourceforge.net/wiki/toolkit/important_changes This is important for languages that already have translations of helpcontent2. Otherwise they will have lots of fuzzy strings with the new files. Just thought I'll make sure you know! By the way, a small packaging bug was discovered in Translate Toolkit 1.1.0 which is fixed and the new version will be necessary for Pootle 1.1.0. This doesn't affect oo2po and po2oo, but just thought I'll let you know. Are you on the translate-devel mailing list? There all things related to the Translate Toolkit are discussed. I built Pootle 1.1.0rc1, and although I haven't announced it yet, a few people have started to test it. Hopefully it is ready quite soon. What is your timeline for deploying the new version of Pootle on sunvirtuallabs? It has a slightly new look, which I think people will like. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle roadmap
Op Donderdag 2008-01-10 skryf Clytie Siddall: I forgot to mention, please also enable the terminology function for Vietnamese, using the standard Vietnamese terminology file as supplied with Pootle. Thankyou :) Aijin, for you benefit, she refers to this file: http://pootle.wordforge.org/vi/terminology/gnome/vi.po Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle roadmap
Op Donderdag 2008-01-10 skryf Clytie Siddall: Hi Aijin :) On 10/01/2008, at 7:35 PM, Aijin Kim wrote: Aijin, can I transfer the access rights and login info from the main Pootle server to OpenOffice.org Pootle? I'd like to avoid having to tell everyone they have to create a new login, then me having to reassign all the access rights, if possible. If you provide me the proper information, I'm able to configure them manually on the server. Hmm, I was looking for a quicker transfer way. You doing them manually would probably take as much time as me doing them. I don't think we have a cross-Pootle login yet, so I suppose all the users of the main Pootle will have to register separately at the OpenOffice.org Pootle. Aijin and I can coordinate this transfer. At least the permissions should port easily, although it might be necessary to recreate the logins. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle roadmap
Op Vrydag 2008-01-11 skryf Clytie Siddall: On 11/01/2008, at 12:20 AM, F Wolff wrote: Op Donderdag 2008-01-10 skryf Clytie Siddall: I forgot to mention, please also enable the terminology function for Vietnamese, using the standard Vietnamese terminology file as supplied with Pootle. Thankyou :) Aijin, for your benefit, she refers to this file: http://pootle.wordforge.org/vi/terminology/gnome/vi.po Friedel, doesn't the Pootle distribution contain the terminology files we translated at Wordforge? :o from Clytie Not yet. The GNOME terminology on our server is not really up to date for many languages, and contains some strange terms. We've worked with the guys from Arabeyes to come up with a useful POT file for this exact purpose, but we haven't advertised this enough yet to get a lot of collaboration. If people are interested in this cross-project terminology project for software l10n, perhaps we should give it some more attention now. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Formats, tools, and workflow
Op Donderdag 2008-01-03 skryf Clytie Siddall: Friedel, thanks for your detailed reply. For now, I want to focus on retaining metadata and a viable update process, so please excuse my not replying to other parts of your message. Of course. As background for uninitiated readers, most of the commands I mention here are programs in the translate toolkit, and not all of these functionalities are provided by the Pootle front-end. They are of course freely available as part of the translate toolkit: http://translate.sourceforge.net/wiki/toolkit/index On 02/01/2008, at 9:39 PM, F Wolff wrote: ... ... We also have a converter that goes directly from SDF to XLIFF. It shipped with the current version of the toolkit, although a packaging bug might hide it for some users. The packaging bug will be fixed in the next versions of the toolkit. How much metadata storable in XLIFF can the filter transfer to SDF? Very little, and I don't think this is where our effort should be spent. Although I consider the SDF file something I only deliver and never touch, I understand the issues you mention below. gsicheck errors: Alessandro, if there are errors reported by gsicheck from the SDF files created by the translate toolkit and that are not reported by pofilter (in Pootle they are listed as checks), I would really like to know. None has been reported on our list or bugzilla as far as I can remember. I agree that we should be generating good SDF files after our translation process. The problem probably is that we use one or the other. I check my PO files with msgfmt when editing offline, then once I convert to SDF, I run gischeck (now I actually have gsicheck for OSX). msgfmt is nice, but very limited especially if you are checking OOo translations. It doesn't know about OOo variables or XML tags and properties. As far as I know there is a pofilter test for each of the things that gsicheck checks for (and several others, of course). Once our files are back on Pootle, I can give you further feedback on pofilter. As you know, we still need to work on language-specific or more inclusive checks (e.g. « guillemets » being used instead of quotation marks, spacing being acceptable before question and exclamation marks with some languages) to reduce the number of false positives which, for my language at least, is discouragingly high. This has been addressed with infrastructure to customise tests per language. At least the guillemets should not pose any problems, and we can discuss the other requirements. I think I solved the spacing before !? for French and there are now some customisations for several languages (including Vietnamese). Clytie wrote: We would need an upgrade process for strings that somehow retains that metadata on our side. I don't know how we could do that. What Javier wrote here is right: we maintain our translations in localisation formats. Then all of the information (not only comments, but also things like state, last translator, etc.) Converting to SDF can therefore be seen as being similar to compiling to binary format. We store our localisation formats in a version control system, and that is considered to be the stored translations. This way we also don't need to retranslate with a TM at the start of version update such as the method is with OmegaT (according to my understanding). The files are just updated with pot2po (which can optionally use a TMX file for fuzzy matching while upgrading the files) If I download the latest GSI file (which is more economical than grabbing the whole POT tree), then convert it (oo2po) to POT, then update (pomigrate) my previous PO files to the new POTs, my PO metadata would remain. (I hope.) Yes However, I find it easier to make quick changes in the GSI file, because it is only one file, which is more viable for global search- and-replace and checking and updating specific strings. I understand that. If you don't like the workflow offered by pogrep and pomerge, I understand that editing the SDF file directly is attractive. We'll hopefully work on search and replace in Pootle soon. for reference: http://translate.sourceforge.net/wiki/toolkit/pogrep http://translate.sourceforge.net/wiki/toolkit/pomerge Of course, searching with pogrep has other advantages, like handling accelerators and unicode normalisation. (It probably wouldn't be more difficult technically to do that over the entire tree, but for some reason it just seems more complex. And I don't have much concentration left to work with.) So if I update the GSI file, before merging with the new POTs, I have to convert my GSI file back into PO, because it is now my current translation. And right there, I lose all my metadata. My PO directory won't have any, because the GSI file doesn't. (Unless there is some way we can merge
Re: [l10n-dev] Is Pootle down?
Op Dinsdag 2007-11-13 skryf Aijin Kim: Hi Jordi, Aijin, There are a few translators that cannot use our Pootle server because it is at port 32300. Many people at their work places and universities have firewalls that block the access for this kind of ports. My suggestion is to consider changing the port to 80 as any regular web service if there are not technical reasons for not doing it. I understand that the translators have a problem with the port 32300. Currently, the Pootle server is in sunvirtuallab and unfortunately, the port 80 is already used for TCM. I'm afraid that it's not easy to switch port 32300 to 80. I think about an workaround. How about if they download the files from Pootle where they can access Pootle and work off-line? Once translation is completed, they can upload the contents. What do you think? Thanks, Aijin Pootle can also run on a part of the URL. Is it possible to allocate part of the URL on port 80 to Pootle? For example sunvirtuallab.com/pootle/. You will probably need to configure the web server to delegate the requests, but if the infrastructure allows, this could perhaps work. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] added script - KeyID builds buildable by the comunity as well as by sun
Op Donderdag 2007-09-27 skryf Rail Aliev: On Thursday 27 September 2007 17:15:22 Ain Vagula wrote: Makes it sense to generate ID-s for Helpcontent? Mostly helpcontent is in logical order and there are not so much problems locating strings. Adding a CLI switch (--without-help) won't be hard IMO. ;) As far as I know some people (at least on the sun server) split the helpcontent into a separate project, so it is easy to just apply it to the rest, I think. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Extensions Website translation : Need help
Op Donderdag 2007-09-27 skryf Laurent Godard: HI all As you may know, the OpenOffice.org Extensions project has built a website gathering all the worldwide contributions. http://extensions.services.openoffice.org/ Coupled to the OOo Extensions Manager, it will be a usefull tool to enrich our favourite office suite The website has been designed using Drupal framework and no attention has been paid to internationalization until now It is now time to solve this issue. So we need help from someone knowing Drupal and wanting to help to setup the site so that it can contain international content There will be 2 parts to be translated - The easiest is the static part - A more challenging will be to allow translation (and at term contributions) of the extensions descriptions Actually, it might be the opposite way round: Drupal can export content to XLIFF files which you can host on a Pootle server to allow online or offline translation. This can be hosted on the same server used for GUI and Help localisation, so the whole community have one place for localisation management. http://drupal.org/project/xliff I have not used it yet, so I can't help with the details, but it exists. I hope it helps Friedel I started some notes here http://wiki.services.openoffice.org/wiki/Extensions/website/Translating All will be discussed on the extensions website mailing list - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: [native-lang] L10n Meeting on IRC
Op Woensdag 2007-09-26 skryf Kazunari Hirano: Hi, CEST means Central European Summer Time, Paris time, right? http://www.timeanddate.com/worldclock/meetingtime.html?day=27month=9year=2007p1=195p2=248p3=-1p4=-1 It's 27 September 2007, 09:00:00 UTC and 18:00 JST for me in Japan. I will try to attend it 11:00-11:30 CEST. See you! Thanks, khirano Thank you Khirano! It always wastes excessive time to find out what some timezone acronym means, figure out whether or not daylight savings is used, whether it is in effect at the given time, etc. With the UTC you give I can work it out in less than a second :-) F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: Question about POT files oo2po
Op Donderdag 02-08-2007 om 22:41 uur [tijdzone +0200], schreef Tim Morley: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2 Aug 2007, at 05:59, Friedel Wolff wrote: Interesting scripts :-) Interesting in the sense of Ooh, it's obvious he hasn't done much programming in a good while...? :o) I honestly didn't take a proper look. It is interesting for me that you solved it. Anybody doing anything with awk impresses me, simply because I don't know it well :-) No offence given, I hope. I'm just curious: was pot2po of the translate toolkit not able to migrate these successfully? I would have thought that it can, but would like to know if there was a shortcoming. Um... don't know. There may well be a certain amount of re-inventing of the wheel here on my part, as I'm not very familiar with much of the translate toolkit. I should probably get to know it better and save myself some work. :o) Tim The translate toolkit is already quite well known for helping in the localisation of OOo and other projects, so if we can make sure that it works well for this issue, then hopefully more people benefit from the work. The other issue is that if it already solves it, it might mean that more people can help maintain the solution in the toolkit :-) But please, feel free to use whatever works for you :-) Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: Question about POT files oo2po
Op Dinsdag 31-07-2007 om 00:24 skryf Tim Morley: On 30 Jul 2007, at 22:42, Damien Donlon wrote: So I guess my question is : How do I adjust the SDF files that I have taken from the database so that they generate PO files which include the comment in the msgid? If I can do this then I can get leverage. On a related note, if you've merged old translations with a new set of .pot files which have had KDE-style duplicate strings added, you've probably got a set of .po files that contain lots of duplicate entries without translations, but with an identical string marked as obsolete at the bottom of the same file, i.e. lots of files containing things like this: msgid _: animals.DIALOG.pushbutton101text My dog msgstr msgid _: animals.DIALOG.pushbutton102text My dog msgstr #~ msgid My dog #~ msgstr Mon chien If you've got lots of these, then I've got a couple of scripts that'll help. Get yourself a copy of the following: http://svn.ikso.net/openoffice/trunk/cxie-retrovi-tradukojn http://svn.ikso.net/openoffice/trunk/retrovi_tradukojn.awk (Don't be put off by the Esperanto names. :o) The files contain explanatory comments in English too.) Hi Tim Interesting scripts :-) I'm just curious: was pot2po of the translate toolkit not able to migrate these successfully? I would have thought that it can, but would like to know if there was a shortcoming. As far as I know msgmerge won't necessarily merge these successfully, and msgmerge might be used if you were using pomigrate2. There is an option --pot2po for pomigrate2 that will use pot2po instead of msgmerge for updating the files. Either way, a solution exists :-) Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Question about POT files oo2po
Op Vrydag 27-07-2007 om 10:57 uur [tijdzone +0100], schreef Damien Donlon: Hi, I have a question about how oo2po extracts PO and POT files. Pavel's POT files contain messages of the format : ... Where the comment becomes part of the msgid string. Presumably this is required for some reason to do with backconverting to SDF and putting the translation back to the appropriate place in the SDF. Can anyone confirm this? My problem is : If I do an export of an SDF from our database and do oo2po on it using the command : oo2po -i something.sdf -o ./po-files -l lang I get : #: abspilot.src#RID_PAGE_FIELDMAPPING.PB_INVOKE_FIELDS_DIALOG.pushbutton.text #: abspilot.src#RID_PAGE_FIELDMAPPING.tabpage.text #: abspilot.src#RID_DLG_ADDRESSBOOKSOURCEPILOT.STR_MANUAL_FIELD_MAPPING.string.text msgid Field Assignment msgstr Assegnazione campo The comment is NOT part of the msgid. This means that when I do a pomigrate2 to merge the database generated PO files to the PO files which use the POTs as a template, the msgid's are not matched and the database contents are not leveraged. So I guess my question is : How do I adjust the SDF files that I have taken from the database so that they generate PO files which include the comment in the msgid? If I can do this then I can get leverage. Thanks in advance! Regards, Damien Hi Damien Have a look at the options for oo2po http://translate.sourceforge.net/wiki/toolkit/oo2po and specifically the option --duplicatestyle http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle These comments are used to disambiguate messages, and there are a few different choices available. I think the second link I gave explains the different choices quite well, but shout if there is anything unclear. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Imagine :)
Op Donderdag 12-07-2007 om 10:36 uur [tijdzone +0200], schreef Rafaella Braconi: Hi Jean-Christophe, thank you once again for sharing your thoughts and experience. I am trying to reproduce and clarify with other engineers what you say here below. However, from what I understand here, the issue you see is not necessarily Pootle but the format Pootle delivers which is .po. As already said, Pootle will be able to deliver in near future the content in xliff format. Would you still see a probelm with this? Regards, Rafaella Pootle has XLIFF functionality since version 1.0. Hopefully we can upgrade the version on the server soon. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: Problem with po2oo script?
Op Sondag 08-07-2007 om 00:25 uur [tijdzone +0100], schreef Tim Morley: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks to Friedel for the earlier reply. Having checked the things suggested, experimented a bit more and read some more docs, I think the problem is that my en_US.sdf file isn't from the same version as my collection of .po files. Trouble is, I have no idea now which version my .po files are from. :o( So, next question for the team: what's the procedure for merging our existing translations into a new set of .po files, say the ones for 2.2.1-RC3? I assume it's going to be based around pomerge, but if there's a step by step guide posted somewhere, I'd be pleased to receive a link to it. Cheers all. Tim Hi Tim Perhaps the following two pages can be of help. Especially the second one might be relevant to your situation. http://translate.sourceforge.net/wiki/toolkit/using_oo2po http://translate.sourceforge.net/wiki/toolkit/migrating_translations F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Error with PO files form Pootle
Op Dinsdag 03-07-2007 om 17:20 uur [tijdzone +0200], schreef Alessandro Cattelan: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, it seems that the PO files in the Pootle server used for the OOo 2.3 L10N are not properly formed. The comments of some strings have been included in the msgid field. Can somebody explain how to handle these strings? Here's an example taken from the UUI folder of the OOo GUI: #: masterpasscrtdlg.src#DLG_UUI_MASTERPASSWORD_CRT.modaldialog.text msgid _: masterpasscrtdlg.src#DLG_UUI_MASTERPASSWORD_CRT.modaldialog.text\n Enter Master Password msgstr #: masterpassworddlg.src#DLG_UUI_MASTERPASSWORD.FT_MASTERPASSWORD.fixedtext.text msgid _: masterpassworddlg.src#DLG_UUI_MASTERPASSWORD.FT_MASTERPASSWORD.fixedtext. text\n Master password msgstr Thanks, Ale. Hi Alessandro The comments are used to disambiguate messages. There are different options for handling disambiguation in oo2po and whoever prepared these files chose msgid comments. See the --duplicates parameter of oo2po. It is documented here: http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Error with PO files form Pootle
Op Woensdag 04-07-2007 om 11:52 uur [tijdzone +0200], schreef Alessandro Cattelan: ... I translated a couple of files offline using OmegaT, writing only the text in the msgstr field as in example 2 above. When I upload that file to Pootle, the server does not consider the strings with that sort of inline comment translated so I have to go through the translation again with Pootle. Am I doing something wrong? I must say that I don't like translating with Pootle - it's a nice tool to manage the translation workflow but it's not as good when it comes to translating. What I'm doing is translate and review the files offline (with OmegaT or with a text editor) and then upload them to Pootle. I'd like to know whether there is a way to automatically mark as translated and reviewed strings edited offline. Ale. I just want to make sure I understand well what you are describing. Were the relevant messages already translated, or did you newly translate these messages? If a message is already translated and a file with translations is uploaded, changes to already translated messages are accepted as suggestions that have to be reviewed. Is this what you are referring to? You are free to translate offline and upload translations. If you don't want the behaviour for merging the translations, you can choose to entirely overwrite files on upload. The administrator for your language (you I think?) might need to give you the overwrite right since this is a bit more dangerous action. Does this help? F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Error with PO files form Pootle
Op Woensdag 04-07-2007 om 13:12 uur [tijdzone +0200], schreef Alessandro Cattelan: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 F Wolff ha scritto: Op Woensdag 04-07-2007 om 11:52 uur [tijdzone +0200], schreef Alessandro Cattelan: ... I translated a couple of files offline using OmegaT, writing only the text in the msgstr field as in example 2 above. When I upload that file to Pootle, the server does not consider the strings with that sort of inline comment translated so I have to go through the translation again with Pootle. Am I doing something wrong? I must say that I don't like translating with Pootle - it's a nice tool to manage the translation workflow but it's not as good when it comes to translating. What I'm doing is translate and review the files offline (with OmegaT or with a text editor) and then upload them to Pootle. I'd like to know whether there is a way to automatically mark as translated and reviewed strings edited offline. Ale. I just want to make sure I understand well what you are describing. Were the relevant messages already translated, or did you newly translate these messages? If a message is already translated and a file with translations is uploaded, changes to already translated messages are accepted as suggestions that have to be reviewed. Is this what you are referring to? Not exactly. Let's say that the file I had to translate had 100 strings. 80 were already translated. 10 contained the inline comments of my previous message and the remaining 10 strings were just plain text, with no tags and no comments (something like msgid Open). I translated the whole file offline and then uploaded it to Pootle using the overwrite option. Before I started translating it, Pootle reported that the file had 20 strings to be translated. After uploading it, Pootle reported that I still had to translate 10 strings. I used the Quick Translate command from Pootle to see which strings were to be translated and it came out that they were the ones with the inline comments, such as: #:masterpassworddlg.src#DLG_UUI_MASTERPASSWORD.FT_MASTERPASSWORD.fixedtext.text msgid _: masterpassworddlg.src#DLG_UUI_MASTERPASSWORD.FT_MASTERPASSWORD.fixedtext. text\n Master password msgstr Password principale Can you provide the URL to the file, please? I'll try to have a look at it. You are free to translate offline and upload translations. If you don't want the behaviour for merging the translations, you can choose to entirely overwrite files on upload. The administrator for your language (you I think?) might need to give you the overwrite right since this is a bit more dangerous action. If I merge a translation only the newly translated strings are updated, right? Thanks for your help. I'm off to work now. I'll be online again tonight. Regards, Ale. The newly translated strings are updated and the others are stored as suggestions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Problem with po2oo script?
On So, 2007-07-01 at 15:12 +0100, Tim Morley wrote: Hi all. Our team has a 100% translated UI -- at least, we would have, if everything from our .po files was making it into the GSI file. :o( I'm writing to ask for help in diagnosing and solving the problem. Our .po files are here, the GSI file is here, and to get the GSI from the .po files, I used: ~$ po2oo -l eo -t en-US.sdf -i . -o GSI_eo.sdf as described here. In the GSI file, for about 40 lines from line 15835 onwards, the translations are missing. The first few are ~Help, ~File, Alignmen~t, ~Shapes, but in the file officecfg/registry/data/org/openoffice/Office/UI.po we can find: #: GenericCommands.xcu#..GenericCommands.Popups..uno_HelpMenu.Label.value.text #: StartModuleCommands.xcu#..StartModuleCommands.UserInterface.Popups..uno_HelpMenu.Label.value.text msgid ~Help msgstr Helpo #: GenericCommands.xcu#..GenericCommands.Popups..uno_PickList.Label.value.text #: StartModuleCommands.xcu#..StartModuleCommands.UserInterface.Popups..uno_PickList.Label.value.text msgid ~File msgstr Dosiero #: GenericCommands.xcu#..GenericCommands.Popups..uno_ObjectAlign.Label.value.text msgid Alignmen~t msgstr Gxisrandigo #: GenericCommands.xcu#..GenericCommands.Popups..uno_PolyFormen.Label.value.text msgid ~Shapes msgstr Formoj Can anybody suggest what we might be doing wrong? Is it a bug in the po2oo script? Has anyone else discovered and solved this problem already? Thanks very much in advance for your help. Cheers. Tim Esperanto team leader PS Just in case my embedded links above don't make it through, here they are again: .po files: http://svn.ikso.net/openoffice/trunk/ GSI file: http://homepage.ntlworld.com/tim.morley2/OOoEo/GSI_eo.sdf.bz2 Hi Tim You didn't specify which version of the toolkit you are using. Is it the latest version (1.0.1)? My guess is that you are using a version that excludes the strings that might be problematic. In your examples, I see the translations don't have accelerators, which might explain why they were excluded. Did po2oo give any warning messages while running? You might want to experiment with the --filteraction command. See the full documentation for the latest version of po2oo here: http://translate.sourceforge.net/wiki/toolkit/oo2po Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OmegaT and PO files
On Di, 2007-06-19 at 07:56 +0200, Alessandro Cattelan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The first segment that OmegaT opens for every PO file is the following: segment 0001 Project-Id-Version: PACKAGE VERSION\n Report-Msgid-Bugs-To: http://qa.openoffice.org/issues/enter_bug.cgi?subcomponent=uicomment=short_desc=Localization%20issue%20in%20file%3A%20component=l10nform_name=enter_issue\n; POT-Creation-Date: 2007-06-13 21:53+0200\n PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n Last-Translator: FULL NAME [EMAIL PROTECTED]\n Language-Team: LANGUAGE [EMAIL PROTECTED]\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n X-Generator: Translate Toolkit 0.10.1\n X-Accelerator-Marker: ~\n end segment I think nothing needs to be changed here, right? It seems to me those are all optional information for project management. The only thing I'm not sure about is the Plural-Forms field: does that need to be edited anyhow? Thanks, Ale. The Plural-Forms header entry is part of the gettext library (the library that designed the PO format). Nothing in OpenOffice.org will need or use it, so it can be safely ignored. If you use any of the gettext tools on the PO files, they might complain about that, but I would simply ignore it until then. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] escaping
On Di, 2007-06-19 at 00:44 +0900, Jean-Christophe Helary wrote: On 18 juin 07, at 23:28, F Wolff wrote: ... So this is the PO file, am I correct? Does OmegaT handle the escapes in the PO file? Does the actual PO file (opened in a normal text editor) have \\\ or something else? This would of course mean \ since both the backslash and the double quote must be escaped in PO files (along with newlines and tabs). In TMX they are of course put in unescaped as \ since the escaping is not necessary for TMX. Would this explain what you are seeing? OmegaT handles PO files pretty much as text files and thus does not care about \, for it, the \ is just another character. Hence, there is nothing that is generated by OmegaT in the screenshot I showed. The files are displayed as they are. Unfortunately a PO file isn't just a text file. It is a file format that presents data in a specific way. To escape the slash (\) and the quotes () is part of the format that we try to conform to. To make sure I am not wrong, let me reproduce the process here with an example string: 1) the .sdf I have contains: helpcontent2source\text\sbasic\shared\01\0613.xhp 0 help par_id3149124 20 0 en-US To create a new macro, select the Standard module in the \emph\Macro from\/emph\ list, and then click \emph\New\/emph\. 2007-04-11 15:55:00.0 helpcontent2source\text\sbasic\shared\01\0613.xhp 0 help par_id3149124 20 0 fr Pour créer une nouvelle macro, sélectionnez le module Standard dans la liste (lines 3 and 4 of HC2_93824_89_2007-06-05_33.sdf) When I use oo2po (oo2po --language=fr --nonrecursiveinput HC2_93824_89_2007-06-05_33.sdf HC.po), I get the following strings: #: 0613.xhp#par_id3149124.20.help.text msgid To create a new macro, select the \Standard\ module in the \ \emph\\Macro from\\/emph\\ list, and then click \\emph\\New\\/emph\\. msgstr Pour créer une nouvelle macro, sélectionnez le module \Standard\ dans la liste \\emph\\Macro de\\/emph\\ et cliquez sur \\emph\ \Nouveau\\/emph\\. Vous pouvez également créer un nouveau module. Pour ce faire, s électionnez-le dans la liste \\emph\\Macro de\\/emph\\ et cliquez sur \\emph\\Nouveau\\/emph\\. You can see that a number of characters have been escaped. Now, when I create a TMX from this file (even though I know this file is a pseudo translation) ($ po2tmx --language=fr HC.po HC.tmx), I get: tuv xml:lang=en segTo create a new macro, select the quot;Standardquot; module in the \lt;emph\gt;Macro from\lt;/emph\gt; list, and then click \lt;emph\gt;New\lt;/emph\gt;. /seg /tuv tuv xml:lang=fr segPour créer une nouvelle macro, sélectionnez le module quot;Standardquot; dans la liste \lt;emph\gt;Macro de\lt;/emph \gt; et cliquez sur \lt;emph\gt;Nouveau\lt;/emph\gt;. Vous pouvez également créer un nouveau module. Pour ce faire, sélectionnez-le dans la liste \lt;emph\gt;Macro de\lt;/emph\gt; et cliquez sur \lt;emph\gt;Nouveau\lt;/emph\gt;./seg /tuv So, you see, the TMX does not exactly match the original .po file. Although it does match the .sdf, but this is irrelevant. When I created the TMX by using XLFEdit from Heartsome, I first too the converted po, converted it to XLIFF and then exported it as TMX and the TMX contained the same number of escapes as the po. I would consider this behaviour by the Heartsome tool to be a bug, to be honest. Do they convert '' to 'lt;' ? Then they should also convert the rest. I would say this is part of the rules of data conversion between these formats. I believe our conversion conforms to the XLIFF representation guide for PO files: http://xliff-tools.freedesktop.org/snapshots/po-repr-guide/wd-xliff-profile-po.html#s.general_considerations.escapechars I think it follows logically that the same rules should apply for converting to TMX. Well, not when converted to an XML based type, I would say. In the same way a left angular bracket () can be put normally (unescaped) in a PO file, but in TMX it would have to go in as lt; Now, whatever is required or not in an XML document is not relevant here. What I need is that created TMX contents match exactly my source content otherwise I am going to edit each and every segment to add escapes so that my target matches my source... Which is defeating the point of using a TMX file. If the .po file contains 3 \ and if I created a TMX with a .po that has 3 \ I want the TMX to contain the 3 \. Otherwise it is not useful at all anymore. JC With the lt; I was just trying to explain why things might differ between two different data formats with an example that is perhaps slightly more well known because of its use in HTML
Re: [l10n-dev] OmegaT or poEdit?
On Ma, 2007-06-18 at 22:40 +0900, Jean-Christophe Helary wrote: On 18 juin 07, at 22:22, Alessandro Cattelan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, starting from today I'll have some more free time to dedicate to OOo L10N so I'd like to start working on it. I'm wondering whether the Italian team should use OmegaT or poEdit to translate the OLH and possibly the GUI (using Pootle as a translation workflow manager). Petr, Rafaella, can I go ahead and use OmegaT? Ale, I noticed that the TMX I created with translate-toolkit from the pseudo-translated .sdf are not useable because for some reason the po2tmx script systematically removed one escape \ character from the original po file. Hi Jean-Christophe Please elaborate on the problem so that we can find out where the error comes in and fix it if necessary. You can reply here, in private mail or the translate-toolkit mailing list - as you prefer. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle and terminology
On Ma, 2007-06-11 at 02:11 +0200, Alessandro Cattelan wrote: Aiet Kolkhi ha scritto: Ciao Alessandro! sorry for the mix up ;) yes, the syntax of PO files is very simple. And WordForge project has created Translate Toolkit that enables converting to GNU Gettext PO files from great many formats. This is how a simple terminology PO file entry can look like: #. Any piece of information (text, graphics, executable) put together and given a name. All the information you have on the hard drive is arranged as a collection of files. msgid File msgstr Lima The text after # sign is merely an explanation and is not needed by Pootle. The important lines are: msgid, followed by the original word in double quotes, and msgstr, followed by translation in double quotes. So it should be fairly easy to convert any text-based list to PO. I'd been told before that it should be quite easy to convert a txt into PO but unfortunately I don't know how to do it. Basically what I have is a long list of terms and expressions in two tab-separated columns, one for the English version and one for the Italian translation. Something like this: fraction frazione fraction divisore fraction bar linee di frazione frame frame frame cornice frame contentscontenuto cornice I understand that a PO files with these entries would look something like this: msgid fraction msgstr frazione msgid fraction msgstr divisore msgid fraction bar msgstr linee di frazione msgid frame msgstr frame msgid frame msgstr cornice msgid frame contents msgstr contenuto cornice Is that correct? I assume it would be quite easy to write a script for that, but I can't do it. Open your text file in OOo Calc as a CSV file and choose tab as the delimiter. Save it as a normal CSV file (comma seperated) and then you can convert it to PO using csv2po from the translate toolkit. Here is the documentation for that: http://translate.sourceforge.net/wiki/toolkit/csv2po I have another question: how would Pootle manage two entries with two different translations, such as frame above? Ale. It should suggest both. Note that (in the current implementation) the target field (msgstr) of the terminology files are considered free form, so you are free to add something like frame (verb) or cornice (noun) to help the translators. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle and terminology
On Ma, 2007-06-11 at 09:43 +0200, Alessandro Cattelan wrote: F Wolff ha scritto: Open your text file in OOo Calc as a CSV file and choose tab as the delimiter. Save it as a normal CSV file (comma seperated) and then you can convert it to PO using csv2po from the translate toolkit. Here is the documentation for that: http://translate.sourceforge.net/wiki/toolkit/csv2po I have another question: how would Pootle manage two entries with two different translations, such as frame above? Ale. It should suggest both. Note that (in the current implementation) the target field (msgstr) of the terminology files are considered free form, so you are free to add something like frame (verb) or cornice (noun) to help the translators. I'm still having trouble with this... :o( I've done what you suggested above and I got a csv text with two tab-separated columns, one with the English text and the next with the Italian translation: semi bold semigrassetto semi lightsemileggero semiautomatic semiautomatico semibold semigrassetto semicolon punto e virgola semicondensed semi compatto semiexpanded semiespanso semilight semichiaro If I run the csv2po command, the po file is not created. I've tried running the csv2po on the single file and on a directory. Here's the output: [EMAIL PROTECTED]:~/Desktop$ ls csv/ glossariostaroffice.csv [EMAIL PROTECTED]:~/Desktop$ ls po/ [EMAIL PROTECTED]:~/Desktop$ csv2po csv/ po/ /usr/lib/python2.5/site-packages/translate/storage/po.py:31: DeprecationWarning: The sre module is deprecated, please import re. import sre processing 1 files... [###] 100% [EMAIL PROTECTED]:~/Desktop$ ls po/ [EMAIL PROTECTED]:~/Desktop$ What am I doing wrong? Ale. You need to make a _comma_ separated file. This is the format that the converter is expecting. Does OOo Calc give the option of choosing the delimiter style? Perhaps it is using the tabs because the initial file had them. Then you might need to open the file in a text editor and replace the tabs with commas. Take note of the expected file format that csv2po expects (three columns with source and target in the second and third columns respectively). It might be easiest to ensure that your file has this format, otherwise you will have to specify the format using the --columnorder parameter. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle and terminology
On Ma, 2007-06-11 at 10:03 +0200, Alessandro Cattelan wrote: F Wolff ha scritto: On Ma, 2007-06-11 at 09:43 +0200, Alessandro Cattelan wrote: F Wolff ha scritto: ... I think it worked now!!! Thank you! Great! Here's the output: #: msgid year msgstr anno #: msgid z axis msgstr asse Z #: msgid zero line msgstr linea dello zero #: msgid zero values msgstr valori zero Would it make sense to put a comment in there which tells that the file comes from a glossary (for the translator to know where the term comes from)? Would the following work? #: Extracted from the SunGloss msgid zero line msgstr linea dello zero Thanks again, Ale. The best might be to add it with a #. comment - this way it will display in the tooltip of the suggestion in Pootle (if this is what you want). The #: comment will only show when you actually view / translate this specific file. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle and terminology
On Ma, 2007-06-11 at 13:32 +0400, Aiet Kolkhi wrote: Allesandro, Pootle does not yet support TM, but I know some people have used its terminology feature to include longer phrases. If you are interested in TM and automated translation, I would run this from the offline tool like KBabel or PoEdit and import the PO files to Pootle later. Friedel, do you think TM functionality will be added to Pootle anytime soon? Regards, Aiet There is TM functionality, it just doesn't work the same way as that of KBabel so it might be considered not all that user friendly. See http://translate.sourceforge.net/wiki/pootle/updatetm for some notes. Once again, this is something where we need a sever administrator for. By the way, we also have a tool to generate a glossary from existing translations to give you a start in defining your own glossary. It is packaged with translate toolkit 1.0, but I see there is no documentation for it yet. You can run it with --help to see some of the possibilities. We just have to watch the performance of the terminology matching - I have a suspicion that a very large glossary might impact performance, and on a shared system, this is something to consider. Remember that you can still translate all the PO files offline even if they are hosted on Pootle. Click on View editing functions and click on PO file for the file you want to translate offline. You can also download a ZIP of a project or a ZIP of a goal and upload the ZIP file with translations again later. F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] translate XML tags?
On Sa, 2007-04-14 at 13:09 +0200, Erdal Ronahi wrote: Hi, when using the translate-toolkit and Pootle I frequently come across warnings and error messages that XML tags should not be translated. This refers to strings like None for instance in sw / source / ui / index.po Should they be translated of left alone? Are they really XML tags? Regards, Erdal Hi Erdal Yes, pofilter has it's limitations. It is a bit difficult to know that None is not an XML tag :-) We are continuously working on improving the quality of the pofilter checks. Clytie reported a few limitations in two reports in our bugzilla (many of them has since been fixed). For reference: http://bugs.wordforge.org/show_bug.cgi?id=178 http://bugs.wordforge.org/show_bug.cgi?id=215 Recently we started making pofilter language aware, for example to understand the punctuation styles of different languages. Currently only a few languages have been described, but hopefully people will help us improve that. With all this said, translators should understand that there might be false positives, and use own judgement where necessary. Some checks are almost guaranteed to indicate translation errors, while others might be more likely to be false error reports in some cases. Certain tests are also more useful for certain languages than for others. Still, pofilter remains a useful tool to direct the review time in the directions where it is more likely to be of use. It is expendable to contain more tests, and adaptable to understand your language. Please help us to improve it to make version 1.0 maximally useful to as many languages as possible. Regards Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] translate XML tags?
On Sa, 2007-04-14 at 19:34 +0200, F Wolff wrote: On Sa, 2007-04-14 at 13:09 +0200, Erdal Ronahi wrote: ... Still, pofilter remains a useful tool to direct the review time in the directions where it is more likely to be of use. It is expendable to ...that should read _expandable_ :-) F - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Need italian PO files
On Di, 2007-04-03 at 11:30 +0200, Petr Dudacek wrote: Hi Enrico, it seems that something went wrong during the sdf-po conversion. For your case, the correct should probably be like this: #: swslots.src#FN_CHANGE_PAGENUM.sfxslotinfo.text msgid Page Number msgstr Numeri di pagina and similar for the remaining corrupted entries in the file. The metadata information was somehow copied into the English string, which is wrong. The best would be to ask the one who provided you with the .po files about this problem... Regards, Petr There is no corruption. The extra information is msgid comments (KDE style comments) and are used for disambiguation. There are different ways in oo2po of handling duplicate strings in a file. For more information, see http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle and http://translate.sourceforge.net/wiki/toolkit/oo2po Regards Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Occitan-langadocian : Change OOo1X's tranlation in OOo2x's translation
On Vr, 2007-03-30 at 14:39 +0200, Bruno wrote: Hi all, Hi Javier, I have 2 questions about the conversion from translation OOo1x to OOo2x. I don't succeed in doing this change. It is related to the OOo1's folder organisation, which is not the same as OOo2's folder. I don't understand how the translator of OOo1x did this. Actually, I have only somes files like, officecfg.po, offmgr.po, goodies.po...But not a folder organized. ** Question : If I have not the same organisation of OOo1x's folder and OOo2x's folder, how can I make the change with the translation's tools (http://translate.sourceforge.net) ? This week, a group of Occitan's translators contacted me because they are translating OOo2 in Ubuntu with the project Rosetta. They translated, already, the ooo-base modul and ooo-write modul. For me it will be better to try to integrate this translation in OpenOffice.org because it is more modern. I think there is a link somewhere in Rosetta to get the PO file. They then email it to you a day later or something like that (not really sure). I don't know if there is any way to easily get all of them (svn or something would be nice for you). ** Question : Is it possible, with the same translation's tool (http://translate.sourceforge.net) to make the change of translations OpenOffice-Ubuntu-Rosetta in OpenOffice.org ? If it is possible, how ? Thanks a lot for your patience, Best regards Bruno Have a look at pocompendium (it is not currently supplied with the translate toolkit, but is pat of the same project): http://translate.sourceforge.net/wiki/toolkit/pocompendium With this you can make a Translation Memory of the old files and the rosetta files (you can include any PO files you have, for that matter). Then you can use this compendium (translation memory) with pot2po. Note: this will probably take very long for the whole OpenOffice.org - so get a cup of coffee or something. But when it is done, you should hopefully have something useful to start with. It also gives you some fuzzy matching for the new untranslated things that should help a bit. Hope this helps. Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
