Translation plugin
-
Here is the request for translation of a plugin.
Is it possible to translate any other plugin?
-
It is possible, for example, for HexEdit:
https://github.com/chcg/NPP_HexEdit/tree/master/HexEditor/lang
https://github.com/chcg/NPP_HexEdit/tree/master/NativeLang/src/lang -
@conky77 said in Translation plugin:
Here is the request for translation of a plugin.
Is it possible to translate any other plugin?
It is possible to translate any plugin where the plugin’s author has already defined a method of translation for that plugin.
The post you linked to was the author of that plugin, who has already implemented the code to allow translations, coming and asking users of that plugin to help by providing the translation text for that plugin; and the link that @Karlo-F listed is another plugin that has the hooks compiled in to allow translation.
But you cannot come into the forum and just ask “could someone translate plugin XYZ for me”, for a random plugin that you use, and expect someone else to be able to translate it for you. If you have a specific plugin that you’d like to see have the hooks to be translatable, you’d have to go to that plugin’s issue-list, and request that the author add in those hooks (assuming the hooks don’t already exist), and then once a version was released that had the ability to accept translations, you or someone else who knows the destination language would have to spend the time to do all the translations for that destination language, verify they work, then submit them to the plugin to be included with future releases.
-
@PeterJones
Probably my request wasn’t very clear. I wanted to ask if other plugins are translatable, not ask if someone can translate the plugin for me.
I usually translate italian.xml of N++, and it wouldn’t be very difficult to translate some plugins.
I wanted to understand if there was a list of plugins translatable in order to decide which one to translate first .
Since the plugins that I use the most (xml tool, json tool, json viewer, compare) don’t seem to be translatable, I wanted to understand if there is a “standard” way for plugin translation.
If each author of a plugin has to invent his own way of translating them, not so many authors will implement it -
@conky77 ,
The ability to translate is not built into the various plugin templates, as far as I know, so each plugin author is responsible for implementing translatability on their own. As far as I know, there is no standardization for translations on plugins.
-
At the moment the translatable plugins are:
- Hex editor available in German
- Multireplace available in German and Russian
- json tool , available in Italian (it gets the Windows languages/cultures, not all Notepad++ languages can be supported)
If I understood well, there is also a proposal for making a standard for translations here
-
@conky77 said in Translation plugin:
If I understood well, there is also a proposal for making a standard for translations here
You partially understood. Unfortunately, my code can’t really be a general “standard for translations” because plugin authors can’t adopt it unless:
- their plugin is written in C# (most plugins are written in C++)
- they are willing to include the code necessary to parse JSON with comments (JsonTools naturally has that code for obvious reasons).
- they are using Windows Forms to make forms (WPF is more popular IIRC, although this isn’t too big of an issue)