- This topic has 45 replies, 4 voices, and was last updated May 2-6:56 pm by Wallon.
-
Posts
-
Robin
Dear fellow translators, we have a new resource ready for translation at antiX-development at transifex.
Link:
https://www.transifex.com/anticapitalista/antix-development/antix23-desktop-files/Please read carefully the developers notes for each string (right hand side in transifex editor, below the source string and above the translation entry field), which show to which .desktop file and in which section of this file the entry belongs.
Basically there are three types of entries:
Name GenericName Comment– The Name is the entry which will show up in antiX Menu by default. This entry should be concise and short, in many cases it is simply the program name.
Example: »Clawsmail«– The GenericName entry describes what Program class the Program belongs to, for the claws mail example it should read something like »Email Client«. Also this entry should be kept short, since it can be switched visible in Menus.
– The Comment entry is meant to explain in very brief words what the user needs to know about the programs. Not a lengthy explanation, but a short info what the program does. It should be displayed as Tooltip, but unfortunately IceWM fails to display these tooltips in Menus, so user either has to activate the comment display in menus (which renders menus extremely wide) or will not be able to see the comments on antiX.
Not all program’s desktop files provide all types of entries by now. They will by and by get updated so all entries will be present in the end. Also translatable keywords entries will get added later.
Offline editing
The file type is “apple strings file”, and you can manually edit them directly in antiX using geany, even if the file type is not registered in zzzFM for this file type. Just add it permanently (right click on the file, open with…, then select geany from the list and check the box “use always this program for this file type”). The downloaded translation file doesn’t contain the original string, but a key instead. If working offline you’ll need to download the English source file from top of the language list as well, and look up the respective key therein to see the original string once a string was translated. As long no translation was done for a string, transifex will fill up the translation file with original stringsExample:
"antix-user|Desktop Entry|Name" = "antiX kasutajahaldur";herein “antix-user|Desktop Entry|Name” is the key, and when you look this key up in the English source file, you’ll get the line:
"antix-user|Desktop Entry|Name" = "antiX User Manager";The key gives you also full information about where to find the respective entry in antiX:
The example line refers to a file named antix-user.desktop on your system, and within this file you’ll find it under the header [Desktop Entry], in this case it’s the entry name=… which means it’s about the entry visible by default in e.g. Menus.But I believe easiest way to edit the files is within transifex translation editor online. There you can see directly the developers notes (generally these are present in the comment lines in the downloaded strings files also, but a bit difficult to read there).
If any questions left, please feel free to post here.
Many thanks for participating in antiX translation!
Happy translating!
RobinWindows is like a submarine. Open a window and serious problems will start.
Wallon
Dear Robin,
You have done a tremendous job. Congratulations.
There is a lot to read and translate. There are a lot of programs I don’t know about and I have to see on the internet what they are for. This way, I increase my general knowledge and I can give a better translation.I am working on an anti-X23 version to see if it fits with Transifex.
Liebe Grüße,
WallonAdditional hint for easy offline translation:
You can use meld (sudo apt-get update && sudo apt-get install meld) with a two way file comparison to access the files. Just found out meld can read the UTF16 encoded strings files as well. Many thanks @BobC for making me aware of this great tool some time ago while working on antiXscreenshot2 script:
As you can see in the screenshot, the highlighting works „wrong” way around for our purpose: All the highlighted lines are translated already, while all entries without a highlighted line in it are the untranslated ones, they contain the original English strings still in the localised file version. But at least you can easily compare and edit them this way, seeing immediately the differences and the still untranslated strings (which are the entries without a highlighted line)
– All text between
/* ... ... ... */are comments, which show you some details about where this entry belongs, they are the “developers notes” as seen in transifex online editor.
– All entries are separated from each other by a blank line.
– Don’t use ASCII quotings within the string texts: As you can see they are enclosed in double ASCII quouting, so you’ll confuse the program running the translations later on by adding some more of them. (probably you could mask ASCII qotings if really needed by writing \” instead of “ but I’m not sure by now whether this will not break freedesktop.org specifications for .desktop files making them fail to work. So better safe than sorry, just use the typographic UTF8-replacements within your strings. Please see https://www.antixforum.com/forums/topic/antix-23-beta1-runit-full-64bit-for-testing/page/7/#post-103017 for details of typographic replacement.
Windows is like a submarine. Open a window and serious problems will start.
And yet another hint for easy handling of this resource at transifex:
To look up all the strings belonging to a specific desktop file within the transifex translation editor, just enter the respective desktop file name (without file name extension) into the filter field (left hand), prefixed by the filter keyword “ key: ”
Example:
To look up the translations for e.g. “runit-service-manager.desktop” enter into the filter field the expression
key:runit-service-managerSee screenshot for how to do it:
To learn whether the recent entry is referring to a Name, GenericName or Comment line of the desktop file, or whether it belongs to an additional section other than „Desktop entry”, please check the developer notes (right hand) of the transifex entry.
For conversation about the transifex entries (e.g. reporting issues here in forum), please don’t use the transifex entry number from left border column of entry listing as reference. These are subject of change. Use instead the key of the entry, which is unique and won’t change.
Windows is like a submarine. Open a window and serious problems will start.
Wallon
Dear Robin,
There are some strange things in the antiX 23 Desktop Files.
String 3 – “Refesh Menu” is incorrect in English. It’s refresh, not refesh.
String 7 – “Image;Slideshow;View;Transform;Enhance;F/X;Special Effects” is wrong. There is no semicolon at the end.
String 22 – “midi audio sequencer music notation score” error in English. There is no semicolon.
There seems to be a problem with the export of your file to Transifex. I’ll stop translating because I’ll have to do it all over again.
I haven’t checked everything.
Best regards,
WallonDear fellow translators,
this source has been updated with the “Keywords=” entry type.
Keywords: A list of strings which may be used in addition to other metadata to describe this entry. This can be useful e.g. to facilitate searching through entries. The values are not meant for display, and should not be redundant with the values of Name or GenericName.
All keywords are to be separated by a semicolon, just as the developer’s notes of these entries at transifex read, and the list MUST end with a semicolon always. Blanks are allowed for the keywords between the semicolons, e.g. if a keyword consists of multiple words. If for an entry is only a single keyword needed, this is also to be followed by a semicolon, since it will be treated as a list with a single entry.
Behind the very same link you’ll find some useful hints for the other entry types also:
Name: Specific name of the application, for example “Mozilla”.
GenericName: Generic name of the application, for example “Web Browser”. The value should not be redundant with the values of Name and Comment.
Comment: Tooltip for the entry, for example “View sites on the Internet”. The value should not be redundant with the values of Name and GenericName.
Happy translating
RobinWindows is like a submarine. Open a window and serious problems will start.
Dear Wallon,
many thanks for spotting the first errors in the resource. Will be fixed soon.There are some strange things in the antiX 23 Desktop Files.
These are errors in the original .desktop files. Some developers have goofed obviously and not carefully read the freedesktop.org specifications for .desktop files. If you recognise them, please post your findings here, I’ll fix them then in the English original of the respective files. (We’ll inform the upstream developers as well, so it can get fixed on their sources also.)
Please don’t refer to transifex entry numbers (e.g. String 3, String 7, String 22, these are subject of change) but to the keys of an entry (visible at transifex when clicking on “context”) or at least use the “Program or file name” value from the developer’s notes instead for this resource to describe what entry you are talking about.
There seems to be a problem with the export of your file to Transifex. I’ll stop translating because I’ll have to do it all over again.
As said, it’s not an issue with the extraction and export, but it’s about errors in the original .desktop files from antiX 23, which are to be fixed.
Since the translations are not bound to the English original string in this apple strings file type (but to the entry key instead), you can safely go on with translations. The original strings can get fixed without touching your translations, you won’t have to do it again and again. Just make sure your translation follows properly the instructions from the freedesktop.org specification (which are in short words summarised in the developer’s notes of each entry) — And please report here whatever strange things you notice.
Kind regards
RobinWindows is like a submarine. Open a window and serious problems will start.
Wallon
Dear Robin,
Here is a screenshot of my Transifex. Sorry, I can’t get it in English. I still don’t understand how I can have an English interface in Transifex.
I can’t find the “context” button. Maybe it’s translated into French in some other way.
Can you give me an arrow on what you want?It’s a bit silly but with all our language and translation problems, it’s not always obvious. I think there are even differences between the translators’ screens. I noticed that Marcelocripe had other options that I didn’t have in Transifex for example. I also noticed that if I work with a 15″ screen, I don’t have the same window as my 24″ screens.
Kind regards,
WallonAttachments:
Wallon
Here are the editor preferences. This is the gear icon.
Attachments:
I can’t find the “context” button. Maybe it’s translated into French in some other way.
Yes, it’s translated to « Contexte »
I also noticed that if I work with a 15″ screen, I don’t have the same window as my 24″ screens.
Exactly for this reason in your screenshot it is not visible (it will show up as soon you narrow the window a bit.) But you don’t need it, since the context and key is displayed directly, straight in front of your nose: it is simply named « Clé » . Below this header you’ll see the key I was referring to, and this key will be stable whatever the transifex entry numbers might change. In your screenshot the Clé reads « display-im6|Desktop Entry|Keywords » .
Meanwhile all the missing semicolons in the endings of keywords entries should be fixed, I’ve used geany to look them up alltogether in the source strings file by means of regex. Wouldn’t have guessed there were so many errors in the antiX desktop files…
Sorry, I can’t get it in English. I still don’t understand how I can have an English interface in Transifex.
No problem, I’ll read it in French all the same. And you can have it in any language you like (but not in German, that’s missing). Just click the pulldown in the lower right corner of the screen reading “French”.
———————-
Update:
From your second screenshot (Preferences dialog) I have the following activated for easy working:
– Activer le mode éditeur brut
– Afficher les espaces
– Afficher les traductions
– Afficher les chaînes complètesAnd these I have deactivated:
– Utiliser les raccourcis d’espaces réservés
– Afficher le compteur de caractères
– Afficher la différence avec la précédenteWindows is like a submarine. Open a window and serious problems will start.
Wallon
Thank you for all the explanations and changes made in the Transifex file.
Dear fellow translators,
The resource has been updated again.
1.) Some new „GenericNames” entries have been added. Since these were missing completely in the respective .desktop files there were no original translations which could have been carried over.
2.) Some existing original English strings have been refined. The keys are:
rox-filer|Desktop Entry|Comment blueman-manager|Desktop Entry|Comment org.gnome.FileRoller|Desktop Entry|Comment antix-firewall-toggle|Desktop Entry|Keywords mcedit|Desktop Entry|Comment firetools|Desktop Entry|Comment display-im6.q16|Desktop Entry|Comment leafpad|Desktop Entry|Comment dosbox|Desktop Entry|Name cherrytree|Desktop Entry|Comment galculator|Desktop Entry|Name simplescreenrecorder|Desktop Entry|Name connectshares-config|Desktop Entry|Comment mc|Desktop Entry|Comment screenshot|Desktop Entry|GenericName PlayOnLinux|Desktop Entry|Comment xournal|Desktop Entry|CommentPlease check whether your translation of these very strings still matches the meaning. And please remember, you can easily look these keys up by using the filter function in transifex editor as described some postings above.
Generally, if you consider an English original text as insufficient when translated to your language, please feel free to translate it freely the way you feel it works best in your country. No strict translation expected.
Many greetings
Robin———————–
P.S.: No other modifications have been made, so no need to recheck all the other entries you had already finished before the update.Windows is like a submarine. Open a window and serious problems will start.
marcelocripe
Generally, if you consider an English original text as insufficient when translated to your language, please feel free to translate it freely the way you feel it works best in your country. No strict translation expected.
I believe that we have to think not only about translating, but also about making the necessary adaptations so that communication is complete and that native speakers of the respective language can understand the texts of the programs and menus without great difficulty. But I know that this is not always possible, when there is not enough information in the original text or even when it is ambiguous and even searching the internet we cannot be sure what it is or what a certain program is for.
Robin, thank you so much for all your great work and effort on the new “antix23-desktop-files” feature.
– – – – –
Generally, if you consider an English original text as insufficient when translated to your language, please feel free to translate it freely the way you feel it works best in your country. No strict translation expected.
Eu acredito que temos que pensar não somente em traduzir, mas em fazer as adaptações necessárias para que a comunicação seja plena e que os nativos do respectivo idioma possam compreender sem grandes dificuldades os textos dos propramas e dos menus. Mas eu sei que nem sempre isso é possível, quando não há informações suficientes no texto original ou ainda quando é ambíguo e mesmo pesquisando na internet não conseguimos ter certeza do que é ou para que serve um determinado programa.
Robin, muito obrigado por todo o seu excelente trabalho e empenho no novo recurso “antix23-desktop-files”.
Wallon
Dear Robin,
Your file is getting really important. It’s a great job.
But as you know, I am replacing the English apostrophe in all antiX and MX Linux files. This is taking me a long time. I also very often find the English double quotes (right form) in the translations. For example: “antiX”. These inverted commas are not in the English text but are in the French text. These quotes are also used in the bash code. This is dangerous and I replace them with the French typographical inverted commas. For example « antiX ». On the forums of French developers, I learned that it was the same problem for HTML. They are forced to replace the English apostrophe with the French “typographical” apostrophe in the translations.
Can you give me a due date for the translation of your file?
If it’s for antiX 23, I think I have some time to spare.Is there anyone who can help anticapistalista with the translation updates? Is there an automatic procedure that sends the files from Transifex to Github? As I edit thousands of lines for antiX and MX Linux, I don’t know how we can help anticapitalista.
Cordialement,
Wallonmarcelocripe
Wallon, here are my suggestions for optimizing your time and volunteer work:
Translate the Official Transifex resource “antix23-desktop-files”, reference your Transifex Contribs file “antix-desktop-files”.
When you finish the “antix23-desktop-files”, download your file and send it to the other language that you are also responsible for (I hope this is possible with the “.strings” format file).
About the general review of all quotes, you can do it visually directly in Transifex (I believe it is faster if you have two windows side by side, one of the “fr” language and the other window of the “fr_BE” language of the same resource) or you can download the resource file and open it with Geany (search for the quotes that you used to enter with the key combination “Ctrl” together with “F”, after making the modifications, send the file to Transifex).
– – – – –
Wallon, aqui estão as minhas sugestões para otimizar o seu tempo e trabalho voluntário:
Traduza o recurso “antix23-desktop-files” do Transifex Oficial, tome como referência o seu arquivo “antix-desktop-files” do Transifex Contribs.
Quando você concluir o “antix23-desktop-files”, baixe o seu arquivo e envie para o outro idioma que você também é responsável (eu espero que isto seja possível com o arquivo do formato “.strings”).
Sobre a revisão geral de todas as aspas, você pode fazer visualmente direto no Transifex (eu acredito que seja mais rápido se você tiver duas janelas lado a lado, sendo uma do idioma “fr” e a outra janela do idioma “fr_BE” do mesmo recurso) ou você pode baixar o arquivo do recurso e abrir com o Geany (busque as aspas que você costumava inserir com a combinação das teclas “Ctrl” junto com “F”, após fazer as modificações, envie o arquivo para o Transifex).
- You must be logged in to reply to this topic.
