Extension translation

[buzzia2001]

In Code4i FS extension we use QSYS2.SYSCOLUMNS2 to get the column description...

However, this choice means that the connection (and consequently the results) are influenced by the system language and the local language, effectively creating the possibility of inconsistencies within the same screen.

Guys, @sebjulliand @chrjorgensen @marcin-ogon @NicolasSchindler, Do you think it would be possible to use the translation framework for this extension as well?

Let's say that now would be ideal, given that the release is not yet public, etc.

[sebjulliand]

That was done to not have to worry too much about the labels and have a way to build UI fast (espiaclly when lot of columns were fetched).

But now would be a goot time to switch to VS Code's l10n framework, for sure.

[buzzia2001]

Hi @sebjulliand @chrjorgensen @marcin-ogon @NicolasSchindler

I have completed the PR containing support for the l10n framework. We are talking about approximately 1,300 items to be translated, both in terms of actions/messages and tooltips.

If you are available, and of course depending on your commitments, it would be interesting to add support for other languages besides English and Italian... bear in mind that ALL messages have been prepared for translation, there are no hardcoded strings 🥳

[SanjulaGanepola]

@buzzia2001 I am looking to have some translation stuff done for some of the other extensions right now. I can have a look at if this can be done for this extension too if you like?

[buzzia2001]

@buzzia2001 I am looking to have some translation stuff done for some of the other extensions right now. I can have a look at if this can be done for this extension too if you like?

I would really appreciate it

[SanjulaGanepola]

Should I go ahead with the translation now or would you like me to wait until more changes are in?