Skip to main content

Invariant.json

Comments

3 comments

  • Nico Burgerhart

    Same question here.

    0
  • Permanently deleted user

    Yes, the Invariant.json file was actually supposed to be renamed to Mapping.en-US.json.js as part of our automatic build process, but this was broken in 2.4, which results in both the mysterious Invariant.json and an out-of-date Mapping.en-US.json.js file. As a result, some of our partners who have translated our viewer from English have noticed a few English strings popping up in their viewers. We've fixed this in version 2.4.1, which will be released very soon (refer to issue GVH-6035 GVH-388). In the meantime, if you have translated Invariant.json, you can rename it to be the Mapping.xx-XX.json.js file for your locale (where "xx-XX" is your locale) -- that should keep the English strings out of your translated viewer.

    If you haven't translated your viewer, you can safely remove Invariant.json; it's not being used by the viewer.

    *edit: the issue is actually GVH-388, although GVH-6035 is related.

    0
  • Permanently deleted user

    Thanks Jordan, that's very useful.

    I only noticed Invariant.json when I was trying to find the source of the few strings that wouldn't show up in Norwegian after I had translated the other language files. We'll update to 2.4.1 and translate the new strings in the language files then, I guess (so we don't have to translate the whole of Invariant.json).

     

    0

Please sign in to leave a comment.