W3C home > Mailing lists > Public > public-webplatform@w3.org > December 2012

Re: Translations

From: Doug Schepers <schepers@w3.org>
Date: Wed, 05 Dec 2012 14:05:37 -0500
Message-ID: <50BF9B01.5010503@w3.org>
To: frozenice <frozenice@frozenice.de>
CC: public-webplatform@w3.org
Hi, frozenice-

On 12/5/12 1:52 PM, frozenice wrote:
> Uhm, yeah:
>
> css/properties/border-radius?zh is the same page as
> css/properties/border-radius, you just added a parameter.
> (I'm assuming we want translations on their own page)

We would need to add our own extension to take care of this. I think 
that's possible.


> css/properties/border-radius/lang:zh is still in the default namespace.

Ah, are namespaces only at the "root"? Pity.

> Also there could be problems with wiki markup, don't know for sure, but
> wouldn't risk it.
> If we want people to be able to filter search results by language, that
> one does not help.
>
> css/properties/border-radius/lang-zh seems ok from a technical
> standpoint, but doesn't look pretty. :(

Hard to maintain.


> css/properties/border-radius/$zh just looks wrong to me as a programmer :>
>
> I don't know, maybe some other char?
> css/properties/border-radius/.zh
> css/properties/border-radius/~zh
> css/properties/border-radius/!zh
> css/properties/border-radius/-zh
> css/properties/border-radius/'zh
> css/properties/border-radius/_zh
> css/properties/border-radius/:zh (looks the best to me, also shouldn't
> clash with CSS stuff)

All these are assumed to use the existing subpage hack, which honestly, 
I'd prefer to avoid, if possible. But I could live with them, if we can 
automate how they are created.


Regards-
-Doug

> On 05.12.2012 17:25, Chris Mills wrote:
>>
>>
>> On 5 Dec 2012, at 16:19, Doug Schepers <schepers@w3.org> wrote:
>>
>>> Hi, Chris-
>>>
>>> On 12/5/12 10:55 AM, Chris Mills wrote:
>>>>
>>>> On 5 Dec 2012, at 15:50, Doug Schepers <schepers@w3.org> wrote:
>>>>
>>>>> Hi, folks-
>>>>>
>>>>> Yes, good point, Phistuck.
>>>>>
>>>>> The lang: namespace idea is interesting. Namespaces have
>>>>> implications for search, which may be a good thing... we want
>>>>> someone to be able to search within their own language (or rather,
>>>>> within any particular language). It is a bit long, though...
>>>>>
>>>>> Chris, why did you dismiss the query-string delimiter? For
>>>>> technical MediaWiki reasons, or some other reason?
>>>>
>>>> Oh, I'm sorry - I didn't mean to dismiss ? - that was supposed to be
>>>> part of the previous sentence. I was only dismissing # and @
>>>
>>> LOL... I misread your message. I agree about # and @.
>>>
>>> Since we're on the topic... what about it?
>>>
>>> Chinese: docs/webplatform.org/wiki/css/properties/border-radius?zh
>>>
>>
>> That would work pretty well, afaics. Anyone got any ideas on why this
>> wouldn't work?
>>
>
Received on Wednesday, 5 December 2012 19:05:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:57:36 UTC