Usher wrote:

Alex wrote:

Usher wrote:And what about updating language files? Four pull requests stuck in the queue…

Sorry, I can't answer this question. But, FDM6 is our main goal. It should kick both FDM3 and FDM5 (I hope). FDM6 does not support language files currently. We plan to add this as soon as it gets mature.

I'm talking about pull requests on Github. There are almost complete and of good quality translations for FDM 5.1 there. They should replace horrible automatic translation provided for unkown reasons (to make laugh or to be nominated to The Hall of Shame maybe?) by FDM team and they should be reused in FDM 6 in the future. If you add them now, other users will be able to add missing strings of translation and improve existing ones.

Some good willing person finally updated language translation files on github, but where are updated FDM5 installers containing these translations?

netbug wrote:I didn't find the English po on github.

Read more carefully, please. You can download ANY new po file in ANY language, it always contains source English strings.
For example, you can download freshly updated French file fdm_fr.po, which seems to be the most complete one. Just compare: 2893 lines (2217 sloc) in French verson versus 2857 lines (2180 sloc) in Polish fdm_pl.po.

Some more notes:
1. There are *.po files for FDM 5.x only on github, FDM 6 isn't localized yet.
2. You may wait a very long time with your pull request, so if you want to publish your translation immediately, you can send it also to me. I will convert it to needed format and put it in my FDM utils repository.

Clive Sorensson wrote:Hello, the language packs are always in development.

Wrong, and it's not for the first time.

1. The language packs for FDM 5.1 have NOT been updated for almost a year. Last commit on Github was on 24 May 2018, the newest qm file in FDM is dated on 28 May 2018.

2. Pull requests from Github users to update language packs are ignored. It's not me who breaks Github working rules and doesn't merge updates.

3. There is NO current language template (*.pot) to create complete language pack. Both compiled *.qm files in FDM and *.po files on Github don't contain strings displayed in newer FDM builds, f.e.: "Join to FDM mosaic" or "Show special offers". Some older strings, f.e. dialog window titles are also missing.

If you need i18n maintainer, just ask.

You should ask more general question: Why do developers ignore helpful requests or reports?

What about lang files in FDM - most of them are automatic translations with strings suggested by poedit.
It's been already discussed, just read more carefully about pull requests:
search.php?keywords=pull+request*&terms=all&author=Usher&sc=1&sf=all&sr=posts&sk=t&sd=d&st=0&ch=-1&t=0&submit=Search

Alex wrote:

Usher wrote:Did you uninstall older FDM version before installing a newer one? It's an alpha version, for testing only – you should even delete old FDM settings as there might be some incompatible changes…

This is not required.

Unless there is regression - new or ignored. ;-P

And you know that there are ignored pull requests to fix regressions in FDM 5.1 localization files?

Alex wrote:

Usher wrote:I think that it would be better to add current extensions to new builds. That way FDM will be ready-to-use without any update needed.

This can't be done. Installation from .XPI is not compatible with installation from Store. That's why .XPI will be removed.

Now it's clear…

Alex wrote:

Usher wrote:And what about updating language files? Four pull requests stuck in the queue…

Sorry, I can't answer this question. But, FDM6 is our main goal. It should kick both FDM3 and FDM5 (I hope). FDM6 does not support language files currently. We plan to add this as soon as it gets mature.

I'm talking about pull requests on Github. There are almost complete and of good quality translations for FDM 5.1 there. They should replace horrible automatic translation provided for unkown reasons (to make laugh or to be nominated to The Hall of Shame maybe?) by FDM team and they should be reused in FDM 6 in the future. If you add them now, other users will be able to add missing strings of translation and improve existing ones.

In any case you should NOT start translations in FDM 6 from the scratch again, it would be a plan for suicide. You DID it wrong in FDM 5.x, you should reuse translations from FDM 3.x instead. Automatic translations are so horrible or ridiculous that they should be immediately removed as severe errors.

Without good quality translations you are losing users and you will lose more and more users in the future… It's just a particular case of missing features. Many advanced users have already moved to other software as FDM 5.x doesn't provide features available in FDM 3.x and fixes from FDM 5.x aren't backported to FDM 3.x. Some users did report their dissatisfaction publicly also on this forum.

I think that it would be better to add current extensions to new builds. That way FDM will be ready-to-use without any update needed.

And what about updating language files? Four pull requests stuck in the queue…

FDM 5.1 uses QT Framework format and QT tools to generate output *.qm language files from *.po source texts. If you
aren't familiar with QT Framework, you should choose one of following actions:

* Follow the FDM FAQ and send *.po to developers. It may be a good way for the new language file, but not so good for updates.

* Follow the How to translate… info, register on Github, sign in and work with Github. This way is preferred as you will probably want to update the translation in the future.

Note that whatever way you choose, you must wait for FDM team acceptance and it may take some time… Now I can see 2 pull requests on Github waiting already a month for commit, so it's not so fast as you can expect.