W3C home > Mailing lists > Public > public-webplatform@w3.org > April 2013

AW: Translation process and Portuguese content

From: David Kirstein <frozenice@frozenice.de>
Date: Fri, 5 Apr 2013 12:29:58 +0200
To: "'Chris Mills'" <cmills@opera.com>
Cc: "'Julee Burdekin'" <jburdeki@adobe.com>, "'Tomoyuki SHIMIZU'" <tomoyuki.labs@gmail.com>, "'Juarez P. A. Filho'" <juarezpaf@gmail.com>, <public-webplatform@w3.org>
Message-ID: <071a01ce31e8$86414040$92c3c0c0$@frozenice.de>
Chris Mills wrote:
> Ok, so lang- or lang: would still be ok.

Yep, those are my favorites, too. Although we currently have some problems
with colons (:) and SMW, but I think that can be fixed. :)


-fro


-----Ursprüngliche Nachricht-----
Von: Chris Mills [mailto:cmills@opera.com] 
Gesendet: Freitag, 5. April 2013 11:38
An: David Kirstein
Cc: 'Julee Burdekin'; 'Tomoyuki SHIMIZU'; 'Juarez P. A. Filho';
public-webplatform@w3.org
Betreff: Re: Translation process and Portuguese content

On 5 Apr 2013, at 10:09, "David Kirstein" <frozenice@frozenice.de> wrote:

> Hi,
> 
> the reason why Wikipedia uses subdomains for each language is, that there
is a completely separate wiki instance for each language. Interwiki-Bots
then maintain the connections between the articles in the separate wikis. I
imagine we don't want to maintain several wiki instances.

One is hard enough ;-)

> 
> The easiest way to add a functional translations-bar to articles is to
append something to the path, like it is done now. The only problem with our
current solution is that there might be some name clashes (IIRC PhistucK
pointed out that for example css/units/pt could be a redirect to points or a
translation).
> 
> Prefixing the language code should be easy enough (just move the already
translated pages and tweak the language-related templates). Now just to find
out what the best prefix is...
> 
> Some prefixes that would make sense to me are "lang-" or some single
characters like ! or something like that (we need to make sure this doesn't
break page-name like pseudo-classes or wiki-stuff). Also don't confuse
actual MW-Namespaces (like WPD:, Special:, Templates: etc. with just
appending something to the page path.

Ok, so lang- or lang: would still be ok. The latter would not cause conflict
with CSS :lang()

I would prefer lang than some kind of single character, as I think what we
would gain in brevity we would lose in readability.

> 
> Oh, and one more thing: this would also help with searches that filter by
language, so one could easily find all .../lang-es (or whatever) articles.

good point!

Received on Friday, 5 April 2013 10:30:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:13:45 UTC