Re: [libreoffice-l10n] Invalid XML errors in help translations

2013-02-12 Thread Adolfo Jayme Barrientos
On Mon, Feb 11, 2013 at 9:30 AM, Andras Timar  wrote:
> Dear localizers,
>
> There is a very important check in Pootle: Invalid XML. When a
> translated segment contains invalid XML, that segment will be
> discarded, and en-US will be used instead. The error message however
> appears in the build log and makes noise.
>
> David Tardon fixed these in git, so you'll see what languages are
> affected. Unfortunately his work will be ruined when I update git from
> Pootle next time. So please always check for Invalid XML errors, and
> correct them.

Thanks for the heads-up, Andras! For what it’s worth, I’ve already
fixed the invalid Spanish strings found by David — one of these was my
fault BTW, oops!

-- 
Adolfo

-- 
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted



Re: [libreoffice-l10n] Invalid XML errors in help translations

2013-02-12 Thread Andras Timar
Hi Zeki,

On Tue, Feb 12, 2013 at 11:09 PM, Zeki Bildirici  wrote:
>
> The first string in a/m gerrit log. At the bottom page for Turkish
> starting with: "Automatically assigns consecutive numbers to the
> footnotes..." gaves n result in search.
>
> :(
>

Yes, search feature in Pootle is not so great in these days. Hopefully
it was fixed in the meantime. If not, I'll fix it in Pootle manually,
when I see the bug again.

> Also there was 5 invalid xml in help and 3(not sure) in ui.
>
> Currently there are 2 invalid xml checks but i cannot see any wrong xml input.
>
> - 
> https://translations.documentfoundation.org/tr/libo_ui/translate.html#unit=32679620
> - 
> https://translations.documentfoundation.org/tr/libo_help/translate.html#unit=33060896
>

False positives. There are a few. You can remove the Invalid XML flag from them.

Best regards,
Andras

-- 
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted


Re: [libreoffice-l10n] Invalid XML errors in help translations

2013-02-12 Thread Zeki Bildirici
2013/2/11 Andras Timar :
> Dear localizers,
Hi Andras,
> There is a very important check in Pootle: Invalid XML. When a
> translated segment contains invalid XML, that segment will be
> discarded, and en-US will be used instead. The error message however
> appears in the build log and makes noise.

I've just seen it, Invalid XML check is great. Previously we had to
find strings from your error logs, and fighting with XML check was
hard.

I have fixed one of this. But i cannot find the other string. The
search comes with no results again :(

The first string in a/m gerrit log. At the bottom page for Turkish
starting with: "Automatically assigns consecutive numbers to the
footnotes..." gaves n result in search.

:(

Also there was 5 invalid xml in help and 3(not sure) in ui.

Currently there are 2 invalid xml checks but i cannot see any wrong xml input.

- 
https://translations.documentfoundation.org/tr/libo_ui/translate.html#unit=32679620
- 
https://translations.documentfoundation.org/tr/libo_help/translate.html#unit=33060896

> https://gerrit.libreoffice.org/gitweb?p=translations.git;a=commitdiff;h=6ee465836d1fee4b4fbe714bde3b804cdda1b4ff

Best regards,
Zeki

-- 
Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted