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

Den 30.05.2015 14:36, Dwayne Bailey skreiv:
On 30 May 2015 at 12:51, Kolbjørn Stuestøl < <>> wrote:

    The new version looks fine but I do have problems with the
    "Critical errors".
    Some examples:
    When translating a plain text, for example "Print Preview Bar" and
    inserting XML tags ("Print <emph>Preview Bar</emph>") in the
    translated text I get an error. Error message: XML tags.

Ideally, please point to a specific unit, you can get the permalink from the unit number at the end of the breadcrumbs for the unit you are editing.
Sorry, wasn't aware of that. But in this case it applies to all units.

Also note. The checks have not changed. The editor has changed in that it prevents a Critical failure from being submitted to Pootle. The logic is that we want to stop breakages much much earlier in the process.

Now the check is right (the check is also dumb). There is no <emph> in the source, so it assume that you've likely broken something. Its XML and thus its risky.

Because you know better you can click on the Mute symbol. The small (-) after the check name. If a check is muted it means you've signaled that it is a false positive and Pootle should ignore it for that unit.
Wasn't aware of this either. Thought it was a warning sign or something :-). Thank you.

    If I insert the quotation marks « and » ( instead of the " and "),
    press Send and then open it again, it is opened with the error
    message "Double quotes" and the Send button is grayed out.

So quote are not critical. Pootle has actually accepted the unit but warned that your quotes are different.

Which raises another issue. We build rules for languages to take into consideration their specific quoting styles. This reduces false positives on quotes.

If you can let me know for nn what the quoting style is then I can add that.
For Norwegian bokmål (language code nb) and nynorsk (nn) the recommended quotes are
At start « (Unicode hex 00AB); at end » (Unicode hex 00BB).
I do not think we needs the quote in quote characters neither the quotes in quotes in quotes. Is it possible to use the <quote> tag and let LibreOffice "translate" it to the language used?

    Translating "Print Statement [Runtime]" to "Print-uttrykk
    [køyretid]" returns the error "Placeholders". Inserting the
    original text into my translation using the + button or by copy
    and paste, pressing Send works as normal. Changing my text to
    "Print-uttrykk [Rundtime]" it is accepted, but "Print-uttrykk" or,
    as mentioned above, "Print-uttrykk [køyretid]" is not. Error
    message: Placeholders.

Yip false positive again.

I need some help here. For [XXX] was used as a variable in some files. With the change to use PO directly in LibreOffice I'm not sure if that has changed. In fact if someone has an idea of the correct variable styles for LO across the project I can likely remove some redundant ones.

    Tried on LibreOffice 4.4 - Help. Windows 7. Norwegian nynorsk (nn)

Thanks for the testing.

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.