Re: [l10n-dev] Re: [qa-dev] Re: [l10n-dev] Re: [qa-dev] Re: [l10n-dev] Full install set for Bengali (bn)
Estonian full installation set is missing again. The UI is fully translated except some extensions we dont have to translate. Ain On Tue, Dec 22, 2009 at 17:44, Martin Srebotnjak mi...@filmsi.net wrote: Sorry, the links seem to have been fixed already. Thanks, m. 2009/12/22 Martin Srebotnjak mi...@filmsi.net There was a bug entered into IZ by smolejv (Vito Smolej) - Slovenian builds and Serbian builds have wrong paths to downloads on the RC1 download page. Lp, m. 2009/12/22 Marcus Lange marcus.la...@sun.com Jamil Ahmed wrote: On Mon, Dec 21, 2009 at 9:34 AM, Marcus Lange marcus.la...@sun.com wrote: Jamil Ahmed wrote: On Mon, Dec 21, 2009 at 6:35 AM, Marcus Lange marcus.la...@sun.com wrote: Hi Jamil, OK, I've uploaded them to the mirror network. Additionally they should be available hopefully tomorrow on the RC download website http://download.openoffice.org/all_rc.html; Thanks a lot! it's now online on the download website. Best regards Marcus - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: [qa-dev] Re: [l10n-dev] Re: [qa-dev] Re: [l10n-dev] Full install set for Bengali (bn)
Nevermind, my English is much worse than yours so I understood pretty well. :) Thanks a lot. Should I file an issue to be sure? Ain On Tue, Dec 22, 2009 at 19:05, Marcus Lange marcus.la...@sun.com wrote: Marcus Lange wrote: Just to be sure to use the same terms: I'm sorry, of course I mean Just to be sure that we both speak about the same terms. On Tue, Dec 22, 2009 at 18:30, Marcus Lange marcus.la...@sun.com wrote: Hi Ain, I cannot find your language (et) on the Pootle servers. Have you used them for translation (or at least for uploading the translation files)? If not maybe that's why we cannot see how much strings are translated and if you come at or over the 80% limit. I'm sorry but at the moment I cannot tell you more. I think we have to wait for Ivo or Frank beginning or January. PS: Don't worry, we can still add Estonian language for the RC2. ;-) Best regards Marcus Ain Vagula wrote: Estonian full installation set is missing again. The UI is fully translated except some extensions we dont have to translate. Ain On Tue, Dec 22, 2009 at 17:44, Martin Srebotnjak mi...@filmsi.net wrote: Sorry, the links seem to have been fixed already. Thanks, m. 2009/12/22 Martin Srebotnjak mi...@filmsi.net There was a bug entered into IZ by smolejv (Vito Smolej) - Slovenian builds and Serbian builds have wrong paths to downloads on the RC1 download page. Lp, m. 2009/12/22 Marcus Lange marcus.la...@sun.com Jamil Ahmed wrote: On Mon, Dec 21, 2009 at 9:34 AM, Marcus Lange marcus.la...@sun.com wrote: Jamil Ahmed wrote: On Mon, Dec 21, 2009 at 6:35 AM, Marcus Lange marcus.la...@sun.com wrote: Hi Jamil, OK, I've uploaded them to the mirror network. Additionally they should be available hopefully tomorrow on the RC download website http://download.openoffice.org/all_rc.html; Thanks a lot! it's now online on the download website. Best regards Marcus - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Collation problems in Latvian language.
Could be localedata issue. File an issue and assign it to person who is responsible for Latvian localedata or to user er. Ain On Wed, Dec 9, 2009 at 15:51, Viesturs Zarins viesturs.zar...@mii.lu.lv wrote: Can someone help me to fix this? Viesturs Zarins wrote: Hi, When testing the Latvian translation, I noticed that collation does not wok correctly. When sorting in Calc, the letter Y is placed between letters Ī and J, but it should be between letters X and Z. Thanks, Viesturs Ivo Hinkelmann wrote: Hi, I merged the latest fixes I found so far on pootle and from some issues. I created new installsets for the languages that changed: my ja uz fr nl vi ca pt-BR ru gl ko om gu zh-CN or de ta hu lv tr ast id eo es is it You can find the builds here: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/localization37fix/ This cws will be integrated on friday, I know there are only 2 days left for testing but this cws should only cover some minor fixes. Extending the test time is not possible or we violate the release schedule ... Please report any issue *ASAP* Cheeers, Ivo - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Agenda for the joint NLC/L10N meeting
On Tue, Nov 24, 2009 at 16:36, Andre Schnabel andre.schna...@gmx.net wrote: Hi, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com I created a wiki page to report and track the AIs I noted down during our NLC/L10n meeting in Orvieto. If you have attended the meeting, please do add yourself to the attendee list and please do let me know if anything is missing. It was not part of the official meeting, but I had a evening talk with Frank Mau about a quicker update of localized developer builds. Basic idea is to automate the pootle - sdf thing, have this synced to some cws repository and then buils langpacks .. or let buildbots build installsets on request. Frank might have more input, on what might be possible or not. André And for other languages (outside of Pootle) just grab sdf-files from predefined URL? ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: Re: New home for downloading language packs
You are mostly right. Anyways, I dont believe that there exists some widely used software that you can FULLY rely on in production. Maybe some space and military pieces ... ;) Maybe then: these untested packages can fail with a bit bigger probability than tested ones but are still much better in quality than Microsoft Office? :) ain On Sun, Nov 22, 2009 at 18:15, Martin Srebotnjak mi...@filmsi.net wrote: Hello, Marcus et. al., I was warned again by Slovenian community about the wording of the Disclaimer on the download site (http://download.openoffice.org/all_rc.html ): *OpenOffice.org 3.1.1 RC2 - untested full installation sets* *Disclaimer: The software in the following table is based on the final release but has not passed all final tests. Therefore it cannot be seen as a released build and should not be deployed in a production environment.* Firstly, but has not passed all final tests implies, that tests were performed but that the software packages listed failed them (did not pass = fail). Actually these builds were just not tested and there is no proof that they would fail those tests, probably the reverse is true, they would probably all pass tests if someone tested them. If not, language communities or users would be entering issues in IZ already. So we propose the following wording: but were not fully tested or but did not undergo the regular OpenOffice.org testing procedure or but did not undergo the regular QA testing procedures or something like that. Also should not be deployed in a production environment means that if they are used it is illegal or something, or your computer might explode. This might be very negative for promotion of OOo in government and civic environments. We would suggest something like this: are not recommended for use in a production environment. One could insert also a yet. These two issues might apply to one of the other two download pages if the Disclaimer is reused there. Just our two cents, m. - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: Re: New home for downloading language packs
This sentence irritates me a bit in the head of RC downloads: The software in the following table is not recommended for production deployment. These builds are under development and therefore unstable. This software is based on final source of released version, therefore these builds are not more under active development (can have only critical fixes) and these builds are with big probability as stable as released version and removing characters R, C and 2 from filename doesnt make these builds more stable. These builds are released 'as is' also as the released builds (there is a certain paragraph about it in license, number 15). So or so all our software is used at users own risk. Why then claim a software which has high probabilty to have very good quality to be clearly unstable? So I see 2 possibilities to rewrite this sentence above: 1. This software made from our stable source is ruined by evil localization teams you can easily decrypt from language names. When you meet them at street, kick their ass. 2. This software is based on final released version but has not passed all final tests. Please use this at your own risk and report possible issues to (IZ address). For more information visit the homepage of particular localization team listed in bottom of http://native-lang.openoffice.org/ First makes even to not educated people clear what we mean. Second maybe helps a potential downloader a bit further. There is of course a third sort of people who can use google or already know where to find download pages of localization teams (with tested or not packages) but unfortunately not the new users... And exactly to new users we just say: hey, when you install this software in your language you will have serious problems, please dont do it. Other problem is, that as policy says, langpack - when 80% of UI is translated and full set - when both help and UI are over 80%. I can see at least 2 missing languages from full set table, Czech and Estonian, I'm sure that there are a lot more. When submitting translations, we usually state the percentage. With high probability we don't submit any translations to minor versions (like 3.1.1) as we dont have any so critical fixes since major version (string changes in source are not allowed any more in this period), so how could we state it? ain On Mon, Nov 16, 2009 at 18:48, Marcus Lange marcus.la...@sun.com wrote: Hi all, both websites are now online. Best regards Marcus Marcus Lange wrote: Hi all, when there are no further comments, then I'll start to bring both sites to the new location at download.openoffice.org/other.html and download.openoffice.org/langpack.html. Thanks Marcus Marcus Lange wrote: Hi, because IA64 and Linux PPC builds are only available for English US and no other language, I've moved the columns to a separate table below the first one. This will save a bit space to the right hand side. Best regards Marcus Marcus Lange wrote: Hi, I've done some further changes: - Placed all notes to another website, so that the tables with download links will come a bit higher. - Furthermore I think it is better to name the download links as Download instead of the version number. Because the normal user will search for links that provide the actual download. So when naming it in this way it's easier to find and understand. Therefore I've named the links with the 3.1.1 builds with Download and (re)introduced the Latest release column. - I've extended the concept also to the full installation builds: http://download.openoffice.org/next/other_all.html Best regards Marcus Marcus Lange wrote: Hi all, as an alternative I've created a langpack website with all files listed in 2 tables: http://download.openoffice.org/next/langpack_all.html Maybe we can agree on this as commpromise? Best regards Marcus Marcus Lange wrote: Hi all, as promised I thought about a new structure and have created the following websites to ease the download of RC builds: http://download.openoffice.org/next/other_rc.html http://download.openoffice.org/next/langpack_rc.html Please have a look if the names of the languages are correct. It's not easy to find the correct wording for so many, so please bear with me. ;-) Keep in mind that this is just a test to show you how it could look like. It's not yet the final version (e.g., all builds that are already released have to be deleted from here, of course). Once we have a final state I would update the index page (http://download.openoffice.org/next), so that both new websites can be found via links and make some announcements. Please tell me what you think about this. Thanks in advance. Best regards Marcus Marcus Lange wrote: Hi all, I think I haven't taken into account the many differences with builds, testing and NL communities. So, I'm sorry if anyone feels offend. This was not my intension or to ignore the situation.
Re: [l10n-dev] Re: Re: New home for downloading language packs
Thank you! ain. On Thu, Nov 19, 2009 at 18:05, Marcus Lange marcus.la...@sun.com wrote: Ain Vagula wrote: Hi Ain, This sentence irritates me a bit in the head of RC downloads: The software in the following table is not recommended for production deployment. These builds are under development and therefore unstable. yes, it is not the best wording for a RC. This software is based on final source of released version, therefore these builds are not more under active development (can have only critical fixes) and these builds are with big probability as stable as released version and removing characters R, C and 2 from filename doesnt make these builds more stable. These builds are released 'as is' also as the released builds (there is a certain paragraph about it in license, number 15). So or so all our software is used at users own risk. Why then claim a software which has high probabilty to have very good quality to be clearly unstable? So I see 2 possibilities to rewrite this sentence above: 1. This software made from our stable source is ruined by evil localization teams you can easily decrypt from language names. When you meet them at street, kick their ass. 2. This software is based on final released version but has not passed all final tests. Please use this at your own risk and report possible issues to (IZ address). For more information visit the homepage of particular localization team listed in bottom of http://native-lang.openoffice.org/ First makes even to not educated people clear what we mean. Second But I doubt that it is political correct. ;-) maybe helps a potential downloader a bit further. There is of course a third sort of people who can use google or already know where to find download pages of localization teams (with tested or not packages) but unfortunately not the new users... And exactly to new users we just say: hey, when you install this software in your language you will have serious problems, please dont do it. Of course we have to say that it is not a released version. But it don't should scare the user, too, to test it nevertheless. The point is now to hit the middle. I've taken your idea and changed the websites like the following: The software in the following table is based on the final release but has not passed all final tests. Therefore it cannot be seen as a released build and should not be deployed in a production environment. However, you are invited to use and test these builds. Please report any possible issues. For more information visit the homepage of the particular localization team. Other problem is, that as policy says, langpack - when 80% of UI is translated and full set - when both help and UI are over 80%. I can see at least 2 missing languages from full set table, Czech and Estonian, I'm sure that there are a lot more. When submitting translations, we usually state the percentage. With high probability we don't submit any translations to minor versions (like 3.1.1) as we dont have any so critical fixes since major version (string changes in source are not allowed any more in this period), so how could we state it? Such requests for a full build/langpack please address to Ivo Hinkelmann (i...@openoffice.org). He is coordinating the integration of l10n stuff and can add the language to the list for building. Best regards Marcus On Mon, Nov 16, 2009 at 18:48, Marcus Lange marcus.la...@sun.com wrote: Hi all, both websites are now online. Best regards Marcus Marcus Lange wrote: Hi all, when there are no further comments, then I'll start to bring both sites to the new location at download.openoffice.org/other.html and download.openoffice.org/langpack.html. Thanks Marcus Marcus Lange wrote: Hi, because IA64 and Linux PPC builds are only available for English US and no other language, I've moved the columns to a separate table below the first one. This will save a bit space to the right hand side. Best regards Marcus Marcus Lange wrote: Hi, I've done some further changes: - Placed all notes to another website, so that the tables with download links will come a bit higher. - Furthermore I think it is better to name the download links as Download instead of the version number. Because the normal user will search for links that provide the actual download. So when naming it in this way it's easier to find and understand. Therefore I've named the links with the 3.1.1 builds with Download and (re)introduced the Latest release column. - I've extended the concept also to the full installation builds: http://download.openoffice.org/next/other_all.html Best regards Marcus Marcus Lange wrote: Hi all, as an alternative I've created a langpack website with all files listed in 2 tables: http://download.openoffice.org/next/langpack_all.html Maybe we can agree on this as commpromise? Best regards Marcus Marcus
[l10n-dev] Localized releases
Followup to 'new home for downloads' thing. Anyways when we take a look at list of approved and released packages and rc-list and list with language packs only then it seems to me that minority of teams are taking part in testing process at moment. Maybe it could help, when these teams who have resources to do all tests, register yourself for participating in localization QA and we could figure out something for others without showing to world this weird RCx stuff? For example, when translation is submitted via IZ and merged later, the submitter could verify the same issue itself to find out was the merging made without any artefacts? Because these people know at best which changes they made and can check it quickly. When OK, submitter can say that translation was verified in test build and can be used in final build (of course only for major releases, minor releases should usually not require any interaction at all when no critical faults were discovered). Honestly I cannot imagine that faulty, bad or even crappy translation could break the main functionality and stability of application. Sure that applications based on earlier proprietary software (OpenOffice, various *zillas Sons) have invented a way to crash program, when langpack of wrong version is installed (some mismatch of resources), but it is not the case. I have seen faulty fallbacks in OO.o when some localizable component was missing (eg. to first or next language in alphabet instead of English) but it is also not the case, even with P2 fixing these issues takes 3 or more years. Has someone an idea what really can happen that makes localized build so dangerous? Is this something specific for RTL or CTL languages? Or something specific for languages having poor support by operating system? I believe that wrong translations and typos (and even unmerged parts of translation) we will still discover visually during in a quite long time and more users could give us more feedback about such inconstencies. ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Localized releases
I dont believe such issues come up during simple qa tests. Ok, as I so or so work every day 4 or more hours with oo.o development and rc builds on Windows and Linux and can be sure that these builds install, run, and what a surprise, even can open and save the documents, I can just get an qa account for my language and mark these platforms tested to be distributed. ain 2009/11/19 Harri Pitkänen hatap...@iki.fi: On Thursday 19 November 2009 19:20:21 Ain Vagula wrote: Has someone an idea what really can happen that makes localized build so dangerous? There have been two bugs in Finnish translation that have caused corruption upon saving documents. Both were caused by accidentally giving two different style names the same Finnish translation. In the first case the original English names were Header and Heading, in the second case Title and Heading. Both of these bugs have been fixed since 2.1.1. Harri - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: Re: New home for downloading language packs
Interesting, I have several years UI translation between 99-100% and Help over 90 and always stated it when submitting translations. Though I havent seen full builds exept pre-last release when I asked Ivo to make a build for win32. ain On Mon, Nov 2, 2009 at 18:11, Joost Andrae joost.and...@sun.com wrote: Hi, IMHO nobody has said this. ;-) We are doing full install sets when the L10N has reached 75 or 80 %. Langpacks are always done. Sun Hamburg team is doing full builds if at least 80% UI has been translated and at least 80% help content has been translated Sun Hamburg team is building language packs if at least 80% UI has been translated The percentage about current translation status is collected after l10n teams submitted their translations. I'll gather the current status from Ivo Hinkelmann and from Frank Mau right after the OpenOffice.org conference. Kind regards, Joost - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: [releases] Re: [l10n-dev] New home for downloading language packs
It doesnt matter at all. I have resources to distribute my native language version by myself. I dont have resources to follow this insane QA prodedure. Only a bit pity that all users who visit Openoffice.org main website will have a false imagination that there is no oo.o version in particular language. ain On Fri, Oct 16, 2009 at 22:06, Sophie sgautier@free.fr wrote: Resent with the good adress and to l10n@ also, sorry. Hi Bernard, Bernard Marcelly wrote: Hi, IMHO translation work is probably too cautious, and this hinders usage of OpenOffice.org. Take swedish (sv) or spanish (es) languages : - There is no full package available for 3.1.1, only version 3.1.0. - The langpacks for 3.1.1 have not been released. - But langpacks are available as 3.1.1RC2. So power users can install OOo 3.1.1 in these languages, and be happy. Take italian (it) language : - Full packages are released for 3.1.1 - Langpacks for 3.1.1 are *not* released. - But langpacks are available as 3.1.1RC2. I don't understand why the full package is released but not the langpack. I don't understand why a langpack in RC2 stays unreleased. RC2 means that it seems good enough for public tests. If there are some strings not yet translated, or badly translated, this does not prevent from using OpenOffice.org as a whole. If a user does not master one of the published languages, it is better than nothing. And then users of this language will find and report residual errors. This is not a matter of strings not translated, but of the stability of the version as Joost mentioned. Releasing or not releasing as stable has always been a difficult choice. User that faces a not fully functional version or version that crashes may never come back to OOo, however if you don't release the version, you will miss testers and their feedback. We have already seen language specific bugs and for that have decided that a version or language pack that is not tested should not become public. OOo has a QA process even for localized version, this what we have agreed on several times ago. I've offered my help to each l10n team to help them in this process, it is still valid my time is still dedicated to these teams because it will give more visibility to their versions if they are on the main network, but also, and more important to my eyes, to their teams and the work they have done. Kind regards Sophie - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: [releases] Re: [l10n-dev] New home for downloading language packs
ie. this fine download page would have a sense when it lists all NL projects (including official mirrors for NL versions) and points to their download pages. It is not fair at all to ignore availability of NL version of oo.o to this short lists because of some language dependent issues - what do you propose? To use en-us version because NL version has issues? Excuse me, this sucks. ain On Fri, Oct 16, 2009 at 23:24, Ain Vagula avag...@gmail.com wrote: It doesnt matter at all. I have resources to distribute my native language version by myself. I dont have resources to follow this insane QA prodedure. Only a bit pity that all users who visit Openoffice.org main website will have a false imagination that there is no oo.o version in particular language. ain On Fri, Oct 16, 2009 at 22:06, Sophie sgautier@free.fr wrote: Resent with the good adress and to l10n@ also, sorry. Hi Bernard, Bernard Marcelly wrote: Hi, IMHO translation work is probably too cautious, and this hinders usage of OpenOffice.org. Take swedish (sv) or spanish (es) languages : - There is no full package available for 3.1.1, only version 3.1.0. - The langpacks for 3.1.1 have not been released. - But langpacks are available as 3.1.1RC2. So power users can install OOo 3.1.1 in these languages, and be happy. Take italian (it) language : - Full packages are released for 3.1.1 - Langpacks for 3.1.1 are *not* released. - But langpacks are available as 3.1.1RC2. I don't understand why the full package is released but not the langpack. I don't understand why a langpack in RC2 stays unreleased. RC2 means that it seems good enough for public tests. If there are some strings not yet translated, or badly translated, this does not prevent from using OpenOffice.org as a whole. If a user does not master one of the published languages, it is better than nothing. And then users of this language will find and report residual errors. This is not a matter of strings not translated, but of the stability of the version as Joost mentioned. Releasing or not releasing as stable has always been a difficult choice. User that faces a not fully functional version or version that crashes may never come back to OOo, however if you don't release the version, you will miss testers and their feedback. We have already seen language specific bugs and for that have decided that a version or language pack that is not tested should not become public. OOo has a QA process even for localized version, this what we have agreed on several times ago. I've offered my help to each l10n team to help them in this process, it is still valid my time is still dedicated to these teams because it will give more visibility to their versions if they are on the main network, but also, and more important to my eyes, to their teams and the work they have done. Kind regards Sophie - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: [releases] Re: [l10n-dev] New home for downloading language packs
So hard to understand? I know my NL version has issues, too serious, not depending on me. Why the heck should I follow the procedure? I just want that availabilility of my version is visible on oo.o main site? I dont want to lie. There are issues. But a version is available, good for 99.99% of users. But everyone says to me, that my NL version is not available via oo.o main website. ain On Fri, Oct 16, 2009 at 23:32, Mechtilde o...@mechtilde.de wrote: Hello, Ain Vagula schrieb: It doesnt matter at all. I have resources to distribute my native language version by myself. I dont have resources to follow this insane QA prodedure. Only a bit pity that all users who visit Openoffice.org main website will have a false imagination that there is no oo.o version in particular language. IMO it is very easy. The l10n leead decide whether they want to release there national version or not. (S)He decide whether the user can install and works with it or not. The l10n lead is resposible about the quality of the national version compared with the other ones. Kind regards Mechtilde -- Dipl. Ing. Mechtilde Stehmann ## http://de.openoffice.org ## Ansprechpartnerin für die deutschsprachige QA ## Freie Office-Suite für Linux, Mac, Windows, Solaris ## Meine Seite http://www.mechtilde.de ## PGP encryption welcome! Key-ID: 0x53B3892B - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Re: [releases] Re: [l10n-dev] New home for downloading language packs
Dear coworker, whatever I ment: When I translate or localize gnumeric or koffice, the localized version is always available to all users 'as is' via repositories. Why should oo.o make a difference, I mean to follow some formal procedures without any real sense? Isnt that enough that translations are submitted and possible issues are filed via IZ? ain On Fri, Oct 16, 2009 at 23:54, Mechtilde o...@mechtilde.de wrote: Hello Ain, Ain Vagula schrieb: So hard to understand? I know my NL version has issues, too serious, not depending on me. Are these issues different to the ones in the other NL versions? Are they specific for the ee version? Why the heck should I follow the procedure? I just want that availabilility of my version is visible on oo.o main site? I dont want to lie. There are issues. But a version is available, good for 99.99% of users. But everyone says to me, that my NL version is not available via oo.o main website. Otherewise you are the person who decide and is responsible about your NL version whether it can be released or not. Or are there too many text untranslated? If you decide it is good enough to release this is your decision. Special problems can also be discussed at #ooonlc at irc.freenode.net Kind regards Mechtilde -- Dipl. Ing. Mechtilde Stehmann ## http://de.openoffice.org ## Ansprechpartnerin für die deutschsprachige QA ## Freie Office-Suite für Linux, Mac, Windows, Solaris ## Meine Seite http://www.mechtilde.de ## PGP encryption welcome! Key-ID: 0x53B3892B - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] 3.2 (m60) done!
You can see it in Sun builds. ;) And yes, the text quality is horrible. As I dont understand half of this pidgin, I'll leave it untranslated, so or so it is not accessible in community builds. Ain On Tue, Oct 13, 2009 at 17:31, Martin Srebotnjak mi...@filmsi.net wrote: 2009/10/13 Olivier Hallot ohal...@scinergy.com.br: Regards, (*) I found the lingustic quality of the migration tool below OO standards... Am I the only one who catched this? No, you are not :) The funny part is - where can the translators even see how this tool looks like? But obviously this won't be a part of the official 3.2 release, maybe a freeware extension or what? Or part of StarOffice? :) Lp, m. - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] 3.2 (m60) done!
Hm, as Ivo said ATM these tools are not provided. I messed it up with this User Feedback or something thingie, thats also missing from community builds. I'm sorry for that. Anyways, such a big parts of text with unclear future and bad quality - these should be announced in this list to prevent silly and bogus work. Translators, do not hesitate to ask here about every single suspicion you may have. As you see this question was answered. Thats pity it wasnt asked earlier. Ain On Tue, Oct 13, 2009 at 21:30, Martin Srebotnjak mi...@filmsi.net wrote: Well, if Sun sells it, then they have to pay for my translation, I guess :) Lp, m. 2009/10/13 Ain Vagula avag...@gmail.com: You can see it in Sun builds. ;) And yes, the text quality is horrible. As I dont understand half of this pidgin, I'll leave it untranslated, so or so it is not accessible in community builds. Ain On Tue, Oct 13, 2009 at 17:31, Martin Srebotnjak mi...@filmsi.net wrote: 2009/10/13 Olivier Hallot ohal...@scinergy.com.br: Regards, (*) I found the lingustic quality of the migration tool below OO standards... Am I the only one who catched this? No, you are not :) The funny part is - where can the translators even see how this tool looks like? But obviously this won't be a part of the official 3.2 release, maybe a freeware extension or what? Or part of StarOffice? :) Lp, m. - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] 3.2 (m60) done!
That I didnt read it ;) ain 2009/10/13 André Schnabel andre.schna...@gmx.net: Hi, Ain Vagula schrieb: Translators, do not hesitate to ask here about every single suspicion you may have. As you see this question was answered. Thats pity it wasnt asked earlier. Actually it had ben asked (1st 2009-06-10). The statement that thismodule needs not to be translated was given on 2009-09-24 (not really quick answer, but there *was* an answer). Later Rafaella even stated, that the module is not inclded in normal OOo builds and is rather considered as some knd of extension. So I don't know, what is the pity we need to speak about? André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] How to handle the character ' in our translations
You dont need to escape single quotes. ain On Fri, Oct 9, 2009 at 03:34, Belayneh Melka demb...@yahoo.com wrote: Hi all , The Oromo Language - the language for which we are doing translation- has lots of words which when written have the character ' . Here are some examples showing translation of English words to Oromo Language: Load - Fe'i Save - Olkaa'i Add - Ida'i Substract - Hir'isi Multiply - Baay'isi , and so on. We have used this character as shown above in our translations. Is it correct or do we have to write it with escape character as follows? Fe\'i Olkaa\'i Ida\'i , etc... Do our translations affect the build due to not using the escape character (\) in our translations? Thanks in advance, Dawit - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: Helpcontent changes in m57
hcshared22 also introduced a lot of needed changes about new or changed features in 3.1, so we cannot use older source here. I believe that there is no time any more to select out unwanted changes. When we ignore unwanted changes because we dont want to handle about 2000 strings twice, the quality of translated help in 3.1 will be worse than ever. If we decide fix the translation, we may run out of time. Anyways, it does not harm, when img-strings are fuzzy, default pictures are mostly same in all languages so the fallback displays the same. It makes the count of strings that need attention a bit smaller. ain 2009/9/18 André Schnabel andre.schna...@gmx.net: Hi, Mathias Bauer schrieb: Correct me if I'm wrong, but wouldn't it be possible to provide a custom build that contains the rollback changes that didn't make it into m59/m60? Translators could use this one instead of the milestone build. We do not translate builds we translate source. So a custom build would not help. To map the idea to source code, we would need a special CWS, that rolls back the changes - and we would need to have another cws to hold translations for the Rollback CWS ... seems to be a little complicated procedure to me. (At the other hand this is quite similar to what the documentation team just tried). Sorry in advance if that is a bad idea for some other reasons that my tiny little brain doesn't know. :-) It's friday - you are excused ;) André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: Helpcontent changes in m57
and the worse of all is that we already wasted 2 weeks, waiting hcshared23 which didnt fix much... to be exact I wasted 2 months because I didnt know what to do with changes since July 9th. ain On Fri, Sep 18, 2009 at 09:22, Ain Vagula avag...@gmail.com wrote: hcshared22 also introduced a lot of needed changes about new or changed features in 3.1, so we cannot use older source here. I believe that there is no time any more to select out unwanted changes. When we ignore unwanted changes because we dont want to handle about 2000 strings twice, the quality of translated help in 3.1 will be worse than ever. If we decide fix the translation, we may run out of time. Anyways, it does not harm, when img-strings are fuzzy, default pictures are mostly same in all languages so the fallback displays the same. It makes the count of strings that need attention a bit smaller. ain 2009/9/18 André Schnabel andre.schna...@gmx.net: Hi, Mathias Bauer schrieb: Correct me if I'm wrong, but wouldn't it be possible to provide a custom build that contains the rollback changes that didn't make it into m59/m60? Translators could use this one instead of the milestone build. We do not translate builds we translate source. So a custom build would not help. To map the idea to source code, we would need a special CWS, that rolls back the changes - and we would need to have another cws to hold translations for the Rollback CWS ... seems to be a little complicated procedure to me. (At the other hand this is quite similar to what the documentation team just tried). Sorry in advance if that is a bad idea for some other reasons that my tiny little brain doesn't know. :-) It's friday - you are excused ;) André - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: Helpcontent changes in m57
Ok, this number is good to know. I apologize. Translator sees all changes as fuzzy, seems like I have to rollback in cvs a bit and do merge again against m59 ain On Fri, Sep 18, 2009 at 11:06, Frank Peters f...@sun.com wrote: Ain Vagula wrote: and the worse of all is that we already wasted 2 weeks, waiting hcshared23 which didnt fix much... IIRC, we rolled back around 900 changes menuitem emph and insignificant spaces. The rollback was complicated because there was only little time to do it and we needed to make sure that we only rolled back changes made for m56 and not clean all erroneous strings since that would have created additional l10n effort. -- Frank Peters The OOo Documentation Project: SIGN UP - PARTICIPATE - CONTRIBUTE IT'S FREE! NO OBLIGATIONS! http://documentation.openoffice.org http://wiki.services.openoffice.org/wiki/Documentation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: Helpcontent changes in m57
It returns an error ;) ain On Thu, Sep 17, 2009 at 12:23, Uwe Fischer uwe.fisc...@sun.com wrote: Hi Martin, I trust that Slovenians can make it happen! Don't give up, just re-use the old translations wherever only spaces got added or removed. I will try to find the cause of the additional space characters inside long xml constructs later today. You may translate or neglect the emph--menuitem changes as you like. In the final Help page that the user gets to see, there is no difference between the two tags. Don't know what the translation syntax checker will return, however. Uwe On 09/17/09 10:47, Martin Srebotnjak wrote: Thanks, Uwe, for the reply. That probably means that I as single translator for Slovenian will not translate those strings with added 6 and 9 spaces that were introduced since m56 as that would make my work redundant - I would have to again go through them. I wonder if other smaller localization teams will do the same. This probably means that many localized versions just won't be fully localized for 3.2 and that would not be the responsibility of localizers. As for added MAC space - in all those places that it was introduced since m56 it was not necessary in my opinion (it would have been, if in the displayed text there would be a space missing between the shortcut word and another word). Here is an example from m56-m59: m56: To insert a new paragraph immediately before or after a section, click in front or behind the section, and then press switchinline select=\sys\caseinline select=\MAC\Option/caseinlinedefaultinlineAlt/defaultinline/switchinline+Enter. m59: To insert a new paragraph immediately before or after a section, click in front or behind the section, and then press switchinline select=\sys\caseinline select=\MAC\Option /caseinlinedefaultinlineAlt/defaultinline/switchinline+Enter. Uwe, do you think this addition of space after Option in this case is necessary? Does this mean that besides added 6 and 9 spaces and the tags change there is another automatic change problem, the added unnecessary spaces after Option and Command in MAC shortcuts? Also, what should we the localizers do with the emph - menuitem change? Do you expect us to translate/localize these manually or will you revert them back after 3.2 and make this change automatically in the localization teams' SDF files as was discussed in this thread? If I have to manually edit those strings in time for 3.2 - well, I just probably won't, - I wonder what other localization teams' opinion is on this matter? What about all the errors introduced with this change, like the one I reported in my previous post (with the emph-menuitem replacement some emph closing tags remaining etc.)? Thanks, m. 2009/9/17 Uwe Fischer uwe.fisc...@sun.com: Hi Martin, first we must apologize for some unintended changes that appeared in the *.xhp help source files in the last few months. Be assured that we do not want to make the life of translators uncomfortable in any way, just the opposite. The unnecessary blank spaces were introduced by using some pretty xml formatting plug-in or add-on or option in jEdit. This should have worked only at places where whitespace is not important, but obviously that assumption was false. And I was quite sure, additionally, that the pretty formatting works only for the view and never expected that it saves those indents as spaces to the files. Sure, some testing would have revealed this in time, but then ... who will run the tests, who has the time ... The changes from emph tags to menuitem tags, although very useful to use xml structure instead of visual attribution for tagging, just came in at the wrong moment. We tried to roll back those changes from cws hcshared22 to hcshared23. However, a tight deadline demanded that we could not roll back the changes in all those files that already got edited in hcshared23. Also other feature CWSs with edited help files were merged in automatically, and those other files are based on whatever version the feature CWS was based on. This may have resulted in even more conflicts in the new master help files. By now, Help contents for OOo 3.2 are delivered. We have some months until OOo 3.3. So we can now take care of all unwanted pecularities that mess up the Help contents. Of course we will do this by creating script based tests and/or improved import and export filters so that those issues will not happen again. Uwe btw, the single space inside inline switches problem can be resolved by looking at the whole sentence where it appears. Normally, a single space should follow the switch construct and inside the switch tags there should be no space before or after the text contents. Take care that at the end, following the switch for every condition, there is one space between words. On 09/17/09 01:44, Martin Srebotnjak wrote: Hello again, I just updated to
Re: [l10n-dev] IMPORTANT: Helpcontent changes in m57
There are some issues raised both about unneccesary tags and a also about l10n tools: http://qa.openoffice.org/issues/show_bug.cgi?id=40920 http://qa.openoffice.org/issues/show_bug.cgi?id=43810 http://qa.openoffice.org/issues/show_bug.cgi?id=47563 Those are only issues that I have CC-d, maybe there are more. Should be interesting to view full list. ;) ain On Tue, Sep 8, 2009 at 12:50, Andras Timarti...@fsf.hu wrote: 2009.09.07. 15:14 keltezéssel, Olivier Hallot írta: 3) Tons of mostly unit measures changes only. A no-brainer task to copy/paste, but nevertheless very time consuming I think all of us would agree, that no-brainer tasks should not be done by human beings. Although help writers made a mistake here, in fact it is a problem with your l10n tools. Tools should handle tag changes and whitespace changes in a smarter way. With PO files there is little chance to improve things, but at least the #| msgid previous-untranslated-string comment could be used. Good PO editors can make a diff, and translators do not have to read and interpret the whole segment. With XLIFF there are more possibilities. Tags and variables can be marked up as placeables which means that the editor can make a difference between them and normal text. Currently tags and variables are not marked up in OOo XLIFF files. I wonder why. With a little effort put into l10n tool development OOo translation experience would improve dramatically. I'm using a proprietary tool. The money I spent on it have been re-gained 10 times, because I can save a lot of time. I know it is not an option for everybody. I know that many of you haven't seen better tools than the mainstream open source tools (Translate Toolkit, Pootle, POEdit, Lokalize, KBabel, etc.). I'm afraid that long time contributors will quit due to frustration and new contributors will not come. Noboby likes brainless copy-pasting. Best regards, Andras hu l10n - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Massive English help stampedo
On Mon, Sep 7, 2009 at 11:52, Frank Petersf...@sun.com wrote: Martin, Apparently, those changes came in by error. So we need to evaluate how that happened and how it can be prevented in the future. Accusing co-contributors of being malicious or inconsiderate will certainly not facilitate this effort. So, please, (and I am minding my tone), who did these changes? Who is In what way do persons matter here? responsible? Who did QA? This did already happen some milestones ago I was not aware of this. Has this been reported before when you first noticed it? This was reported 9th July after m51 milestone in d...@docs list by Hristo Histov (to be honest he asked me and I suggested him to write to list): http://documentation.openoffice.org/servlets/ReadMsg?list=devmsgNo=5573 ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Massive English help stampedo
And that is not all... in m57: paveljanik there are zillions of TAB changes =9 paveljanik :-( paveljanik image/icon changes :-( ain On Sun, Sep 6, 2009 at 17:58, Martin Srebotnjakmi...@filmsi.net wrote: Hello, I am new to this list (I am the lead translator of OOo into Slovenian language), I hope I am posting to the right group. I am currently very pissed off so I did not bother checking if someone alredy asked this question. And taking in a breath or two will not help calming me down. So, here are the questios. And I do apologize if this venting is too much for this list in advance. Who is the genius who has completely revamped the English OOo Help content in one of the past milestones and now again (repeating the mistakes while eliminating some from previous CWS!) in the m57 introducing tons and tons of (unnecessary, unwanted 6 empty spaces) in otherwise unchanged English strings? Who is the genius changing tags from item to item type=\menuitem\ (where applicable) in several files? Although that might be useful and logical and a decision, agreed on by OOo developers, 100 translators to other languages must replicate the manual work in each and every string (and there are more than 500 strings changed in this way in m57)! Are you nuts? Can't you offer an automatic tool for that? Do we have to retranslate or retype/repaste all the help all the time? And then English strings like this one appear: Click the item type=\menuitem\Outline Numbering/item emph/tab. Not to mention the fact that the gettext tools fuzzy-match more or less the type=\menuitem\ part of the string and not what's inside, so fuzzy matching in most of these cases does not help translators. Here is schematic example: Choose emphSOMETHING/emph. gets a fuzzy translation like: Choose item type=\menuitem\SOMETHING-ELSE/item. So almost all of these must be manually edited, and you must know (or look up) the translation of all those menu entries or buttons. And mistakes might happen ... Please, instruct me, what do I do with strings like: Choose emphTools - Language - Thesaurus/emph changed from Choose emphTools - Language - Thesaurus/emph Do I have to add 6 spaces at the end in Slovenian version? Or will there be an update on September 21 where all these mistakes will be erradicated and I will have to go through all the wrong strings with spaces (there must be 400 or more of them) and use my through-out ok Slovenian translations, marking them ok from being fuzzied again? How do such changes pass QA? Do you really not care for (mostly) open-source translators around the world giving up their spare time to this project? Not to mention that sdf for this massive change got available just two days ago, only two weeks before feature freeze, when testing and finishing up of translations starts ... If all translators would be paid by Sun by the hour, the developers QA would really think about such massive changes before approving them. Sorry, but I just could not beat around the bush. I guess other translators must feel about the same (or there is something very much wrong with me). Lp, m. - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Massive English help stampedo
updating to m57 added about 2000 fuzzy strings to help :( a lot of image/icon string changes. Is this all really necessary? Can these actions to be reverted? I can return my own translation cvs repository to any healthy point, but what to do with people/languages who have already translated this and who dont have version management environment? This is a major issue and very urgent! Things are gone to dogs starting from m51 and I suggest you to review all diffs made since this milestone and revert unnecesary changes. ain On Sun, Sep 6, 2009 at 19:45, Frank Petersf...@sun.com wrote: Martin Srebotnjak schrieb: I am new to this list (I am the lead translator of OOo into Slovenian language), I hope I am posting to the right group. in future you should copy d...@documentation.oo.o as well on documentation issues. I am currently very pissed off so I did not bother checking if someone alredy asked this question. And taking in a breath or two will not help calming me down. So, here are the questios. And I do apologize if this venting is too much for this list in advance. This and other lists are not for venting. While I understand your frustration, it would be better to shout at your room mate if you want to vent. Who is the genius who has completely revamped the English OOo Help content in one of the past milestones and now again (repeating the mistakes while eliminating some from previous CWS!) in the m57 introducing tons and tons of (unnecessary, unwanted 6 empty spaces) in otherwise unchanged English strings? Who is the genius changing tags from item to item type=\menuitem\ (where applicable) in several files? Although that might be useful and logical and a decision, agreed on by OOo developers, 100 translators to other languages must replicate the manual work in each and every string (and there are more than 500 strings changed in this way in m57)! Are you nuts? Can't you offer an automatic tool for that? Do we have to retranslate or retype/repaste all the help all the time? And then English strings like this one appear: Click the item type=\menuitem\Outline Numbering/item emph/tab. Not to mention the fact that the gettext tools fuzzy-match more or less the type=\menuitem\ part of the string and not what's inside, so fuzzy matching in most of these cases does not help translators. Here is schematic example: Choose emphSOMETHING/emph. gets a fuzzy translation like: Choose item type=\menuitem\SOMETHING-ELSE/item. So almost all of these must be manually edited, and you must know (or look up) the translation of all those menu entries or buttons. And mistakes might happen ... Please, instruct me, what do I do with strings like: Choose emphTools - Language - Thesaurus/emph changed from Choose emphTools - Language - Thesaurus/emph Do I have to add 6 spaces at the end in Slovenian version? Or will there be an update on September 21 where all these mistakes will be erradicated and I will have to go through all the wrong strings with spaces (there must be 400 or more of them) and use my through-out ok Slovenian translations, marking them ok from being fuzzied again? How do such changes pass QA? Do you really not care for (mostly) open-source translators around the world giving up their spare time to this project? Not to mention that sdf for this massive change got available just two days ago, only two weeks before feature freeze, when testing and finishing up of translations starts ... If all translators would be paid by Sun by the hour, the developers QA would really think about such massive changes before approving them. Mind your tone, please. Apparently, those changes came in by error. So we need to evaluate how that happened and how it can be prevented in the future. Accusing co-contributors of being malicious or inconsiderate will certainly not facilitate this effort. Back to the problem: we seem to require some sort of normalization process for the help files to compensate for stupid actions some XML editors might take, like introducing spaces. I'll have a look at this with Uwe and Sun Release Engineering. Frank XPost to d...@doc.oo.o -- Frank Peters Documentation Project Co-Lead The OOo Documentation Project: SIGN UP - PARTICIPATE - CONTRIBUTE IT'S FREE! NO OBLIGATIONS! http://documentation.openoffice.org http://wiki.services.openoffice.org/wiki/Documentation - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] No source to translate ?
These messages are generated by gettext's msgmerge and there is a key for switching this. I think that these obsolete messages are usually not needed. `--previous' Keep the previous msgids of translated messages, marked with `#|', when adding the fuzzy marker to such messages. Ain On Mon, Aug 24, 2009 at 08:55, Dwayne Baileydwa...@translate.org.za wrote: Hi All, On Mon, 2009-08-24 at 10:42 +0800, Aijin Kim wrote: Hi Dick and all, Sophie wrote: Dick Groskamp wrote: Sophie schreef: Hi Dick, As André said, this a bug on Pootle. If you use an external tool to translate, these strings won't appear in the tool, only if you edit the file with an application like gedit or the like, you will see the .txt file structure. The strings were used on the UI but they have been migrated to cui.po. Why they are kept here? I don't know, may be we could discuss this. Your translation memory should have them any way if you choose to use it. Thanks SOPHIE, I understand but my main point is that it shouldn't be visible in Pootle at all. That means that it is to be corrected. Yes, you're right so this bug has to be reported to the Pootle team. I forwarded this issue to Friedel who is the Pootle developer. Let's wait for his reply if it's a known bug. Friedel and a number of other Pootle coders have been in Egypt at Pootlemania for a code sprint. He is back so I'm sure he'll chip in today if needed. I've had a quick look at the issue and I'll try summarise then explain the issue so that everyone gets an idea of what's going on even if you don't care for code! Here is the bug that I've raised to track this: http://bugs.locamotion.org/show_bug.cgi?id=1114 Issue = These strings are being presented by Pootle because Pootle is seeing obsolete messages (marked as #~ in PO files) as untranslated. There is nothing wrong with the PO files which is why translators who are using offline tools are not seeing the issue. Fix === Fortunately I don't think the fix will be too hard and it will probably be easy to patch the OOo Pootle server. I'm hopeful that we'll be able to have a fix before the end of today. So you might not need to try any of the following workarounds. Workaround == 1) Ignore these messages with no source text until we fix the issue. 2) Try work offline by downloading and uploading PO files to Pootle. (There have been a few suggestions of possible tools, you can also try out Virtaal http://virtaal.org/) Issue in more detail Pootle uses the Translate Toolkit to do much of its manipulation of PO files. We did a major work in the Translate Toolkit for v1.4 where we removed the old KDE style comments and replaced them with proper Gettext msgctxt. The change was important as it meant that we got proper PO files for OpenOffice.org and did away with the non-standard KDE comments. Many PO editors didn't understand KDE comments and it could lead to translators being confused and translating the KDE comment instead of ignoring them. It was an invasive change, we knew that, but the benefits were great. We tested quite extensively doing roundtrip test but unfortunately it seemed the change has impacted our code that tracks the state of a string. I.e. whether a string is translated, fuzzy, untranslated or obsolete. The toolkit is now seeing an obsolete message with msgctxt as untranslated when it should be ignoring them completely. Pootle relies on this state information to find untranslated strings and is thus finding them and presenting them to you even though they should be ignored. The bad news is that our battery of unit tests didn't check for this condition so it slipped through in our changes. The fix should be as simple as to ensure that obsolete messages with a msgctxt field are not seen as untranslated. Please feel free to join the bug but I'm sure we'll announce the fix on the list. -- Dwayne Bailey Associate Research Director +27 12 460 1095 (w) Translate.org.za ANLoc +27 83 443 7114 (c) Recent blog posts: * Google Translate + libtranslate + Virtaal = machine translation in 7 new languages http://www.translate.org.za/blogs/dwayne/en/content/google-translate-libtranslate-virtaal-machine-translation-7-new-languages * Fixes for Skype Video, Webcam on Fedora * libtranslate, TM plugins and Virtaal Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail:
Re: [l10n-dev] Spaces in new m51 strings
Please follow the same thread in docs-devel list ;)
ain
On Thu, Jul 9, 2009 at 15:41, Ivo Hinkelmannivo.hinkelm...@sun.com wrote:
Hi Pavel,
( cc'ed ufi and d...@l10n list )
yes you are right ... I looked at the wrong entry :S
The problem is that the cws hcshared21 indent the xhp file like this:
before:
paragraph
emphNumber:/emph Numeric expression .
/paragraph
after:
paragraph
emphNumber:/emph Numeric expression .
/paragraph
Everything within the paragraph tag is take as string. So I can either trim
the leading spaces out of all strings in the l10n tooling or just modify
those files with the wrong indention.
imho this would be the correct format for the source xhp file:
paragraphemphNumber:/emph Numeric expression ./paragraph
all in one line but how to tell this the xml editors.
Any opinions?
Cheers,
Ivo
Pavel Janík schrieb:
Hi,
On 8.7.2009, at 14:40, Ivo Hinkelmann wrote:
the first string is like this in the sdf:
helpcontent2^Isource\text\sbasic\shared\03030104.xhp^I0^Ihelp^Ipar_id3156423^I8^I^I^I0^Ien-US^I\emph\Number:\/emph\
Numeric expression that contains the serial date number that is used to
determine the month of the year.^I^I^I^I2002-02-02 02:02:02$
not here - here it contains:
paveljanik:/Volumes/Build/pavel/AQUA pavel$ grep Numeric expression that
contains the serial time value that is used to return the hour value.
BuildDir/DEV300_m51/Build-1/GSI/en-US.sdf | awk -F' ' '{print
$11}'|hexdump -C
20 20 20 20 20 20 20 20 20 5c 3c 65 6d 70 68 5c |
\emph\|
0010 3e 4e 75 6d 62 65 72 3a 5c 3c 2f 65 6d 70 68 5c
|Number:\/emph\|
0020 3e 20 4e 75 6d 65 72 69 63 20 65 78 70 72 65 73 | Numeric
expres|
0030 73 69 6f 6e 20 74 68 61 74 20 63 6f 6e 74 61 69 |sion that
contai|
0040 6e 73 20 74 68 65 20 73 65 72 69 61 6c 20 74 69 |ns the serial
ti|
0050 6d 65 20 76 61 6c 75 65 20 74 68 61 74 20 69 73 |me value that
is|
0060 20 75 73 65 64 20 74 6f 20 72 65 74 75 72 6e 20 | used to
return |
0070 74 68 65 20 68 6f 75 72 20 76 61 6c 75 65 2e 0a |the hour
value..|
0080
paveljanik:/Volumes/Build/pavel/AQUA pavel$
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Spaces in new m51 strings
Please tell about this to documentation devel-list too. ain On Tue, Jul 7, 2009 at 23:59, Hristo Hristovico...@abv.bg wrote: For example in helpcontent2/source/text/sbasic/shared.pot #: 03030201.xhp#par_id3154366.8.help.text msgid emphNumber:/emph Numeric expression that contains the serial time value that is used to return the hour value. msgstr in helpcontent2/source/text/shared/05.pot #: 0001.xhp#bm_id3143272.help.text msgid bookmark_valuesupport on the Web/bookmark_value bookmark_valuegetting support/bookmark_value bookmark_valueforums and support/bookmark_value bookmark_valueWeb support/bookmark_value msgstr But there are a lot of such strings. I get this POT files from Pavel's location: ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/OpenOffice.org- DEV300_m51-POT.tar.gz -- Hristo Simeonov Hristov Leader of OpenOffice.org - Bulgarian GnuPG key 0xD0D895EB: 0282 D8D0 90D3 963F E57E B0A7 2670 88D9 D0D8 95EB On 7.7.2009 11:21:09 Rafaella Braconi wrote: Hi, On 07/06/09 20:39, Hristo Hristov wrote: Hi, I'm merging the new m51 strings and I see a lot of strings with spaces at the begining of the strings. Is these spcaces are normal? regards, can you please provide a couple of examples? Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] migration analysis tool on dev300_m49
Fix me when I'm wrong. There is no linguistic check any more several years and new strings appear 'as they are'. Yes it is hard to translate it, but at least we can make translations look and sound much better than original is. ;) ain On Wed, Jun 10, 2009 at 15:02, Frco. Javier Rialfjr...@cesga.es wrote: Hi: [Sorry if it's dupe] We, at galician localization team (gl.openoffice.org), are now updating our translation. We're planning this update for OOo 3.2 (november), but we're starting working now. We found that POT files from May, 26 (DEV300_m49) include a folder called migrationanalysis which contains ~900 strings.. Those original english strings are very poor, strange, and not under the same linguistic criteria... so it's very difficult to translate them. So, I'm asking myself, Are we working in the right branch of code??, or do you know in advance, which will be the branch to translate OOO 3.2?? I know that this's not the last branch, there'll be DEV300_m50 or whatever but, we cannot wait to work in our translation because we'll be on holidays during the summer and we have too much strings to translate in help section -- Frco. Javier Rial Rodríguez http://gl.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Product Name
This bug was filed long time ago as I wrote in previous letter and in last days there is some progress http://www.openoffice.org/issues/show_bug.cgi?id=88544 ain On Wed, May 20, 2009 at 11:02, Per Eriksson pereriks...@openoffice.org wrote: Hello Nguyen and Dick, Will this bug be filed or is the outcome that it shouldn't be fixed? I'm not sure I follow you on that part. :.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:. Best Regards Per Eriksson Co-Lead Swedish Language Project Marketing Contact Sweden OpenOffice.org Community Phone: +46 70 560 10 33 Email: pereriks...@openoffice.org Web: http://sv.openoffice.org/ Nguyen Vu Hung skrev: On Sun, May 17, 2009 at 11:06 PM, Dick Groskamp th.grosk...@quicknet.nlwrote: Nguyen Vu Hung schreef: Hi all, I've found this string in a .po file. Before you install the @WIKIEXTENSIONPRODUCTNAME@, ensure that StarOffice or OpenOffice.org uses a Java Runtime Environment (JRE). To check the status of the JRE, choose item type=menuitemTools - Options - StarOffice/OpenOffice.org - Java/item. Ensure that Use a Java runtime environment is marked and that a Java runtime folder is selected in the big listbox. If no JRE was activated, then activate a JRE 1.4 or later and restart StarOffice/OpenOffice.org. wiki.xhp#par_id4277169.help.text Is that a good idea to change StarOffice/OpenOffice.org to %PRODUCTNAME? Well, the idea is not bad at all. However: Staroffice and OpenOffice.org are two separate products with separated items all over. The fact is obvious enough: StarOffice users don't see OpenOffice and via versa. And Sun doesn't want StarOffice users wink their eyes and ask themself: What the heck is OpenOffice Therefore you probably should end up somewhere with a StarOffice where yoy expected an Openoffice.org I will call it bug then. Developing 2+ product lines are hard yet this kind of mistakes should/must be avoid. - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Latest OOO310 m5 based keyid builds
Many thanks, Ivo! ain On Mon, May 18, 2009 at 16:14, Ivo Hinkelmann ivo.hinkelm...@sun.com wrote: Hi all, I created installsets for OOO310 m11 , you can access them here: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/OOO310_m11_win/ Please take a look at the builds, I did not checked them! Cheers, Ivo Ain Vagula schrieb: Hi Ivo, as Pavel currently has troubles providing Windows builds, cant you please provide whole language builds for Windows? I'm just asking because having only language packs for Windows platform is a big step back, specially fos so important release as 3.1 is. Ain On Thu, May 7, 2009 at 17:05, Ivo Hinkelmann ivo.hinkelm...@sun.com wrote: Hi, the new windows keyid builds have been uploaded. Cheers, Ivo Ivo Hinkelmann schrieb: Hi all, sorry sorry ... I lost the focus on those builds due to the OOo 3.1 release mixup. I expect to uploaded the new windows builds tomorrow. Was it correct that only the windows builds were affected? Cheers, Ivo sophie schrieb: Hi Ivo, all, Jacqueline Rahemipour wrote: Hi Ivo, *, do you have any news on this? Same for german keyid build... Any news? it seems the keyid builds are broken. Kind regards Sophie - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] OO.o 3.10 Windows builds
I resend this message under new topic, in case someone didnt follow the offtopic conversation (my fault) Ain -- Forwarded message -- From: Ivo Hinkelmann ivo.hinkelm...@sun.com Date: Mon, May 18, 2009 at 16:14 Subject: Re: [l10n-dev] Latest OOO310 m5 based keyid builds To: dev@l10n.openoffice.org Hi all, I created installsets for OOO310 m11 , you can access them here: http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/OOO310_m11_win/ Please take a look at the builds, I did not checked them! Cheers, Ivo Ain Vagula schrieb: Hi Ivo, as Pavel currently has troubles providing Windows builds, cant you please provide whole language builds for Windows? I'm just asking because having only language packs for Windows platform is a big step back, specially fos so important release as 3.1 is. Ain On Thu, May 7, 2009 at 17:05, Ivo Hinkelmann ivo.hinkelm...@sun.com wrote: Hi, the new windows keyid builds have been uploaded. Cheers, Ivo Ivo Hinkelmann schrieb: Hi all, sorry sorry ... I lost the focus on those builds due to the OOo 3.1 release mixup. I expect to uploaded the new windows builds tomorrow. Was it correct that only the windows builds were affected? Cheers, Ivo sophie schrieb: Hi Ivo, all, Jacqueline Rahemipour wrote: Hi Ivo, *, do you have any news on this? Same for german keyid build... Any news? it seems the keyid builds are broken. Kind regards Sophie - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Product Name
I think I wrote an issue about this year ago or so
ain
On Sun, May 17, 2009 at 18:16, Nguyen Vu Hung vuhung16p...@gmail.com wrote:
Hi all,
I've found this string in a .po file.
Before you install the @WIKIEXTENSIONPRODUCTNAME@, ensure that StarOffice or
OpenOffice.org uses a Java Runtime Environment (JRE). To check the status of
the JRE, choose item type=menuitemTools - Options -
StarOffice/OpenOffice.org - Java/item. Ensure that Use a Java runtime
environment is marked and that a Java runtime folder is selected in the big
listbox. If no JRE was activated, then activate a JRE 1.4 or later and
restart StarOffice/OpenOffice.org.
wiki.xhp#par_id4277169.help.text
Is that a good idea to change StarOffice/OpenOffice.org to %PRODUCTNAME?
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remo...@gmail.dot.com
vuhung16plus%7bremove...@gmail.dot.com, YIM: vuhung16 , Skype:
vuhung16dg
A brief profile: http://www.hn.is.uec.ac.jp/~vuhung/Nguyen.Vu.Hung.html
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Product Name
http://qa.openoffice.org/issues/show_bug.cgi?id=88544
it was
ain
On Sun, May 17, 2009 at 18:25, Ain Vagula avag...@gmail.com wrote:
I think I wrote an issue about this year ago or so
ain
On Sun, May 17, 2009 at 18:16, Nguyen Vu Hung vuhung16p...@gmail.com wrote:
Hi all,
I've found this string in a .po file.
Before you install the @WIKIEXTENSIONPRODUCTNAME@, ensure that StarOffice or
OpenOffice.org uses a Java Runtime Environment (JRE). To check the status of
the JRE, choose item type=menuitemTools - Options -
StarOffice/OpenOffice.org - Java/item. Ensure that Use a Java runtime
environment is marked and that a Java runtime folder is selected in the big
listbox. If no JRE was activated, then activate a JRE 1.4 or later and
restart StarOffice/OpenOffice.org.
wiki.xhp#par_id4277169.help.text
Is that a good idea to change StarOffice/OpenOffice.org to %PRODUCTNAME?
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remo...@gmail.dot.com
vuhung16plus%7bremove...@gmail.dot.com, YIM: vuhung16 , Skype:
vuhung16dg
A brief profile: http://www.hn.is.uec.ac.jp/~vuhung/Nguyen.Vu.Hung.html
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Latest OOO310 m5 based keyid builds
Hi Ivo, as Pavel currently has troubles providing Windows builds, cant you please provide whole language builds for Windows? I'm just asking because having only language packs for Windows platform is a big step back, specially fos so important release as 3.1 is. Ain On Thu, May 7, 2009 at 17:05, Ivo Hinkelmann ivo.hinkelm...@sun.com wrote: Hi, the new windows keyid builds have been uploaded. Cheers, Ivo Ivo Hinkelmann schrieb: Hi all, sorry sorry ... I lost the focus on those builds due to the OOo 3.1 release mixup. I expect to uploaded the new windows builds tomorrow. Was it correct that only the windows builds were affected? Cheers, Ivo sophie schrieb: Hi Ivo, all, Jacqueline Rahemipour wrote: Hi Ivo, *, do you have any news on this? Same for german keyid build... Any news? it seems the keyid builds are broken. Kind regards Sophie - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Strings and the ~ character
By the way, oo.o automatically can add underlines (marking shortcuts) to strings when needed. There are only two exeptions: - main menu labels - some pushbuttons (usually those at bottom of dialogs, like Apply, Cancel, etc.) I personally removed all other shortcut markers except above ones from my translation, because when oo.o puts shortcuts, it will put unique shortcuts. For translator its quite hard to keep it right. Ain On Wed, May 6, 2009 at 17:15, Per Eriksson pereriks...@openoffice.org wrote: Hello, The Swedish team has a translation looking like this: Original string: ~Save Swedish translation: Spara But the underline is present in the OOo. So the displayed string IS ~Spara. Why is the tilde added to the Swedish translation even if it is not in the string? :.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:. Best Regards Per Eriksson Co-Lead Swedish Language Project Marketing Contact Sweden OpenOffice.org Community Phone: +46 70 560 10 33 Email: pereriks...@openoffice.org Web: http://sv.openoffice.org/ - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Labels strings in the UI
there is an issue about it: http://www.openoffice.org/issues/show_bug.cgi?id=96791 It will be handled in os127, which is verified but not yet integrated. So I'll suggest to wait a little. ain On Thu, Mar 26, 2009 at 07:07, Hristo Hristov ico...@abv.bg wrote: Hi, somebody maybe already discussed this but I need to be sure. There are a thousand and a half strings for some labels. Where I can find those strings in the OpenOffice.org suite. Should we translate them or they will be removed? Are they specific for one language or for every one? Best regards, -- Hristo Simeonov Hristov Leader of OpenOffice.org - Bulgarian GnuPG key 0xD0D895EB: 0282 D8D0 90D3 963F E57E B0A7 2670 88D9 D0D8 95EB - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] changed strings in 310_m4
On Fri, Mar 6, 2009 at 15:16, sophie sgautier@free.fr wrote: Hi Ivo, Ivo Hinkelmann wrote: Hi Sophie, it is quite simple, it is not allowed to add , move or modify strings or string identifier after the UI freeze! yes, it is... As all strings are just moved I will repair this, moving the translation and modifying the identifyer myself thus the translation will fit again. No need for translating or submiting any fixes for this issue. I've understand this, Beside, I don't like to do this (often) as it might cause errors and is totally out of any processes. All people that are involved are aware that this should not happend. and it takes you time where you have other things to do. My proposal was only to repeat again and again that this should not happen. But if you think that those who are involved will take care the next time, it's ok. It happened many many many times that such things are caused by Sun (TM) extensions late minute changes. Looks like these extensions are primary over all other office suite. ;) ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] changed strings in 310_m3
Changes brought by m1 in dbaccess module are reverted by m3. ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] Re: changed strings in 310_m3
also is deleted odd module, added by m2 ain On Fri, Feb 27, 2009 at 16:14, Ain Vagula avag...@gmail.com wrote: Changes brought by m1 in dbaccess module are reverted by m3. ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] changed strings in 310_m2
There is whole new module in strings: ../instsetoo_native/inc_ooolangpack/windows/msi_languages.po Fortunately only 4 strings. #: CustomAc.ulf#OOO_CUSTOMACTION_1.LngText.text msgid A newer version of [ProductName] was found. To install an older version, the newer version needs to be removed first. msgstr #: CustomAc.ulf#OOO_CUSTOMACTION_2.LngText.text msgid The same version of this product is already installed. msgstr #: CustomAc.ulf#OOO_CUSTOMACTION_3.LngText.text msgid An older version of [ProductName] was found. To install a newer version, the older version needs to be removed first. msgstr #: CustomAc.ulf#OOO_CUSTOMACTION_4.LngText.text msgid Please exit [DEFINEDPRODUCT] [DEFINEDVERSION] and the [DEFINEDPRODUCT] [DEFINEDVERSION] Quickstarter before you continue. If you are using a multi-user system, also make sure that no other user has [DEFINEDPRODUCT] [DEFINEDVERSION] open. msgstr ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Integration error : remove property
Anyways, this Object - Drawing Object exists also in m1 and I'm pretty sure that this came from m40 or earlier, because m40 - m41 there was no diff in strings. ain On Fri, Feb 20, 2009 at 07:43, Yuko Ohsumi yuko.ohs...@sun.com wrote: Hi Ain, Thank you for the reply. - From: Ain Vagula , Date: 02/20/09 02:12 PM : DEV300m41 is not for 3.1.0, it is made after branch and is for 3.2.0. For 3.1.0, after DEV300m40 came OOO310m1. It is my mistake. I will update the test cases in TCM. Thanks, Yuko ain On Fri, Feb 20, 2009 at 03:15, Yuko Ohsumi yuko.ohs...@sun.com wrote: Hi Ivo, Thank you for working on l10n build. There were some English messages that were added/changed in DEV300m41. However, the localization35 was built based on DEV300m40. so we cannot verify their translated messages in localization35. For example, the following menus were changed from DEV400m40 to DEV300m41. DEV400m40DEV400m41 Insert Object Insert Drawing Object Format Object Format Drawing Object If the new installation sets are built, is it possible to build it based on DEV300m41? If we have it, it would be helpful our testing. Thanks, Yuko - From: Ivo Hinkelmann - Sun Germany - , Date: 02/19/09 10:32 PM : Hi, looks like big mess happend there on the cws. I will take over the cws and check all errors tomorrow. I hope most of the issues can be fixed fast thus I can create new installation sets. Thanks for the detailed error reports! Cheers, Ivo sophie schrieb: Hi Andras, Andras Timar wrote: 2009.02.19. 11:02 keltezéssel, sophie írta: here is another one in the main menu Format: Hi Sophie, This is the tip of the iceberg, I'm afraid. You can check your French diff at the following URL: http://ftp.fsf.hu/OpenOffice.org_hu/devel/loc35-fr.diff.txt OLD: DEV300_m40 (freshly downloaded from Pootle) NEW: localization35 CWS source Thank you very much for the diff you provided. I've been able to find more English strings in the UI as your diff pointed :( Rafaella, this is not possible to test the cws in that condition, there is really to much bugs, it will take twice the time to check between integration errors and l10n errors. Kind regards Sophie Best regards, Andras - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Integration error : remove property
and more... you should avoid updating at this moment, because there is CWS pending for m2 that reverts string changes in dbaccess module, accidentally happened in m1. ain On Fri, Feb 20, 2009 at 07:43, Yuko Ohsumi yuko.ohs...@sun.com wrote: Hi Ain, Thank you for the reply. - From: Ain Vagula , Date: 02/20/09 02:12 PM : DEV300m41 is not for 3.1.0, it is made after branch and is for 3.2.0. For 3.1.0, after DEV300m40 came OOO310m1. It is my mistake. I will update the test cases in TCM. Thanks, Yuko ain On Fri, Feb 20, 2009 at 03:15, Yuko Ohsumi yuko.ohs...@sun.com wrote: Hi Ivo, Thank you for working on l10n build. There were some English messages that were added/changed in DEV300m41. However, the localization35 was built based on DEV300m40. so we cannot verify their translated messages in localization35. For example, the following menus were changed from DEV400m40 to DEV300m41. DEV400m40DEV400m41 Insert Object Insert Drawing Object Format Object Format Drawing Object If the new installation sets are built, is it possible to build it based on DEV300m41? If we have it, it would be helpful our testing. Thanks, Yuko - From: Ivo Hinkelmann - Sun Germany - , Date: 02/19/09 10:32 PM : Hi, looks like big mess happend there on the cws. I will take over the cws and check all errors tomorrow. I hope most of the issues can be fixed fast thus I can create new installation sets. Thanks for the detailed error reports! Cheers, Ivo sophie schrieb: Hi Andras, Andras Timar wrote: 2009.02.19. 11:02 keltezéssel, sophie írta: here is another one in the main menu Format: Hi Sophie, This is the tip of the iceberg, I'm afraid. You can check your French diff at the following URL: http://ftp.fsf.hu/OpenOffice.org_hu/devel/loc35-fr.diff.txt OLD: DEV300_m40 (freshly downloaded from Pootle) NEW: localization35 CWS source Thank you very much for the diff you provided. I've been able to find more English strings in the UI as your diff pointed :( Rafaella, this is not possible to test the cws in that condition, there is really to much bugs, it will take twice the time to check between integration errors and l10n errors. Kind regards Sophie Best regards, Andras - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] changed strings in 310_m1
On Fri, Feb 13, 2009 at 22:41, André Schnabel andre.schna...@gmx.net wrote: Hi, sophie schrieb: Hi Ain, Ain Vagula wrote: In dbaccess/ui/dlg.po 8 strings changed since m40. Only removal of fuzzy-tags was necessary. Thank you for following this and inform us :) Sorry, but I cannot see any point to put a smiley here. Indeed thanks to Ain as he is only reporting this but not the guilty one. I really love people smiling, even after bad news :) And I dont remember, that I even have brought some good news, for good news there is a marketing team. ;) ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Register Latvian lokalization project at Pottle
On Mon, Feb 9, 2009 at 16:36, Viesturs Zarins viesturs.zar...@mii.lu.lv wrote: Hello Aijin and others, I'm Viesturs Zarins, the new lead for OpenOffice localization project for Latvian language. I'm currently taking over the project. The previous effort was all but dead for about 3 yeas and much has changed since then. Currently I have successfully merged the old translations with the new R40 pot files. We have completed all Writer files (SW folder) and would like to test the result. Current PO files are available from Latvian project CVS: http://lv.openoffice.org/source/browse/lv/src/po/ . The old process seems very cumbersome and I would like to move the project over to Pootle. Also I would like to know how much do we need to translate before some initial builds can be made? Welcome to project. I remember when Gints started localization, he made a lot of work in short time. And it was very sorry to see that translation was abandoned in last years. I hope you will have well translated Latvian OO.o soon. :) ain - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Confusing text...
Help - Index tab
You see these entries separated by semicolon together only in input
box. In list entries are sorted by first term and second terms are
indented.
ain
On Mon, Feb 9, 2009 at 06:39, Nguyen Vu Hung vuhung16p...@gmail.com wrote:
On Sat, Feb 7, 2009 at 1:16 AM, Uwe Fischer u...@openoffice.org wrote:
do not remove the tags. And do not look at line breaks in the po file. The
source files are xml files with tags. I suppose that the *.po file includes
the tags just as a reference to translators so that they know the context of
the text strings.
The line breaks that you see do not have any meaning in the xml source
file. They are artifacts of the po file display. Bad tool, I would say. Not
really useful for editing xml source files.
I can't imagine how will it look like.
Can you send a screenshot of the window that contains this text?
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remo...@gmail.dot.com
vuhung16plus%7bremove...@gmail.dot.com, YIM: vuhung16 , Skype:
vuhung16dg
A brief profile: http://www.hn.is.uec.ac.jp/~vuhung/Nguyen.Vu.Hung.html
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Confusing text...
Uwe, you understood wrong. He (?) removed tags here, in list message to make string error better visible: instead to jumping;to text should be to text;jumping or at least jumping;to text ain On Fri, Feb 6, 2009 at 18:16, Uwe Fischer u...@openoffice.org wrote: Hi, On 02/06/09 13:06, Nguyen Vu Hung wrote: On Fri, Feb 6, 2009 at 8:48 PM, Uwe Fischer u...@openoffice.org wrote: Hi, On 02/06/09 12:15, Nguyen Vu Hung wrote: Hi all, Is that jumping to jumping correct? ... However, I did mean that, if you remove all the tags, the Help will look like: --- Navigator; overview in texts hyperlinks;jumping to objects;quickly moving to, within text frames;jumping to tables;jumping to headings;jumping to pages;jumping to jumping;to text elements overviews;Navigator in text documents - So I think that in the 3rd line from the bottom, to jumping and to text should be swap. do not remove the tags. And do not look at line breaks in the po file. The source files are xml files with tags. I suppose that the *.po file includes the tags just as a reference to translators so that they know the context of the text strings. The line breaks that you see do not have any meaning in the xml source file. They are artifacts of the po file display. Bad tool, I would say. Not really useful for editing xml source files. Uwe -- uwe.fisc...@sun.com - Technical Writer StarOffice - Sun Microsystems, Inc. - Hamburg, Germany http://documentation.openoffice.org/ http://wiki.services.openoffice.org/wiki/Documentation http://blogs.sun.com/oootnt http://user.services.openoffice.org/en/forum - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Confusing text...
oops I deleted old messages and could not check out and it seemed obvious... I apologize ain On Fri, Feb 6, 2009 at 21:08, Dick Groskamp th.grosk...@quicknet.nl wrote: Ain Vagula schreef: Uwe, you understood wrong. He (?) removed tags here, in list message to make string error better visible: instead to jumping;to text should be to text;jumping or at least jumping;to text ain Or did you Ain ? (misunderstod that is ;-) ) If I place all strings within their own tags (only in this message to make visibility/readability better) there is no: to jumping;to text (see below) helpcontent2/swriter/guide.po navigator.xhp#bm_id3154897.help.text bookmark_valueNavigator; overview in texts/bookmark_value bookmark_valuehyperlinks;jumping to/bookmark_value bookmark_valueobjects;quickly moving to, within text/bookmark_value bookmark_valueframes;jumping to/bookmark_value bookmark_valuetables;jumping to/bookmark_value bookmark_valueheadings;jumping to/bookmark_value bookmark_valuepages;jumping to/bookmark_value bookmark_valuejumping;to text elements/bookmark_value bookmark_valueoverviews;Navigator in text documents/bookmark_value So I think evrything should stay as it is. I don't see any mishap -- DiGro Windows XP Professional SP2 and OOo 3.0 Scanned with: Ziggo uitgebreide internetbeveiliging - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Deadline for OOo 3.0 final translations
m40 contains tasks for 3.1 and as there is no branch for 3.1 still, I'd assume that m40 is targeted for 3.1. http://eis.services.openoffice.org/EIS2/cws.rss.CWSAnnounceNewsFeed/mws?guid=7116 ain On Tue, Jan 27, 2009 at 10:20, Frco. Javier Rial fjr...@cesga.es wrote: I'll assume that version targeted for OpenOffice.org 3.1 is m39 as it was planned.. Frco. Javier Rial escribió: I know that m40 contains changed string (about one hundred strings changed in UI), but what I want to ask is: is DEV300_m40 the version target for 3.1 or still remains m39 for OOO3.1 (as Rafaella Braconi said)?? Quoting Rafaella: http://l10n.openoffice.org/servlets/ReadMsg?list=devmsgNo=10265 Dear All, this is to inform you that the m39 that we were targeting as the *translation* milestone for the 3.1 is not yet ready. I know that many of you are waiting for the latest milestone to start translation. However, I would encourage you to translate or continue to translate (if you haven't done so already) using the available Andras Timar escribió: 2009.01.26. 9:42 keltezéssel, Frco. Javier Rial írta: I' ve already done the job for DEV300_m39 but, on January 23, DEV300_m40 appeared. Is this the version to translate for OOo3.1?? Thanks DEV300_m40 contains new and changed strings compared to DEV300_m39. See http://ftp.fsf.hu/OpenOffice.org_hu/devel/m39_m40.comp.txt Regards, Andras - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org -- Frco. Javier Rial Rodríguez Técnico Centro de Referencia e Servizos de Software Libre www.mancomun.org Praza de Europa, nº 10A, 6ºB 15707Santiago de Compostela (Galiza/ES) Tel/ Fax: (0034) 981 957 867/ 881 999 113fjrial @ mancomun.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] How to translate Accelerator-keys in Office.po on Pootle
This should not be translated at all, it is an issue. Ain On Mon, Dec 15, 2008 at 13:43, Dick Groskamp th.grosk...@quicknet.nl wrote: Would like to know how the Accelerator-keys in Office.po are to be translated. Source (for instance) is: .uno:SelectAll Translation could be: A .unoAllesselecteren B Alles selecteren C .unoAlles selecteren I'm in the dark about the visible use of these keys and, if done wrong, would it break functionality ? If the source is to be used as the visible use of the key I would translate this example as: Alles selecteren. Since I'm not sure if that breaks functionality since it is a Command.value I would like someone to shine some light on this. So, please enlighten me -- DiGro Windows XP Professional SP2 and OOo 2.4 Scanned with Multikabel Internet Security Plus - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IRC Meeting on Quality assurance of l10n builds
I'd like to bring these issues up in meeting (maybe someone helps to complete the list): http://www.openoffice.org/issues/show_bug.cgi?id=96909 http://www.openoffice.org/issues/show_bug.cgi?id=96791 http://www.openoffice.org/issues/show_bug.cgi?id=96934 http://www.openoffice.org/issues/show_bug.cgi?id=86901 ain On Tue, Dec 9, 2008 at 18:34, Rafaella Braconi rafaella.brac...@sun.com wrote: Dear All, I would like to invite you to an l10n/QA meeting on IRC to discuss in more detail the topic: Quality assurance of l10n builds. Date/Time: Tuesday, December 16th at 5:00 pm UTC Channel: IRC network FreeNode, #ooonlc http://wiki.services.openoffice.org/wiki/IRC_Meetings#Logistics See you on IRC next Tuesday, Rafaella - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Help for German strings
On Wed, Dec 3, 2008 at 14:47, Eike Rathke [EMAIL PROTECTED] wrote: Hi sophie, On Monday, 2008-12-01 18:16:27 +0100, sophie wrote: It seems that the texts are names of products delivered by Avery. Brand Avery seems to list products available in the U.S. Brand Avery Zweckform seems to list ones available in Germany. Do we really need to translate them? If you want to have them in your language in the UI you need to translate them and labels are often used by companies. But what is incorrect is to have German strings as source for our translation. I don't know who has approved this but it's a mistake for me. Depends on ... ;-) I don't know whether you can buy the Zweckform labels anywhere else than in Germany, and I also don't know a translation of the examples given, or if there exists one if they were sold abroad. Heck, I'm a native German speaker and I even don't know the German terms used with those labels ;-) So, it might be better to not translate them, unless there are official translations used by the Zweckform company for packaging. For the Avery labels probably native English terms do exist. You can buy Zweckform labels in most of European countries. Packages for export have usually labels in all languages of target region and also English one as far I remember. In most of countries you cannot sell any goods without translated label and/or usage guide. ain
Re: [l10n-dev] Help for German strings
Are you sure, you have to translate it? Looks like someone merged all paper and label formats into translatable strings not thinking at all (or not much). Maybe there is an issue about that or should we file one? About 2000 strings, where some hundreds are in German, is a piece of cake. ;) ain On Mon, Dec 1, 2008 at 18:04, sophie [EMAIL PROTECTED] wrote: Hi all, There is some German strings that I'm not able to translate, anybody here can give me some hints on them? The word between brackets is the one I don't understand. 32011 Visitenkarten, blanko, [schnittgestanzt] 6021 [Sichtreiter]-Etiketten, Stick+Lift J8871 Inkjet-Magnet-[Schilder]** 083271/7 [Ordnerrückeneinsteckschilder] 1681 [Kartonrückenschilder, schmal] 1685 [Papierrückenschilder] selbstkl., breit LP734 Ordner-[Einsteckschild] Thanks in advance Kind regards Sophie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] string changes in m35
about 1000 new entries in officecfg - label, business card, etc. formats ain
[l10n-dev] pot files for dev300_m29
changes in 3 modules: - chart: 4 strings - filter/pdf: 4 strings - sfx2/dialog: 47 strings attention: m29 is first milestone in oo.o 3.1 tree, so no panic ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for DEV300_m28
no changes at all ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m27
no visible changes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m26
44 strings need some work in modules: instsetoo_native officecfg scp2 sdext svx sysui Like UI freeze never happened... ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] pot files for dev300_m25
dev300 should still be 3.0 tree, beb is only branch for beta2 as far I understand ain On Tue, Jul 15, 2008 at 8:48 AM, Robert Ludvik [EMAIL PROTECTED] wrote: Ain Vagula pravi: One new module: scp2/source/sdkoo, contains 2 strings, one of them very ugly. The SDK provides all necessary tools, examples and documentation to program with and for the office. Interesting, is this office some office room or some (unknown) office software? ain Hi Which m will be for 3.0 stable? m21, which is BEB based on? Regards Robert Ludvik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m25
One new module: scp2/source/sdkoo, contains 2 strings, one of them very ugly. The SDK provides all necessary tools, examples and documentation to program with and for the office. Interesting, is this office some office room or some (unknown) office software? ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Re: pot files for dev300_m24
and one removed 1-string file in sdext ain On Tue, Jul 8, 2008 at 11:51 PM, Ain Vagula [EMAIL PROTECTED] wrote: 2 changed strings, one in sw, one in svx, the last is very visible - about classic icon styles ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Error in DEV300_m23 new original string: fails gsicheck
you can download gsicheck 1.9 or just ignore the error. ain On Sat, Jul 5, 2008 at 11:35 AM, Clytie Siddall [EMAIL PROTECTED] wrote: Hi everyone :) I've downloaded our complete DEV300_m23 Pootle files and converted them to SDF format, and gsicheck reports this error: ___ Error: Line format, Line 118122, UniqueID sdext/source\presenter\registry\data\org\openoffice\Office\Addons.xcu/value/.Addons.AddonUI.OfficeMenuBarMerging.org.openoffice.Office.PresenterScreen.org.openoffice.Office.PresenterScreenCommand1.MenuItems.org.openoffice.Office.PresenterScreenAbout/Title//: GID and LID may only be 125 chars long each! en-US ___ against this newly-introduced original string: ___ sdext source\presenter\registry\data\org\openoffice\Office\Addons.xcu 0 value .Addons.AddonUI.OfficeMenuBarMerging.org.openoffice.Office.PresenterScreen.org.openoffice.Office.PresenterScreenCommand1.MenuItems.org.openoffice.Office.PresenterScreenAbout Title 0 en-US About Presenter Screen 2002-02-02 02:02:02 ___ gsicheck reports the same error against the translated string, but it's not a translation error, since it appears to be about the length of the ID string. What do we do about this? :S from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] 3.0 deadline
Is today submission date for 3.0 translations or it is not? http://wiki.services.openoffice.org/wiki/OOoRelease30 tells: # code_freeze, last regular translation delivery: July 4th, 2008 http://wiki.services.openoffice.org/wiki/Translation_for_3.0 tells: # June 27th - Translation delivery date for OOo 3.0 final # July 4th - last delivery date for translation and language fixes ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] 3.0 deadline
On Fri, Jun 27, 2008 at 2:51 PM, Rafaella Braconi [EMAIL PROTECTED] wrote: Hi Ain, Ain Vagula ha scritto: Is today submission date for 3.0 translations or it is not? yes today is the delivery date for all the teams which have finished translation. Since the import and integration process takes some time, it is really convenient to start delivering today. http://wiki.services.openoffice.org/wiki/OOoRelease30 tells: # code_freeze, last regular translation delivery: July 4th, 2008 http://wiki.services.openoffice.org/wiki/Translation_for_3.0 tells: # June 27th - Translation delivery date for OOo 3.0 final # July 4th - last delivery date for translation and language fixes If there are some teams who are a bit behind with their translation and or bug fixes, they can deliver on July 4th, bests at 10:00 am CEST. This very last delivery date should really be used to submit translations if the team cannot deliver before. Earlier the engineer who was responsible for integration wrote itself a message to list with delivery dates and details and we could trust him (Vladimir or Ivo). Now the information is in two different wiki articles and differs in some details (or is wrong at all - like with Beta1, where assignee in wiki was Vladimir but Ivo did integration - a lot of redirected issues). Can we please have earlier situation back to keep things understandable for everyone? ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Changing existing style format names
On Fri, Jun 27, 2008 at 8:58 PM, Per Eriksson [EMAIL PROTECTED] wrote: Hello, The Swedish native lang group is concidering changing the name for the Headline styles to a new name. Instead of Överskrift 1 - 10 we are concidering: Rubrik 1 - 10 If we do this change, will both sets of styles be visible if you would open an old document? (created with the old names)? no, when you look at document source xml file, you'll see that default styles are saved with en-us names and localized names are taken from translation. this rule is not always about .doc files because in mso this feature is buggy ain
Re: [l10n-dev] Sheet tabs in Calc: OOo is haunted
On Thu, Jun 26, 2008 at 8:56 AM, Clytie Siddall [EMAIL PROTECTED] wrote: Hi everyone :) I have sort of solved the problem of why the sheet tabs weren't localized in my spreadsheet. It looks like somehow, files from previous versions of OpenOffice.org retain some properties of those versions. In DEV300_m17 (Mac OSX Intel), I have two spreadsheets open: 1. spreadsheet I created in an older version: the sheet tabs _are not_ localized 2. spreadsheet I created in this version: the sheet tabs _are_ localized. While this is reassuring for our 3.0 release, I find it rather puzzling. I'm also concerned that users who have created files in previous versions may encounter this problem. It may even affect other aspects of the files. Does anyone here understand why this would happen? :o I think sheet names are saved as they are created. Sheet name string gives sheet a name in _moment of creation_ of new empty document and so the names are saved. It's quite logical, that existing sheet names will not change when changing UI language, because you can have formulas or references containing sheet names. This string (translated or not) affects only new spreadsheets, created by current version. ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m21
7 strings that need some work - in modules desktop, officecfg and svx ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] splitting huge help files
We had such a conversation in translate-devel list: Clytie wrote: Splitting help files: How did your team split the large file? Did someone just choose to break it at a certain point? What I'm really after is is their an automated way to do this? Dwayne wrote: Manually, arbitrarily. No rule. I think he actually split them by size, e.g. into four equally-sized pieces. It makes more sense to split them by content, but that would require someone going through and putting in markers. Arbitrary splits are hard to automate I'm afraid :( I wrote: Big help po-files are very discouraging for translators ;) Maybe it makes sense to split files so: when xhp-file begins with number, then by first 6 numbers, when with letter, then by first letter. First 6 numbers means that every po-file will contain logically splitted help part, first letter means nothing but makes just guide.po files smaller. Dwayne wrote: Sounds like we're on to something. This looks like it might be quite easy to achieve. Could I ask for a bug report and my hope is that tomorrows bug day can help tackle it if we have some active testing. I think: This needs agreement from the rest of translators, using po-format (or whatever format converted by translate-tools). But I think also it is worth testing, because smaller files are easier to handle and ... it just makes good feeling to finish a file. With 5000-strings file it feels that I will never finish it... Testing, because i have no idea at moment how much files it will generate and how the result will look like. Ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Re: splitting huge help files
On Thu, Jun 19, 2008 at 3:59 PM, Ain Vagula [EMAIL PROTECTED] wrote: We had such a conversation in translate-devel list: Clytie wrote: Splitting help files: How did your team split the large file? Did someone just choose to break it at a certain point? What I'm really after is is their an automated way to do this? Dwayne wrote: Manually, arbitrarily. No rule. I think he actually split them by size, e.g. into four equally-sized pieces. It makes more sense to split them by content, but that would require someone going through and putting in markers. Arbitrary splits are hard to automate I'm afraid :( I wrote: Big help po-files are very discouraging for translators ;) Maybe it makes sense to split files so: when xhp-file begins with number, then by first 6 numbers, when with letter, then by first letter. First 6 numbers means that every po-file will contain logically splitted help part, first letter means nothing but makes just guide.po files smaller. umm, when using 6 numbers for sorting, there will be 1500 po files... when using 5 numbers, then about 700 and including many one-liners. Even this will be overhead... ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] New l10n builds
On Mon, Jun 16, 2008 at 5:30 PM, Olivier Hallot [EMAIL PROTECTED] wrote: Hi Ivo Where else old strings are missing beside Base? Fo the time being, I have: File - New - Templates and Documents http://qa.openoffice.org/issues/show_bug.cgi?id=89698 File - Wizzard - Document Converter reported many times: eg. in http://qa.openoffice.org/issues/show_bug.cgi?id=89977 ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m19
paveljanik ain: m19 POT: no changes. ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] %s-click variable
as ctrl is here variable you can move it around in string and translate correctly ain On Mon, Jun 9, 2008 at 5:15 PM, sophie [EMAIL PROTECTED] wrote: Hi all, In the last m17 files uploaded in Pootle, in openoffice_org/sw/source/ui/utlui.po, there is #: initui.src#RID_SW_SHELLRES.STR_HYPERLINK_CLICK.string.text msgid %s-click to open hyperlink msgstr Cliquer-%s pour ouvrir un hyperlien What does %s stand for ? If this is for a command, like Ctrl (I imagine), this is untranslatable in French because Ctrl-click doesn't mean anything in French. You need to be more precise like 'Click while pressing Ctrl key', a verb can't be contracted with a command. This variable is also used in docvw.po for SmarTags. Kind regards Sophie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m18
minor changes in several modules (connectivity, dbaccess, officecfg, sw, sxv) - not more than dozen strings need some work (mostly to cancel fuzzy status). alas, binfilter submodule is integrated in scp2, with 2 strings only but I dont believe it is translation subject. ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m17
several new stings about Improvement Program and spelling grammar. affected modules: officecfg/registry/data/org/openoffice/Office/UI officecfg/registry/data/org/openoffice/Office sfx2/source/dialog svtools/source/contnr svx/source/dialog svx/source/options ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Submitting translations for Beta 2
On Tue, Jun 3, 2008 at 12:21 PM, dooteo [EMAIL PROTECTED] wrote: Hi Rafaella, Jatorrizko mezua: ar., 2008-06-03 10:43 +0200, egilea: Rafaella Braconi Hi Dooteo, dooteo wrote: Hi Rafaella, On '' page it ask us to 'remove non translated strings from the sdf file'. I know it will be a silly wuestion, but for sure: did it means to remove from sdf file all en-US strings which are not translated? in the gsi file the strings are in pairs: Source en_US Target *translation*(example) When the target is not translated you have: Source en_US Target en_US What we are asking you is to delete all pairs (source + target) which have not been translated. Not sure if this information is clarifying or confusing things :-\ M... let me explain step by step :) GSI/SDF file (created with toolkit 1.1.1) have pairs like (when messages are translated) Source en_US (#1 source message) Target eu (#1 translated message) Source en_US (#2 source message) Target eu (#2 translated message) Source en_US (#3 source message) Target eu (#3 translated message) (...) Source en_US (#n source message) Target eu (#n translated message) but if there are some not translated messages in PO file, converting PO files into a GSI file, GSI could have next pairs (ie. #2 and #3 message) Source en_US (#1 source message) Target eu (#1 translated message) Source en_US (#2 source message) Source en_US (#3 source message) Source en_US (#4 source message) Target eu (#4 translated message) (...) Source en_US (#n source message) Target eu (#n translated message) this example right above is normal behaviour. from such GSI you can recreate set of po files when you need (example when switching between toolkit major versions), where translated messages are translated and untranslated messages are untranslated. When you dont have 'single' en-us lines, you will miss all untranslated messages and when you have filled pairs, you will go crazy searching what is translated in relity and what is not. ;) ain
Re: [l10n-dev] Submitting translations for Beta 2
I dont believe it. which version of toolkit you are using? default behaviour is not to insert language lines, when untranslated. I opposite case it makes resulting sdf file useless for backup purpose. ain On Mon, Jun 2, 2008 at 11:03 PM, dooteo [EMAIL PROTECTED] wrote: Ouch! I'd realice that untranslated messages are inserted by po2oo into GSI file as translated ISO code too (in my case there appears english messages in 'eu' code lines). Forget this message... and I'm sorry bout my fault... Anyway, I wrote a little script to delete untranslated strings from GSI/SDF file. So, if somebody needs it, please feel free to ask me :) Best regards, dooteo Jatorrizko mezua: al., 2008-06-02 18:54 +0200, egilea: dooteo Upps! On '' page it ask us to 'remove non translated strings from the sdf file'. I wanna mean: How_to_deliver_translated_files page :) I know it will be a silly wuestion, but for sure: did it means to remove from sdf file all en-US strings which are not translated? And, as Goran asked before, should we based on DEV_m15? Thanks and best regards, Dooteo Jatorrizko mezua: al., 2008-06-02 17:21 +0200, egilea: Goran Rakic Thanks, great news! Should I send translated SDF file from BEA300_m2 or from DEV300_m15 milestone for this Beta 2 release? Regards, Goran У пон, 02. 06 2008. у 13:50 +0200, Rafaella Braconi пише: Goran, good news. Yes you can submit the translated files for Beta 2. Deadline is June 4th 10:00 am CEST. Please proceed as follows, http://wiki.services.openoffice.org/wiki/Translation_for_3.0#How_to_deliver_translated_files Regards, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Which builds should we test?
On Sat, May 31, 2008 at 11:25 AM, Clytie Siddall [EMAIL PROTECTED] wrote: Hi everyone :) I'm a little confused about codelines. Thanks to Pavel's excellent presentation [1], I do understand that we branch the main codeline for releases (and branch it even more for child workspaces), but I don't know if the main codeline also includes the newer features and translations. For example, we have been testing the DEV300 codeline, which will eventually become the OpenOffice.org 3.0 release. The BEA300 codeline so far has contained the 3.0 Beta m1 and m2 builds. But the OOH680 main codeline, which continues to develop, does it also include all the new code and updated translation of OpenOffice.org 3.0? Is it, in fact, the ongoing development codeline? This is 2.4 branch for 2.4.1 and there is nothing for 3.0 ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m15
A lot of changed or new strings in readme (hm, was it worth to mess with last minute updates translation in beta???). I ignored the issue, seems like reasonable decision. 1-2 updates in sc, sw, svx, vcl. Ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m14
about 50 changed strings alltogether (24 in help), mostly about extensions and online update ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m13
About 85 new or changed strings, including new module - sdext/source/presenter. Also significant changes in chart module. ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Re: pot files for dev300_m13
see also http://www.openoffice.org/issues/show_bug.cgi?id=89566 when checking translations On Fri, May 16, 2008 at 7:06 PM, Ain Vagula [EMAIL PROTECTED] wrote: About 85 new or changed strings, including new module - sdext/source/presenter. Also significant changes in chart module. ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Request for more space in dialogs
Therefore we have assignees in our project, to redirect issues to original components. When issue appears in one on several localized versions ut not in en-us version, it is surely worth that l10n team is informed about state of these issues. ain On Tue, May 13, 2008 at 11:37 AM, sophie [EMAIL PROTECTED] wrote: Hi Khirano, Kazunari Hirano a écrit : Hi Eike and Sphie, On Mon, Apr 28, 2008 at 9:03 PM, Eike Rathke [EMAIL PROTECTED] wrote: The available space for a dialog's radio button text IIRC is given in the resource file, it should be possible to enlarge that to the width of the group column if there is no extra element like a spin button to the right. Please file an issue. Yuko Osumi has worked hard for us to find truncated issues and kindly filed the following issues: Thanks :) 89160 Button's labels are truncated in Resolve Conflicts dialog 89161 Japanese message for Collate is truncated in Print dialog 89164 Ja message for 200 DPI (default) is truncated in Option dialog 89165 Ja message for Single page and Book mode are truncated in Zoom View Layout dialog I've open a similar issue for the Zoom dialog : http://www.openoffice.org/issues/show_bug.cgi?id=88829 However, I'm not sure in which component this should go, Framework or GSL? but I don't think it's l10n issues. I've several other issues to open too, I'll check if they are the same as yours, but I'll wait first to be sure of the component. Hope we get more space soon :) Yes, me too :) Kind regards Sophie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] oo2po current Pootle files
hm? http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/ ain Clytie Siddall wrote: Whoops, another question... On 07/05/2008, at 11:36 AM, Aijin Kim wrote: Current Pootle content was updated with DEV300_m3 milestone on March 13th. That's pretty old, nearly two months. Are you sure that's the right milestone (and date)? Also, if this is the correct milestone, where can I find the en_US.sdf file? Pavel's server only has DEV300_m9-m11, and BEA300_m1-m2. Thanks again for the help. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] oo2po current Pootle files
pot tarballs contain also en-us.sdf ain Ain Vagula wrote: hm? http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/ ain Clytie Siddall wrote: Whoops, another question... On 07/05/2008, at 11:36 AM, Aijin Kim wrote: Current Pootle content was updated with DEV300_m3 milestone on March 13th. That's pretty old, nearly two months. Are you sure that's the right milestone (and date)? Also, if this is the correct milestone, where can I find the en_US.sdf file? Pavel's server only has DEV300_m9-m11, and BEA300_m1-m2. Thanks again for the help. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] oo2po current Pootle files
when you look at folder structure, you'll see that there isnt such file helpcontent2/scalc.po, is helpcontent2/source/text/scalc.po (and all other help files). Seems like you need to create similar folder tree in your computer, ie. add missing parent directiories. ain Clytie Siddall wrote: Hi everyone :) I'm trying to update our file for Pavel's builds, so I need to convert our current Pootle translation (interface and help) to a GSI file. In doing that, I need to use the correct en_US.sdf file. This is the latest update info I can find here about the Pootle files: On 21/04/2008, at 11:08 PM, Ain Vagula wrote: [l10n-dev] pot files for dev300_m10 no changes since m9 ain so I used the DEV300_m10 en_US.sdf file from Pavel's server, and Translate Toolkit 1.1.1. However, the conversion did not go well. There were a lot of errors like this: ___ po2oo: warning: No template at None. Skipping helpcontent2/scalc.po. ___ it seemed to skip _all_ the Help files. And a few errors like this: ___ couldn't find key sbabrw.src#STR_DSBROWSER_TITLE.string from po in 38 keys #: sbabrw.src#STR_DSBROWSER_TITLE.string.text msgid Data sources view msgstr Xem nguồn dữ liệu ___ The resulting GSI file was much smaller than it should have been, so something definitely didn't work. I'm wondering if I have the correct en_US.sdf file for the current Pootle files. Do I? (The Toolkit still tells me I don't have lxml, although I have installed both py-lxml and py25-lxml, but in this latest version the non-XML conversions seem to run OK without lxml.) Thanks for any help you can offer with this. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] oo2po current Pootle files
xsltfilter.xhp was splitted to several files around March 8th according my cvs log. So seems that helpcontent in your Pootle is older. ain Clytie Siddall wrote: I still think I have a mismatch between the en_US.sdf file (DEV300_m10) and the files I downloaded from Pootle last night (UI) and today (Help), and combined into the appropriate tree. When I run the conversion po2oo, there are pages and pages listing individual strings that can't be found in the template. e.g. ___ couldn't find key xsltfilter.xhp#par_idN10D0E.help from po in 2470 keys #: xsltfilter.xhp#par_idN10D0E.help.text msgid This identifier is used to detect the file type on import. msgstr Dấu nhận dạng này được dùng để phát hiện kiểu tập tin khi nhập khẩu. ___ So somehow the DEV300_m10 en_US.sdf file and the current Pootle files don't match. :( Has anyone else done the po2oo conversion in the last day or so with current Pootle files? I've never had this problem before. Usually, my Toolkit processes work like a charm. Help ! Clytie On 06/05/2008, at 11:13 PM, Clytie Siddall wrote: On 06/05/2008, at 10:23 PM, Ain Vagula wrote: when you look at folder structure, you'll see that there isnt such file helpcontent2/scalc.po, is helpcontent2/source/text/scalc.po (and all other help files). Seems like you need to create similar folder tree in your computer, ie. add missing parent directiories. Drat, I should have remembered that. :S Thankyou. :) BTW, does anyone know why helpcontent2 has those extra layers? Is it hiding from anything? (Overdue taxes? Spellchecks?) Clytie ain Clytie Siddall wrote: Hi everyone :) I'm trying to update our file for Pavel's builds, so I need to convert our current Pootle translation (interface and help) to a GSI file. In doing that, I need to use the correct en_US.sdf file. This is the latest update info I can find here about the Pootle files: On 21/04/2008, at 11:08 PM, Ain Vagula wrote: [l10n-dev] pot files for dev300_m10 no changes since m9 ain so I used the DEV300_m10 en_US.sdf file from Pavel's server, and Translate Toolkit 1.1.1. However, the conversion did not go well. There were a lot of errors like this: ___ po2oo: warning: No template at None. Skipping helpcontent2/scalc.po. ___ it seemed to skip _all_ the Help files. And a few errors like this: ___ couldn't find key sbabrw.src#STR_DSBROWSER_TITLE.string from po in 38 keys #: sbabrw.src#STR_DSBROWSER_TITLE.string.text msgid Data sources view msgstr Xem nguồn dữ liệu ___ The resulting GSI file was much smaller than it should have been, so something definitely didn't work. I'm wondering if I have the correct en_US.sdf file for the current Pootle files. Do I? (The Toolkit still tells me I don't have lxml, although I have installed both py-lxml and py25-lxml, but in this latest version the non-XML conversions seem to run OK without lxml.) Thanks for any help you can offer with this. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Request for more space in dialogs
Maybe I misunderstood something but I've heard that automatically resizing dialogs are work in progress? ain On Thu, Apr 24, 2008 at 12:03 PM, Rafaella Braconi [EMAIL PROTECTED] wrote: Hi Sophie, So better put a question mark in it and a 'Guess what?' in the tip ;) I'm kidding too, but as said Andre, it doesn't help to have a button you can't understand. I know it's difficult, but may be the solution for us would be to work with the English linguistic team to find a formulation suitable for the more language as possible? or is it another utopia? I am glad you brought up this very well known and old issue :-) . Every time the correct translated string has not enough space in a dialog this is CLEARLY a BUG. This is in fact bad user interface design. Asking the localizers to make the translated strings shorter is - in most cases - not an option. Working with the user designer team? IMHO, I think that filing issues, for every dialog in which we do not have enough space, would remind them that the user interface in most case is not only English ;-) and that in case they want to see how much space for the translation is needed they should ask at least the Brazilian or French team to check if they have enough space for their translation :-) . Kind Regards, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m10
no changes since m9 ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m9
A few changes: - 14 changed or new strings in Readme - ~5 strings in vcl ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m8
- A few changes in writer - about notes, 4 strings. - MediaWiki extension help strings moved into right place. Strange ways fma has uploaded changes to readme into issuezilla and whole 81 times. I really hope that in future rest of developers will integrate their string changes as usual with CWS in according milestone, so we can translate them using usual workflow. ;) ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Re: [l10n-issues] [Issue 88387] 2 buttons in calc solver are English
On Thu, Apr 17, 2008 at 10:10 PM, [EMAIL PROTECTED] wrote: To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=88387 --- Additional comments from [EMAIL PROTECTED] Thu Apr 17 19:10:27 + 2008 --- same for pt-BR Are you L10N folks seeing File - Wizzards - Document Converter untranslated? (Common.xcu#..Common.Menus.Wizard.m11.Title.value.text in officecfg / registry / data / org / openoffice / Office.po ? should we open another issue? There should be issue already ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] L10n mailing list for translation tools
On Tue, Apr 8, 2008 at 6:20 PM, Rafaella Braconi [EMAIL PROTECTED] wrote: Dear All, despite my initial assumption that the traffic on Pootle and various tools would decrease, I must admit that this hasn't happened. I take it as a sign that there is a a great need to share best practices and to propose features, work flows and tools which can make the localizer's life much easier. I'm still convinced that we do not need a *Pootle* only mailing list, and this because Pootle is not the only tool we are using to localize OOo. What I am proposing here is actually what Olivier Hallot suggested during our last l10n meeting on IRC: to set up a translation tool list where to discuss all tool related topics. Just to clarify: translation schedules and deadlines will still be posted to the [EMAIL PROTECTED] list which is to be considered the main discussion list of the l10n project. But information and discussion on Pootle and its functionality will be moved there (I am quite sure some people will be happy about that). If I get your support, I will go ahead and set up a [EMAIL PROTECTED] list - discussion list on translation tools and workflows. It is easy to put all possible problems under term 'workflow(s)'. e.g when I'm announcing about new pot-files, it's a workflow related thing, because using po-files is just one of thousands workflows? (just to be sure what is this I'm voting for) :) ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot files for dev300_m6
http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/OpenOffice.org-DEV300_m6-POT.tar.gz About dozen changed strings in dbaccess, framework, officecfg, sd, svx. ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] pot files for dev300_m6
On Sun, Apr 6, 2008 at 10:47 PM, Yury Tarasievich [EMAIL PROTECTED] wrote: On Sun, 06 Apr 2008 20:15:37 +0300, Ain Vagula [EMAIL PROTECTED] wrote: http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/OpenOffice.org-DEV300_m6-POT.tar.gz About dozen changed strings in dbaccess, framework, officecfg, sd, svx. How should the GSI files be named, for the milestones building processes to pick? I dug a little in the build script of Pavel Janik and didn't understand — it uses the same names both for the 2.* and 3.* series? I provide gsi files from different locations for different branches. Its not ideal, but better than nothing. Renaming were an option too, but when all teams will not follow this, there will be a big mess. At moment it goes so that I drop e-mail to Pavel and he changes the URL for stable tree. ain
[l10n-dev] Re: pot-files for dev300_m5
I was a bit wrong... scp2/src/lingu.pot is removed. ain On Thu, Mar 27, 2008 at 6:26 PM, Ain Vagula [EMAIL PROTECTED] wrote: are ready for download. my cvs-diff is empty, it means there are no changes since m4. http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/ ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] pot-files for dev300_m5
are ready for download. my cvs-diff is empty, it means there are no changes since m4. http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/ ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] dev300_m4 pot-files
... contain no big changes since m3. One string is removed. http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/ ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Content update is completed
sophie wrote: Hi Rail, Rail Aliev wrote: On Monday 17 March 2008 11:44:54 Frank Mau wrote: AFAIK know basic/source/app needs no translation readlicense_oo needs translation only for French Frank, Can you describe the reason? Because a product can't be distributed in France if its documentation is not translated in French. I don't have the law article at hand, but without this translation, OOo can be rejected during a bid invitation for example. However, I don't know if it's France specific. readlicense_oo module name is misleading a bit, at moment it contains only README, which is an important document for enduser (contains system requirements and many other useful things to know). Bad thingie is that license itself is not translatable in oo.o (at least in common way) and this really violates laws not only in France. (Here too by the way, but no software seller cares...) Anyways there is no reason not to translate README-file (even never heard of that, we translated it since it became available). ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Content update is completed
On Fri, Mar 14, 2008 at 10:09 AM, Pavel Janík [EMAIL PROTECTED] wrote: I was told that those module/files have no need to be translated by base team and we decided not to upload them from Pootle to avoide confusion. They have never been translated and I've been removing the module/files every updates. Who told it to you? -- Pavel Janík That's a good example what will happen after separating pootle list. Looks like I have to take my vote back. ;) ain
