Hi all,
I'm having some trouble with translationg some of the new terms appearing on Inkscape. I suppose other people have the same doubts, too. Any suggestion on the meaning of the following terms?
#: ../src/flood-context.cpp:993 msgid "<b>Draw over</b> areas to add to fill, hold <b>Alt</b> for touch fill" msgstr ""
touch fill?
#: ../src/select-context.cpp:537 msgid "" "<b>Drag around</b> objects to select them; press <b>Alt</b> to switch to " "touch selection" msgstr ""
touch selection?
#: ../src/widgets/toolbox.cpp:2205 msgid "Toggle VP in X direction" msgstr ""
VP?
#. Width #: ../src/widgets/toolbox.cpp:2628 msgid "(hairline)" msgstr ""
#. Thinning #: ../src/widgets/toolbox.cpp:2643 msgid "(speed blows up stroke)" msgstr ""
speed blows up stroke?
#: ../src/widgets/toolbox.cpp:2689 msgid "(slightly bulging)" msgstr ""
bulging?
#: ../src/widgets/toolbox.cpp:2689 msgid "(long protruding caps)" msgstr ""
long protruding caps?
#. Wiggle #: ../src/widgets/toolbox.cpp:2721 msgid "(no wiggle)" msgstr ""
wiggle?
#: ../src/widgets/toolbox.cpp:2736 msgid "(noticeable lagging)" msgstr ""
lagging?
Many thanks in advance for your help!
Hi Xavier :)
On 15/08/2007, at 9:14 PM, Xavier Conde Rueda wrote:
I'm having some trouble with translationg some of the new terms appearing on Inkscape. I suppose other people have the same doubts, too. Any suggestion on the meaning of the following terms?
#: ../src/flood-context.cpp:993 msgid "<b>Draw over</b> areas to add to fill, hold <b>Alt</b> for touch fill" msgstr ""
touch fill?
Fill with colour/pattern by pressing the mouse (or light pen) on specific areas, I think. It probably works better for light pen, but most detailed graphics things do. (My graphics-mad teenage daughter has one, so I have some feedback on this.)
#: ../src/select-context.cpp:537 msgid "" "<b>Drag around</b> objects to select them; press <b>Alt</b> to switch to " "touch selection" msgstr ""
touch selection?
Again, selecting specific parts of the object by touching them with the mouse or pen. This is different, in this case, from selecting by dragging around the object. So you're toggling from one selection mode to the other.
#: ../src/widgets/toolbox.cpp:2205 msgid "Toggle VP in X direction" msgstr ""
VP?
I'm not sure about this one, sorry. I think I chickened out and repeated "VP" in my translation. <blush>
#. Width #: ../src/widgets/toolbox.cpp:2628 msgid "(hairline)" msgstr ""
A very thin line, not quite as thin as a single human hair.
#. Thinning #: ../src/widgets/toolbox.cpp:2643 msgid "(speed blows up stroke)" msgstr ""
speed blows up stroke?
Moving the mouse or pen faster as you draw will widen the pen stroke. You can get some interesting graduated effects this way.
#: ../src/widgets/toolbox.cpp:2689 msgid "(slightly bulging)" msgstr ""
bulging?
Like when you try to put on clothes which are too small for you. You bulge. :D (At least, I do!)
So this means the object or appearance is not quite smooth, looks too full.
#: ../src/widgets/toolbox.cpp:2689 msgid "(long protruding caps)" msgstr ""
long protruding caps?
Caps in this context are the ends of lines or linear objects. An arrow-headed line is a common example of a cap, but there are much more subtle types of caps. A long protruding cap would be an end on a line which stuck out a long way, rather like a skinny chef's hat stuck on the end of the line.
#. Wiggle #: ../src/widgets/toolbox.cpp:2721 msgid "(no wiggle)" msgstr ""
wiggle?
When you're tipsy (intoxicated), and you try to walk along a straight line, you wiggle! Wiggling is moving from side to side, not following a straight line. So "no wiggle" is good, if you're trying to draw something straight and even.
#: ../src/widgets/toolbox.cpp:2736 msgid "(noticeable lagging)" msgstr ""
lagging?
A lag is a period of time you have to wait. People often encounter lags with their Net connections. So "noticeable lagging" would mean the program is not responding quickly enough: the user will notice it reacts slowly.
Many thanks in advance for your help!
I hope it does help. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
Clytie Siddall scrisse:
#: ../src/widgets/toolbox.cpp:2205 msgid "Toggle VP in X direction" msgstr ""
VP?
I'm not sure about this one, sorry. I think I chickened out and repeated "VP" in my translation. <blush>
I think it comes from the 3D-Box tool, and this should mean "vanishing point", ie. the point where all parallel line tend to converge.
In Italian this is called "punto di fuga", if this can help for Spanish...
Ciao, Luca
Luca Bruno <gnug.torte@...20...> writes:
Clytie Siddall scrisse:
#: ../src/widgets/toolbox.cpp:2205 msgid "Toggle VP in X direction" msgstr ""
VP?
I'm not sure about this one, sorry. I think I chickened out and repeated "VP" in my translation. <blush>
I think it comes from the 3D-Box tool, and this should mean "vanishing point", ie. the point where all parallel line tend to converge.
Yeah, it's "vanishing point", but I don't think we can leave that cryptic "VP" in the original strings either, so I didn't bother translating them yet into German.
Cheers Colin
On 16/08/2007, at 1:20 AM, Luca Bruno wrote:
Clytie Siddall scrisse:
#: ../src/widgets/toolbox.cpp:2205 msgid "Toggle VP in X direction" msgstr ""
VP?
I'm not sure about this one, sorry. I think I chickened out and repeated "VP" in my translation. <blush>
I think it comes from the 3D-Box tool, and this should mean "vanishing point", ie. the point where all parallel line tend to converge.
I thought the main thing about parallel lines was that they _didn't_ converge. :o
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
On 16/08/2007, at 1:20 AM, Luca Bruno wrote:
I think it comes from the 3D-Box tool, and this should mean "vanishing point", ie. the point where all parallel line tend to converge.
According to my graphics-mad teenage daughter, "The vanishing point is the point where all straight lines converge.". So I am now unconfused. ;)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
Hi all,
many thanks for your help! Anyway, I think developers should add comments explaining the meaning of these terms, so I'll open a bugzilla case for it too.
Regards!
To: Inkscape Translators' list Cc: Christian Perrier, Debian-Installer co-ordinator (FYI ;) )
On 18/08/2007, at 12:53 AM, Xavier Conde Rueda wrote:
Hi all,
many thanks for your help! Anyway, I think developers should add comments explaining the meaning of these terms, so I'll open a bugzilla case for it too.
Actually, the Inkscape PO file explains a lot more terms than any other graphics package I've translated.
The Best and the Worst in i18n Context _________________________________________
BEST: The Debian Installer Level 1 file has excellent, detailed use of contextual information.
WORST: GIMP is notorious for its cryptic strings and complete lack of context. When I queried some strings which were one character long and had no explanation whatsoever, the developer responded curtly, "You should know what it means." Gee, I should be an expert on all aspects of software. _________________________________________
Inkscape ranks close to the top. :)
However, that's because most PO files don't supply contextual information. They should, if they want accurate translations.
I suggest Inkscape starts using the msgctxt [1] feature in the more recent gettext packages. This feature has been created specifically for contextual information, and works with translation memory, so we don't have the context all mixed up with the string IDs.
Instead of:
msgid "action|Clone"
msgid "object|Clone"
(context should _never_ be quoted in the original string)
or
#, This is an action msgid "Clone"
#, This is an object msgid "Clone"
You have:
msgctxt "Action" msgid "Clone" msgstr ""
msgctxt "Object" msgid "Clone" msgstr ""
This is a much easier to manipulate with translation memory and merging, and much less confusing, in every way.
Xavier, please quote your bug link here, and I'll add the info on msgctxt. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
[1] GUI program support: - PO files can now contain messages constrained to a certain context. Most often such a context is a menu, dialog or panel identification. The syntax in the PO file is msgctxt "context" msgid "original" msgstr "translation" - The xgettext program can be told through the --keyword flag which function/macro argument has the role of a context. - The (non-public) include file gettext.h defines macros pgettext, dpgettext etc. that take a context argument. For more information, see the node "Contexts" in the manual.
http://www.gnu.org/software/gettext/manual/
I also recommend using msgid-previous, which allows you to diff changed strings. D-I uses that, too. They set an excellent example for the rest of free-software i18n.
Hi,
Inkscape ranks close to the top. :)
Sure! I agree.
I suggest Inkscape starts using the msgctxt [1] feature in the more recent gettext packages. This feature has been created specifically for contextual information, and works with translation memory, so we don't have the context all mixed up with the string IDs.
I didn't know it, but looks better than the old way.
Xavier, please quote your bug link here, and I'll add the info on msgctxt. :)
http://sourceforge.net/tracker/index.php?func=detail&aid=1776790&gro...
I've added the link to this thread, so this thread can be used for further discussion on this topic.
Regards.
I suggest Inkscape starts using the msgctxt [1] feature in the more recent gettext packages. This feature has been created specifically for contextual information, and works with translation memory, so we don't have the context all mixed up with the string IDs.
I didn't know it, but looks better than the old way.
Yes, It looks better. Having that contextual information on the field to translate could confuse people.
Bye, Leandro Regueiro
On 18/08/2007, at 9:14 PM, Leandro Regueiro wrote:
I suggest Inkscape starts using the msgctxt [1] feature in the more recent gettext packages. This feature has been created specifically for contextual information, and works with translation memory, so we don't have the context all mixed up with the string IDs.
I didn't know it, but looks better than the old way.
Yes, It looks better. Having that contextual information on the field to translate could confuse people.
It does. I've updated files where the previous translator has been confused by context in the original string. S/he has translated it, which is quite an understandable reaction. Even if there's a warning in the string headers, we don't focus on the string headers. The msgctxt feature will avoid incorrect translations of this type.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
On 18/08/2007, at 9:03 PM, Xavier Conde Rueda wrote:
Hi,
Inkscape ranks close to the top. :)
Sure! I agree.
I suggest Inkscape starts using the msgctxt [1] feature in the more recent gettext packages. This feature has been created specifically for contextual information, and works with translation memory, so we don't have the context all mixed up with the string IDs.
I didn't know it, but looks better than the old way.
Xavier, please quote your bug link here, and I'll add the info on msgctxt. :)
http://sourceforge.net/tracker/index.php? func=detail&aid=1776790&group_id=93438&atid=604306
I've added the link to this thread, so this thread can be used for further discussion on this topic
Thanks, Xavier: I've added the msgctxt info to the bug anyway, so it's in both places. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
participants (5)
-
Clytie Siddall -
Colin Marquardt -
Leandro Regueiro -
Luca Bruno -
Xavier Conde Rueda