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

Well .desktop files have nothing to do with Qt or C++, they are just text files used by the Desktop Environment to create menu entries. I mean there might be a way to set up the .pro file and building procedure to have that generated at build time, but even if possible, the simplest way is just to add the translations in the .desktop text file.

The presentation is not the same in Transifex for all files.
I'm talking about mx-all-dektop-entries which presents the Name and Comment variables in the translations!
Here I think it is better to put the local language after Name and Comment.

Adrian wrote: Wed Jan 05, 2022 3:40 pm Well .desktop files have nothing to do with Qt or C++, they are just text files used by the Desktop Environment to create menu entries. I mean there might be a way to set up the .pro file and building procedure to have that generated at build time, but even if possible, the simplest way is just to add the translations in the .desktop text file.

That's not the simplest way for the poor translators to have two distinct transifex-resources for one application. They translations tend to go out of sync esp, if the same string is used within both places, or simply just get not updated over time. In theory, the translations on transfix could be stored as po files, and on the fly at build time converted to qm-translations. Or just the .ts files can be converted (using Qt's own tools) to po files to generate any other app related file with translations like desktop file, autostart entries or policy-xml files. I'm not aware that Qt offer such tools itself, but it's easy with po-based gettext-tools todo. Might be I'm preparing something to demonstrate.

I think the question is simple.

If Transifex puts the variables Name and Comment in the translation, the local language should be put.

If Transifex does not put the variables Name and Comment in the translation, the local language should not be put.

I think this is how it should be understood.

Now, this has to be confirmed by the development team.

"Name" and "Comment" in .desktop are the name of the "variables" and should not be translated, what comes after them should.

So in:
Name=MX Samba Config
Comment=Manage user Samba shares

Only what comes after "=" should be translated.

When I started in August 2020 with the voluntary work of reviewing, correcting and improving the translations of the project /anticapitalist/antix-development/ for antiX and MX linux, I found the file "mx-all-desktop-entries" with "Name[pt_BR] =" and "Comment[pt_BR] =" and I didn't change it because
there are no developer/developer comments on this information.
The file "antix-all-desktop-entries" does not have "Name[pt_BR]=" and "Comment[pt_BR] =", and the anti-capitalist orientation (https://www.antixforum.com/forums/topic ... #post-2558) was to not translate "Name=" and "Comment=".
What is the orientation in MX Linux?

I learned from Robin-antiX that .pot files can receive programmer comments, if memory serves, the comment text in the .pot file starts with '#. ', this way the comments will be visible in Transifex. Please confirm this information as it may just be my misunderstanding due to machine translation.

I imagine you use some script to extract from the "mx-all-desktop-entries" file of each language the translated texts of the entries
"Name=" and "Comment=". Does the script expect to find "Name =" or "Name[pt_BR]=", "Comment=" or "Comment[pt_BR]="?

If the guidance so that I don't need to include in the Transifex translation text [pt_BR] or [fr_BE] or [pt], I will need to remove from the Transifex files the 85 entries.

Grateful.

- - - - -

Quando eu iniciei em agosto de 2020 com os trabalhos voluntários de revisão, correção e melhorias das traduções do projeto /anticapitalista/antix-development/ para o antiX e para o MX linux, eu encontrei o arquivo "mx-all-desktop-entries" com "Name[pt_BR] =" e "Comment[pt_BR] =" e não alterei isso porque
não há comentários do programador/desenvolvedor sobre esta informação.
O arquivo "antix-all-desktop-entries" não possui "Name[pt_BR]=" e "Comment[pt_BR] =", e a orientação do anticapitalista (https://www.antixforum.com/forums/topic ... #post-2558) foi para não traduzir "Name=" e "Comment=".
Qual é a orientação no MX Linux?

Eu aprendi com o Robin-antiX que os arquivos .pot podem receber comentários do programador, se não me falha a memória, o texto do comentário no arquivo .pot inicia com '#. ', desta forma os comentários ficarão visíveis no Transifex. Por favor, confirme esta informação, pois pode ser apenas um mal entendido meu devido a tradução automática.

Eu imagino que vocês utilizam algum script para extrair do arquivo "mx-all-desktop-entries" de cada idioma dos textos traduzidos das entradas
"Name=" e "Comment=". O script espera encontrar "Name =" ou "Name[pt_BR]=", "Comment=" ou "Comment[pt_BR]="?

Se a orientação para que não é preciso incluir no texto da tradução do Transifex [pt_BR] ou [fr_BE] ou [pt], eu precisarei remover dos arquivos do Transifex das 85 entradas.

Grato.

Dear developers and programmers.

Yesterday I removed "Name[pt_BR]=" and "Comment[pt_BR]=" from all entries in the translations of the file "mx-all-desktop-entries" from the Trasnifex site and left only "Name=" and "Comment=" , after the equal sign ' = ' is the translation in pt-BR.
Please use all texts contained in the file "mx-all-desktop-entries", I updated it and made several improvements that will be beneficial to MX Linux when read by Brazilians.

On behalf of the Telegram group "MX Linux and antiX Brasil" (with over 400 people participating), I thank you for creating, developing and maintaining MX Linux.

- - - - -

Caros desenvolvedores e programadores.

Ontem eu removi "Name[pt_BR]=" e "Comment[pt_BR]=" de todas as entradas das traduções do arquivo "mx-all-desktop-entries" do sítio Trasnifex e deixei apenas "Name=" e "Comment=", após o sinal de igual ' = ' está a tradução em pt-BR.
Por favor, utilizem todos os textos contidos no arquivo "mx-all-desktop-entries", eu o atualizei e fiz várias melhorias que serão benéficas ao MX Linux quando lidas por Brasileiros.

Em nome do grupo de Telegram "MX Linux e antiX Brasil" (com mais de 400 pessoas participantes), eu agradeço por criarem, desenvolverem e manterem o MX Linux.