Page 1 of 1

Ukrainian translation - how to test it?

Posted: Wed Aug 22, 2018 3:52 pm
by opa79_
I've completed translation of interfface (.po file) for FDM 5.1 (taken from GitHub according to instructions on that site). How can I test it and where to send, when testing is done?

Re: Ukrainian translation - how to test it?

Posted: Fri Aug 24, 2018 5:09 am
by Clive Sorensson
opa79_ wrote:I've completed translation of interfface (.po file) for FDM 5.1 (taken from GitHub according to instructions on that site). How can I test it and where to send, when testing is done?


It will be implemented in time, but I'm not sure when.

Re: Ukrainian translation - how to test it?

Posted: Fri Aug 24, 2018 10:34 am
by opa79_
I think you didn't undrestand me. I've already finished translation and I have .po file ready for use by your dev team. I juat want to test that file to be sure that interface is translared Ok. As far as I understand, translation must be compiled and placed in folder with other localization files. How can I do that?
Meanwhile, I've sent that fole via support request to FDM dev. team.

Re: Ukrainian translation - how to test it?

Posted: Fri Aug 24, 2018 3:39 pm
by Usher
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.

Re: Ukrainian translation - how to test it?

Posted: Mon Aug 27, 2018 4:52 pm
by opa79_
UsherUsher, thanks. I've posted translation to GitHub.