Enable translation for part names

[davidperrenoud]

From andre.knoerig@gmail.com on April 01, 2011 07:50:45

I assume non-English people will have trouble with part names like "Resistor", "Capacitor", etc.

Ultimately, one would also like to translate part description, pin labels and description, and even property values.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=1420

[davidperrenoud]

From irasc...@gmail.com on April 01, 2011 07:19:50

Issue 998 has been merged into this issue.

[davidperrenoud]

From irasc...@gmail.com on April 01, 2011 07:34:40

We could write a script that would go through all the core parts and add the relevant texts to the .ts files. I'm not sure how to create the runtime link between a piece of text in code and its translation in the qm file, but I imagine this can be figured out.

This approach would add a huge quantity of text to the translation files, so it may be better to stick with isolated words.

[davidperrenoud]

From irasc...@gmail.com on April 04, 2011 09:19:08

A script goes through all the fzp files that ship with fritzing, and generates a temporary fzp file for each, placing QT_TRANSLATE_NOOP(, ) on each translatable entry.

Each fzp filepath is added (with a newline) to a text file, call it "whatever.txt".

Create a text file "output.txt" with the name of each translation file, e.g. "parts_en.ts", "parts_de.ts", "parts_fr.ts", etc. This has to happen only once, and only needs to be updated when we add a new language. For extra credit, this file could be generated by looking at phoenix.pro, or by looking at the already existing .ts files in the translations folder.

Then run lupdate @whatever.text -ts @outputfiles.txt. Translators work with the part_xx.ts files just like they do with fritzing_xx.ts files. After the translators make changes, run lrelease.exe part_xx.ts part_yy.ts ...

[failiz]

Remove imported label