A new resource present at transifex: »antiX .desktop files«

[Member Robin]

There again a new resource is present at antiX-contribs on transifex: antiX desktop files. This time all the missing translations collected from .desktop files of antiX 21 (suitable for antiX 19 also) are waiting for translation. By now manual translation only, we’ll have to learn how to machine translate this filetype for all the languages with no active translators, before we can supply machine translation for this resource.

Please carefully look into the “developers notes” at the right side of transifex translation editor to get an idea what a specific string is meant for and to which program or file it belongs.

Basically there exist three types of entries:

• Name
• GenericName
• Comment

These three types of entries refer to the translatable entries within all our desktop files.
»Name« and »GenericName« means the Name of the program or file, these entries should get translated to strings not too long.
»Comment« will probably show up as short additional information about the program. You can add synonyms here, and a short description what the program will do when executed.

Not all .desktop files dispose of all types of entries. Sometimes only “Name” is present, sometimes only “Name” and “Comment”. This will get fixed by and by. By now the translatable entries as well as the existing translations depend on what was found within the .desktop files present in recent antiX 21 (full). No completely missing entries have been added.

Moreover there may be found multiple e.g. »Name« entries existing for a specific file, in case the .desktop file consists of more than one section.

Examples for sections might be »desktop entry« (present in most .desktop files), »Desktop Action SendFile«, »Desktop Action ComposeMail« and so on, each of which referring to another functionality of a program. Treat them as all the other entries also, but be aware they do belong to a single .desktop file. You will find the section name of an entry in the developers notes, along with the entry type and the (file-)name of the .desktop file an entry belongs to.

Many thanks to @marcelocripe helping me to let this project turn into reality.

And now: happy translating!

Robin

P.S.: The .string type files downloadable from transifex “for use” and “for translation” are no .desktop files, but they can be used for offline editing the strings stored within. These files are apple style simple text files, utf-16 encoded, and in antiX they can be edited without any conversion, using “geany” simply (open them from within geany using its “open” file menue, since the antiX file managers won’t know about this specific file type.) If you have to edit them on “windows”, notepad++ should do the job also.

Windows is like a submarine. Open a window and serious problems will start.

[Member marcelocripe]

Helpful

Up

0

::

Hello dears.

Complementing some information.

The “Name” entry is the text that will be displayed in the antiX menu.

The “Comment” entry is the text that will be displayed when searching for App Select or Rofi or similar programs. The texts of the “Comment” input help the user to find the program when he does not recognize it by name, but recognize its function or purpose. It is important to understand that the “Comment” entry is to describe what the respective program is and what it is for, this entry can be used to display information when the mouse cursor is stopped over the text displayed in “Name”.

The entry “GenericName” I still couldn’t understand its importance.

Thank you so much Robin for all your effort and commitment to antiX.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Olá caros.

Complementando algumas informações.

A entrada “Name” é o texto que será exibido no menu do antiX.

A entrada “Comment” é o texto que será exibido na busca do App Select ou do Rofi ou de programas similares a estes. Os textos da entrada “Comment” ajudam o usuário a encontrar o programa quando não o reconhece por nome, mas reconhece por sua função ou finalidade. É importante compreender que a entrada “Comment” serve para descrever o que é e para que serve o respectivo programa, esta entrada pode ser utilizada para exibir informações quando o cursor do rato fica parado sobre o texto exibido em “Name”.

A entrada “GenericName” eu ainda não consegui compreender a sua importância.

Muito obrigado Robin por todo o seu esforço e empenho no antiX.

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

[Member Wallon]

Helpful

Up

0

::

Thank you both for the explanations.

I have the impression that “antiX desktop files” is only for the antiX net or core version. Is there all the entries for the antiX full menu?

Concerning the “comment” line, I’m confused because I found at Debian or Wikipedia explanations for programs I don’t know. I explain briefly what the program does but it takes several lines. How many characters can you type? Can we put a line break (Enter key) or put the abbreviation \n in a string?

Regarding strings 137 and 138 at Transifex, I have a doubt.
NXterm, isn’t it a terminal? It is written in English that it is an editor. I did not find with Google NXterm text file editor. Strange!

Kind regards,
Wallon

[Member Wallon]

Helpful

Up

0

::

Dear Robin,

Is there a deadline for the translation of this file?
Wallonne, my wife, says that I spend too much time on antiX translations.
I have already worked almost every night of the week and almost all my weekend.
I’ll take a break.

Kind regards,
Walloon

[Member Robin]

Helpful

Up

0

::

I’ll try to answer the questions.

There is no deadline I do know of. All of us do this volunteer in our spare time, and we all have real lives “outside the PC”. So please, use only the amount of time for this project, you feel it doesn’t keep you from other real live activities. Don’t feel obliged to take the workload. We are a community, and will work on the project like a community, meaning not a single person has to stem all the tasks on his own. So, please follow the good advice of Wallonne, and take a rest from all your great translation work. There is no good in getting burned out by something which is meant as a leisure-time pursuit.
The single consideration concerning something what could be seen as a “deadline” could be the perspective of including as many translations as possible into the ISOs of antiX 21.1 release. But I have no idea when this version update will come. And as said before, none of us on community side of the project can’t do magic, it will simply be that way: what is ready by then, will be included, and what is not ready, will go into next antiX 21.2, or 21.3, and so on.

Wallon wrote:

I have the impression that “antiX desktop files” is only for the antiX net or core version. Is there all the entries for the antiX full menu?

Marcelo has taken the files for preparation from an antiX 21 “full”, so there should be all of the entries of “full” flavour present (even some more in order to cover antiX 19 also by the this translation set.) If there are still translations in menus of antiX 21 “full” missing, this is probably due to the fact, that some window managers keep their own lists of entries for the menus. So these might need some extra treatment later. Probably we should try to automatically generate the respective menu entries for e.g. IceWM, Rox or Fluxbox or whatever from the complemented .desktop files instead of translating the program lists of these desktop managers for their menus separately, providing consistency in wording and avoiding redundant translation work. But what is possible or not under these aspects will turn out only once we have the basic .desktop files translated to all languages we cover. So, keep calm, let us see what we can achieve following this path.

Wallon wrote:

Regarding strings 137 and 138 at Transifex, I have a doubt.
NXterm, isn’t it a terminal? It is written in English that it is an editor.

I can’t extemporise anything about it. As said in my very first posting: All strings and their descriptions present on transifex for translation of these desktop files now, are extracted automatically and systematically from the .desktop files of all programs living in antiX (full). This is all I know. Let’s find out, what the programs are good for. In Linux it is a good traditional habit to name programs a bit queer, so NXterm might very well be a kind of editor. Somebody must have written this description into its original .desktop file, so you found it now. We have a community, this forum, and a translator channel on IRC to discuss things like that during next weeks, months or how long it will take to sort out all the questions left.

There is a first approach you can use for all entries you don’t know to make something of:
Find the corresponding .desktop file on your system by typing

find /usr -type f -name '*.desktop' | grep nxterm
/usr/share/xfce4/helpers/nxterm.desktop

As you can see, this program is part of xfce, some kind of helper tool obviously.
Now enter

cat /usr/share/xfce4/helpers/nxterm.desktop
[Desktop Entry]
Version=1.0
Icon=nxterm
Type=X-XFCE-Helper
Name=NXterm
...
...
X-XFCE-Binaries=nxterm;
X-XFCE-Category=TerminalEmulator
X-XFCE-Commands=%B;
X-XFCE-CommandsWithParameter=%B -e %s;

So, now at least you know definitely (from its special entry “X-XFCE-Category=”) this is a terminal emulator, started by the command “nxterm”, accepting some additional parameters.

The .desktop file of this nxterm program doesn’t incorporate a “comment” entry by now (which can be true for some of the files as I mentioned in my entrance posting), so transifex entry 138 of this resource refers to another program or file already, its desktop-file-name is “root-editor”, just as its first line in its developer note reads. This one is actually a text editor obviously.
You’ll have to turn yourself into kind of »Sherlock Holms« or »Miss Marple« to find out things like that on our antiX linux sometimes.

But in most cases it is simply enough to read very carefully the content of the lines found in each single developers notes. They simply can’t be wrong (as long as the .desktop file is not wrong itself already) since they are machine generated from the .desktop files, not manually edited.

Wallon wrote:

How many characters can you type? Can we put a line break (Enter key) or put the abbreviation \n in a string?

Well, these are .desktop files. I doubt whether we can use newlines or \n within the strings, but I have to admit: This is more kind of a feeling but true knowledge. We have to find out. So simply write everything in a single line until we know about this definitely. The same goes for the maximum line length allowed in these .desktop files for the specific entry types. I don’t know where the limits of length could get calculated from. Here we need the advice of people familiar with the handling of this file type.

@marcelocripe: I hope the way I modified the developer notes for improved handling meets your expectations. The location references presented in each entry are split to three lines now, instead of forming a vertical bar separated string line only, and an additional line explains what can be done with the specific entry.

Many Greetings
Robin

Windows is like a submarine. Open a window and serious problems will start.

[Member Wallon]

Helpful

Up

0

::

Dear Robin,

I have finished translating the file.

I have deeply modified my translations so that the sorting in the menus is more rational.

Before with iceWM in French the sub-menu sorting was;

Configure firewall
Configure mouse
Configure persistence,
Configure printer,
Navigator Opera
Set up persistence,
Web navigator Chromium

Now with iceWM in French, we will have a new sub-menu sort,

Chromium navigator.
Firewall configuration
Mouse configuration
Opera navigator
Persistence configuration
Persistence set up,
Printer configuration.

This may give an idea to another translator to sort out the menus.

Best regards,
Wallon

[Member Robin]

Helpful

Up

0

::

Hello @Wallon , I’m deeply impressed! You have managed the oodles of string translations covered by this resource in a hard to beat period. Congrats! I have not been that fast with the automatic translation setup for this special kind of files, nor with manual translation to German language, so it will take some time until first harvesting of these strings from transifex will be rolled out. Everything for harvesting is prepared already, but a run makes sense only when more languages are filled in. This will change as soon the upload of the rebuilt desktop files to gitlab hasn’t to be done manually one by one anymore. We are working on this to automatise also, so we can harvest frequently then.
(But for now I’m struck with the creation of a working USB stick for antiX 21… Haven’t seen it run until today.)

Many thanks for your tireless translation work here! And great work, what you did by reorganising all the strings. This actually will give some inspiration to other translators, I believe.

Best regards
Robin

P.S.: Please, Wallon, commemorate Wallonnes interjection 😉 !

Windows is like a submarine. Open a window and serious problems will start.

[Member Wallon]

Helpful

Up

0

::

Guten Abend Rotkehlchen,
Good evening Robin,

I am always impressed by the high level of translation of my friend Marcelocripe.
This time, I really searched the internet to give an explanation in the comments. I even used the French Debian documentation to explain some applications.
It’s a bit of a pity not to have a tooltip with a comment when you go to the iceWM menus.
I sent 2 messages to the Italian team in Transifex to invite them to translate this new project but I didn’t receive any answer. I hope to see them again as soon as possible.

Vielen Dank für den Tipp mit Wallonne.
Auf Wiedersehen und bis bald.
Wallon

[Member marcelocripe]

Helpful

Up

0

::

Dear Wallon,

Congratulations on being able to complete the translation in your language.

Unfortunately, I have not yet been able to start translating and proofreading in pt-BR, due to the other translation and testing work of aCSTV (from program and manual) and from PPC’s FT10 transformation package.

“Wallonne” is absolutely right, we spend many hours of our free time with antiX and this drastically cuts down on family time.

I will try to remember to send a message in the Telegram group of Italian translators.

– – – – –

Caro Wallon,

Meus parabéns por você conseguir concluir a tradução em seu idioma.

Infelizmente, eu ainda não consegui começar a tradução e revisão em pt-BR, devido aos outros trabalhos de tradução e de testes do aCSTV (do programa e do manual) e do pacote de tranformação FT10 do PPC.

A “Wallonne” tem toda razão, nós dedicamos muitas horas do nosso tempo livre com o antiX e isso diminui drasticamente o tempo com a família.

Eu vou tentar me lembrar de enviar uma mensagem no grupo de Telegram dos tradutores italianos.

[Member Robin]

Helpful

Up

0

::

Yesterday I’ve managed to write the script code for automatic translation of the .desktop files resource on transifex, and it has run on the first languages already during night and morning. It takes 2 hours per language. So in some days we’ll see basic machine translations for all languages to be present. The machine translation won’t touch any existing translation found in a language on transifex. But there is a slight chance it might conflict with modifications of translations manually added at transifex within exactly the period of two hours the script needs to translate to a specific language. In this hopefully rare case please restore your manual translation of the strings affected again afterwards to this language, in case you notice this has happened. I didn’t find a way to block a specific language of a specific resource separately for manual translation on transifex for the two hours the script runs on it.

Windows is like a submarine. Open a window and serious problems will start.

[Member marcelocripe]

Helpful

Up

0

::

Dear Robin,

I will wait for the automatic translation of your powerful program to be sent, then I will review/correct all texts.

PPC finished the translation in pt, for safety, I downloaded the files in pt and pt-BR (even though pt-BR is unreviewed and incomplete).

Wallon, for safety, download all antix-contribs and antix-development translation files.

– – – – –

Caro Robin,

Eu vou aguardar o envio da tradução automática do seu poderoso programa, depois eu faço a revisão/correções de todos os textos.

O PPC concluiu a tradução em pt, por segurança, eu baixei os arquivos em pt e em pt-BR (mesmo que o pt-BR esteja sem a revisão e incompleto).

Wallon, por segurança, baixe todos os arquivos de tradução do antix-contribs e antix-development.

[Member Wallon]

Helpful

Up

0

::

Dear Marcelocripe,

“all antix-contribs and antix-development translation files”

But it is a lot of work. Besides, I think Transifex does not replace one translation with another when I use the “Upload file” function in Transifex. Transifex only completes empty strings.
If the strings are overwritten by the artificial intelligence created by Robin, all projects have to be revised. This is an impossible job to do.

Is there a backup function that saves everything on Transifex or do you have to select each file one by one?

Sincerely,
Wallon.

[Member marcelocripe]

Helpful

Up

0

::

Dear Wallon,

Is there a backup function that saves everything on Transifex or do you have to select each file one by one?

I think it’s only possible to download one at a time, so since 15-12-2020 I download every file I change. I listed in a plain text file the name of each antix-development (antiX and MX Linux) and antix-community file with the respective date of my last change along with the files “for_use_????”. I did the same with the other translation files from the other translation platforms.

It would be nice to have everything backed up, programming codes, translations, GitLab, GitHub, Transifex, etc. We never know when a service will stop working or just close its doors and everything is lost overnight.

– – – – –

Caro Wallon,

Is there a backup function that saves everything on Transifex or do you have to select each file one by one?

Eu acho que só é possível baixar um de cada vez, por isso, desde 15-12-2020 eu baixo todo arquivo que faço alteração. Eu listei em um arquivo de texto simples o nome da cada arquivo do antix-development (antiX e MX Linux) e do antix-community com a respectiva data da minha última alteração junto com os arquivos “for_use_????”. Eu fiz o mesmo com os outros arquivos de tradução das outras plataformas de traduções.

Seria interessante termos cópia de segurança de tudo, códigos de programação, traduções, GitLab, GitHub, Transifex, etc. Nunca sabemos quando um serviço vai parar de funcionar ou simplesmente fecha as portas e tudo é perdido da noite para o dia.

[Member Wallon]

Helpful

Up

0

::

Dear Marcelocripe,

When I export “antiX desktop file”, I have only the french translation.

Below is an extract of my exported file.
For example, I take the second string in my exported file.
You have the French words only “Affichage et manipulation d’images”.
At Transifex, you have this string in English “Image viewer”. “Image viewer” is not in my file.

/* File or program name: . . . . . . . feh
Section within .desktop file: . . Desktop Entry
Entry type: . . . . . . . . . . . . . . . . GenericName=
This entry may be additionally displayed e.g. in menus. */
"feh|Desktop Entry|GenericName" = "Affichage et manipulation d'images";

How do I get the English original and the translation in one file?

Kind regards,
Wallon

[Member marcelocripe]

Helpful

Up

0

::

Dear Wallon.

Did you download from the option: “Download file for translation” or “Download for use”?

This is the file “for_use_antix-contribs_antix-desktop-files_pt_BR.strings” from the “Download for use” option:

/* File or program name: . . . . . . . feh
Section within .desktop file: . . Desktop Entry
Entry type: . . . . . . . . . . . . . . . . Name=
This entry will be displayed e.g. in menus. Keep it as short as possible, please. */
"feh|Desktop Entry|Name" = "Feh";

/* File or program name: . . . . . . . feh
Section within .desktop file: . . Desktop Entry
Entry type: . . . . . . . . . . . . . . . . GenericName=
This entry may be additionally displayed e.g. in menus. */
"feh|Desktop Entry|GenericName" = "Visualizador de imagens";

This file is quite different from the others, it has a “strings” extension that I don’t think it has in other Transifex files. Robin must have done some exhausting work to build this translation resource. Unfortunately I don’t know much more to help you with “antiX desktop files”.

I hope you have downloaded everything from Transifex and the other translation platforms for the fr and fr_BE languages. The antix-development (antiX and MX Linux) and antix-community Transifex files have about 10 MB of disk space.

– – – – –

Caro Wallon.

Você baixou da opção: “Descarregar ficheiro para tradução” ou “Descarregar para utilização”?

Assim está o arquivo “for_use_antix-contribs_antix-desktop-files_pt_BR.strings” da opção “Descarregar para utilização”:

/* File or program name: . . . . . . . feh
Section within .desktop file: . . Desktop Entry
Entry type: . . . . . . . . . . . . . . . . Name=
This entry will be displayed e.g. in menus. Keep it as short as possible, please. */
"feh|Desktop Entry|Name" = "Feh";

/* File or program name: . . . . . . . feh
Section within .desktop file: . . Desktop Entry
Entry type: . . . . . . . . . . . . . . . . GenericName=
This entry may be additionally displayed e.g. in menus. */
"feh|Desktop Entry|GenericName" = "Visualizador de imagens";

Este arquivo é bem diferente dos outros, possui uma extensão “strings” que eu acho que não tem em outros arquivos do Transifex. O Robin deve ter feito um trabalho exaustivo para construir este recurso de tradução. Infelizmente eu não sei muito mais para poder te ajudar com o “antiX desktop files”.

Eu espero que você tenha baixado tudo do Transifex e das outras plataformas de tradução para os idiomas fr e fr_BE. Os arquivos do Transifex do antix-development (antiX e MX Linux) e do antix-community possuem cerca de 10 MB de espaço em disco.

[Author]

Posts