How to translate an extension

Asked by Nick

I'm writing an extension that provides export to Gcode functionality.
How can I add translations to my extension?

Question information

Language:
English Edit question
Status:
Answered
For:
Inkscape Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
jazzynico (jazzynico) said :
#1

Hi,

Extensions don't have standalone translation files, and Inkscape adds their translatable entries directly in its global translation file at compile time. Thus, AFAIU, the only way to have your extension translated is to suggest (using the bugs tab in Launchpad) that the Inkscape team include it in the official package.

Could you provide a link to your extension?

Revision history for this message
Nick (xepecine) said :
#2

Sure here are the link to launchpad: https://launchpad.net/gcodetools (It's used only to host the code) and link to the page that describes extension: http://www.cnc-club.ru/forum/viewtopic.php?f=33&t=35

The problem is that the extension is complex (~1700 lines of code ) and changes are made really often so I thought about external translates.

Revision history for this message
jazzynico (jazzynico) said :
#3

Hi Nick,

Your extension looks great! Unfortunately I can't test it with EMC now, and I don't have a machine tool, but I feel it would have its place as a very useful export extension. We already have cutters export format such cutting plotters, but nothing for machine tools.
It's already gettext compliant, and thus should be very easy to translate.
I strongly suggest that you post a new wishlist report (such as the one you have posted for the bezmisc improvements).

Regards.

Revision history for this message
Nick (xepecine) said :
#4

Ok, I will do it but I think it will be in a half of a year when gcodetools becomes more stable. Now it's not ready for that. The development is in a progress.

Revision history for this message
jazzynico (jazzynico) said :
#5

Don't worry, you can take your time! We're now too close to the 0.48 release, and the next development cycle (for 0.49) is planned to be quite long (lots of refactoring, and probably new GSoC project to include). Thus you have at least a year. 6 months to code and the rest to debug ;).

Regards.

Can you help with this problem?

Provide an answer of your own, or ask Nick for more information if necessary.

To post a message you must log in.