we are trying to work out the best approach to translations of the
openEHR website. The mechanism for the website itself is probably
straightforward:
* for each language xx, we create a copy of the current website under
a directory /xx/, and push this to the Github repo that contains the
website
o or perhaps separate repos, one per language?
* the people who want to do the translation work clone the repo,
replace the EN text with their language and upload the changes
* we push the changes to the main website
Most URLs in the website are relative, so this should work. Clearly
changes on the main website need to be reflected over time on the other
websites, but we can rely on proper commit comments in the Git repo to
take care of that.
*First question *- does this seem a reasonable workflow to adopt?
The *second question *that I can see is: what is the starting URL &
location? Taking Japan as an example:
Shinji's group already has openEHR.jp. Currently it is their own
website. However, with a translated form of the international website,
would it make sense for openEHR.jp to point to www.openEHR.org/jp? If
so, then the translated international website would need a prominent
link back to the current openEHR.jp. OR... if they prefer to land on the
current openEHR.jp, what URL should get a user to www.openEHR.org/jp -
presumably just that.
These questions apply to all languages, but not all locations or
languages equate to a country. For example, if we made
www.openEHR.org/es, I am sure we only want one of those, even though
there can technically be some small differences between the Spain /
Central & South America variants. But there is no openEHR.es and
openEHR.org.es (which appears to be taken) would correspond to Spain only.
In the end, I think the best we may be able to do is to provide a
www.openEHR.org/xx for each language translation, and it will be up to
local openEHR.orgs to add links or Apache rewrite rules to connect to
these locations. So multiple Spanish-speaking countries could all point
to this ES translation of the central site.
All ideas welcome.
- thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121217/f4beccba/attachment.html>
