Where are the [fr_BE] translations on Github?

[Wallon]

Dear developers,

How can translators update Github?

I can't find the translated files in Transifex on Github for the [fr_BE] language.

Thank you for your support,
Wallon

[Eadwine Rose]

Belgian French is the same as French French? Is it not?

[Utopia]

Can't find any translations at Github, only the apps.
Henry

[Wallon]

Dear developers,

I'm a translator for antiX and MX Linux. I worked a lot on antiX with anticapitalista.

I found some amazing things during my installations of antiX and MX Linux in French. Anticapitalista showed me that some packages should also be translated into French for the [fr_BE] language.

There are several rules to consider.

1) If Debian can't find an application translated into [fr_BE], Debian will look for an application in [fr].

2) It is not the same for packages made for antiX or MX Linux. If the installer can't find some files translated into [fr_BE], it will look for an English version. Beware, not all packages are translated into English, but it is very difficult to predict.
The localization is important because the layout of the keys on the AZERTY keyboard for France are not the same as the AZERTY keyboard for Belgium.

Concrete example for MX Linux;
If I install MX Linux in [fr] with FRANCE AZERTY keyboard, the Desktop directory will be translated into French "Bureau" on the disk / USB key.
If I install MX Linux in [fr] with BELGIUM AZERTY keyboard, the Desktop directory will not be translated into French on the disk / USB key.

You may also have differences for Dutch in Belgium and the Netherlands;
Dutch in Belgium = AZERTY keyboard.
Dutch in the Netherlands = QWERTY keyboard.

You may also have differences for German in Belgium and Germany.
German in Belgium = AZERTY keyboard
German in Germany = QWERTZ keyboard (not QWERTY).

So, how to put the translated Transifex files on Github?

Best regards,
Wallon

[Wallon]

If I type the command "locale" in a terminal, it is not [fr] the answer. This affects the installation of some packages.

Code: Select all

$ locale
LANG=fr_BE.UTF-8
LANGUAGE=
LC_CTYPE="fr_BE.UTF-8"
LC_NUMERIC="fr_BE.UTF-8"
LC_TIME="fr_BE.UTF-8"
LC_COLLATE="fr_BE.UTF-8"
LC_MONETARY="fr_BE.UTF-8"
LC_MESSAGES="fr_BE.UTF-8"
LC_PAPER="fr_BE.UTF-8"
LC_NAME="fr_BE.UTF-8"
LC_ADDRESS="fr_BE.UTF-8"
LC_TELEPHONE="fr_BE.UTF-8"
LC_MEASUREMENT="fr_BE.UTF-8"
LC_IDENTIFICATION="fr_BE.UTF-8"
LC_ALL=

[ravrett]

Translators cannot update the GitHub repos directly. Translators use the Transifex website to upload translations.

[ravrett]

Wallon,

I think I see what the problem has been for fr_BE. I have fixed it and will start pulling translations from Transifex. You should see those translations as the MX apps get updated going forward.

[fehlix]

Concrete example for MX Linux;
If I install MX Linux in [fr] with FRANCE AZERTY keyboard, the Desktop directory will be translated into French "Bureau" on the disk / USB key.
If I install MX Linux in [fr] with BELGIUM AZERTY keyboard, the Desktop directory will not be translated into French on the disk / USB key.

@Wallon would you mind to check the translation of the Desktop-directory, when login with fr_FR locale and also when changing language to fr_BE at the login screen.
At least in my tests it offers me the change the Desktop-directory translated from German to French translated Desktop for both fr_FR and fr_BE.

But... I see an issue within mx-tools not only for fr_BE translations but for other ll_RR languages whre ll != RR, like fr_LU, de_DE, de_AT, de_CH etc
Example:
French
Open mx-tools for fr_FR this way - they are translated:

Code: Select all

LANG=fr_FR.UTF-8 mx-tools

MX-Tools_fr_FR.png

Code: Select all

LANG=fr_BE.UTF-8 mx-tools

not translated:

MX-Tools_fr_BE.png

or

Code: Select all

LANG=fr_LU.UTF-8 mx-tools

not translated:

MX-Tools_fr_LU.png

Same for German:

Code: Select all

LANG=de_DE.UTF-8 mx-tools

are tranlated:

MX-Tools_de_DE.png

Code: Select all

LANG=de_AT.UTF-8 mx-tools
LANG=de_CH.UTF-8 mx-tools

are not translated:

MX-Tools_de_AT.png

I think I see what the problem has been for fr_BE. I have fixed it and will start pulling translations from Transifex. You should see those translations as the MX apps get updated going forward.

@ravrett Not sure what you found, but at least for mx-tools there seem to be a translation issue within the tool, for language where lang-code is not equals region-code, and not ll_R translation present within the desktop-files.
@dolphin_oracle @Adrian Do we have a translation issue within mx-tools?

[ravrett]

@fehlix When the fr_BE language was approved for use, the scripts I use for downloading the translations were not updated to download that language. Additionally, it appears that in the handful of QT apps I looked into today, the .pro files had also not been updated to account for the language. I will have to do a general refresh of each app, make the needed updates, etc. It will take me some time to work through them all. I am also double checking all the other languages to make sure they are all accounted for as I go through the apps. So far, it's just fr_BE.

[ravrett]

But... I see an issue within mx-tools not only for fr_BE translations but for other ll_RR languages whre ll != RR, like fr_LU, de_DE, de_AT, de_CH etc

The languages that you are showing examples of are not languages that we track translations through on Transifex. For example, I just download and push de for German. I assume this is due to us never having had a translator request those language variations previously. The translations you are getting are likely fall back translations like the ones that Wallon was talking about in his post above. I am speculating though.