[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:       Chusslove Illich <caslav.ilic () gmx ! net>
Date:       2008-10-11 11:37:03
Message-ID: 200810111337.08117.caslav.ilic () gmx ! net
[Download RAW message or body]


> [: Sebastian Trüg :]
> Maybe you are right. So maybe we stick to simply adding a plural form and
> leave it at that...

Plural form would be fine, simple and obvious enough to use.

I'm just wondering, who is supposed to add these plural forms? The writer of
ontology file? Plural form would then also be available for translation,
right?

>> [: Chusslove Illich :]
>> [...] if some ontology files are going to be translated in the same
>> manner as .desktop files [...]
>
> [: Sebastian Trüg :]
> that is the plan.

These ontology files, where would they be -- scattered across modules, or in
one or few concentrated places? I.e. what is the "ideal world" usage
pattern, in what situations are they supposed to spring up?

Depending on this and previous question (on addition of plural form),
translators may -- just may -- be able to do some fancy stuff when a random
KDE app throws a message like "%1 is a %2". To this end, how conceivable
would be the following:

* that "context" can be provided to arbitrary words/phrases in ontology
  files, akin to first argument in i18nc? So that it finds it's way into the
  extracted POT file (e.g. this is *not* possible with stuff from .desktop
  files)?

* if the previous is impossible, that at least every extracted text from
  ontology file gets "automatic" context (e.g. "element path" or something),
  such that it never happens that two same texts in the ontology file (or
  files) are given as single message in a PO file?

* that translators may insert extra properties, in some suitable format, to
  phrases extracted in the PO file, and that these are then converted back
  into proper ontology? For example:

    # An ordinary translation:
    msgctxt "..."
    msgid "plum"
    msgstr "šljiva"

    # Translation with translator-inserted properties:
    msgctxt "..."
    msgid "plum"
    msgstr "šljiva||gender:f|number:s"

  where then "gender" and "number" properties, with values "f" and "s",
  would be inserted into ontology file, filed under the language of the
  given PO (i.e. if another language is actual when application tries
  to fetch them, some sort of "undefined" is returned)?

-- 
Chusslove Illich (Часлав Илић)
Serbian KDE translation team

["signature.asc" (application/pgp-signature)]

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