Hi, Sean!

I'm also wondering if there is any advice on the best way to deploy the language pack (global) with an application on GitHub. If the application was developed such that it bakes the language at compile time, then how would you bundle the language into the build file. Would you just include all of the languages or have the user install the language of choice separately.

I would suggest to export global in XML and store the file in sources. Pro: no losses, no conversion issues, same import/export as for code stuff. Like:

D $System.OBJ.Export("CacheMsg.GBL","cachemsg.gbl.xml")

Con: large size. But lang resources don't seem to be example of really large global.

For deployment purposes, e.g. what to upload to Github's Releases section, I like recently discussed recipe to export/import global with gz packing on the fly.

Hi, Peter!

I guess it's more about the source value list type:

We can put this option if the value for the level is a list which provides the way to introduce all the list elements as level members and link the current fact to all of them.

But I was interesting to me too how to manage the second level of hierarchy for such a first level? How Deepsee guesses which list element of the first level have the certain members of the second level and should I show it in expression somehow?

Am I right, Gevorg?