localization

[crayxt]

It would be good to provide users with translated UI. Usually you just provide source file for translation and show your willingness to accept such translations, and over the time people will contribute. Just tried to generate source translation file

[user@linux engauge6]$ lupdate-qt5 engauge.pro -ts out.ts
WARNING: Project ERROR: Unknown module(s) in QT: help
/home/user/engauge6/src/Checklist/ChecklistGuideWizard.cpp:23: Class 'ChecklistGuideWizard' lacks Q_OBJECT macro
/home/user/engauge6/src/Dlg/DlgAbout.cpp:9: Class 'DlgAbout' lacks Q_OBJECT macro
Updating 'out.ts'...
    Found 380 source text(s) (380 new and 0 already existing)

[markummitchell]

Anything else?

[crayxt]

So far so good for release 7. TODO: 1) Put to separate directory, like translations; 2) Compile translated TS files to final message catalog files (.qm I think) in release build scripts; 3) Link with some external translation service, like Transifex. Special care needed since it tends to pollute git history. Probably manual pull from such service is preferred.

[markummitchell]

Translations can be done at Transifex (https://www.transifex.com/self-31/engauge-digitizer-1/dashboard/), although I do not know if translators also need accounts there, and what happens after the 15 day free trial.

• Project at Transifex has been moved to https://www.transifex.com/self-31/engauge-digitizer.

[crayxt]

@markummitchell I can release the engauge-digiziter project name. Open-source projects must be served free on Transifex

[crayxt]

@markummitchell I have deleted the engauge-digitizer organization, so you can create your own with that name.

[markummitchell]

Very good. I set up 'Engauge Digitizer' in just a few minutes, and can easily do the same again.

On Sun, Mar 27, 2016 at 8:51 PM, Baurzhan Muftakhidinov < notifications@github.com> wrote:

@markummitchell https://github.com/markummitchell I can release the engauge-digiziter project name. Open-source projects must be served free on Transifex

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/markummitchell/engauge-digitizer/issues/85#issuecomment-202221111

[markummitchell]

I will immediately.

On Sun, Mar 27, 2016 at 8:55 PM, Baurzhan Muftakhidinov < notifications@github.com> wrote:

@markummitchell https://github.com/markummitchell I have deleted the engauge-digitizer organization, so you can create your own with that name.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/markummitchell/engauge-digitizer/issues/85#issuecomment-202221510

[crayxt]

@markummitchell what happened with engauge-digitizer organization name on Transifex? Why didn't you use it

[markummitchell]

I replaced the old group. You should be getting an invitation.

On Tue, Mar 29, 2016 at 3:49 AM, Baurzhan Muftakhidinov < notifications@github.com> wrote:

@markummitchell https://github.com/markummitchell what happened with engauge-digitizer organization name on Transifex? Why didn't you use it

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/markummitchell/engauge-digitizer/issues/85#issuecomment-202828997

[crayxt]

https://www.transifex.com/engauge-digitizer/ still gives 404 No invitation received ;)

[markummitchell]

I fixed the url so transifex.com/engauge-digitizer works. I must have put in a bad email address so your invitation was lost, but the project is open to any volunteers. On Mar 29, 2016 11:06 PM, "Baurzhan Muftakhidinov" notifications@github.com wrote:

https://www.transifex.com/engauge-digitizer/ still gives 404 No invitation received ;)

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/markummitchell/engauge-digitizer/issues/85#issuecomment-203265294

[crayxt]

Ok, I think this one could be closed. Thanks