[etoys-notify] [JIRA] Commented: (SQ-675) Break up very long
strings for translators
Clytie Siddall (JIRA)
tracker at squeakland.org
Sat Mar 20 05:14:33 EDT 2010
[ http://tracker.squeakland.org/browse/SQ-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39155#action_39155 ]
Clytie Siddall commented on SQ-675:
And yet another:
"An Event Roll is a used to visualize and edit the score, or \"tape\", of an Event Theatre's \"event movie\".\n"
"The Roll shows three \"tracks\", one for all Mouse events, one for Keyboard events, and one for all other events, such as sound.\n"
1.75 pages in my text editor. <sigh>
You know, I'm getting tired, but I can keep translating one string at a time, as long as they're not too long. A 1.75 page string just makes my eyes glaze over at this point. Segment that string into sentence-length strings, and I can keep on translating, because it's only one step at a time, not jumping over a house. Volunteers don't have a lot of time or energy to contribute. Use this resource wisely.
> Break up very long strings for translators
> Key: SQ-675
> URL: http://tracker.squeakland.org/browse/SQ-675
> Project: squeakland
> Issue Type: Bug
> Components: etoys, translation
> Reporter: Bert Freudenberg
> Fix For: etoys 5 and showcase
> (original report by Clytie Siddall of the Vietnamese Free Software Translation Team at http://lists.laptop.org/pipermail/localization/2010-March/002479.html )
> Updating our etoys translation today, I encountered an extremely long string. I won't quote it here, since it's two-and-a-half pages long on my screen in a text editor, but it's string 1225 in Pootle, and starts like this in the PO file:
> #: Morphic-Flaps,Flaps_class>>explainFlapsText
> msgid ""
> "Flaps are like drawers on the edge of the screen, which can be opened so that you can use what is inside them, and closed when you do not need them. They have many possible uses, a few of which are illustrated by the default set of flaps you can get as described below.\n"
> Please divide this enormous string into paragraphs, one paragraph per translation string. Ideally, a translation string should not be more than one or two sentences long. However, most of the paragraphs in this multi-page string are reasonably short and independent: they will translate effectively as standalone strings.
> (Reminder for developers: long strings are bad localization practice! Translators avoid them, since they have very little time available (thus you don't get the translation); there's much more room for error and confusion (so you get bad translations); translators can't review the string properly (more errors); and finally, most translation editors don't expect long strings, so they don't handle them well (confused and grumpy translators).
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tracker.squeakland.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the etoys-notify