Translations of add-ins

[Fool-DupleX]

This is actually more a question than a feature request. I'm currently working on a French translation package and I noticed that the add-in msvc.dll (importe vc project), which is bundled with v12rc1, cannot be translated, since it's provided already compiled. While the goal is not to translate all externally contributed add-ins, I think that, for consistency, the add-ins that are bundled with the release should have translations. How can I discuss this with the author(s) (Pelle ?) It could be as simple, afaimc, as providing the necessary resource to Pelle. Since I'm new here, what is the preferred way to contribute to the main project ? I guess Pelle must be flooded with requests and my goal is not to add more noise. Thanks.

[John Z]

Hi DupleX,

You'll need to be patient to get a better answer . . .  but my take is that
afaik there is only one developer in the main, that is Pelle. 

User contributions are through bug reports, feature requests,
translations, ADD-IN contributions and if possible some money.

I think that there are a very few key users which I suspect may have contributed code to the main program.

Add-ins are all using the Pelles C API SDK functions and macros, source code is often available for the add-ins.

Your same question was raised before, see here -
https://forum.pellesc.de/index.php?topic=7651.msg28849#msg28849

The answer seems to be that this is a task to be done within the Add-IN code, and since this was 2019 ....


John Z

[Pelle]

There are basically two ways to extend the IDE: writing an add-in DLL, or writing a project wizard DLL.

A project wizard can only, by definition, handle a single project. To be able to import a Visual Studio solution, possibly containing numerous (sub-)projects, an add-in DLL is the only option (since this has no business being part of the core IDE code).

For both add-in and project wizard DLLs, the only realistic way to add translations is to stack them on top of each other in the same DLL. This will however be hard to maintain in practice. Having them load translations from the IDE language file is also not practical.

I guess "Import Microsoft Visual Studio Solution..." could be changed from a menu entry to a toolbar icon, but this would make it less visible/obvious. Including the source of this add-in in the distribution is another option, but still no real help handling multiple translations...

[Fool-DupleX]

Thanks for the answer. I expected that the translation of add-ins at this stage at least, could be an issue. I will put that aside for the time being and focus on the translation package itself.