Re: Translations

What if there is a lang attribute (hey, there is)? a lang property? a lang
element?

How about the way Wikipedia does it?...
es.docs.webplatform.org
Or
docs-es.webplatform.org

This really solves all of the problems.

☆*PhistucK*



On Thu, Dec 6, 2012 at 11:46 AM, Chris Mills <cmills@opera.com> wrote:

> How about always having a /lang/ subdirectory between the main page and
> the translations?
>
> So
>
> css/properties/border-radius/lang/zh
>
> ?
>
> Chris Mills
> Open standards evangelist and dev.opera.com editor, Opera Software
> Co-chair, web education community group, W3C
> Author of "Practical CSS3: Develop and Design" (
> http://my.opera.com/chrismills/blog/2012/07/12/practical-css3-my-book-is-finally-published
> )
>
> * Try Opera: http://www.opera.com
> * Learn about the latest open standards technologies and techniques:
> http://dev.opera.com
> * Contribute to web education: http://www.w3.org/community/webed/
>
> On 5 Dec 2012, at 23:26, Alex Komoroske <komoroske@google.com> wrote:
>
> > I'd think we should stay away from ?, #, and :, all of which mean
> something specific in URLs (or MediaWiki namespaces). Other than that, i
> don't have a strong opinion.
> >
> > On Thu, Dec 6, 2012 at 6:04 AM, PhistucK <phistuck@gmail.com> wrote:
> > Regarding your last option, :zh can potentially clash with pseudo
> classes.
> >
> > ☆PhistucK
> >
> >
> >
> > On Wed, Dec 5, 2012 at 8:52 PM, frozenice <frozenice@frozenice.de>
> 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)
> >
> > css/properties/border-radius/lang:zh is still in the default namespace.
> > 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. :(
> >
> > 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)
> >
> >
> >
> > 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?
> >
> >
> >
> >
>
>