Currently, Light.vn supports English & Japanese for Commands & Parameters in Scripts, right?
It's probably a Great Addition to be able to Write Scripts in your Native Language
~ at least, if you're japanese, that is.
The downside of natively supporting One other Language is:
a) things might get mixed up in multiple levels & areas of development or production (bad)
b) the loss in flexibility (since a great feature which could provide lots of potential to other users as well is limited to japanese users)
c) loss of unification (opinion on this is in part controversial ~ but it's commonly known that it's best to use english for any kind of (software) development task since it has clear benefits for such things over other languages (including least logical & technical complexity))
Instead, Light.vn could localize Scripting by integrating Language Definition Tables.
In other words: It internally uses English but can dynamically interpret any kind of Language using a Definition Table (Descriptor) ~ in a similar way Dynamic UI Localisation works (based on String Definitions).
That way, even Custom Languages could be implemented to further enhance the approach of making the Source Script comprehensible, for example.
Based on Size, Languages can be either included or dynamically downloaded when needed (or Manually put in a Specific Directory).
PS:
commands_to_english.exe is 16.5MB in size!
Isn't that a bit much?!
Currently, Light.vn supports English & Japanese for Commands & Parameters in Scripts, right?
It's probably a Great Addition to be able to Write Scripts in your Native Language
~ at least, if you're japanese, that is.
The downside of natively supporting One other Language is:
a) things might get mixed up in multiple levels & areas of development or production (bad)
b) the loss in flexibility (since a great feature which could provide lots of potential to other users as well is limited to japanese users)
c) loss of unification (opinion on this is in part controversial ~ but it's commonly known that it's best to use english for any kind of (software) development task since it has clear benefits for such things over other languages (including least logical & technical complexity))
Instead, Light.vn could localize Scripting by integrating Language Definition Tables.
In other words: It internally uses English but can dynamically interpret any kind of Language using a Definition Table (Descriptor) ~ in a similar way Dynamic UI Localisation works (based on String Definitions).
That way, even Custom Languages could be implemented to further enhance the approach of making the Source Script comprehensible, for example.
Based on Size, Languages can be either included or dynamically downloaded when needed (or Manually put in a Specific Directory).
PS:
commands_to_english.exeis 16.5MB in size!Isn't that a bit much?!