Update of TSCP example file for localization

l10n
#1

Hi all.

Localization teams may want to follow the example below and update + localize their TSCP configuration file:

https://gerrit.libreoffice.org/c/core/+/117267

The strings of this file are not brought to weblate.

Kind regards

#2

Hello, Olivier,

what is this now?
How is it possible that this cannot be localized via po files?

Lp, m.

V V tor., 15. jun. 2021 ob 19:49 je oseba Olivier Hallot <
olivier.hallot@libreoffice.org> napisala:

#3

What can we do with the link you provided?
What English strings need to be translated?
This is very poorly managed for the stake of l10n teams...

Please give detailed directions for every single instance of a file that
needs to be localized outside of Weblate.
This cannot be some black magic, handled by the Documentation team and not
clearly documented for the l10n teams ...

Lp, m.

V V tor., 15. jun. 2021 ob 23:38 je oseba Martin Srebotnjak <
miles@filmsi.net> napisala:

#4

V V tor., 15. jun. 2021 ob 19:49 je oseba Olivier Hallot <
olivier.hallot@libreoffice.org> napisala:

Hi all.

Localization teams may want to follow the example below and update +
localize their TSCP configuration file:

https://gerrit.libreoffice.org/c/core/+/117267

The strings of this file are not brought to weblate.

Kind regards
--
Olivier Hallot
LibreOffice Documentation Coordinator
Rio de Janeiro - Brasil - Local Time: UTC-03:00
LibreOffice – free and open source office suite:
https://www.libreoffice.org
Respects your privacy, and gives you back control over your data
http://tdf.io/joinus

--
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

V V tor., 15. jun. 2021 ob 23:38 je oseba Martin Srebotnjak <
miles@filmsi.net> napisala:

Hello, Olivier,

what is this now?
How is it possible that this cannot be localized via po files?

Lp, m.

> What can we do with the link you provided?
> What English strings need to be translated?
> This is very poorly managed for the stake of l10n teams...
>
> Please give detailed directions for every single instance of a file that
> needs to be localized outside of Weblate.
> This cannot be some black magic, handled by the Documentation team and not
> clearly documented for the l10n teams ...
>

Here you can see the existing files:

https://git.libreoffice.org/core/+/refs/heads/master/sfx2/classification/

You can add new files or edit existing files in the Gerrit web interface: https://gerrit.libreoffice.org/Documentation/user-inline-edit.html

In the Open File dialog, input sfx2/classification/example_...xml according to your language code.

Ilmari

#5

Hi Martin, all,

What can we do with the link you provided?
What English strings need to be translated?
This is very poorly managed for the stake of l10n teams...

Please give detailed directions for every single instance of a file that
needs to be localized outside of Weblate.
This cannot be some black magic, handled by the Documentation team and not
clearly documented for the l10n teams ...

From the ESC minutes:
* l10n (Sophie)
  + work is ongoing
  + Christian is looking after some bugs in glossaries
  + could we have
https://git.libreoffice.org/core/+/refs/heads/master/sfx2/classification/ in
a more translator friendly way?
    + lacking original English text in the file
    + raised on l10n list (Olivier)
      sample file in Gerrit, needs to be cloned and translated, not
possible on Weblate but needs to be done in Gerrit, which is an issue
for translator
    + might be possible to use some existing tooling (Cloph, will work
on that)
    + a feature implemented by Collabora, unfortunately not widely
publicized
     (Olivier)

As a general note, it's not a good process to update translation
directly in Gerrit. And in this particular case, Christian will work on
it to reuse existing tool and have it in Weblate.
Cheers
Sophie