Tue 11. Jul 2017, 13:36
Hi misterionkell,
the "en" was just a hardcoded string because we didn't have a proper way to tell the language of the project in articy:draft.
Also it is never used as an actual CultureInfo anywhere, so you could even use fantasy names like "klingon" or "elvish".
The point is, the "en" was just an arbitrary name picked by me to identify the default exported language.
But we have discussed it internally and decided that it could throw some customers off and we will implement a commandline switch to set a substitute for the "en" string.
That way the language from articy:draft will always export the new substitute string. We have scheduled a new service release(no definite date yet) anyhow, so i try to squeeze that in.
While testing how that would behave in unity, i discovered that the entered language does not always stick. (Workaround is changing the language, on off toggeling a package and then saving the project. That way the language is saved).
This will be fixed in an upcoming plugin version.
Best regards
Nico