« Return to Thread: l10n architecture proposal available for comments
Re: l10n architecture proposal available for comments
by Axel Hecht
::
Rate this Message:
Rimas Kudelis wrote:
> Axel Hecht wrote:
>> Rimas Kudelis wrote:
>>> Do you intend to support Grammatical cases [1] in any way? If yes,
>>> then how do you see it?..
>>>
>>> [1] http://en.wikipedia.org/wiki/Grammatical_case
>>>
>>> RQ
>> Yes, it works pretty much like the gender example in
>> http://people.mozilla.com/~axel/l20n/js-l20n/sample-01.html.
>>
>> If you create a sample output similar to one of the js examples I did, I
>> can create a corresponding lol file to demo that.
>>
>> Sadly, neither German nor English really show this off canonically, so I
>> didn't do an example for that yet.
>
>
> OK, here's an example. From Microsoft Windows XP. Every user has a "My
> Documents" folder there. Now in English, you can see "Jane Doe's
> Documents" for user Jane Doe, "Jack Daniels' Documents" for user Jack
> Daniels etc.
>
> Meanwhile in Lithuanian, to be gramatically correct, it cannot be
> "Rimas Kudelis' dokumentai" or "Rimas' Kudelis' dokumentai" or "Rimas
> Kudelis dokumentai" or anything like that. It has to be "Rimo Kudelio
> dokumentai".
>
> And your gender example would sound like this:
>
> Gerb. p. Kudeli,
>
> šis tekstas lokalizuotas
>
> Jūs užsisakėte vieną prekę.
>
> Name: Kudelis
> gender: male
> Items: 1
> Language: Lietuvių
>
> Now, do you think such DYNAMIC casing would be possible?
>
> RQ
Probably still somewhat simplified, but here it goes:
<owner: "Rimas Kudelis"
othercase: "Rimo Kudelio"
gender: "male">
<myDocuments: "${owner.othercase} dokumentai">
Of course, you could have myDocuments depend on the gender of owner, for
example.
The tricky part comes when you actually realize that you want to get
"owner" from the user settings, at which point you probably bite a
bullet here, as I doubt that a user likes the idea of entering his name
in all genders, nor do I expect that there's a descent machine logic to
guess the grammar for a name.
Additional caveat, you don't really know whether the name of owner is
actually a lithuanian name or not, which might impact it, too. Like,
what would happen to "Axel Hecht" in this case?
Simply shows that "Axel's Documents" is a i18n bug. :-)
Axel
_______________________________________________
dev-i18n mailing list
dev-i18n@...
https://lists.mozilla.org/listinfo/dev-i18n
> Axel Hecht wrote:
>> Rimas Kudelis wrote:
>>> Do you intend to support Grammatical cases [1] in any way? If yes,
>>> then how do you see it?..
>>>
>>> [1] http://en.wikipedia.org/wiki/Grammatical_case
>>>
>>> RQ
>> Yes, it works pretty much like the gender example in
>> http://people.mozilla.com/~axel/l20n/js-l20n/sample-01.html.
>>
>> If you create a sample output similar to one of the js examples I did, I
>> can create a corresponding lol file to demo that.
>>
>> Sadly, neither German nor English really show this off canonically, so I
>> didn't do an example for that yet.
>
>
> OK, here's an example. From Microsoft Windows XP. Every user has a "My
> Documents" folder there. Now in English, you can see "Jane Doe's
> Documents" for user Jane Doe, "Jack Daniels' Documents" for user Jack
> Daniels etc.
>
> Meanwhile in Lithuanian, to be gramatically correct, it cannot be
> "Rimas Kudelis' dokumentai" or "Rimas' Kudelis' dokumentai" or "Rimas
> Kudelis dokumentai" or anything like that. It has to be "Rimo Kudelio
> dokumentai".
>
> And your gender example would sound like this:
>
> Gerb. p. Kudeli,
>
> šis tekstas lokalizuotas
>
> Jūs užsisakėte vieną prekę.
>
> Name: Kudelis
> gender: male
> Items: 1
> Language: Lietuvių
>
> Now, do you think such DYNAMIC casing would be possible?
>
> RQ
Probably still somewhat simplified, but here it goes:
<owner: "Rimas Kudelis"
othercase: "Rimo Kudelio"
gender: "male">
<myDocuments: "${owner.othercase} dokumentai">
Of course, you could have myDocuments depend on the gender of owner, for
example.
The tricky part comes when you actually realize that you want to get
"owner" from the user settings, at which point you probably bite a
bullet here, as I doubt that a user likes the idea of entering his name
in all genders, nor do I expect that there's a descent machine logic to
guess the grammar for a name.
Additional caveat, you don't really know whether the name of owner is
actually a lithuanian name or not, which might impact it, too. Like,
what would happen to "Axel Hecht" in this case?
Simply shows that "Axel's Documents" is a i18n bug. :-)
Axel
_______________________________________________
dev-i18n mailing list
dev-i18n@...
https://lists.mozilla.org/listinfo/dev-i18n
« Return to Thread: l10n architecture proposal available for comments
| Free embeddable forum powered by Nabble | Forum Help |
