[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Please discuss: Translation of types and properties in Nepomuk
From:       Sebastian =?utf-8?q?Tr=C3=BCg?= <strueg () mandriva ! com>
Date:       2008-10-16 13:43:10
Message-ID: 200810161543.10886.strueg () mandriva ! com
[Download RAW message or body]

Ok, great, I think I got it now. :)

A last thing: do you know who did the desktop file string extraction and could 
help me with the ontology files?

Cheers,
Sebastian


On Tuesday 14 October 2008 13:02:31 Chusslove Illich wrote:
> > [: Sebastian Trüg :]
> > [...] The only problem left is that translators need to inform app
> > developers about all the possible contexts they come up with. Do we
> > already have a platform for that?
>
> (May be I didn't quite understand what you meant :)
>
> I take this, as mostly it is with contexts, to be translator-driven. Chain
> of events to be as follows:
>
> 1. While translating an application, a translator sees a message:
>
>   #: foo.cpp:100
>   msgid "%1 is a %2"
>   msgstr ""
>
> and thinks "what the hell are %1 and %2?"
>
> 2. This translator asks for addition of context (the static one, in
> msgctxt) here on the list, and gets response "%1 is... %2 is... from
> ontology..."
>
> 3. A translator, the one who requested context or another one who observes
> the thread, remembers "ah, ontology stuff can also have dynamic contexts"
> and requests it.
>
> 4. A programmer the original one or one of fix-around i18n people, is
> notified to modify the code in the way as mentioned in my previous message.
>
> If you are wondering on dynamic context labels, the first argument to
> inContext(), these are arbitrary and should be mentioned in static context
> (the first argument to ki18nc()); we *could* have a convention of naming
> them "td-x" or whatever, but that's not too important, so long as they are
> explicitly stated in static context.

[prev in list] [next in list] [prev in thread] [next in thread]