You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2021. It is now read-only.
Is it possible to have the lang.propertie files as actual files, on the harddrive, after compiling?
So that users kann translate for themselves. (A possible scenario would be to test out the translation before commiting them here or to be able to slightly change the existing translation so that the own quest writers can use a known vocabulary.)
Also it would be nice if the Settings-File ( #31 ) could include a setting to which language-file should be used. (Because even so I'm a german, I'm more used to the english vocabulary now 😁 )
The text was updated successfully, but these errors were encountered:
Is it possible to have the lang.propertie files as actual files, on the harddrive, after compiling?
So that users kann translate for themselves. (A possible scenario would be to test out the translation before commiting them here or to be able to slightly change the existing translation so that the own quest writers can use a known vocabulary.)
Also it would be nice if the Settings-File ( #31 ) could include a setting to which language-file should be used. (Because even so I'm a german, I'm more used to the english vocabulary now 😁 )
The text was updated successfully, but these errors were encountered: