On 18/12/2012 12:49, Athanasios Anastasiou wrote: > Hello Thomas and everyone > > Just a quick question/suggestion: > > Are we really talking about fundamentally different websites or just > translations?
Here I am talking about a translation of (parts of) the central website (as Gunnar said, some bits probably should just stay in English). We expect there to be separate websites in specific locales, either on a country basis, or like Pablo said, openEHR.org.es that covers a Spanish language community. Those sites are managed by people in those locales, and reflect local interests & needs. Koray has been working on some general concepts to get 'order' in this world. Eventually I would suggest that we think about adopting similar colours / scheme from the central website, to make all these sites look 'openEHR-ish'. For website developers of any local sites, please feel free to copy anything you see in the Git repo of the central site <https://github.com/openEHR/openehr-website>. > > In other words, are we just talking about changing the "labels" > according to openehr.org/[language-code] or could it be that a few of > the pages of the "/es" (for example) website would have different > content (perhaps adapted to local conditions)?. Well there is technically no reason not to do that - since if we put each translation under its own directory, other content can go into those directories. But I do think we should not try to make the central site do everything - there is a lot of local content for each country that would be very local indeed. Note - we can however keep adding more rules to Apache to do redirections so that local content has nicer URLs. I could be proven wrong however! > > If the websites are addressing a [language-users] community (as it was > mentioned before) and not a specific geographic area, maybe it would > be worth taking the time to add (or borrow) some minimal > internationalization features on the current website. Adriana only just started looking at this, and has no special expertise in this area. There doesn't seem to be any textbook on how to do this, and info on the web is sparse. If you know the magic process for internationalising a website, I'll get her in touch with you and you can help her out. > > Therefore, instead of translating all resources, we just translate a > big key/value dictionary (in text format). > > What do you think? I don't know how that works - since most content pages (i.e. the most useful stuff to translated) is static HTML. My approach (possibly to dumb) would have been to run the pages through google translate and then fix all the wrong bits ;-) > > > All the best > Athanasios Anastasiou > > P.S. The site already uses php anyway, so why not make it a bit more > "active"? any suggestions welcome. - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121218/0989d62c/attachment.html>
