[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] Weblate instance for testing purposes


Hi *,

On Wed, Aug 28, 2019 at 12:13 PM Yaron Shahrabani <sh.yaron@gmail.com> wrote:
>
> https://vm137.documentfoundation.org/translate/libo_ui-master/dbaccessmessages/he/?type=todo&offset=2
>
> This is the exact path, sorry.

Hint: similar to poolte, weblate has direct/permalink functionality
that is better to use than offset/todo links, as those might change -
and in this case the string that shows up is in Hebrew (but I see the
German strings in the "nearby strings" view)
This is not a bug in weblate or in the migration path, but rather a
problem that already exists in the files on pootle:
https://translations.documentfoundation.org/he/libo_ui/translate/dbaccess/messages.po#unit=137591116
And given the history of the string (or rather the translation memory
entry) it's an old issue, at least since 5.3..
No idea when or how those strings were turned to German...

tldr; no issue with weblate, was already having German stings in the
files from pootle used for the import to weblate

ciao
Christian

--
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/
Privacy Policy: https://www.documentfoundation.org/privacy

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.