Axel Hecht wrote:<...>
As you indicated translations, should they happen on the same site, if ever? Should we try to be ready to get them in now?
That's why I proposed, in shameless imitation of msdn except for the name, a Worldwide item on the link toolbar. That would lead to an index page of links to various localizations.
Should the localizations be hosted at developer.mozilla.org? I think so, for the same reason we want to "stand alone" if necessary for XUL docs. That does mean we need assistant editors who speak various languages and can help the editor-in-chief run a tight ship across many localizations.
From our (kinda limited) experience with the www.mozilla-europe.org site, having concurrent localized versions of a website puts quite some management task on the iron fist. And forget about that velvet glove ;-).
Anyway, we most definitly don't want to start with translations, I'd say. Localizers should be able to get a grip on what needs translation, and that requires a halfway-live site.
But. If the site should be ready to get localized, internal links should be made up right from the start. This requires a settlement on the URL scheme as well as a policy about linking to other pages, shared images and localized images. We at mozilla-europe.org use a scheme that goes like
www.mozilla-europe.org/lang/dir/ec/to/ries/file.html.
We don't use absolute links at all, so that translations can reuse links more easily. So the question would be, do we wanna go for a top-level lang dir, do we wanna use Gerv's redirect magic [1], too? In the scenario of having both /dir and /en/dir pointing to the same resource, we need to care about links even more.
Axel
[1] http://www.gerv.net/hacking/language-selection/ _______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
