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

List:       kde-i18n-doc
Subject:    Re: Date format in libtemplateparser.po
From:       Dimitrios Glentadakis <dglent () gmail ! com>
Date:       2012-03-30 9:03:16
Message-ID: 201203301103.16244.dglent () gmail ! com
[Download RAW message or body]

Στις 30/03/2012 10:21:13 Chusslove Illich γράψατε:
> > [: Dimitrios Glentadakis :]
> > So, could be a solution to use the 'KLocale::LongName Possessive' for the
> > languages that they use the possessive form for months ?
> 
> The problem is that the string is not fixed but user-modifiable, that you
> only translate the default variant of it. So, the PO message:
> 
> msgid "On %1 %2 you wrote..."
> 
> produces the translated equivalent of
> 
> On %ODATE %OTIMELONG you wrote...
> 
> which in my language needs genitive of date. But this string is exposed to
> the user, who might change it to the equivalent of
> 
> (%ODATE %OTIMELONG) You wrote...
> 
> which in my language needs the nominative of date. (In KMail 1.4.x, this is
> reached through Configure KMail -> Composer -> Standard Templates -> Reply
> to Sender.)

In the templates, if i change to %ODATESHORT it is ok for me as there is no available \
a variable like '%ODATEPOSSESSIVE.'

* In the case that you mentioned inside the parentheses in Greek it needs the \
genitive case. 

> 
> The question then is how to enable the user to select one of possible
> grammar forms (the particular set of which is language-dependent), how to
> explain this to the user, how to represent this as a PO message for the
> default string, or more generally how (and where) the translator should
> define various possible forms.

The translator does nt translate the date syntax form but only the first article "On" \
and the "you wrote". A note that the form is in nominative case  might be helpful.  
> And the counter-question is whether this
> trouble is worth the result.

I don't want to take this responsibility. Surely, the email is finally sent.

We had a discussion in the Greek ml the last year about this issue as all users see \
that the message is not correct. So, i decided at least to mention it as a non \
correct syntax in messages .

If it is a worth to be a correction? i think it depends on the developer, his \
workflow in kmail, the priorities that he wants to give in localization issues \
etc.... 

-- 
Dimitrios Glentadakis


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