[Localization] Forward of moderated message

[Samuel Klein]

Hello Y,

Please look at wiki.laptop.org/go/Glossary
is this appropriate for what you have in mind?  each term in a
glossary may have a number of different contexts or definitions.

Better information on fuzzy translations should definitely be captured
in the wiki, until we have a more flexible terminology database.

SJ

On Jan 6, 2008 1:09 PM,  <localization-bounces at lists.laptop.org> wrote:
>
>
> ---------- Forwarded message ----------
> From: "苑田義明" <y at sonoda.ac>
> To: localization at lists.laptop.org
> Date: Fri, 7 Dec 2007 09:18:07 +0900
> Subject: Re: [Localization] The virtue of being fuzzy...
> Hi! Xavier,
>
> Sorry for my very slow response...
> And thank you for your comments below.
>
> It seemed I've missed your important point in the comment.
> I totally agree with preparation for some kind of discussion
> place for various terminology issues.
>
> But, I myself don't have good idea how to set up such a place
> in wiki. Because its spectrum will be so wide to cover with
> simple mechanism.
>
> One idea will be preparation of well-know "Forum" style page.
> And categolization will be
>  - Terminology context
>    All translators recommended to take part in.
>    discussion about contextual topics behind the terms to make sure
>    and keep integrity of the translated words with single English word.
> - <Forums for each language>
> - ...etc
>
> 2007/12/4, Xavier Alvarez <xavi.alvarez at gmail.com>:
> > For me that is *exactly* the sort of place where the tag should
> > go: the translator is not sure about its appropriateness,
> > universality, wording, context of use, etc. and thus tags it.
>
> Yes, I agree with above.
>
> > When you follow the "Quick Translate" links (of a file or
> > project), Pootle will cycle all the messages that are either
> > blank / untranslated together with those tagged as fuzzy. This
> > gives you the chance to see and/or change them. If a translation
> > has not been tagged as fuzzy, you will fail to 'have a second
> > chance' and you will have to go through the *whole* file...
>
> Oh, that's a nice technic. I try to use it.
> And I understand the importance of "Fuzzy" tag.
> So I'm going to tag "fuzzy" whenever I'm not sure its
> appropriateness with respect to various reason.
> Then those terms will have chances to be improved in
> future work, right?
>
> Well I think I understand your point fundamentaly, and there's not
> big gaps. What I'm worrying about is simple. When I've tried to
> translate TEST(Etoys) (I stopped right now), and "XO-core/sugre.po",
> it is slight difficult to assign Japanese word with respect to the following
> points;
>
>   - Contextual issue
>      We, all translators should visit XO HU guideline, though,
>      it is slight difficult to imagine which word is used in where
>      only looking at the terms themselves.
>
>      I guess if all terms have some kind of explanation about
>      where the terms are used and what are the objects of these terms
>      in the context where those words terms appeared.
>
>      I think it will be nice if, for example, we can see the screen shots
>      and the terms are circled or pointed exactly where they are used in,
>      for example, sugar interface, when we follow the links attached at
>      the end of the each terms line. (Of course, there's not such a link
>      right now).
>
>  - Expression issue
>      Once we understand the context, we may be ready to assign proper
>      local words for them. But still we think better fit words once more.
>
>      If the user is, for example, matured people, it is slightly simple to
>      assign the words, because the choices are very small because
>      they will have common recognition about what words are used in
>      which situation. But, as you wrote, we have to rethink the users are
>      kids, so we may need to discuss which word better explain for
>      those kids. This might be a local issue and will be nice if we can
>      exchange idea somewhere. (like individual language categories in
>      above forums)
>
>      Simple example is like this. I found the term "open", "開く" might be
>      a proper word for the Japanese translation in the context of menu items
>      in some user interface. But it should be written in Hiragana "ひらく",
>      not in Chinese characters because kids around 6 or 7 may not be able to
>      read this characters. Or in another case, we may have to use more
>      plain expressions. It will be nice if we can discuss such topics somewhere.
>
> Well we, all translators, should be also experts of all about XO user interface,
> and this is your point, right?
>
> Best regards,
> Spiky
>
>