Re: [Inkscape-translator] Fwd: Inkscape 0.92pre4 released
Yes, they added some strings - and those are especially important as they concern the document conversion between 0.91 and 0.92 (units change to match CSS specification). Users who are presented with an English message might find this even more difficult to decide than in their native language.
Could someone update the po files in the Inkscape 0.92.x repo, please?
Regards, Maren
Hi,
Some relatively new strings in 0.92.x branch are actually untranslatable due to such called "string puzzles":
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/share/e...
inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) ))
extracts as
Side Length 'a' ( Side Length 'b' ( Side Length 'c' (
That is not what expected.
Can this be fixed before the release and the last update before the string freeze?
Thanks in advance for your answers.
Best regards, Yuri
Am 19.12.2016 um 18:27 schrieb Sylvain Chiron:
According to the message below, it’s still possible to submit translations for 0.92.
Kind regards,
Sylvain
-------- Message transféré -------- Sujet : [Inkscape-devel] Inkscape 0.92pre4 released Date : Sun, 18 Dec 2016 22:50:03 -0800 De : Bryce Harrington <bryce@...1...> Pour : inkscape-devel@...3...
The 0.92pre4 source package has been released and can be downloaded
from Launchpad: https://launchpad.net/inkscape/0.92.x/0.92pre4
[…]
Please try to avoid making any further changes on the 0.92.x tree - consider it in final freeze before release. The one exception being translations - the mesh gradient changes were allowed to break string freeze, so due to that we'll be giving permission to translators for breaking this final freeze.
[…]
Thanks, Bryce
On Mon, Dec 19, 2016 at 10:05:12PM +0200, Yuri Chornoivan wrote:
Yes, they added some strings - and those are especially important as they concern the document conversion between 0.91 and 0.92 (units change to match CSS specification). Users who are presented with an English message might find this even more difficult to decide than in their native language.
Could someone update the po files in the Inkscape 0.92.x repo, please?
Regards, Maren
Hi,
Some relatively new strings in 0.92.x branch are actually untranslatable due to such called "string puzzles":
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/share/e...
inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) ))
extracts as
Side Length 'a' ( Side Length 'b' ( Side Length 'c' (
That is not what expected.
Good point. There are probably other instances like this where variables are being included in the translatable. I would guess the proper way to do it would be something like:
inkex.errormsg(_("Side Length 'a'") + " (" + unit + "): " + str( params[0][0] ) )
Can this be fixed before the release and the last update before the string freeze?
We're already far into string freeze, and actually very close to final freeze. This particular issue is just an error message printed to the console for one of the extension programs, so the severity of having it untranslated seems quite low.
I would suggest filing a bug report to seek getting it fixed in trunk for future releases.
Thanks, Bryce
Thanks in advance for your answers.
Best regards, Yuri
Am 19.12.2016 um 18:27 schrieb Sylvain Chiron:
According to the message below, it’s still possible to submit translations for 0.92.
Kind regards,
Sylvain
-------- Message transféré -------- Sujet : [Inkscape-devel] Inkscape 0.92pre4 released Date : Sun, 18 Dec 2016 22:50:03 -0800 De : Bryce Harrington <bryce@...1...> Pour : inkscape-devel@...3...
The 0.92pre4 source package has been released and can be downloaded
from Launchpad: https://launchpad.net/inkscape/0.92.x/0.92pre4
[…]
Please try to avoid making any further changes on the 0.92.x tree - consider it in final freeze before release. The one exception being translations - the mesh gradient changes were allowed to break string freeze, so due to that we'll be giving permission to translators for breaking this final freeze.
[…]
Thanks, Bryce
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
Le 20/12/2016 à 03:47, Bryce Harrington a écrit :
On Mon, Dec 19, 2016 at 10:05:12PM +0200, Yuri Chornoivan wrote:
Some relatively new strings in 0.92.x branch are actually untranslatable due to such called "string puzzles":
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/share/e...
inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) ))
extracts as
Side Length 'a' ( Side Length 'b' ( Side Length 'c' (
Good point. There are probably other instances like this where variables are being included in the translatable. I would guess the proper way to do it would be something like:
inkex.errormsg(_("Side Length 'a'") + " (" + unit + "): " + str( params[0][0] ) )
Punctuation must be translatable too, e.g. in French you need a no-break space before the colon, so it would be closer to something like this:
inkex.errormsg(_("Side Length 'a' ({0}):").format(unit) + " " + str( params[0][0] ) )
But one should refer to the Gettext doc for Python.
Regards, -- Sylvain
20 грудня 2016, 13:07:29, від "Sylvain Chiron" <chironsylvain@...364...>:
Le 20/12/2016 à 03:47, Bryce Harrington a écrit :
On Mon, Dec 19, 2016 at 10:05:12PM +0200, Yuri Chornoivan wrote:
Some relatively new strings in 0.92.x branch are actually untranslatable due to such called "string puzzles":
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/share/e...
inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) ))
extracts as
Side Length 'a' ( Side Length 'b' ( Side Length 'c' (
Good point. There are probably other instances like this where variables are being included in the translatable. I would guess the proper way to do it would be something like:
inkex.errormsg(_("Side Length 'a'") + " (" + unit + "): " + str( params[0][0] ) )
Punctuation must be translatable too, e.g. in French you need a no-break space before the colon, so it would be closer to something like this:
inkex.errormsg(_("Side Length 'a' ({0}):").format(unit) + " " + str( params[0][0] ) )
But one should refer to the Gettext doc for Python.
Regards,
Just for the reference, I filed BR #1651334
https://bugs.launchpad.net/inkscape/+bug/1651334
Best regards, Yuri
Sorry, now I am requesting an update:
This string, which is related to the dpi switcher, is not marked as translatable in the source code (the underscore is missing), but contains very important info:
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/src/fil...
Could it be considered to update the branch for this change?
(please, if someone makes this change, also directly update the po files, and if possible also the pot file for trunk - it's easier to keep translations in sync automatically when editing them in parallel, than updating each one separately.)
Regards, Maren
Am 20.12.2016 um 12:07 schrieb Sylvain Chiron:
Le 20/12/2016 à 03:47, Bryce Harrington a écrit :
On Mon, Dec 19, 2016 at 10:05:12PM +0200, Yuri Chornoivan wrote:
Some relatively new strings in 0.92.x branch are actually untranslatable due to such called "string puzzles":
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/share/e...
inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) ))
extracts as
Side Length 'a' ( Side Length 'b' ( Side Length 'c' (
Good point. There are probably other instances like this where variables are being included in the translatable. I would guess the proper way to do it would be something like:
inkex.errormsg(_("Side Length 'a'") + " (" + unit + "): " + str( params[0][0] ) )
Punctuation must be translatable too, e.g. in French you need a no-break space before the colon, so it would be closer to something like this:
inkex.errormsg(_("Side Length 'a' ({0}):").format(unit) + " " + str( params[0][0] ) )
But one should refer to the Gettext doc for Python.
Regards,
Sylvain
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Done in trunk and in 0.92.x
On Wed, 2016-12-21 at 00:37 +0100, Maren Hachmann wrote:
Sorry, now I am requesting an update:
This string, which is related to the dpi switcher, is not marked as translatable in the source code (the underscore is missing), but contains very important info:
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/ src/file.cpp#L516
Could it be considered to update the branch for this change?
(please, if someone makes this change, also directly update the po files, and if possible also the pot file for trunk - it's easier to keep translations in sync automatically when editing them in parallel, than updating each one separately.)
Regards, Maren
Am 20.12.2016 um 12:07 schrieb Sylvain Chiron:
Le 20/12/2016 à 03:47, Bryce Harrington a écrit :
On Mon, Dec 19, 2016 at 10:05:12PM +0200, Yuri Chornoivan wrote:
Some relatively new strings in 0.92.x branch are actually untranslatable due to such called "string puzzles":
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/ head:/share/extensions/draw_from_triangle.py#L179
inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) ))
extracts as
Side Length 'a' ( Side Length 'b' ( Side Length 'c' (
Good point. There are probably other instances like this where variables are being included in the translatable. I would guess the proper way to do it would be something like:
inkex.errormsg(_("Side Length 'a'") + " (" + unit + "): " + str( params[0][0] ) )
Punctuation must be translatable too, e.g. in French you need a no- break space before the colon, so it would be closer to something like this:
inkex.errormsg(_("Side Length 'a' ({0}):").format(unit) + " " + str( params[0][0] ) )
But one should refer to the Gettext doc for Python.
Regards,
Sylvain
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Am 21.12.2016 um 01:23 schrieb Jabier Arraiza:
Done in trunk and in 0.92.x
Thank you, Jabier!
Btw. the pot file in trunk hasn't been updated along with the other files, though. Last change: 2016-11-12 09:55:09 UTC. Was that intended?
Regards, Maren
On Wed, 2016-12-21 at 00:37 +0100, Maren Hachmann wrote:
Sorry, now I am requesting an update:
This string, which is related to the dpi switcher, is not marked as translatable in the source code (the underscore is missing), but contains very important info:
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/ src/file.cpp#L516
Could it be considered to update the branch for this change?
(please, if someone makes this change, also directly update the po files, and if possible also the pot file for trunk - it's easier to keep translations in sync automatically when editing them in parallel, than updating each one separately.)
Regards, Maren
Am 20.12.2016 um 12:07 schrieb Sylvain Chiron:
Le 20/12/2016 à 03:47, Bryce Harrington a écrit :
On Mon, Dec 19, 2016 at 10:05:12PM +0200, Yuri Chornoivan wrote:
Some relatively new strings in 0.92.x branch are actually untranslatable due to such called "string puzzles":
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/ head:/share/extensions/draw_from_triangle.py#L179
inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) ))
extracts as
Side Length 'a' ( Side Length 'b' ( Side Length 'c' (
Good point. There are probably other instances like this where variables are being included in the translatable. I would guess the proper way to do it would be something like:
inkex.errormsg(_("Side Length 'a'") + " (" + unit + "): " + str( params[0][0] ) )
Punctuation must be translatable too, e.g. in French you need a no- break space before the colon, so it would be closer to something like this:
inkex.errormsg(_("Side Length 'a' ({0}):").format(unit) + " " + str( params[0][0] ) )
But one should refer to the Gettext doc for Python.
Regards,
Sylvain
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
In lines ~10218-10226:
#: ../src/live_effects/lpe-measure-line.cpp:55 #, fuzzy msgid "Positon*" msgstr "Staðsetning"
#: ../src/live_effects/lpe-measure-line.cpp:55 #, fuzzy msgid "Positon" msgstr "Staðsetning"
Is this supposed to be "Position" (as was the case in prvious versions)?
Best regards, Sveinn í Felli
There's also a "Rotate Anotation" --> "Rotate Annotation" !!!
Something is seriously broken in the spellchecker of those who are writing the LPE-code ;-(
Best regards Sveinn í Felli
Þann mið 28.des 2016 10:46, skrifaði Sveinn í Felli:
In lines ~10218-10226:
#: ../src/live_effects/lpe-measure-line.cpp:55 #, fuzzy msgid "Positon*" msgstr "Staðsetning"
#: ../src/live_effects/lpe-measure-line.cpp:55 #, fuzzy msgid "Positon" msgstr "Staðsetning"
Is this supposed to be "Position" (as was the case in prvious versions)?
Best regards, Sveinn í Felli
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-translator
In lines ~10248-10254:
#: ../src/live_effects/lpe-measure-line.cpp:58 msgid "Helpline distance*" msgstr ""
#: ../src/live_effects/lpe-measure-line.cpp:58 msgid "Helpline distance" msgstr ""
#: ../src/live_effects/lpe-measure-line.cpp:59 msgid "Helpline overlap*" msgstr ""
#: ../src/live_effects/lpe-measure-line.cpp:59 msgid "Helpline overlap" msgstr ""
Never seen this concept of "Helpline" before, is this the same as "Guideline" ?
Best regards, Sveinn í Felli
Le 28/12/2016 à 11:52, Sveinn í Felli a écrit :
In lines ~10248-10254:
#: ../src/live_effects/lpe-measure-line.cpp:58 msgid "Helpline distance*" msgstr ""
#: ../src/live_effects/lpe-measure-line.cpp:58 msgid "Helpline distance" msgstr ""
#: ../src/live_effects/lpe-measure-line.cpp:59 msgid "Helpline overlap*" msgstr ""
#: ../src/live_effects/lpe-measure-line.cpp:59 msgid "Helpline overlap" msgstr ""
Never seen this concept of "Helpline" before, is this the same as "Guideline" ?
No.
A guideline is defined here: https://en.wiktionary.org/wiki/guideline
I think a ‘helpline’ is more like a phantom line, to help you align items for example. -- Sylvain
participants (6)
-
Bryce Harrington -
Jabier Arraiza -
Maren Hachmann -
Sveinn í Felli -
Sylvain Chiron -
Yuri Chornoivan