MX Linux Forum

All,

We have a new repo we need translations for. There are about 79 new lines in this one, so please take a look when you get a chance. Your efforts are greatly appreciated!

https://www.transifex.com/anticapitalis ... ba-config/

Thank you all!

Thanks Roy, I think the .desktop file also needs to be translated (the Comment fields)

Hi Ravrett.

Could you please clarify a question I have about what we should do in Transifex when we find it:

Name=MX Samba Config
Comment=Manage user Samba shares

In the translation should I include?
Name[pt_BR]=
Comment[pt_BR]=

Or is it not necessary and in the translation should I just keep Name= and Comment= followed by the translated text?

Grateful.

marcelocripe
(Original text in Brazilian Portuguese language)

- - - - -

Olá Ravrett.

Por favor, você poderia esclarecer uma dúvida que eu possuo sobre o que devemos fazer no Transifex quando encontramos:

Name=MX Samba Config
Comment=Manage user Samba shares

Na tradução eu devo incluir?
Name[pt_BR]=
Comment[pt_BR]=

Ou não é necessário e na tradução devo manter apenas Name= e Comment= seguido do texto traduzido?

Grato.

marcelocripe
(Texto original em idioma Português do Brasil)

You can translate both Name and Comment. Something like

Name=MX Samba Configuração
Comment=Gerenciar sua configuração Samba

Shortly; no need to [pt_BR] (etc.) (as all will be already in that language section) :)

This is surprising because we have not always been told this.
There are many languages translated at Transifex that have added the local language after Name and Comment.
Should [fr], [fr_BE], [pt], [pt_BR]... be removed at Transifex?
What is best for the development team, with or without?

I mean, like this :

@Wallon & @marcelocripe :

Just, not to be confused with this way of (direct) translation: viewtopic.php?p=656992#p656992

Huckleberry Finn wrote: Wed Jan 05, 2022 1:15 pm Shortly; no need to [pt_BR] (etc.) (as all will be already in that language section) :)

Note: Quite a lot of MX apps, do have two entries on transifex one for the application translations and another one for the translations of the desktop-files. That's the way it was setup for MX quite a long time ago.
In theory, those desktop-file translation could go into the application transifex-resource, but currently this way is not prepared for at least the most Qt-based applications, b/c Qt uses a complete different translation api and translation files ".ts", no po-files . It might be simpler for non Qt-based apps, as with the modern xgettext tools, generating desktop-files (and xml-policy files) based on po-translations files is easy. Generating desktop-files from QT ts-files is something we might look into in the future.
HTH