> 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>. Yes, that was my next question (where is the main "template" and css files?) :-).
> 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! Alright, then we are indeed talking about localised resources which would mean that content would change. >> >> 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. Yes, no problem. There is no "magic" solution it just involves substituting the actual message with a look-up to a table that is different for every language. Having a stable template would also help in this case. I have created a branch in my local copy to look at just that, so i am going to put together an example in just one page and share it later. >> >> 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 ;-) Yes, that's what you can do once all the messages are pooled in one file....Google can produce "interesting" results, especially when translating specialised terminology so maybe it is quicker to go through the actual translation (for a native speaker). All the best Athanasios Anastasiou > >> >> >> 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 >
