bzg at altern.org
Thu Jul 10 04:11:15 EDT 2008
To avoid bikesheds, let me rephrase my modest proposal:
when translating a string (or a group of strings, if there is such a
concept at some point), if the user thinks it might be helpful for
other translators to have a screenshot showing the context for this
(group of) string(s), let him upload one.
Nothing systematic, no huge machinery here.
Looking at the code might help in the case of Etoys, but my idea was
not really software-specific.
Of course, having screenshots only makes sense when the translation
deals with a _user interface_, which is not the case for manuals or
Yoshiki Ohshima <yoshiki at vpri.org> writes:
> At Wed, 09 Jul 2008 18:00:56 +0200,
> Bastien wrote:
>> Bert Freudenberg <bert at freudenbergs.de> writes:
>> >> So, I can see nothing wrong with having a clickable thumbnail allowing
>> >> you to get a better idea of the meaning of a string.
>> >> Whether Pootle people want to consider this idea is another issue, of
>> >> course.
>> > And who exactly would make these screenshots?
>> The Etoys devel team, for example.
>> Or maybe you, me, and the "community".
>> If 1 screenshot spares 100 questions by 100 translators (and, say, 50
>> answers by the devel team), then I think it might be useful.
> The higher level answer is to look at the code that uses the phrase
> in question (and Etoys system more or less encourage it). So if one
> person is serious enough to ask the same question "where phrase xyz is
> used?" three times, he can learn how to look at the code.
> One could imagine to have an automated way to get the screenshot
> with the pharse, but that would be a crazy project.
> At the same time, I would think screenshots provide much less
> context than looking at the phrases in action. If the goal is to
> provide high quality consistent translation, there will be some real
> work (other than looking at static web pages) involved.
> BTW, there is/was an in-system translation editor that can make the
> translated phrase take effect right away in place. Some people would
> prefer to use that for doing larger number of translations.
More information about the Localization