Localization of Simplified Chinese is different between released version and local built version

[bianyun1981]

System information:

• Operating system (distribution) and version: Windows 10 Enterprise Edition (Simplified Chinese), 21H1
• DBeaver version: 21.3.1.202112130652
• Additional extensions

Describe the problem you're observing:

I am a DBeaver fan, and I want to contribute to the localization of DBeaver (Simplified Chinese). So I decided to fork the DBeaver repo, and clone it and build it yesterday, but when I execute the local built executable file (path: dbeaver\product\community\target\products\org.jkiss.dbeaver.core.product\win32\win32\x86_64\dbeaver\dbeaver.exe), I found that the localization part is different from the release version (21.3.1.202112130652). I make some comparison pictures for illustration, left side is the released version, right side is the local built version.

I try to search some original key text (which has error in localization) from some bundle.properties (listed in a table from https://github.com/dbeaver/dbeaver/wiki/Localization), but none of them can be found, such as (menu 'Edit' -> 'Find Next', menu 'Edit' -> 'Find Previous').

To sum up, I need some help to find out why the local built version is not same as the released version, and why some original key text of l10n cannot be found in any bundle.properties. Or in short, what is the right steps to contribute to the localization of DBeaver.

[ShadelessFox]

Hello @bianyun1981,

The locally built version lacks some localization because it's a part of Eclipse localization.

We use Babel while packaging to include that localization too. You can install it manually.

I'm going to convert this issue to the discussion.

[VolareYang]

Hello, I also encountered the problem of localization packaging, how did the landlord solve it

[VolareYang]

Hello @bianyun1981,

The locally built version lacks some localization because it's a part of Eclipse localization.

We use Babel while packaging to include that localization too. You can install it manually.

I'm going to convert this issue to the discussion.

Hello，How to automatically integrate Babel packages when packing.

[VolareYang]

Hello,@ShadelessFox,
How to automatically integrate Babel packages when packing.

[bianyun]

@VolareYang

Hi, I think this babel package is integrated into DBeaver release as a internal plugin (maintained by eclipse community) when DBeaver is published, and the release publisher is in charge of setting up the stable version of babel packages plugin.

I think what we can do is to do the locallization work for the DBeaver-specific (that is to say, you should only work on all the localizaiton properties file in the DBeaver source code).

And if some piece of unlocalized text has no corresponding key defined in properties file, then you should find out whether eclipse babel is reponsible for localization for this piece of text. If this piece of text is releated with DBeaver specific feature, then I think it should be localized in DBeaver propreties files, and these properties file should be created first (usually by committing a new issue and waiting for other contributers to create those properties files, like this #21384, and then you can do your localization work).

Hope this helps you. :)

P.S. @bianyun1981 is my old account, it is deprecated.

[VolareYang]

Thank you! @bianyun
How do I manually install the babel language pack to a locally built version.
ask for your help.