Record the CLDR bug tracking the mn_Mong_MN number format

As previously commented, mn_Mong_MN would end up with the same decimal
and group separators if we trusted its draft="contributed" amendment
to the decimal separator. I reported this to the CLDR folk some time
ago and they now have a Jira ticket for it, which turns out to be a
duplicate, so we can track them and know when to remove my
hack-around.

Change-Id: Ib8f49dbdce090393ad20cd50969d6323818ee4ff
Reviewed-by: Mate Barany <mate.barany@qt.io>
This commit is contained in:
Edward Welbourne 2024-08-13 10:12:55 +02:00
parent 77a9a20822
commit f29b82f478

View File

@ -287,6 +287,8 @@ class LocaleScanner (object):
group = self.find(f'{stem}group')
if decimal == group:
# mn_Mong_MN @v43 :-(
# https://unicode-org.atlassian.net/browse/CLDR-17883
# https://unicode-org.atlassian.net/browse/CLDR-16413
clean = Node.draftScore('approved')
decimal = self.find(f'{stem}decimal', draft=clean)
group = self.find(f'{stem}group', draft=clean)