http://ddtp.debian.net -> https://ddtp2.debian.net
|Deletions are marked like this.||Additions are marked like this.|
|Line 10:||Line 10:|
|Line 15:||Line 16:|
|Line 20:||Line 22:|
|Line 32:||Line 35:|
|It would be nice is to have a similar behaviour as what's used for www.debian.org ([[http://www.debian.org/intro/cn|content negotiation]]):||It would be nice is to have a similar behaviour as what's used for www.debian.org ([[https://www.debian.org/intro/cn|content negotiation]]):|
|Line 34:||Line 37:|
|* The page are exported (as docbook, html...) then translated using regular I18n tools (see Debian I18n [[http://wiki.debian.org/I18n|#1]] and [[http://i18n.debian.net/wiki/|#2]]).||* The page are exported (as docbook, html...) then translated using regular I18n tools (see Debian I18n [[I18n|#1]] and [[https://i18n.debian.org/|#2]]).|
|Line 38:||Line 41:|
|1. visitors use http://wiki.debian.org (the html is served by Apache, which can be mirrored)||1. visitors use https://wiki.debian.org (the html is served by Apache, which can be mirrored)|
|Line 40:||Line 43:|
|3. Translators use a tool like [[http://pootle.debian.net|Pootle]] or [[https://ddtp2.debian.net/ddtss/index.cgi/|DDTSS]] to do their translation||3. Translators use a tool like [[WikiPedia:Pootle]] or [[https://ddtp.debian.org/ddtss/index.cgi/|DDTSS]] to do their translation|
|Line 48:||Line 51:|
|== See also ==|
|Line 49:||Line 53:|
== See also ==
- English pages are name like "Hardware"
Translated pages are named like "de/Hardware" (i.e language code, followed by the English name).
The English page should be the "Master" page (contributions are made to the English page, then they are translated).
- It's liberal
- It's possible to create a page in German, even if there is no English version (Rarely used).
Non-english contributors can contribute actual content, directly in their native language, but that's discouraged (See #TODO).
- Updating the links to the translated pages is painful:
- Each page should link to all alternatives languages (that's boring, but easy to do).
Once a page (eg ?Example) is translated (to e.g, ?fr/Example) the translator should search all the pages in French that link to ?Example, then update the link to the newly translated page: ?fr/Example).
It is not possible to detect (and disable) a translated page, if it's lagging too much.
- Content negotiation isn't possible: When a user visit a page, it isn't possible to automatically present the best page for him (note that this would solve the 2 problem above!).
- It isn't possible to translate the URL (but that's another story, which may not be a good idea, anyway).
Translate using pootle, publish as html
It would be nice is to have a similar behaviour as what's used for www.debian.org (content negotiation):
- The master page for translation is English.
All the pages are then published as html by apache (with a nice theme which looks like a wiki )
Therefore there are three interfaces for the wiki (which could all look the same, with appropriate theme):
visitors use https://wiki.debian.org (the html is served by Apache, which can be mirrored)
- Editors for the English pages use the plain wiki engine (probably served over https)
- Fast (the page is served as HTML, using Apache. It's possible to mirror the page)
- Properly translated: Every language have the same quality. If a translation is lagging behind the master page, it can be disable. any we present the English version.
- Needs development that no one seems to want to do.