Robin
Hi @Kempelen, I’m not sure whether I understand what you want to express.
Could this be shortened down, and start with the TYPE of the TEXT, e.g. “Program name”, “Program description”, so that even without opening the longer explanation on Transifex, or trying to read/interpret the whole thing, we could see which is what.
In your screenshot I see the note starts precisely with the Program name already like you suggest, followed by the header section within the .desktop file under which the entry was found, and finally the entry type. This order has been chosen, since it turned out, that there exist .desktop files with multiple entries of same type in different sections, so it is not enough to start with the type. An identical type can exist two or more times for the same program name. While the program name itself in the first line is needed to identify the .desktop file to which an entry belongs. And there may live more than a single .desktop file for the same program in different versions, only distinguishable by this very file name in this line. This way all associated entries can be identified immediately and unambiguously, before going into the details of what type (Name, GenericName, Comment, Keywords) the entry deals with.
Concerning the long text: You can ignore it safely, if you are familiar with how these .desktop files work. It’s just the general usage/translation instruction for the respective entry type.
Significant are merely the first three lines in each entry:
File or program name: ............... ddm-nvidia
Section within .desktop file ........ Desktop Entry
Entry type .......................... NameI guess, one can hardly put the needed core info any shorter, or place it in a more prominent position of the dev notes: Your example is a “Name” type entry in the section “Desktop Entry” of the “ddm-nvidia” program’s .desktop file. Actually ddm-nvidia is the .desktop filename already, stripped off its .desktop extension.
Please note, all the developer notes for this resource are not created manually, but autogenerated from the .desktop file itself by the extraction tool, so they can only contain what the .desktop file itself provides, along with a standard instructions message, which is different for each entry type. This additional explanatory message is repeated in each entry, in order to ensure that even when a new translator jumps directly to a single still untranslated entry he happens to meet, he can understand what he should take from these three lines, which would be hard to interpret without these additional instructions. For experienced translators who have met them already before, no need to read that additional text again and again, just check the three starting lines to know what an entry deals with. You’ll not find anything beyond that in the long explanatory text.
You see me a bit puzzled what you actually want me to change here. There is never any need to read or interpret the whole thing again and again. Maybe I misread your intention?
Windows is like a submarine. Open a window and serious problems will start.