Date Picker is not localized for Bulgarian (bg)

[zaramatheson]

AGOL introduced Bulgarian as a new language for this release and it looks like Calcite Date Picker has not been updated with it:
Locale = bg

https://codepen.io/zmatheson/pen/YzrPwdb?editors=1010

cc @jcfranco

[github-actions]

More information is required to proceed with this issue:

• Copy the appropriate issue template format and paste it into a comment, providing all of the requested items

This issue will be automatically closed in three days if the information is not provided. Thanks for your understanding.

[zaramatheson]

Description

AGOL introduced Bulgarian as a new language for this release and it looks like Calcite Date Picker has not been updated with it:
Locale = bg

Acceptance Criteria

Support Bulgarian Languague

Relevant Info

Which Component

calcite-input-date-picker

Example Use Case

ArcGIS Online Map Viewer Time Slider, Filter,

[driskull]

@jcfranco @paulcpederson Do you know the process for localization within calcite for this? Its kind of an outlier because we don't do any other localization within calcite.

[bsvensson]

FYI - The actual Bulgarian CLDR strings can be found in https://github.com/unicode-org/cldr-json/blob/main/cldr-json/cldr-dates-modern/main/bg/ca-generic.json
Compare the English (World) strings in https://github.com/unicode-org/cldr-json/blob/main/cldr-json/cldr-dates-modern/main/en-001/ca-gregorian.json

[jcfranco]

Deferring to @paulcpederson since he introduced those localization files. We should add this info to a wiki page for posterity. cc @benelan

[paulcpederson]

We had Babak Bolour and Rajeev Krishnan send us these json files. I spec'd what we'd need and they delivered a folder of them which I pr'd in.

[paulcpederson]

Now that we dropped ie11 we could theoretically start using Intl for this as I think the api's have good enough support IIRC, but I could be wrong on that one...

[driskull]

That would be ideal so we don't have to manage this :)

[jcfranco]

Thanks for the info, @paulcpederson! I'll work on a prototype to see if we can leverage Intl. In the meantime, I'll reach out to get the missing localization file.

[jcfranco]

Early prototyping shows that Intl does not have the necessary info to replace the localization files 1-1. Some items are not available or don't match from Intl.DateTimeFormat.formatToParts:

• default-calendar - this may be fine since it doesn't seem to be used at the moment
• weekStart - missing 🚫
• unitOrder/placeholder - it looks like these could be inferred from the order of formatToParts, but we'd need to confirm
• days.abbreviated - missing 🚫
• numerals - this could be fine if we format each day individually
• days.narrow/months.narrow - the short date style show numbers
• year.suffix - this could be obtained from the year separator, but we'd need a list of locales to do this for since all of them seem to have a separator

The rest from the DateLocaleData interface can be generated dynamically.

IMO, not having weekStart is a showstopper.

[driskull]

bummer :(

[github-actions]

Installed and assigned for verification.

[AdelheidF]

Changed the codepen to beta.74 and now I see this. I don't think it's correct for Bulgarian, the input box doesn't show DD.MM.YYYY, like in all other languages.
The calendar is good now.

https://codepen.io/afreitag/pen/KKXrGKE

I also noticed none of the Chinese language codes work. They stay English, see codepen.

[jcfranco]

the input box doesn't show DD.MM.YYYY, like in all other languages.

I believe this is expected. The placeholder format comes from the bg localization file. cc @raje9276

I also noticed none of the Chinese language codes work. They stay English, see codepen.

I created #3925 for this.

[AdelheidF]

BG is good: https://www.localeplanet.com/icu/bg-BG/index.html