[l10n-dev] SDF-Files from Key ID builds urgently needed
Hi, thanks for the KeyID-builds, but at the moment I have the problem to identify the strings in my translation files. As long as we do not have the sdf files that were used to create those builds, I have no idea how to do this. I need to fix some accellerators in very prominent places (like StartCenter and new Printer UI). If I cannot to this before regular translation deadline, I need to raise this as stopper. regards, André -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] SDF-Files from Key ID builds urgently needed
Hi Vladimir, Original-Nachricht Von: Vladimir Glazounov vladimir.glazou...@sun.com An: dev@l10n.openoffice.org Done, hope that is what you need. yes, thanks. just to get fast access to the file, it is located at http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/ooo330l10n/kid/ :) regards, André -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] SDF-Files from Key ID builds urgently needed
Hi, Von: Martin Srebotnjak mi...@filmsi.net An: dev@l10n.openoffice.org Betreff: Re: [l10n-dev] SDF-Files from Key ID builds urgently needed Hi, Andre, what do these builds do? Do they show id-s of the used strings in the GUI and help? Yes, that's what they do. Each string gets a 6 characters unique ID displayed (like v+q5p2). You then can use the sdf file to locate the exact string location. Regards, André -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] For POOTLE / TCM Users [Fwd: [l10n-tools] Aug 9 - sunvirtuallab.com planned outage]
Hi Thorsten, Original-Nachricht Datum: Fri, 06 Aug 2010 13:27:03 +0200 Von: Thorsten Ziehm thorsten.zi...@oracle.com An: dev@l10n.openoffice.org Betreff: Re: [l10n-dev] For POOTLE / TCM Users [Fwd: [l10n-tools] Aug 9 - sunvirtuallab.com planned outage] Reminder Hi, Pootle was updated with m3. Please try to update your translation files before the down time. Why? Translation delivery is Aug. 19th. So - I agree, that we should try to get our translations in better now than later, but there is no need to hurry (and risk low quality). At the other hand I see no reason to get ~20 Strings translated, when only one was requested as bugfix. We had UI freeze, it is *not* my duty to fix UI changes that other people introduced. (I'll do it, just because I do not want that such bugs are presented to the end user). regards, André -- GMX DSL SOMMER-SPECIAL: Surf Phone Flat 16.000 für nur 19,99 ¿/mtl.!* http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Issues in ooo330l10n
Just for information for the other teams - issues with not enough space we filed so far are: 113442 - new html import in calc 113446 - Custom Pages per sheet in new print dialog on calc 113469 - enhanced data pilot popup (Cancel button) regards, André -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] Status of l10n integration and CWS availability
Hi, according to http://wiki.services.openoffice.org/wiki/Translation_for_3.3 the first deadline for l10n delivery was 6 days ago. Unfortunately we have no information, if strings have been retrieved from pootle, if there are problems with gsicheck etc. I've seen cws ooo330l10n has been created two days ago, but there is no status information on the cws (no due date, no ready for qa date ...). According to the wiki, builds should be ready for testing by tomorrow. This would be really great, as we have a project workshop session during the weekend - and I planned to have a cws testing session. Could someone give more information? One wish for the future: could someone take care, that not only the l10n community is asked to meet the deadlines? It happened now several times, that l10n engineering did not meet deadlines, without informing us beforehand. Often we see such information when the deadline is due or one day later. This does not only raise pressure on our teams (as time for our work is reduced) but makes planning of our work a superfluous waste of time. -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenCTI use?
Hi, Von: Reiko Saito reiko.sa...@oracle.com An: dev@l10n.openoffice.org Could anyone let me know why TBX is desireble, rather than csv in your translation ? Because it is a LISA standard that can be (and is) implemented by several tools? So instead of using csv (where each and every tool might have a different idea, what values to export in what order) we might use a file format where tools have a common understanding how to process the content. regards, André -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, In summary, pt-BR UI got back to 90% of translated strings (from 100%) and that does not seem correct with respect to the new features announced for OO 3.3. Same for German here. *but* this is normal behavior having our current workflow in mind. some developer decided to shuffle source strings from location A to location B - our workflow does not apply atuomatic translation to such changes (last time this happened, it seemed as if developers are not aware of the l10n workload they are causing). On a side note, I really think we need a version control on the po files... Yes, would also be nice to have, but would not solve the specific problem. I did not check yet, if the strings at the new location can be translated automatic. Regards, André -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Von: Sophie sgautier@free.fr It can for more than 90% of them, but you have to check for it any way... Yes, but verification of a string is less then one second in most cases vs. up to several minutes for a new translation ;) Regards, André -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] IMPORTANT: OpenOffice.org 3.3 - translation schedule
Hi, Von: Rafaella Braconi rafaella.brac...@sun.com On a side note, I really think we need a version control on the po files... I think that a more powerful translation memory in Pootle would help... Pootle (or more precise translate toolkit) can use old translation files (set of po files) as translation memory. I'd guess, using pretranslate instead of pomerge would give much more fuzzy matches (so that you only need to check instead of translate). Still did not test this - quite busiy with other things atm :( Regards, André -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] L10n Schedule Information for 3.2.1 - update
Hi Rafaella, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com Sun translated files - if Community files are not available - are being uploaded to Pootle. Once done, Pootle translations (translation should be at least 80%) as well as translated files delivered via issue will be integrated on the localization CWS. thanks for the update :) For next week, Friday, April 9th, we are expecting a few more strings that will need to be translated. We will follow the *normal* translation process, by indicating which milestone to take to update your translation and by making the strings available via Pootle. Does this mean, Sun will maintain the additional Strings (as with the recent round) or should community take care? (I'm fine with both, just need to know). Regards, André -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OOo 3.2.1 l10n schedule?
Hi, Pootle has not yet been updated (the milestone is not yet ready) Ivo will be posting later today when it's ready. Please note that has already said during the release meeting, Sun will be translating the following 16 languages: es, de, fr, it, pt, pt-br, sv, nl, hu, pl, ru, ar, ja, zh, zh_tw, ko. Once the translation are ready will be made available in Pootle. What exactly does this mean? Will Sun translate the new / changes strings, so that community will have nothing to do (but to check if all is ok)? André -- GMX.at - Österreichs FreeMail-Dienst mit über 2 Mio Mitgliedern E-Mail, SMS mehr! Kostenlos: http://portal.gmx.net/de/go/atfreemail - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] New: OpenOffice.org 3.2.0 Release Candidate 4 (build OOO320_m11) available
Hi, Von: suso suso.bale...@gmail.com Hi all! While testing rc4, another newbie question: - How much time without stoppers is considered to be enough to get approved a given rc? normally until next release status meeting (which is every monday). So for regular RC we have about a week. RC's with only one or two stoppers fixed might have a shorter time for approval. First RC normally gets about two weeks for testing. hth André -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] DEV300m70 introduces - new unwanted empty spaces in help files - again
Hi, Von: Uwe Fischer uwe.fisc...@sun.com .. the only helpcontent relevant changes in m70 came in from the CWS printerpullpages. See issue 104335. Seems to be introduces with some earlier cws. Diff between OOO320_m10.sdf and DEV300_m70.sdf include those changes (sorry for long lines): helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148397 50 0 en-US \item type=\input\\2\/item\ 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148431 63 0 en-US \item type=\input\\0.00 currency units\/item\ 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148462 118 0 en-US \emph\Cost\/emph\ is the initial cost of an asset. 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148488 375 0 en-US \emph\FirstPeriod \/emph\is the end date of the first settlement period. 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148558 407 0 en-US \emph\Maturity\/emph\ is the date on which the security matures (expires). 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148397 50 0 en-US \item type=\input\\2\/item\ 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148431 63 0 en-US \item type=\input\\0.00 currency units\/item\ 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148462 118 0 en-US \emph\Cost\/emph\ is the initial cost of an asset. 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148488 375 0 en-US \emph\FirstPeriod \/emph\is the end date of the first settlement period. 2002-02-02 02:02:02 helpcontent2 source\text\scalc\01\04060103.xhp 0 help par_id3148558 407 0 en-US \emph\Maturity\/emph\ is the date on which the security matures (expires). 2002-02-02 02:02:02 .. and much more. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] List of datasources in new database wizard not translated
Hi, can some l10n teams have a look at issue 107957? http://qa.openoffice.org/issues/show_bug.cgi?id=107957 It is reported for Korean, but it seems, German localization has the same problem (list of datasources in the Connect to existing database list is not translated). I just wonder if this is a general problem or if I should file a new issue for German. In any case, I'd suggest this to be fixed in 3.2.1. Thanks, André -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] List of datasources in new database wizard not translated
Hi, Original-Nachricht Von: Martin Srebotnjak mi...@filmsi.net I have some more non-localizable strings bugs on my list: http://qa.openoffice.org/issues/show_bug.cgi?id=66304 http://qa.openoffice.org/issues/show_bug.cgi?id=94789 yes, there are some more strings that *cannot* be localized. (Not really nice .. but ... :( ) The problem I just mentioned is new - datasource strings were localized in 3.1 and are also translated in pootle (at least for German). So it's a regression and likely an integration problem. (Which we unfortunately missed during cws tests.) André -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Please prepare for 3.2RC2 l10n binaries sanity check next week
Hi, Original-Nachricht Von: Martin Srebotnjak mi...@filmsi.net Just 9 (or 10 if you count two Chinese) languages. OOo is fully built in 31 (!) languages. I guess the French, German, Italian, Japanese, Korean, Spanish and Swedish communities might be happy with this decision, Nope, we are not (ok, we do not yet know, if *we* are, as *we* have not been aware of the decision). Problem is, that wJRE builds are not usefull for users in corporate / business environments. For the moment I just can tell, the we had the discussion on 3.1.1, when we did not test w/o-JRE builds (without clearly stating this beforehand). We definatley have users and project members, who would prefere Windows builds without JRE. André -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser - 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
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é -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] specs for Migration analysis module in 3.2
Hi, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com because you don't need the module when you build OOo. This is a separate *tool*. Translations are not lost. The module has just been *hidden* in Pootle. If you want to have it in Pootle, we can have it added in a separate *Extension* project. Just not to mix up modules that need to be translated for OOo and modules that need to be translated to localize extensions or other tools. Hmm .. good idea. But seems (speaking of extensions) as if we already have a mix. (e.g. all extensions are in the regular pootle structure). Maybe we should not think of external components, but of mandatory components. The rules for building localized version then will apply to those mandatory repository only. (E.g. this should not include the migration wizard or the testtool.) Best, André -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 - 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
Hi, Von: Mathias Bauer nospamfor...@gmx.de Why another CWS? Couldn't we use the same? And if we did it with Mercurial instead of svn it would be easy to handle: provide a repository on services.openoffice.org that everybody can clone and where changes could be pushed to. Translators are not developers. So the people who translate normally have no idea how a source repository works, how they would clone this ... many (if not most) translators don't even know how their translations make their way into the final product (it is not really important to translators, as long as the translation *makes* the way into the builds). I'd guess most of our developers even don't have an idea, what our translation workflow looks like. The other problem with such a CWS would be, that ~100 people would contribute to this cws. Although this might be technical possible, I'd guess this is not our normal way to handle CWSes. BTW: that's how I would recommend to work in future anyway. But YMMV. Yes - we should change the way we we work with translations ... but I don't think, we would gain much, if translators would directly contribute to a CWS. André PS: If you like and have time, I'm in Hamburg next Thursday. I'd be happy to have a beer in the evening somewhere ;) -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 - 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
Hi Frank, Original-Nachricht Von: Frank Peters f...@sun.com Namely, I have seen that also changes in English strings are a bit frustrating for us non-English localizers - in English strings sometimes just fixing a typo makes the string in your language fuzzy, but actually your translation should be just fine. But you want to make it sure what changed and if translation is ok etc. and you lose precious time. If one knew that a typo and English content changing CWS is coming one would go translating through it in a different way compared to an new strings CWS. That is hard to catch without having a flag that says I changed something, but it's irrelevant to l10n. In theory, we have this flag. At least the help XML format is prepared for that. All paragraphs contain an l10n attribute used to specify the localization status of the paragraph. (quote from http://documentation.openoffice.org/files/documents/75/499/XMLHelpSpec10.pdf , page 15). In current help files, the attribute is present with different values. Unfortunately this information gets lost during conversion steps ( xml - sdf - po/xml). As long as we keep thumb sdf as intermediate file format, we won't get around this problem. Best, André -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 - 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
Hi, Von: Uwe Fischer uwe.fisc...@sun.com this flag means this paragraph is irrelevant for translations or never translate this paragraph. I did not know that this does not get passed over to translators, though. Bad tools design :-( What we would need is a flag that says the changes to this paragraph that were done just recently need not go into the translation database. But then, if we later change the same paragraph with relevant edits, this flag must be reset automatically. I think, we have these different flags. The one I mentioned is the l10n attribute that can have different states. But there is also a localize attribute wich can be set to false (indicating that the element should not be translated at all). I'm not sure, but I'd guess that such elemnts never make their way to the sdf files (so these strings a invisible for translators). André -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser - 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
Hi, Original-Nachricht Von: Andras Timar ti...@fsf.hu 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. A quite simple chicken-egg-problem: - (almost) nobody is improving XLIFF workflow as (almost) nobody is using XLIFF for OOo translation workflow. - (almost) nobody is using XLIFF for the OOo translation workflow as the tools have limitation and (almost) nobody is improving the tools. With a little effort put into l10n tool development OOo translation experience would improve dramatically. After spending some time to improve OLT XLIFF editor and had some closer look at our toolchain, I would not call this a little effort. But imo it is the only thing that makes sense. 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. Correct - I once just tried the Swordfish XLIFF editor. Sorry to say so, but every team developing an open source translation editor should be ashamed. Most of the tools have one common problem: they are built around the limited po file format. I (we - Germanophone team) were thinking about getting some licenses of Swordfish. But after all we dropped the idea, because this would limit our translation team to the numbers of licenses. Best, André PS.: If there are some developers with Java skills, knowing about XML, XSLTs and interested in translation work ... https://open-language-tools.dev.java.net/ needs help. If you are more comfortable with python, help at the translate toolkit project. I know that the people there are actually interested in better XLIFF support - but as long as there are no users and no developers it has low priority. -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 - 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
Hi Martin, first: thanks for bringing the issue to the list - I share your opinion, that these really hurt translators. But a small side note ... Original-Nachricht An: dev@l10n.openoffice.org ... Just a small regression from a translator's perspective. When you stumble upon such a fuzzy string with changed tags and/or unwanted blanks added, you do not and cannot know, what other change happened in the string. So you are being careful and recheck the translation, then repair the tags and remove the spaces. Sometimes you check the old po file, to chack what was changed from previous mXX. So in the end one changed string like that takes more time from a translator viewpoint than translating it from scratch. Please, keep this in mind when you decide what to do with changes in m51 and m57 and further steps in changing tags in these files. Changing 2000 help strings, some intentionally by just replacing tags and some by mistake of adding blanks mean same as 2000 new untranslated strings. let me promote XLIFF a little ;) Using XLIFF you have much more information available than with po. One of the information is the former source string and it's translation. This actually works with files processed by translate toolkit and XLIFF editors that are aware of the the alt-translation information. In reality it would look like this: http://wiki.services.openoffice.org/w/images/1/18/De_l10n_ote_vorschlag.png You can identify relevant changes quite fast. Anyway .. it is still a stupid and boring work. The risk to lose real changes just by human mistake is high. So if such tag changes are planned, a special CWS could be created, where *all* such tags should be replaced, then all current SDF files from all translation teams should be delivered by the translation teams to Hamburg where they would use this special super-trouper command line tool that would replicate all the tag changes in translations as well +1 André -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser - 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
Hi, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com We need to know if we should roll back the changes listed above that were introduced with m57 (this does not apply to the relevant content changes, just the changes listed above). I agree with Frank that it is important to get your feedback and your GO before we roll back the changes/issues listed above. I have no probelm with rolling back those changes introduced in m57. As we are working on pootle, we are just doing the translations for m54. as these are partially done, please no not rollback changes from m54. André -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Serbian OOo install sets for 3.1
Hi, Original-Nachricht An: dev@l10n.openoffice.org So perhaps Cor can take this with him to the next Council meeting. We are now at least three on this list that think this is worth considering. This has already been discussed in the council meeting. The problem for the coucil is to know the real requierements and troubles. I'll start a new thread on this later today - I just asked some poeple to join this list for discussion. Best, André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Deadline for m40?
Hi, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com Hi Sophie, All, On 02/06/09 07:51, sophie wrote: Hi Rafaella, what is the deadline for m40 translation? thank you for asking. I was actually waiting for the update to be done to make a decision based on the wordcount and as it is very very small, it would really be great if you could complete the translation of the few strings by Monday noon CET. We will then integrate only the latest translated strings. should be possible. @Aijin: can you point us to the sdf file you used to create the new content in pootle? I did not yet apply the corrections I did on the last sdf .. I'll do this during the weekend. But it was good to have the sdf you used, so that I can run gsichek on my new translations. Best, André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Deadline for m40?
Hi, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com Hi Andre, is all in the issue: http://www.openoffice.org/issues/show_bug.cgi?id=98835 hmm .. no. I meant the full sdf file that contains the m40 en-US strings that were pushed to pootle. The issue is about m39. While fixing the errors in this issue, I tried to creat my own (de) sdf from an en-US sdf + translations from pootle. But I was not able to get the same results as Aijin delivered in the issue. This is not mission critical but would help to identify still existing problems in our tools. (E.g. I guess, pomerge broke some of the character encodings and maybe matched some translations to a wrong source segment). best, André -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] Deadline for m40?
Hi, Original-Nachricht Von: Aijin Kim aijin@sun.com Hi André, @Aijin: can you point us to the sdf file you used to create the new content in pootle? Pootle was updated with DEV300_m40. You can download the sdf from: http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/POT/OpenOffice.org-DEV300_m40-POT.tar.gz Thanks! André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] SCA - Sun Contributor Agreement
Hi Rafaella, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com I recently received some questions regarding the process to follow to sign and submit the SCA. Here below in summary, all you need to do, in case you haven't :-) Who is you in this caes - or who has to sign the SCA? Is it a) people who are responsible for a given translation (normally the l10n contacts for a language) - or - b) everyone who is going to translate at least one segment? best, André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] SCA - Sun Contributor Agreement
Hi, Original-Nachricht Von: Rafaella Braconi rafaella.brac...@sun.com Who is you in this caes - or who has to sign the SCA? very good questions :-) Is it a) people who are responsible for a given translation (normally the l10n contacts for a language) - or - b) everyone who is going to translate at least one segment? Everyone who is contributing to the OOo localization with translation (independently from volume) , review + corrections or l10n fixes. Hmm - this is quite different from the last statement I found on the mailing list:_ http://l10n.openoffice.org/servlets/ReadMsg?list=devmsgNo=8201 The old statement is indeed about JCA (not SCA, which is not code specific anymore). The problem is, the did not ask our translators to send in an JCA/SCA, as it was a recommendation. Is this still true or is it now a requirement? In case of being a requirement, we have a problem: two of our main contributors to German localisation did not send in a JCA / SCA yet. André -- NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] SCA - Sun Contributor Agreement
Hi, Original-Nachricht Von: sophie sgautier@free.fr So now, only documentation and extensions (may be also templates) are not covered by the SCA. Ok .. i'll ask our translators to submit a SCA. but still leaves the questions what to do with existing (or prepared but not yet committed) trasnlations. André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
[l10n-dev] New Strings after 3.2 UI-freeze (Re: [l10n-dev] Deadline for OOo 3.0 final translations)
Hi, Original-Nachricht Von: Frco. Javier Rial fjr...@cesga.es I'll assume that version targeted for OpenOffice.org 3.1 is m39 as it was planned.. no ... as the is no special branch yet for 3.1, the code will be branched later and 3.1 will contain all changes from m40. That we have new strings in m40 is just (and once again) caused by breaking our proccesses. I did a quick check in EIS and none of the integrates cws seems to have a word count - so release engineering may not be aware of new strings. As I'm neither a expert for release engineering nor for EIS, I'd ask our project leads to verify the issue and escalate to the release mailing list. André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OO Schedule Tasks!
Hi, Original-Nachricht Von: Ankit Patel ankit...@yahoo.com Looking at the schedule: http://wiki.services.openoffice.org/wiki/OOoRelease31 I can see that there are very few days between code freeze (29th January) and translation delivery (2nd February)? ... One more thing I noticed from the schedule is, there is no String Freeze mentioned anywhere on the schedule! To me, String freeze is the date, till when developers are supposed to make changes to the english messages that are localizable. In OOo terminology this is UI and Feature freeze. If new strings need to be included after this date, this would nee special approval. I can only once agian ask the l10n project leads to request clarification about the new strings in m40. ... One more doubt I had was, can the translators or language maintainers submit their translations till last l10n bug fixes delivery: February 26th, 2009? OR is the date translation delivery deadline: February 2nd, 2009 fixed till when translators can submit translations? Feb. 2nd is the date for regular translation submission. Feb 26th should only be used for very urgend l10n/translation bugfixes that would be considered as showstopper. André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenOffice.org - Translation schedule for 3.1
Hi, Original-Nachricht For Pootle Users: please continue to work on translation (unless you are already done :-) ). We will let you know when the content will be updated. just to be able to choose which file we are going to translate - any idea when the content will be updated (days, weeks ..?) We have some files left, where we would need more than a week of turn-around time. WOuold be unfortunate, if we pick these and the update happens within the next few3 days. Thanks, André -- Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a - To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
Re: [l10n-dev] OpenOffice.org - Translation schedule for 3.1
Hi Rafaella, Original-Nachricht Von: Rafaella Braconi [EMAIL PROTECTED] Here some highlights: New/Changed Estimated Translation Volume since 3.0: === GUI approx. 9,000 words does this count include the label strings (that are currently discussed)? Labels are ~ 6500 words, making 70% (just to estimate the total effort). André -- Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Proposal for issue http://www.openoffice.org/issues/show_bug.cgi?id=96791
Hi, Original-Nachricht Von: Rafaella Braconi [EMAIL PROTECTED] with issue http://www.openoffice.org/issues/show_bug.cgi?id=96791 a number of strings which mainly include German *product names* in the source have been introduced as to be translated. Option 1) close this issue and set the file as not to translate -1 Option 2) translate and maintain the translation of the product names in all languages going forward. +1 and leave the decision to the translation teams. The products may be sold in several countries, so there might exist locale product names. André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Templates, autotext and other NL specific components
Hi, Original-Nachricht Von: Eike Rathke [EMAIL PROTECTED] Sorry, it appeared to me that native language projects idealistically should have QA representatives, who should be able to tell who is responsible for a particular part of their localization who in turn can handle it or tell how. This list here of course would be appropriate, also NL-leads should be able to tell how to process or whom to contact. Olivier's request was unanswered though for 12 days. Because nobody knows the answer. I may have misunderstood the nature of the problem. What exactly are you referring with help how to fix bugs in localized resources? Respectively what was Olivier referring with how do we handle that? Judging from his email address and .sig it is about pt-BR localization. Yes - but this might affect all other localizations as well. The problem is simple (the answer is not). Oliver identified a problem in a localized ressources (tmplates, spellchecker and maybe others). The question now is where to submit the fixes? You are right - you may ask native lang project leads. But afaik, noi nl project lead has this information. Next step is to ask here (as l10n cares about localized resources). Seems, nobody here knows the answer either. I remember a similar discussion about localizing templates some months ago here at the list (I need to dig my archives to find the outcome). For spellcheckers - I had the same problem for German dictionaries and asked at [EMAIL PROTECTED] The answer I got was that I need someone to create a cws and submit the updated spellcheckers to the correct place (I need to dig my mails for the localtion, if this info would help). At the moment it seems, there is no project / subproject who is in charge of maintaining spellcheckers, templates ... The only way atm seems to be to find a developer who is willing to submit the changes (if she has at least a little kno0wledge about where to sumbit). André -- GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] splitting huge help files
Hi, Original-Nachricht Datum: Thu, 19 Jun 2008 10:15:40 -0300 Von: Olivier Hallot [EMAIL PROTECTED] An: dev@l10n.openoffice.org Betreff: Re: [l10n-dev] splitting huge help files Besides the fact that one get tired and is more subject to errors or lack of attention. If I may suggest, I think that +/- 300 strings should be a comofortable size, and if we can implement the split by context it will be even better. I think, this is the more important thing: split (or athoer way round: join) translation files by context. You are correct, that it is booring to translate files with thousands of strings, not coming to an end. But at the moment we had mor problems to give translators work from one context. E.g. I was trying to give away the translation for the Calc solver. Unfortunately the (UI) strings are in about 3 .po-files .. and there are strings in these files that do to rely to solver at all. so what we did was that on solver expert prepared the translation in a wiki (using the solver spec) and i put them into the po-files. Reason for this was that our solver expert was not used to translation and it was to time consuming for him to locate the solver stringfs in the po files. Ok .. this is mainly caused by the way how OOo projects splits the po files - but if someone knows a solution, this would be of great help. :) André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OOo 3.0 Beta Readme to translate
Hi, Original-Nachricht unfortunately, the updated OOo Readme for Beta is not included in the m7 and not in the upcoming m8. The updated Readme will be available in the m9. and has (reading the contents of the sdf files) many errors. E.g. We do not list Win98 or Solaris 8 as supported platforms anymore - but we give special hints for users of those platforms some paragraphs later. So - I guess, we do not need to deliver a 100% translation? (We would need to translate a correct Readme later anyway). André -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: l10n TCM (Re: [l10n-dev] REMINDER: OpenOffice.org 3.0 Translation Delivery for BETA)
Hi Rafaella, Original-Nachricht Datum: Wed, 09 Apr 2008 09:34:59 +0200 Betreff: Re: [l10n-dev] Re: l10n TCM (Re: [l10n-dev] REMINDER: OpenOffice.org 3.0 Translation Delivery for BETA) Hi André, According to EIS, cws localisation28 has a Estimated integration date of 2008-04-17. This would mean, TCM tests should be finished until 2008-04-16? The TCM test on l10n CWS builds should be more a Sanity check to make sure to spot major issues before integration. All the very good points you mention above should be tested on Beta and with the new test cases in May, as Naoyuki announced in the [EMAIL PROTECTED] list. Thanks - I will plan our tests according to that. André -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] L10n Builds: full sets vs. language packs - proposal
Hi Charles, Charles-H.Schulz schrieb: Rafaella Braconi a écrit : 1- the GUI translation must be at least 80% completed 2- the Online translation must be at least 80% completed 3- 1 official build approval must have been submitted to the QATrack tool during the last 3 releases The point 3 is a little bit too strong imho. I'd go for 2 releases. Reducing this to 2 releases is even stronger. To approve 1 build within 3 releases seems ok to me (that means 1 build approved in 9 months). André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Status of QA Localized Builds
Hi, Erdal Ronahi schrieb: Please look at: http://www.qatrack.org/ooo/view.php to get the overview and please do perform testing on the l10n builds and do submit QA approval. This is really important for the OOo project. Maybe I still fail to comprehend the difference between the different build types. On this list Kurdish does not appear, not even in the no build section. Is this due to Kurdish not being an official language at Sun? No ... this has other reasons and a very simple one: no one added the information to qa track, that there is a kurdish build available. Please read the description at the wiki for a description of qatrack: http://wiki.services.openoffice.org/wiki/Release_QA_Tracking_Tool Actually, the week point is that a Build Provider needs to tell qatrack that a build is available. But no Build provider (but Joost Andrae, who does the Sun builds) did request a login for qatrack. And so .. no build provider is providing this information. At the moment, Andrea Pescetti and me are adding new builds .. but we would need to scan several places for new builds and add them to qatrack. Maybe the better way was to remove access restrictions from the build provider interface, so that anybody can add new builds (and maybe this can even be automated). If someone would like to work on that - qatrack is open source ;-) Like Clytie I was not aware of this step of the procedure. Is there a similar procedure for languages that will only be covered by Pavel's builds at ftp.linux.cz? Will there be something like a final relase for our language? I think the latest build there is rc2. There will be a final release as soon as (localized) rc2 has passed qa and is approved. André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Status of QA Localized Builds
Hi, Joost Andrae schrieb: Hello Erdal, if your language is not listed then please ask Andrea Pescetti (the maintainer of qatrack) to add it to www.qatrack.org. The problem is, that kurdish is not available as language in qatrack at the moment :-( André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Migrating to the OpenSolaris TCM
Hi all, (just for coordinating the discussion: please answer to [EMAIL PROTECTED] only. l10n and native-lang lists are cc'ed for information only here). as mentioned at the qa list, last weekend several community members had the chance to see a presentation about the OpenSolaris TCM. The tool was intrododuced by Petr Dudacek and Petr Hruska who showed the TCM in Action and could answer many of our questions. The outcome was, that the OpenSolaris TCM would answer many of our wishes and the enhancements would help to improve our testing process. So we would like to go on and start migrating to the OpenSolaris TCM. I have set up a wiki page for coordinationg the migration at http://wiki.services.openoffice.org/wiki/TCM_migration This is only a draft for the moment. You are welcome to comment and help. Migration would be a joint effort of the Sun g11n, Sun QA and community QA teams. Sun g11n team will start to review current test cases for incorrect descriptions. Within this time, we (community) should think about the next steps. E.g. all current TCM managers should check the new TCM functionalities and prepare the teams for the move. Please request a login to the OpenSolaris TCM (if not already done) and take active part in the process. Related to to this is the definition of test plans. The current situation of two sources for test plans (smoke tests on the website and test cases in TCM) is far from being perfect. As smoke tests are outdated, they would be marked as such and should not be used anymore. There are several test plans available in the Sun QA team. These are mainly for testing new features and more complex than those curently in TCM. At the moment we are looking for a good way to make those Testplans available but have the option to coordinate the tests within TCM. It has been suggested to have the complete testplan at the qa website and have it as a test item in TCM. As always .. comments and help is welcome. André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] [Fwd: [qa-dev] Testing with TCM]
Hi, To the Community members: can you please let me and Karl know who would like to have MGR access to better evaluate the new TCM features? Raising my hand for MGR access ;-) André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] [Fwd: [qa-dev] Testing with TCM]
Hi All, Karl Hong schrieb: ... Karl, from your perspective, can you may be tell us what you think is best? I would suggest to migrate OOo to OpenSolaris. In this case, test cases can be shared. Under new TCM, you can have your own build sequence for OOo test cycle, each build only contains OOo testing. Well .. first I'd like to have some documentation what the items are about. E.g. I see a GO/No Go report. Looks quite as it was something we would nee for Release testing. Scenarios might be related to that. .. but what exactly is a scenario? Second .. would the OpenSolaris TCM answer some of our wishes (http://wiki.services.openoffice.org/wiki/TCM_wishes)? From the current perspective OS TCM seems definately better than OOo TCM .. but I wonder if it fits our needs. André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Dutch OOo 2.0.2 Windows/Linux approved
Simon Brouwer schrieb: Hi all, The Dutch OOo 2.0.2 builds for both Windows and LinuxIntel have been tested and approved. I would appreciate it if someone could update the status page to reflect this. *done* - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Dutch OOo 2.0.2 Windows/Linux approved
Hi, Thanks!!! Another question, I opened an issue to ask for the distribution of the builds to the mirrors: http://www.openoffice.org/issues/show_bug.cgi?id=62986 Is this OK or should I assign the issue to somebody specific? in general this should be picked up without setting a specific owner. You might set st to cc (but afaik he is on vacation atm). The problem at the oment is, that the master server has no space left :-( André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OO on MacOS X_86
Hi, Vladimir Stefanov schrieb: I tried to install Macedonian OO_2.0.1 and 2.0.2RC1 on Mac OS X_86 but with no success. It begin with installation, hang out for about 30 second and then exit with no messages. Is this packages are build strictly only for PowerPC? I'm trying to install it on AMD Athlon64 3200+. hmm.. wouldn't write this to a public list .. and .. is it our policy to support illegal software configurations? André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Improvement of the OOo windows installer translation quality
Hi Charles, * Charles-H.Schulz schrieb: Hello Ivo, If I choose the wrong user please let me know. It would be nice if we can add all ooo usernames to the N-L project web page ( http://projects.openoffice.org/native-lang.html ) , it is too complicated yet to find out ... Luis,Stefan ? We can add them there (I can help): http://wiki.services.openoffice.org/wiki/NLC as the initial post was about translation, the correct place to find the responsible persons was: http://l10n.openoffice.org/languages.html You might see, that the responsible persons listed there are distinct from the NLC project leads .. what is correct. André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Help verifiying issues from CWS
Hi, we have 197 issues fixed in CWS localisation05, but not all of them are verified yet. Those issues belong to german (most of them), hungarian, thai, spanish and dutch localisations. Please help to verivy those issues. A list of issues that needs to be verified: http://tinyurl.com/9p9gc Localised CWS bilds are available from http://oootranslation.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization05/linux/ (These are the same that are used for current TCM testing) To verify the issues - download the localised builds - pick one issue for your localisation - check, if it is fixed - if yes - change status to verified (do not close the issues .. this would be the next step, when the CWS has been integrated into the master) - if not - reopen the issue and set the target milestone to 2.0.3. Please do only check, if the reported issue has been fixed. If you finde other problems, file a new issue. Thanks in advance, André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Localized builds for 2.0.1
Hi, Roberto Salomon schrieb: Any news of when will the localized builds be available? Currently only en_US is available for download. http://qa.openoffice.org/localized/index.html and http://qa.openoffice.org/localized/status.html might help. André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Deadline for OOo 2.0.1 translations
Hi Ivo, All, I'm not very pleased with this dates and the way they have been decided. German localization is far from beeing perfect. We have many inconsistencies in our help. At many places help content still referes to 1.x GUI. But all we can do is to file issues, we cannot provide fixes for such problems. So .. because we cannot fix the content ourselv, we actually do not know, what has been really fixed and how. Time from filing an issue to getting a fixed versions just to test takes months at the moment. What I really would like to see is a snapshot with fixes for german localization, so we have the chance to test, if we have an improvement. André Ivo Hinkelmann schrieb: Hi all, the last cws integration for OOo 2.0.1 is near, thus please provide your translation updates for integration: The deadline for providing GSI / SDF files is 2005/11/03 Keep in mind that the timeline till last cws integration is very tight, so I have to reject all files coming too late. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Bengali localizations (was: [qa-dev] Bengali is not listed in the status page)
Hi Jamil, all Jamil Ahmed schrieb: Jamil Ahmed schrieb: Bengali is not listed in the status page, http://qa.openoffice.org/localized/status.html ok .. I've updated the spreadsheet (which is at http://qa.openoffice.org/localized/qa_localization_status.ods but not linked yet) with most of the languages from http://l10n.openoffice.org/languages.html. Hi André, Thanks for the updates, but there needs some changes. Bengali has only single build. Neither bn_BD nor bn_IN, only bn. :) as I have taken the date from the localization page (http://l10n.openoffice.org/languages.html), I think, this should be corrected there. Pavel, could you take care of it? André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
