For example:
1) Scenario 1
name: Jalan XYZ
2) Scenario 2
name: Jalan XYZ
name:ms: Jalan XYZ
3) Scenario 3
name: XYZ Road
(But this one is actually en, not ms)

Scenario 2 will better in long run

It's optional to add name:ms in Malaysia. Currently name tag data is still remain ms, which refer to local language have no issue at all.

However, adding name:ms in Malaysia case will ease editors from other countries to know which language it refers to.

已修改。

谢谢提醒。

Ok, let's only keep the MRT station ref code for name, and rest translations without ref code.

Thanks angys

For more details on Osmose Level 1 issue on "Default and local language name not the same", you can refer to OpenStreetMap official documentation page here - osm.wiki/Osmose/issues

Refer to local language section, there is:
Class 50601 "Default and local language name not the same"

This is the issue it will generate if you keep ref code name for Sri Delima station, but name:en/name:ms dont have ref code.

So it must be same for all texts (Including translations) in order to avoid this Osmose Level 1 "Default and local language name not the same" issue.

Original:
name Dr Shashikala Clinic
name:en Dr Shashikala Clinic
name:ms Klinik Dr Shashikala

Fixed:
name Klinik Dr Shashikala
name:en Dr Shashikala Clinic
name:ms Klinik Dr Shashikala

As I mentioned earlier, my example node/9404743865 is to show it have Osmose Level 1 issue "Default and local language name not the same", not a good example. This need to be fixed.

Nevertheless, I've fixed it and now no longer have Osmose Level 1 issue anymore.

Despite it's good to have ref code for Maps.me/Organic Maps, but it must not create new Osmose issues.

So my advice is to remove ref code in name OR put ref code in all translation languages, to permanently fix this Osmose Level 1 issue "Default and local language name not the same"

My example on this link (node/9404743865) is to show it have Osmose Level 1 issue "Default and local language name not the same", not a good example. This need to be fixed.

Thus, the better solution is to remove ref code on name itself

Your approach will cause Osmose Level 1 issue "Default and local language name not the same"

For example:
node/9404743865

Actually there is one problem here - The name is different with name:ms.

Not sure who added PY12 ref code in Sri Delima in the first place, so just follow the ref code for rest of translations in the names on last edits.

Now we have a scenario (Not yet fix),
name - KC03 Kampung Batu
name:en - Kampung Batu
name:ms - Kampung Batu
name:zh - 甘榜峇都

How you gonna to fix this issue? Add or remove ref code?

Kindly share ur suggestions.

Actually my end did not add ref code for the translation.

For example, add Malay, Mandarin Chinese, Simplified Mandarin Chinese and Traditional Mandarin Chinese via dropdown, then save the translation.

Is this added automatically due to editor?

Please correct me if I'm wrong.

Hi @pamym,

Yes, I used to stay there.

However, I not sure latest status for now year 2023.

Kindly help to improve it if there is any latest changes on these bus stops.

Thank you!

好的，谢谢@vimacs_hacks！

Hi @rene78,

Not sure about current status.

Last time it's still operational more than one year ago.

If you confirmed that the bus stop no longer operational now, kindly help to remove it.

Thank you!

我是简繁中文使用者，本人不是自动化编辑，是一对一精准修改的。

对于马路繁体的名称，目前不做任何台湾繁体的转换，只对字体本身的简繁转换，以免造成误解。比如你提及的“规划四路”里的“规划”，如果翻译成“計画四路”，这会造成误解和繁体版搜索不到"规划四路"。

谢谢！

明白，谢谢！

@AkuAnakTimur @kucai
Noted. Removed bus stop name in this changesets - changeset/122628376#map=19/4.30371/101.15687

Please add it if any of you all have reliable source

Thanks =)

Refer to this link - https://goo.gl/maps/f88RDHUFYoufK2Rs8