**Is your feature request related to a problem? Please describe.**

The language code for Malay language does not conform to ISO standard in SLiMS. 
Currently in SLiMS the Malay translation folder is labeled  **my_MY** . But the language code for Malay is **ms** , and so the folder should be named **ms_MY** . This is an historical error but is slightly more significant now that a translation for Burmese exists, as **my** is the ISO code for the Burmese ( Myanmar ) language, and that translation will reside in a **my_MM** folder. Some confusion about which language translation is in the folder could arise in the future.

**Describe the solution you'd like**

Ideally, future SLiMS should have the current **my_MY** folder renamed to **ms_MY**  ,  with an appropriate adjustment in _/lib/lang/localisation.php_ and all future translation folders be checked against ISO standards before naming. Any upgrade processes should take into account the change in folder name.

**Describe alternatives you've considered**
The alternative is to continue to use the incorrect naming convention, which may cause some continued confusion for new developers, but won't break any of the code. Most end-users will not notice the issue


Correction for Malay language code
This is a GitHub Issue
repo:slims9_bulian
owner:slims
Title : Correction for Malay language code
Issue date:

--- start body ---
**Is your feature request related to a problem? Please describe.**

The language code for Malay language does not conform to ISO standard in SLiMS. 
Currently in SLiMS the Malay translation folder is labeled  **my_MY** . But the language code for Malay is **ms** , and so the folder should be named **ms_MY** . This is an historical error but is slightly more significant now that a translation for Burmese exists, as **my** is the ISO code for the Burmese ( Myanmar ) language, and that translation will reside in a **my_MM** folder. Some confusion about which language translation is in the folder could arise in the future.

**Describe the solution you'd like**

Ideally, future SLiMS should have the current **my_MY** folder renamed to **ms_MY**  ,  with an appropriate adjustment in _/lib/lang/localisation.php_ and all future translation folders be checked against ISO standards before naming. Any upgrade processes should take into account the change in folder name.

**Describe alternatives you've considered**
The alternative is to continue to use the incorrect naming convention, which may cause some continued confusion for new developers, but won't break any of the code. Most end-users will not notice the issue


--- end body ---
