Re: [libreoffice-l10n] Please help for the Indonesian translation team.
On Kam, 2011-04-21 at 06:32 +0200, Andras Timar wrote: > Dirgita, now I gave you admin rights for Indonesian language. > Thank you very much. - Salam, Dirgita -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Please help for the Indonesian translation team.
2011.04.21. 2:29 keltezéssel, Dirgita írta: > Hello, I'm a new member for LibreOffice Indonesian translator team. > Currently, I was an active translator for OpenOffice.org. > > I have sent message to Indonesian translator team leader almost two > weeks ago for "upload" right. With this right, I hope can speed up the > translation. > > But until now, I have not received any response from the leader. > > What should I do? Can anyone help me? Hi Dirgita, According to http://wiki.documentfoundation.org/Language_Teams Indonesian language lead is Ki Drupadi, but apparently nothing has been uploaded to Pootle since the beginning of the project. Ki Drupadi has two users registered in Pootle (kidrupadi and Ki_Drupadi) but neither have rights associated with it. So Ki Drupadi could not give you upload rights. Ki Drupadi, if you read this and you would like to contribute to Pootle, please respond. Dirgita, now I gave you admin rights for Indonesian language. Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Please help for the Indonesian translation team.
Hello, I'm a new member for LibreOffice Indonesian translator team. Currently, I was an active translator for OpenOffice.org. I have sent message to Indonesian translator team leader almost two weeks ago for "upload" right. With this right, I hope can speed up the translation. But until now, I have not received any response from the leader. What should I do? Can anyone help me? - Salam, Dirgita -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
On 20/04/2011 06:11, Andras Timar wrote: 2011.04.20. 5:34 keltezéssel, Sophie Gautier írta: But thanks a lot again really, that will help me to correct the files quickly later today. I fixed all build build breakers in cy, fr, ja and pt in git. Next time I'll check them before I commit. Best regards, Andras Thanks Andras, I was getting a bit confused as I could not find the errors for the cy translation in the log... ;-) -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
2011/4/20 Anton Meixome : > Is this string correct? Is very strange > > > [file] > LibreOffice 3.4.x – UI » instsetoo_native / inc_openoffice / windows / > msi_languages.po > > [ref] > Control.ulf#OOO_CONTROL_206.LngText.text > > [string] > > error text goes here error text goes here error text goes here error > text goes here error text goes here error text goes here error text > goes here error text goes here error text goes here error text goes > here > This is some dummy text. Don't worry about it. Leave it in English. Maybe the error text really goes to the buffer that is allocated by this string... Best regards, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Is this string correct? Is very strange [file] LibreOffice 3.4.x – UI » instsetoo_native / inc_openoffice / windows / msi_languages.po [ref] Control.ulf#OOO_CONTROL_206.LngText.text [string] error text goes here error text goes here error text goes here error text goes here error text goes here error text goes here error text goes here error text goes here error text goes here error text goes here -- Antón Méixome - Blog about Galician Office Suite Galician community OOo.org & LibO http://blog.openoffice.gl // http://blog.libreoffice.gl -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
O , 2011-04-19 23:34 +0200, Martin Srebotnjak rakstīja: > I don't care what your script says but for Slovenian this is not an > error - > it would be an error if those strings had a different translation. The point is, translating those two strings the same results in lost styles at best, and broken documents at worst. In Latvian there is exactly the same problem, the workaround is that "Title" becomes "Document title" and "Subtitle" — "Document subtitle". It is ugly, but it is also a bug. -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Dear Christian, 2011/4/20 Christian Lohmaier > That's a very strange attitude. So you're telling Slovenian users to > screw themselves > as the sole localizer of OpenOffice.org/LibreOffice versions from 3.0 on I am the last person that could be labeled with such blatant words. I do not want to step up to your level of communication so I will just stop at that. Lp, m. -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
On 2011-04-20 13:12, Dwayne Bailey wrote: https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id3149902.25 (in case sophie is too fast and fixes it in the meantime: Dans une fenêtre de fichier de base de données, cliquez sur l'icôneRequêtes, puis choisissez Éditer - Éditer. Lorsque les champs de référence n'existent plus, vous voyez cette boîte de dialogue i.e. non-matching - missing "h" - pootle doesn't flag it I've created http://bugs.locamotion.org/show_bug.cgi?id=1910 Seems that we do detect this error correctly. My guess is that it was marked as a false positive. We should be seeing puncspacing and doublespacing errors on this one and we're seeing no errors. -- regards Dwayne -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
On 2011-04-20 03:35, Christian Lohmaier wrote:
Hi Dwayne, *,
2011/4/19 Dwayne Bailey:
On 2011-04-19 09:13, Andras Timar wrote:
So now there are 3 checks in place for translations:
gsicheck - standard check for tags etc.
This should be integrated into pootle somehow - and errors in there
should "block" the exporting (syncing to on-disk-files) to avoid
checking in invalid files (that then break the build)
The problem is false positives. So I'm a bit reluctant to make it
blocking. Its also a bit confusing to a user who then can't work out
why their changes aren't on disk.
What probably should be done is to use po2oo with validation enabled.
We coded it a while back and I don't think anyone is using it. This can
either warn or drop translations that are failing, we only do it on
critical tests: variables, escapes IIRC. This could be enabled to drop
in early phases and then warn towards the final release.
readmecheck - same as gsicheck but for the readme
doublecheck - check if different English strings were translated into
the same at critical parts of the code
In an ideal world I'd love those tools to inject the found errors back into
Pootle so that you have one place to find and fix errors and no cryptic
strings we need to search for.
Yes, indeed. But pootle should be more strict than gsicheck (but of
course it should cover everything that gsicheck finds) While pootle
already catches some of the errors, it doesn't flag this one for
example:
We designed it to catch all gischecks and more, so yes please report
ones that we miss. The idea being that it's easier to fix these errors
in Pootle then to try and 1) understand the gsicheck failure and 2) find
the errors in Pootle.
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id3149902.25
(in case sophie is too fast and fixes it in the meantime:
Dans une fenêtre de fichier de base
de données, cliquez sur l'icôneRequêtes, puis choisissez
Éditer - Éditer. Lorsque les champs de référence
n'existent plus, vous voyez cette boîte de dialogue
i.e.
non-matching - missing "h" - pootle doesn't flag it
I've created http://bugs.locamotion.org/show_bug.cgi?id=1910
It's always better to have some false positives than to miss stuff.
Except when we have too many false positives of course :) Now that we
can mark false positives it makes it a bit easier to eliminate those.
And may I suggest to change the theme to give a bigger font for the
translation-box? I guess that's one of the reasons of missing quotes
or writing an *opening* tag as and not noticing it.
You'll have to fight with Friedel on that one. These are in CSS so you
can change that on the LibO server.
But even better would be a "commit-hook" that instead of letting you
advance to the next translation unit points you back at the
just-changed string with a message "You very likely introduce an error
here - you mistyped the tag's name or something" :-)
Or something like that. I'd prefer live, but that involves AJAXy stuff
and probably better suited for Pootle 2.2. I have some other ideas that
could be quick wins and work on 2.1.x.
--
regards
Dwayne
--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Also, same word in English may indeed relate to a different words in translation depending on context. -Yury On 04/19/2011 03:21 PM, Andras Timar wrote: ... This is not a false positive. You need to translate Heading and Title to different words, otherwise you'll have troubles with default styles in the localized product. See for example -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Christian thanks for You explanation. you are correct. I will correct all strings with "Heading" word 2011/4/20 Christian Lohmaier > Hi again, > > On Wed, Apr 20, 2011 at 10:35 AM, Sérgio Marques > wrote: > > > > Your information was relevant. > > Hmm - your fix seems suboptimal. > > the HEADING one is the paragraph style entries in Format & Styles, you got > Heading > Heading 1 > Heading 2 > ... > Heading 10 > > i.e. those are the styles to structure and format your documents. > > You did choose > Cabeçalho principal > Cabeçalho 1 > ... > Cabeçalho 10 > > I think this is misleading, as the "Heading" style is not meant for > structuring, but to define basic styling (Font, ) for all the > other headers, instead of setting this for each Header 1-10 manually. > (i.e. you're not supposed to apply that style to your document, but > only use the numbered ones, the one without number is only to define > common formatting) > > The HEADER one on the other hand has nothing to do with > heading-styles, but it is the one meant for the area on top of each > page, that is the same on all pages (the thing at the bottom is the > footer), you set it in Format|Page > As there are left and right pages, there is the base Header style and > also Header left and Header right. > > Of course I don't really know Portuguese, but having the same word for > both sounds really strange to me (and the pt_BR variant uses Titulo > for the Heading ones) > > ciao > Christian > > -- > Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/www/l10n/ > All messages sent to this list will be publicly archived and cannot be > deleted > > -- Sérgio Marques -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi again, On Wed, Apr 20, 2011 at 10:35 AM, Sérgio Marques wrote: > > Your information was relevant. Hmm - your fix seems suboptimal. the HEADING one is the paragraph style entries in Format & Styles, you got Heading Heading 1 Heading 2 ... Heading 10 i.e. those are the styles to structure and format your documents. You did choose Cabeçalho principal Cabeçalho 1 ... Cabeçalho 10 I think this is misleading, as the "Heading" style is not meant for structuring, but to define basic styling (Font, ) for all the other headers, instead of setting this for each Header 1-10 manually. (i.e. you're not supposed to apply that style to your document, but only use the numbered ones, the one without number is only to define common formatting) The HEADER one on the other hand has nothing to do with heading-styles, but it is the one meant for the area on top of each page, that is the same on all pages (the thing at the bottom is the footer), you set it in Format|Page As there are left and right pages, there is the base Header style and also Header left and Header right. Of course I don't really know Portuguese, but having the same word for both sounds really strange to me (and the pt_BR variant uses Titulo for the Heading ones) ciao Christian -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Thanks Christian, Your information was relevant. regards 2011/4/20 Christian Lohmaier > Hi Sérgio, *, > > On Wed, Apr 20, 2011 at 10:25 AM, Sérgio Marques > wrote: > > Hi Andras > > > > In pt I fixed the lines in > > http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt.err but I cant find > the > > file that has double entry reported in > > http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt.log > > > > Entry double for LANG=pt in file pt.sdf > > > > sw source\ui\utlui\poolfmt.src 0 string > STR_POOLCOLL_HEADLINE_BASE 0 pt > Cabeçalho 2002-02-02 > > > https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?search=STR_POOLCOLL_HEADLINE_BASE&sfields=locations > ( > https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?unit=3495718 > ) > > > 02:02:02 > > sw source\ui\utlui\poolfmt.src 0 string > STR_POOLCOLL_HEADER 0 pt Cabeçalho > 2002-02-02 > > 02:02:02 > > > https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?search=STR_POOLCOLL_HEADER&sfields=locations > > ( > https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?unit=3495837 > ) > > ciao > Christian > > -- > Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/www/l10n/ > All messages sent to this list will be publicly archived and cannot be > deleted > > -- Sérgio Marques -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Sérgio, *, On Wed, Apr 20, 2011 at 10:25 AM, Sérgio Marques wrote: > Hi Andras > > In pt I fixed the lines in > http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt.err but I cant find the > file that has double entry reported in > http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt.log > > Entry double for LANG=pt in file pt.sdf > > sw source\ui\utlui\poolfmt.src 0 string > STR_POOLCOLL_HEADLINE_BASE 0 pt > Cabeçalho 2002-02-02 https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?search=STR_POOLCOLL_HEADLINE_BASE&sfields=locations (https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?unit=3495718) > 02:02:02 > sw source\ui\utlui\poolfmt.src 0 string STR_POOLCOLL_HEADER > 0 pt Cabeçalho > 2002-02-02 > 02:02:02 https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?search=STR_POOLCOLL_HEADER&sfields=locations (https://translations.documentfoundation.org/pt_BR/libo34x_ui/sw/source/ui/utlui.po/translate/?unit=3495837) ciao Christian -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
On 2011-04-20 03:20, Christian Lohmaier wrote:
Hi *,
On Wed, Apr 20, 2011 at 2:15 AM, Christian Lohmaier
wrote:
[broken translations that break the build]
So please fix those "Expected Symbol: Close tag for" ones as
fast as possible, and have Andras upload them, otherwise chances are
that your language will just be skipped.
For your convenience, I wrote a awk one-liner to turn the error-log
into clickable URLs that will take you to the translation unit in
question:
Nice. Could we put an HTML page based on your awk script up to
complement the raw data? This certainly makes finding and fixing the
errors easy.
all in one single line - example for the fr.err log:
awk -F'\t' '$10!="en-US" { n=split($2, fp, /\\/); up=""; for (i=3;
ihttps://translations.documentfoundation.org/"; $10
"/libo34x_" $4 up ".po/translate/?sfields=locations&search=" $5 su}'
< fr.err
would result in
https://translations.documentfoundation.org/fr/libo34x_help/schart/01.po/translate/?sfields=locations&search=par_id7272255
https://translations.documentfoundation.org/fr/libo34x_help/schart/01.po/translate/?sfields=locations&search=par_id2259225
https://translations.documentfoundation.org/fr/libo34x_help/shared/01.po/translate/?sfields=locations&search=par_id31323250502
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id355152952
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id993155271
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id993159201.14
https://translations.documentfoundation.org/fr/libo34x_help/shared/00.po/translate/?sfields=locations&search=par_id3149902.25
https://translations.documentfoundation.org/fr/libo34x_help/scalc/guide.po/translate/?sfields=locations&search=par_id3148576.19
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id3159084.88
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id3146806.89
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id3146130.90
https://translations.documentfoundation.org/fr/libo34x_help/sbasic/shared.po/translate/?sfields=locations&search=par_id31455974
the one-liner explained:
awk -F'\t'
tab is field seperator (I used awk, but of course you could do the
same with perl, sed,)
'$10!="en-US"
we're not interested in the english original strings when creating the
URL, as the original string is displayed in pootle anyway (and the
10th field in the error-log is the language tag)
{ n=split($2, fp, /\\/); up=""; for (i=3; i., also use it.
print "https://translations.documentfoundation.org/"; $10 "/libo34x_"
$4 up ".po/translate/?sfields=locations&search=" $5 su}'
assemble& print the URL
https://translations.documentfoundation.orgtranslate/?sfields=location&search=[]
< fr.err
read the file "fr.err" as input
ciao
Christian
--
regards
Dwayne
--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
Hi Andras In pt I fixed the lines in http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt.err but I cant find the file that has double entry reported in http://ftp.fsf.hu/LibreOffice/3.4-beta2-l10nbugs/pt.log Entry double for LANG=pt in file pt.sdf sw source\ui\utlui\poolfmt.src 0 string STR_POOLCOLL_HEADLINE_BASE 0 pt Cabeçalho 2002-02-02 02:02:02 sw source\ui\utlui\poolfmt.src 0 string STR_POOLCOLL_HEADER 0 pt Cabeçalho 2002-02-02 02:02:02 Can You point me the way? Regards 2011/4/20 Andras Timar > 2011.04.20. 5:34 keltezéssel, Sophie Gautier írta: > > > > But thanks a lot again really, that will help me to correct the files > > quickly later today. > > > > I fixed all build build breakers in cy, fr, ja and pt in git. Next time > I'll check them before I commit. > > Best regards, > Andras > > -- > Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/www/l10n/ > All messages sent to this list will be publicly archived and cannot be > deleted > -- Sérgio Marques -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Translations from Pootle pushed to git (for 3.4 beta2), bugs to fix
On 2011-04-20 05:34, Sophie Gautier wrote: Hi Christian, On 20/04/2011 04:20, Christian Lohmaier wrote: Hi *, On Wed, Apr 20, 2011 at 2:15 AM, Christian Lohmaier wrote: [broken translations that break the build] So please fix those "Expected Symbol: Close tag for" ones as fast as possible, and have Andras upload them, otherwise chances are that your language will just be skipped. For your convenience, I wrote a awk one-liner to turn the error-log into clickable URLs that will take you to the translation unit in question: thanks a lot, it's very kind :) but my issue here is more about my own organization than fixing the errors. I'm translating off line using wordorge of gedit, so I need to get my local files and Pootle files in sync. The process po2sdf -> gsicheck -> correcting po then upload on pootle is quite long and I tend to make it only when I'm over with the most important part of localization. You could try these two suggestions: 1) Run 'po2oo --filteraction=warn' or 'pofilter --openoffice'. Either will pick up your errors before needing to run gsicheck. If you get stuck I can give lessons. Both of these will use the same checks that are available on Pootle. 2) Try Virtaal beta5 - this includes the LibO specific checks as you type. Installation instructions: Win: http://translate.sourceforge.net/snapshots/virtaal-0.7.0-beta5/Virtaal-0.7.0-beta5-setup.exe Debian: http://markmail.org/message/s35zfyofrc3qad2v Fedora: http://markmail.org/message/2wpzjejxgauz5f4k -- regards Dwayne -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
