Stream: IG creation
Topic: A problem of multi-language IG
Li-Hui Lee (Jan 13 2022 at 14:55):
Hi,
Sorry that I re-post my question from #shorthand (https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/A.20problem.20of.20multi-language.20IG) to here. @Chris Moesel thanks for your suggestion!
I have a question that we build IG in two versions, one is in English and the other is in Traditional Chinese.
However, I found that Profile's "differential table" in our Chinese version will not be displayed the same as in the English version. I guess the reason is that we have translated the default description & constraints from English to Chinese. So, the "_genonce.bat" or "publisher.jar" thinks we have modified the default values (even though we only do the translation without redefining cardinality, etc.) and put those translated elements in the differential table. as shown below.
I wonder if there is any possibility that we could figure out the display problem by coding, not by manually deleting the unnecessary content in the output HTML files.
Thank you!
Li-Hui
Lloyd McKenzie (Jan 13 2022 at 18:30):
If there is content in the differential section of your spec, it will show up in the differential rendering - even if the only change is the definitions or usage notes. What you might consider is two layers of profiling. The first would merely translate the set of elements you care to bother translating - but not perform any constraining. The second would be based on the first and impose your constraints. The differential in your second profile would thus only show the changes and the snapshot would show everything - including the Chinese translations for all element you bothered to translate. This would also have the benefit that the "translated" profile could be used as a base for a variety of constraint profiles. Obviously if you wanted to refine the definitions or usage notes in any of the constrained profiles, you could do that.
There may actually be a mechanism to leverage the Chinese translations that have been made to the base specification (i.e. here: https://github.com/wanghaisheng/fhir-cn/blob/source/README.md). However, I'm not sure if we have the machinery in place to support that yet. (If not, it's definitely on our 'list of things to do when we have bandwidth'...) @Grahame Grieve may have more information/ideas.
Grahame Grieve (Jan 13 2022 at 19:26):
multi-language IGs are on the todo list. There needs to be better infrastructure for this, since the approach you're trying - pretty much the only one you have - won't really work
Li-Hui Lee (Jan 15 2022 at 05:46):
Okay. Thanks for your explanation and help. I am looking forward to a better infrastructure for multi-language IGs. Also, the current tools are already easy to use in designing and publishing IGs.
@Lloyd McKenzie @Grahame Grieve
Last updated: Apr 12 2022 at 19:14 UTC
