Am 30.07.2005 um 19:26 schrieb Björn Eiríksson:
Absolutely categorize them as you say, and have a context comment
for every item.
Yeah, I learned this my self. I compiled a set of translation for
standard
terms, but finally used string blindly - and thus they appeared in
the wrong
contect.
You need to account that translation may not be one to one
relationship, in english you could have the term "Save" that works
in many places, but in other languages it might have to be split
into 2 or 3 terms depending on context.
Ah! Yes, really important. I didn't hat the idea in mind, but you
are definitely right.
In this situation, it might even be useful to a short (compact)
translation and a long translation.
And lastly if you or anyone else set up such system (and this is
most important), moderate the database, do not blindly trust the
public.
Yeah, a very important point. I'd even propose a 'proof read' system,
the enable a specific translation iff. at least 2 other translators
accepted the translation.
On 30.7.2005, at 16:33, Stefan Pantke wrote:
How about his idea:
- Let's set up a web site, which stores sentence pairs
sentence2 at Locale1 / sentence2 at Locale2
- Each sentence gets categorized as
Question
Explanation
Menu item
...
- Users add new pairs or add new translation for existing ones
- A client app might retrieve translations
Once this infrastructure is up and running, a localization tool
might be set up, which localizes a certain part of project string
resources.
Might this be useful or far too optimistic?
Kinds
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|