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


Hi Martin, *,

yes, this or another approach... . But sadly, we still haven't one. At least I am not aware of such.

I am a translator, mostly fixing stuff in our own translation or silence false positives, when they occur for better overview.

So I stumbled over the failures in our help text sources, and since I am able to contribute there myself, thank to:

https://wiki.documentfoundation.org/Documentation/GerritEditing .

I do not longer waste my and others time to report them.
In opposite, I asked to forward such reports to me, so I can look into the correspondending file and correct,
what I find there.

But for now, I know I have to be a bit reluctant for the reason already mentioned.


Am 25.04.2018 um 17:49 schrieb Martin Srebotnjak:
Hi, Sophia, *,

that is why I suggested a simple extension of gerrit interface with a flag whether that particular issue changes UI or help strings/affects l10n process.

That way it would be much easier for interested documentation and l10n team members to check on those entries before they get pushed or report errors just as they get pushed. And not after a few months when they land in the updated Pootle and first translators recognize them as errors ...

Lp, m.

2018-04-25 16:47 GMT+02:00 Sophia Schröder <sophia.schroeder@libreoffice.org <mailto:sophia.schroeder@libreoffice.org>>:

    Hi Sophie, *,

    this is what I meant:
    If new strings arrive in pootle, and there are wrong / malformatted,
    leave them out of translation for now and do it *after* they are
    corrected.

    Unhappily I cannot test them beforehand locally
    (and I am not responsible for most of them beeing malformatted,
    but of course a few. ;-))

    Suggestions for improvements even of wording and text formatting
    are always welcome, of course.


    Am 25.04.2018 um 14:47 schrieb Sophie:

        Hi Sophia, Olivier, all
        Le 25/04/2018 à 14:33, Sophia Schröder a écrit :

            I am going to correct them, so they would appear again. ;-)

            Example:

            
https://translations.documentfoundation.org/de/libo_help/translate/#filter=incomplete&unit=149686853&offset=54
            
<https://translations.documentfoundation.org/de/libo_help/translate/#filter=incomplete&unit=149686853&offset=54>

        This should not arrive in Pootle, there is no translation work
        here, so
        why should we care about it? Again, the commit introducing
        spaces should
        not have been pushed. Why hundreds of languages should work on
        that 2 or
        3 times afterwards?
        Cheers
        Sophie



            Am 25.04.2018 um 14:21 schrieb Martin Srebotnjak:

                Why would we do that - leave them untranslated?

                Could you please elaborate with an example?

                Lp, m.

                V sre., 25. apr. 2018 14:07 je oseba Sophia Schröder <
                sophia.schroeder@outlook.com
                <mailto:sophia.schroeder@outlook.com>> napisala:

                    Hello all,

                    please avoid translation of wrongly formatted
                    strings, even their
                    retranslations.

                    I am in a bigger process to correct them and
                    improve formatting like
                    emphasises in help text sentences themself.

                    The only one I leave untouched for now are the
                    malformed bookmark tags.



-- To unsubscribe e-mail to:
                    l10n+unsubscribe@global.libreoffice.org
                    <mailto:l10n%2Bunsubscribe@global.libreoffice.org>
                    Problems?
                    https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
                    <https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/>
                    Posting guidelines + more:
                    https://wiki.documentfoundation.org/Netiquette
                    <https://wiki.documentfoundation.org/Netiquette>
                    List archive:
                    https://listarchives.libreoffice.org/global/l10n/
                    <https://listarchives.libreoffice.org/global/l10n/>
                    All messages sent to this list will be publicly
                    archived and cannot be
                    deleted



-- Regards / Mit freundlichen Grüßen

    Sophia Schröder
    ---
    German Language Team
    LibreOffice.org
    IRC: SophiaS


-- To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
    <mailto:l10n%2Bunsubscribe@global.libreoffice.org>
    Problems?
    https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
    <https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/>
    Posting guidelines + more:
    https://wiki.documentfoundation.org/Netiquette
    <https://wiki.documentfoundation.org/Netiquette>
    List archive: https://listarchives.libreoffice.org/global/l10n/
    <https://listarchives.libreoffice.org/global/l10n/>
    All messages sent to this list will be publicly archived and
    cannot be deleted



--
Regards / Mit freundlichen Grüßen

Sophia Schröder
---
German Language Team
LibreOffice.org
IRC: SophiaS


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

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.