Stream: implementers
Topic: Specs and Unicode
Gino Canessa (Jan 05 2022 at 23:26):
Hi all - trying to diagnose some issues with Unicode and the newest builds. For an example we can use ValueSet-currencies.json. In earlier builds, Unicode characters were encoded... properly? E.g., in 4.0.1 (current R4) and 4.1.0 (R4B ballot) we have "Polish złoty", "Paraguayan guaraní", etc. However, in the snapshots (both R4B and R5) I'm seeing "Polish zE\u0002oty", "Paraguayan guaranC-", etc.
Looking at ...publish\expansions.json on my local builds, they look 'incorrect' there already (recent R4B and R5), but I don't know how that is sourced.
Any thoughts or pointers would be greatly appreciated. (tagging @Grahame Grieve since it's probably in your wheelhouse, but I will also apologize since I know you've had quite a day already)
Gino Canessa (Jan 06 2022 at 16:48):
As a note, I've locally replaced the 4.3.0-snapshot1 and 5.0.0-snapshot1 ValueSet-currencies.json with the version from 4.0.1 (with modified version) for now so that I am unblocked.
Gino Canessa (Jan 06 2022 at 18:02):
As an additional follow-up (@Grahame Grieve ), it looks like the data is incorrect in the Terminology Server (around here?). Thanks to Josh for helping track it that far, but we couldn't figure out if that code is manually entered or generated.
Josh Mandel (Jan 06 2022 at 18:57):
manually entered or generated
And assuming library/fsl/fsl_lang.pas is generated.... by what script or software?
Gino Canessa (Jan 10 2022 at 16:18):
Just pinging here so it doesn't fall off: @Grahame Grieve, what can I do to help for next steps?
Last updated: Apr 12 2022 at 19:14 UTC
