Stream: russia
Topic: Translation
Grahame Grieve (Dec 03 2018 at 21:39):
Hi @Aleksandra Pavlyshina how's it going? @王海生 has asked me about translating FHIR to Chinese, and how much work is involved. I think you know more about that than anyone else.... how much work is it? And how do you do it?
Aleksandra Pavlyshina (Dec 04 2018 at 09:42):
Hi @Grahame Grieve nice to hear from you! How do you do? FHIR specification translation is a big work, at least for me. The most difficult part for me was to update and maintain current version of translation for the CI current build. So, it can be more convenient to choose the latest stable official version and translate it as it will not be changed over time, and there will be no need to merge new English version with previous translated version.
Another thing is where to build the specification. We have been hosting our site with FHIR translation on Github Pages and build it on Travis but now there is a problem with building the specification (There is insufficient memory for the Java Runtime Environment to continue). So, I asked @Josh Mandel about moving our FHIR spec translation builds to your CI https://dev.azure.com/fhir-build/build.fhir.org.
Grahame Grieve (Dec 04 2018 at 09:48):
Thanks. How many weeks of work have you done for how much %complete?
Grahame Grieve (Dec 04 2018 at 09:48):
And yes, we did break the Travis build a while ago
Aleksandra Pavlyshina (Dec 04 2018 at 10:00):
About how I do it. I copied the source folder, named the copy source.ru, and translated files in this folder leaving original English text in HTML comments. This is done to make it easier for future merges with new versions of specification. When I run a build, the content of source.ru substitutes source folder, and the site is built in Russian. Some files from folders implementations, tools also need translation e.g. PageProcessor.java, Publisher.java. The condition in PageProcessor.java should be changed to allow translated titles (line log("file \""+filename+"\": div/div["+Integer.toString(doc.getChildNodes().indexOf(x))+"]/h2 must be either 'Scope and Usage', 'Boundaries and Relationships', or 'Background and Context'").
Aleksandra Pavlyshina (Dec 04 2018 at 10:20):
Let's see. For each resource we need to translate 3 files: *-introduction.xml, *-notes.xml, *-spreadsheet.xml. Usually, it takes a day for one resource except for very big and small, not very mature ones with not much number of elements. So, 116 resources - 116 days. And about 200 *.html files in the root of the source folder, some of them very large e.g. search.html, http.html. For me, it took almost a year.
Grahame Grieve (Dec 04 2018 at 10:42):
Thanks - great information
Josh Mandel (Dec 04 2018 at 13:00):
Indeed, and great work! I'm still happy to help get you set up with Azure DevOps for the build. (Discussed with @nicola (RIO/SS) at Dev Days and I think we'll still push to GH for publication of the translation.)
Josh Mandel (Dec 11 2018 at 01:43):
Just finished configuring https://fhir-build.visualstudio.com/fhir-ru/_build -- should be auto building and pushing to https://fhir-ru.github.io (just kicked off the build after debugging against a test repo; we'll see in 10min or so)
Josh Mandel (Dec 11 2018 at 02:04):
Success! https://github.com/fhir-ru/fhir-ru.github.io/commits/master is where the built spec was pushed, published to the web at https://fhir-ru.github.io/ @Aleksandra Pavlyshina
Aleksandra Pavlyshina (Dec 12 2018 at 14:43):
Many thanks, Josh!
Last updated: Apr 12 2022 at 19:14 UTC
