Re: [l10n-dev] Translations for Extensions
On 31/05/2008, at 12:49 AM, Rafaella Braconi wrote: Dear Localizers, this is for all the ones who wonder where to find the strings for a specific extension I've created a wiki with a short overview of the CVS modules containing the UI and Help strings for the extensions. Also, I have added the languages for which we have translations. Please feel free to add your language, in case you have translated these modules. http://wiki.services.openoffice.org/wiki/Extensions_Overview These are all from the GSI file, aren't they? But I can't find the module customres. Is it inside another upper-level directory? from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part
[l10n-dev] Which builds should we test?
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? If so, then we can test builds on that codeline as well. I ask this question because we're waiting to see the results of some translation fixes we did, and the first build to appear since then on Pavel's invaluable server is OOH680_m17. But I don't want to amend our download page with those builds if they don't contain the features and current translation we need to test. Thankyou for unconfusing me in this area. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n [1] http://blog.janik.cz/files/OOoCon2006/img0.html PGP.sig Description: This is a digitally signed message part
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]
Re: [l10n-dev] Which builds should we test?
On 31/05/2008, at 6:36 PM, Ain Vagula wrote: 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 OOH680 is still the 2.4 branch? from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part
Re: [l10n-dev] Which builds should we test?
Hi Clytie, 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. you can see the DEV300 codeline as TRUNK for all development that is done for versions greater than 2.4.x . Codelines like BEA300 are release branches from DEV300 to allow to stabilize a build just before a release. BEA300_m2 was the build used for OpenOffice.org 3.0 Beta (1). 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? The OOH680 codeline is a branch for the 2.4.x releases and it is based on the main 2.x TRUNK called SRC680. Kind regards, Joost - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Which builds should we test?
On 31/05/2008, at 6:36 PM, Ain Vagula wrote: 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 I then asked if that meant the OOH680 codeline was only for 2.4. Then I saw this on the Releases list: Hello QA team, OpenOffice.org 2.4.1 Release Candidate 2 (build OOH680_m17) which installs as OpenOffice.org 2.4 has been uploaded to the mirror network. so Ain does mean that the OOH680 codeline is just the branch for 2.4. So we need to stick to the DEV300 branch to test OpenOffice.org 3.0. Thankyou for explaining, Ain. I'm glad all this makes sense to someone: I'm just paddling with the tide. ;) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part
Re: [l10n-dev] Translations for Extensions
Hi all, While into dev300 pot files, there is next file, /sdext/source/presenter/registry/data/org/openoffice/Office.pot there isn't any localize.sdf file into OOo dev300 source. Let see: $ ls ooo_DEV300_m14_src/sdext/source/presenter/registry/data/org/openoffice/Office/ Addons.xcu CVS extension Jobs.xcu makefile.mk ProtocolHandler.xcu Is it fixed for m15? Thanks and best regards, Dooteo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] OOo dev300 m14 : localize error
Hi all, Even a GSI file has all UI messages trsnalated, when I'm running: localize -m -l eu -f GSI_eu.dfs it not merge back messages into next file: ooo_DEV300_m14_src/svtools/source/contnr/localize.sdf can be fixed for m15? Thanks and best regards, dooteo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] OOo dev300 m14 : localize error
Hi, please do not start new threads by replying to old mails. If you do so, please do it correctly and do not set In-Reply-To and similar headers. On 31.5.2008, at 16:45, dooteo wrote: Even a GSI file has all UI messages trsnalated, when I'm running: localize -m -l eu -f GSI_eu.dfs it not merge back messages into next file: ooo_DEV300_m14_src/svtools/source/contnr/localize.sdf Interesting. It does here in to-be-DEV300_m15. Does localize print something for you? Does it merge into localize.sdf in other directories in svtools? The file is read-only in the CVS checkout - can you retest after chmod 644 it before? -- Pavel Janík - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Strings outside the GSI file
Hi everyone :) Do we have a wiki page or other doc explaining where to find, and how to translate the OpenOffice.org interface strings which lie outside our current GSI file? I made a note some time ago, that kami said: Note: not all translatable elements in GSI / PO files. Some localization work has to be done on templates or other files: /opt/openoffice.org2.2/share/autocorr /opt/openoffice.org2.2/share/autotext /opt/openoffice.org2.2/share/template/wizard/letter /opt/openoffice.org2.2/share/template/(yourlocale)/internal AFAIR there is a document where it is described in more detail... Brochure: http://qa.openoffice.org/issues/show_bug.cgi?id=88390 However, that issue only contains an introductory pamplet on OpenOffice.org. It has nothing about extra strings to translate. It itself could be translated, of course. We want to start with the external strings still requiring translation in the OpenOffice.org interface, because now we have a 100% interface and Help translation, we are already getting bug reports about untranslated strings which aren't in the GSI file. I have tried finding the above-listed strings in CVS, but I don't know where to look. Thanks for any help you can give with this. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part
Re: [l10n-dev] Which builds should we test?
On 31/05/2008, at 6:51 PM, Joost Andrae wrote: Hi Clytie, 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. you can see the DEV300 codeline as TRUNK for all development that is done for versions greater than 2.4.x . Codelines like BEA300 are release branches from DEV300 to allow to stabilize a build just before a release. BEA300_m2 was the build used for OpenOffice.org 3.0 Beta (1). 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? The OOH680 codeline is a branch for the 2.4.x releases and it is based on the main 2.x TRUNK called SRC680. Thanks, Joost, I think I'm actually starting to understand this. The SVN references definitely help. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part
