search

kaikramer / keystore-explorer

KeyStore Explorer is a free GUI replacement for the Java command-line utilities keytool and jarsigner.
https://keystore-explorer.org/
GNU General Public License v3.0
1.7k stars 275 forks source link

New candidate for translation #432

Open Ricky-Tigg opened 1 year ago

Ricky-Tigg commented 1 year ago

v.: 5.5.2 | Hello. As it appears, there is support for translation of this application's interfaces. No Nordic language yet represented though. As you can expect it, Finnish as language would be proud to be listed along with German, as available. By the present report i announce my will to contribute to this project by being candidate for translating in that language both this application and its related documentation.

kaikramer commented 1 year ago

I am happy to hear this! This is great news!

I can give a short introduction, and you can ask whatever you want to know.

The translation for the application is done in properties files, like for example these ones:

https://github.com/kaikramer/keystore-explorer/blob/main/kse/src/org/kse/gui/resources.properties https://github.com/kaikramer/keystore-explorer/blob/main/kse/src/org/kse/gui/resources_fr.properties https://github.com/kaikramer/keystore-explorer/blob/main/kse/src/org/kse/gui/resources_de.properties

Currently they have to be in Latin-1 (ISO 8859-1) format, which means that characters not included in Latin-1 have to be encoded. But this will change soon when we switch to Java 11 as the minimum requirement for KSE, then we can simply write UTF-8.

There are plugins for IntelliJ and Eclipse that help a lot with writing and synchronizing these files. If you are familiar with one of these IDEs than I would recommend to use one of these plugins.

The documentation is in another git repo and there is currently no translation available.

And as a side note, @The-Lum who gave a "thumbs up" for your announcement has contributed a lot to the French translation.

The-Lum commented 1 year ago

Hello @Ricky-Tigg,

Welcome here. :wave:

Here are some remarks, for translators...

Repetitions

Sometime there are some repetitions. Example here:

Adding English word

Sometime it is difficult to give the good word (the good 'technical word') Also I choice sometime to add the English word (plus numeric value) into bracket: as you want for the Finnish translation. See some examples here:

kse/gui/crypto/distributionpoints:

Similar here, kse/gui/dialogs/extensions:

Or here, kse/gui/dialogs/sign:

Regards, Th.

Ricky-Tigg commented 1 year ago

Last Saturday i completed the translation of main branch's kse/src/org/kse/gui/resources_fi.properties file. I took model upon _resourcesde.properties, thus used the relevant plug-in, –which is since 2017 unmaintained and suffers issues that hence won't be fixed– within Eclipse. I used to work using that latter for my technical degree 2013–2016. Unlike bicycling, the knowledge acquired at the time was gone. I had to start learning once more its fundamentals from the beginning, therefore asking could not be a valid option.. In that context it does not exist better help than self-help.

In the generated content of that file, the characters ä and ö are converted into other strings; that must be the indication that they were encoded. I will figure it out later when i completed the translations of remaining *.properties files. Eclipse's built-in client dedicated for the present platform was a surprise to me. I relied on it in order to clone this main repository. I keep on working with it for now until i am put in situation to create a fork of it and learn how to synchronize it.

kaikramer commented 1 year ago

Last Saturday i completed the translation of main branch's kse/src/org/kse/gui/resources_fi.properties file. I took model upon resources_de.properties, thus used the relevant plug-in, –which is since 2017 unmaintained and suffers issues that hence won't be fixed– within Eclipse.

Oh, I didn't kow that. I have switched from Eclipse to IntelliJ about two years ago and therefore don't use ResourceBundleEditor anymore. It's a pity, RBE is a good tool.

In the generated content of that file, the characters ä and ö are converted into other strings; that must be the indication that they were encoded.

Yes, RBE automatically takes care of this.

kaikramer commented 10 months ago

Just a quick note: I have updated the minimum Java requirement from 8 to 11, which means that we can now simply use UTF-8 for the resource bundles.

Ricky-Tigg commented 10 months ago

Ignoring what effect this announcement should have, I don't know whether to rejoice about it. It can reasonably be assumed that reference is made to the programming language; the latter being mentioned as being one of the languages composing this code. If my assumption is correct, I don't know whether this announcement should be rejoiced; an old version support made obsolete by a version support which is also still old, despite being more recent.

Here are the components that could be relevant to my assumption:

$ dnf -q rq --installed --qf '%{name} %{version} | %{summary}' java-*-openjdk-headless
java-17-openjdk-headless 17.0.9.0.9 | OpenJDK 17 Headless Runtime Environment
java-latest-openjdk-headless 21.0.1.0.12 | OpenJDK 21 Headless Runtime Environment

So latest Java version is 21 not 11.

As for my proposition to contribute to the expansion of this project via my contributions through translation, it seems to me to have made a decision on this subject that was as hasty as it was inconsiderate. It seems that no means have been put in place to increment future changes to the source language file in any way to those of the existing translated language files. As it stands, this makes any attempt at maintenance of these latest files non-viable.

kaikramer commented 10 months ago

Ignoring what effect this announcement should have, I don't know whether to rejoice about it. It can reasonably be assumed that reference is made to the programming language; the latter being mentioned as being one of the languages composing this code. If my assumption is correct, I don't know whether this announcement should be rejoiced; an old version support made obsolete by a version support which is also still old, despite being more recent.

I think you misunderstood this. In the course of the discussion here the topic of the encoding of special characters was addressed several times. A short summary:

Last week I informed you that this time has come now and that you can use UTF-8 in the resource bundles.

Also, "the minimum Java requirement" does not mean "the highest supported version". KSE has always supported the latest available Java version (despite rumors saying otherwise). That is not even difficult. It is however really difficult to support the whole bandwidth of Java releases from version 8 to 21 on three different platforms.

As for my proposition to contribute to the expansion of this project via my contributions through translation, it seems to me to have made a decision on this subject that was as hasty as it was inconsiderate.

Okay

It seems that no means have been put in place to increment future changes to the source language file in any way to those of the existing translated language files. As it stands, this makes any attempt at maintenance of these latest files non-viable.

This is where translation tools or plugins help. For example you can see here clearly that 3 of the resources don't have complete translations:

grafik