From f29b82f47807c861b1a63716efc2d4e81944fe15 Mon Sep 17 00:00:00 2001 From: Edward Welbourne Date: Tue, 13 Aug 2024 10:12:55 +0200 Subject: [PATCH] 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 --- util/locale_database/ldml.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/util/locale_database/ldml.py b/util/locale_database/ldml.py index 3d51e732d16..af8de38689b 100644 --- a/util/locale_database/ldml.py +++ b/util/locale_database/ldml.py @@ -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)