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<dwayne@translate.org.za>:
> > 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:
> <variable id="FehlendesElement">Dans  une fenêtre de fichier de base
> de données, cliquez sur l'icône<emph>Requêtes</emph>, puis choisissez
> <emph>Éditer - Éditer</emp>. Lorsque les champs de référence
> n'existent plus, vous voyez cette boîte de dialogue</variable>
>
> i.e.
> <variable>
>   <emph></emph>
>   <emph></emp>     !!!! non-matching - missing "h" - pootle doesn't flag it
> </variable>
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</tag>  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+help@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