On 18/12/2012 02:26, Shinji KOBAYASHI wrote: > Hi Thomas and Gunner, > > Having translated portal would appeal wider range, especially for > beginners. > On the other hand, openEHR.jp site has another accountability as the > domestic > artefacts repository. We can have two sites for their responsibility. > > 1)http://www.openehr.org/jp/ > Translated version of official openEHR.org site. > 2) http://www.openehr.jp/ > Repository of Japanese artefacts, such as translated documents, > presentation/education materials, > seminar information. > > My answer to the questions. > 1) The workflow on GitHub seems reasonable for me, but we need to try > it to prove that it works. > 2) Your suggested URL openehr.org/jp <http://openehr.org/jp> is good > for us, Japanese community, but I think redirection > openehr.org/jp <http://openehr.org/jp> to openehr.jp > <http://openehr.jp> is not useful as described before. Localisation > has two dimension just > you mentioned, language and geographical location. I do not have good > idea for Spanish community, > but I think it is a common problem for international language > community, even in English. > There are many English speaking countries, but localisation is > necessary, just now Koray is trying.
@Shinji: Ok so let's assume we set up each language on the central site as openehr.org/jp etc, and you will be able to use where you like at your end. @Gunnar: I take your points, but not sure what to do about them - i.e. I am not sure what to practically do about the need for a mix of local and central content, other than for local websites / wikis etc to be created as we are doing. I think the main thing we can do now is to keep the central site small, which was a conscious objective from the start. The local needs in different countries will clearly be different, so I think we just have to see how the local web presence in each place develops. @Bert: thanks for the offer. All - we are still working on some content, so the central website is not 'finished' .. but it will never be, there will always be something more to do. So we could start as an experiment just one translation job to see how the workflow works. The main thing we would need to agree on is probably how we document the changes we make on the central site in Git, so that translators can detect what changes have happened that they need to reflect. I think we might be ready to try this experiment in the next week or so (we are still adjusting some mechanical aspects of the site). It sounds like we make the experiment either Japanese or Dutch - who wants to be the guinea pig? (I.e. who has time ;-) - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121218/b445750f/attachment.html>
