translation in another language possible?

[kyodev]

what do you think, if I translate at least credits.md, home.md, creenshots.md (the presentation) in french?
but I don't know if it's easy to switch language at server level.

[elrido]

I actually already implemented nginx language detection for another static site on the same server:

map $http_accept_language $lang {
	default en;
	~de de;
}

server {
	# other parts of the configuration removed for simplicity
	index index.$lang.html;
}

The above will use the browsers accept language header and fall back to "en" if no language matches the languages in the map (in the above example only "de" is supported). The index page would exist in a version per language, here index.en.html and index.de.html.

What I don't know is how to configure pelican to generate separate navigation trees, one per language. A naive approuch would be to have two projects to generate all the languages and ensure each uses a different file ending. Both would then be deployed into the same location.

What worries me a bit more then the technical aspects is that this means that we would need to maintain these translations. Currently I handle the update of the homepage based on the current README whenever a new version is released. With a french translation, would we then leave that home page on the old version until a translation exists, wait with the release until all content was translated or deliver en-content after the release until a updated translation exists? Probably also depends on how extensive the changes are...

[kyodev]

The above will use...

ok, I've not seen *.de pages.

What I don't know is how to configure pelican...

I don't know pelican

I imagine that a translation is a small benefit for the audience and a first look, for french users.

What worries me a bit more then the technical aspects...

yes, it's important. I would have imagined:

• generally, there are no big changes on the readme page
• I was thinking only translate the 3 most visible major pages
• leave for 3 days or 1 week. If no update, remove '$http_accept_language fr'?
• or remove '$http_accept_language fr' to waiting the new translation
• prevent with mail, or issue subscribe, that a futur readme (and other major pages) is on a dev branch, few days before?

As you like, before you must determine if a translation is useful for your web site