Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Dwayne,

2011.02.20 18:40, Dwayne Bailey rašė:
On 2011-02-20 12:53, Rimas Kudelis wrote:
2011.02.20 11:40, leif rašė:
Hi all,
I have a small question about the merged files on Pootle. We can see
that there is a lot of strings with the a warning (Failing Checks) about
xmltags.

https://translations.documentfoundation.org/da/libo33x_help/translate.html?matchnames=xmltags

Does this indicate a problem or just that the check has failed? As far
as I can see there is no problem with most of these strings.

It looks like the reason behind that is that you change the name= attribute of those tags. However, I'm not sure if that's bad for us or not. :)

Maybe Sophie or someone else can tell more?

There was some discussion about this over at OOo. Seems that the entries when used are case insensitive, but of course our tests aren't. One of their solution was the idea of normalising all these entries.

I'm not sure we want to change the xmltags test in this case but rather fix this in the source and target text.

Well in https://translations.documentfoundation.org/da/libo33x_help/translate.html?matchnames=xmltags, I don't see case differences, but the string is still reported.

Rimas


--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.