Formatting people’s names correctly in a given context, for a given purpose, is hard. International linguists recently helped update the #Unicode Common Locale Data Repository (#CLDR). It will help programmers display person names correctly in many settings.
Mike McKenna wrote about it in “A Story Teller’s Case Study: Unlocking the Power of CLDR Person Name Formatting – A Solution for Formatting Names in a Globalized World” https://www.unicode.org/media/CLDR_Person_Name_White_Paper_June%202023.pdf
Does anyone know what “flavor” of #ABNF / #EBNF this is written in? The table heading says “EBNF,” while the paragraph above references “ABNF,” but it appears to use a format that’s different from what’s defined in RFC 5234 or ISO/IEC 14977:1996.
https://www.unicode.org/reports/tr35/#unicode-locale-identifier
I could make assumptions about some of these characters, but I’d rather be as explicit as possible.
#abnf #ebnf #unicode #cldr #ldml #tr35
@VE2UWY @sungo @randomgeek Considering the complexity of localized date and time formats (see https://cldr.unicode.org/translation/date-time/date-time-patterns for how #Unicode #CLDR does it), I think most are served well with #macOS' menu bar sticking to the brief `MMMd`-style format.
Here's a #Perl one-liner that shows different locales' representations:
perl -CO -MDateTime -E 'say $_->locale->code, " ", $_->format_cldr( $_->locale->format_for("MMMd") ) for map DateTime->now->set_locale($_), sort DateTime::Locale->codes'
@gunchleoc Fun article; you presumably mean this sentence: «no Microsoft product I'm aware of can handle non-English type plurals properly in ANY other language».
Now, I suspect this might be a slight exaggeration. Microsoft participates in #CLDR and I bet they have at least *some* product with plural support. It's even mentioned in their docs for some languages:
https://learn.microsoft.com/en-us/globalization/localization/ministyleguides/mini-style-guide-russian#10-be-careful-with-number-placeholders
But unfortunately plural support is abysmal in most projects. Even in #Wikimedia. :[
https://translatewiki.net/wiki/Plural#Table_of_plural_formats_used_by_projects
Re-#introduction: recurring topics here.
#Wikimedia #Wikidata #Wikipedia #MediaWiki #OpenStreetMap #Wikimania #Wikisource #WikiCite #OpenRefine #wiki #Wiktionary #WikiLovesMonuments #Wikibase #Wikiquote
#i18n #L10n #translatewiki.net #Unicode #CLDR #languages
#Copyright #PublicDomain #PubblicoDominio #Copyleft #CreativeCommons #OpenData #UploadFilters #LicenzaLibera #DatiAperti
#InternetArchive #books #biblioteche #library #Koha #KohaILS #GLAM
#WikiTeam #digipres #ArchiveTeam #XSLT
1/4
#wikiquote #introduction #wikimedia #wikidata #wikipedia #mediawiki #openstreetmap #wikimania #wikisource #wikicite #openrefine #wiki #wiktionary #wikilovesmonuments #wikibase #i18n #l10n #translatewiki #unicode #cldr #languages #copyright #publicdomain #pubblicodominio #copyleft #creativecommons #opendata #uploadfilters #licenzalibera #datiaperti #internetarchive #books #biblioteche #library #koha #kohails #glam #WikiTeam #archiveteam #xslt #digipres
"… Croatia changes to use Euro starting in January 2023."
More #i18n contributions always needed for #CLDR at #Wikimedia / #MediaWiki / #translatewiki.net. There's something for everybody: simple word-by-word translation, more complex localisation, coding, documentation.
https://translatewiki.net/w/i.php?title=CLDR&oldid=10577281
#i18n #cldr #wikimedia #mediawiki #translatewiki
Thanks @alolita for a nice presentation on #Unicode and #CLDR today at #KansallisKirjasto! I loved the focus on interoperability in #i18n and #L10n as requirements for #usability, #a11y.
https://www.kansalliskirjasto.fi/en/events/perspectives-accessibility-ict2022
#unicode #cldr #kansalliskirjasto #i18n #l10n #usability #a11y
@Changaco @aral @fabrice Ohnoes, yet another #Mozilla #i18n system? :D I feel they announce a new one at every FOSDEM but I missed Fluent (or I forgot).
I'm interested in your opinion about https://translatewiki.net/wiki/Gender and https://translatewiki.net/wiki/Plural .
Happy to see that Fluent relies on #Unicode #CLDR too.
https://translatewiki.net/wiki/CLDR