Gcodetools: Unlocalized messages

[Masato HASHIMOTO]

The following messages in Gcodetools-About/Help are translatable but localized messages are not shown.

#: ../share/extensions/gcodetools_about.inx.h:2
msgid ""
"Gcodetools was developed to make simple Gcode from Inkscape's paths. Gcode "
"is a special format which is used in most of CNC machines. So Gcodetools "
"allows you to use Inkscape as CAM program. It can be use with a lot of "
"machine types: Mills Lathes Laser and Plasma cutters and engravers Mill "
"engravers Plotters etc. To get more info visit developers page at http://www."
"cnc-club.ru/gcodetools"

#: ../share/extensions/gcodetools_about.inx.h:4
msgid ""
"Gcodetools plug-in: converts paths to Gcode (using circular interpolation), "
"makes offset paths and engraves sharp corners using cone cutters. This plug-"
"in calculates Gcode for paths using circular interpolation or linear motion "
"when needed. Tutorials, manuals and support can be found at English support "
"forum: http://www.cnc-club.ru/gcodetools and Russian support forum: http://"
"www.cnc-club.ru/gcodetoolsru Credits: Nick Drobchenko, Vladimir Kalyaev, "
"John Brooker, Henry Nicolas, Chris Lusby Taylor. Gcodetools ver. 1.7"

Version: trunk-r11233

[jazzynico (jazzynico)]

Adding the xml:space="preserve" attribute should fix the issue.
I'll take a closer look later today.

[jazzynico (jazzynico)]

xml:space="preserve" fix confirmed.

@Nick - Since the inx files are created from a global inx file (gcodetools-dev.inx in the gcodetools trunk), it would be easier to wait until it is fix upstreams than replacing each inx files in Inkscape. Could you please tell us if you plan to release a new gcodetools version soon?
By the way, the Inkscape extension is tagged 1.7, and the trunk 1.6. I guess it's just you forgot to update it ;)

[jazzynico (jazzynico)]

Patch attached, based on gcodetool revision 228.

[Nick (xepecine)]

Just waiting to finish some new features to make new release, 1.7 is still -dev version.
If it is in hurry we can try to speed up the development a little bit :)

I'll add this xml:space="preserve" to the gcodetools branch.
I can patch the files in inkscape trunk if it's needed...

[jazzynico (jazzynico)]

There's no hurry, and we can wait until 1.7 is out.
Thanks!

[Kris (kris-degussem)]

See also Bug #731177 . Probably worth treating this one simultaneously.

[jazzynico (jazzynico)]

Patch applied to the upstream code, but not ported to Inkscape yet.

[jazzynico (jazzynico)]

Patch for 0.92.x (probably works for the trunk too).

[jazzynico (jazzynico)]

Fixed in lp:inkscape rev. 15543.

[jazzynico (jazzynico)]

Fixed in lp:inkscape/0.92.x rev. 15394.

[Patrick Storz (ede123)]

Is this something we could/should fix?

I didn't look into it, but I assume it's simply not working because whitespace is trimmed (probably inside the extension implementation) but not by intltool to create the .pot file?

[jazzynico (jazzynico)]

Yes, we need to fix the INX files so that multi-lines descriptions always have the white-space=preserve attribute.
It's documented on our wiki: http://wiki.inkscape.org/wiki/index.php/INX_Parameters#Available_types

[Patrick Storz (ede123)]

I meant fixing multiline "description"s in Inkscape code to be translatable even if xml:space="preserve" is *not* used.

Setting xml:space="preserve" basically forces add-on authors to pre-format the description.
Often it might be desirable to use line breaks / indentation in .inx files to keep the source readable (without it influencing text formatting). This should however not break translations...

[jazzynico (jazzynico)]

Well, yes, we could probably fix the case where the newlines are used for source formating only (by testing the presence of the "preserve" value). But I'm not sure it's worth the effort.

[Patrick Storz (ede123)]

Follow-up for the underlying issue in bug #1668115.
There's a question whether we should change behavior of how "description"s are rendered when xml:space="preserve" is not used, so let me know what you think.