On 20/02/2011 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?
Not more, just I agree :-) The guide says that we are allowed to
translate them, page 12 you find:
---------------------------------------------
Element: link
Attributes: href, name, type, target
Description: Designates a hyperlink to another help file or to the WWW
as specified by the href attribute.
Element link
Rule:     - Localize element content
    - Localize the name attribute
    - Copy the rest of the element tags exactly
Example:
Source:
\<link href=\"text/swriter/123.xhp\" name=\"Name of the
link\"\>Using Headings\<\/item\>
Localized:
\<link href=\"text/swriter/123.xhp\" name=\"Name des
Links\"\>Überschriften verwenden\<\/item\>
------------------------------------------
So, if you are sure that you didn't forget any part of the link, you
can simply ignore it.
Kind regards
Sophie
  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.