Hugo M
Hugo M
Having the same issue, this is definitely a bug, and can be easily reproduced as per @Nicksil 's instructions.
> Hi, thanks for reporting this, let me look into this. > > This is on 1.8, yeah? Yep: `{:ex_openai, "~> 1.8.0"}`
Thanks for pointing this out @dvcrn!
Hi @bbradz I had the same problem as you. Still can't get the version to display properly. But with regards to the second issue, I fixed that by installing `scikeras`...
> This is because in [CLDR](https://github.com/unicode-org/cldr/tree/main/common/main) there is no such locale as `en-US`, `es-ES` or `zh-Hans`. CLDRs locale naming is that the territory with the most native speakers of that...
> Are you able to share what the output of: > > 1. `MyApp.Cldr.known_locale_names()` ```elixir iex(5)> MarketplaceSearch.Cldr.known_locale_names [:ar, :bg, :cs, :da, :de, :el, :en, :"en-CA", :"en-GB", :es, :fi, :fr, :"fr-CA",...
> > Yep, but under BCP47 I think that zh-Hant is still valid as traditional Chinese script, whose nearest match should be zh-HK. > > `zh-Hant` is definitely a valid...
> TLDR; (but do please read). I can do as you'd like to best match `zh-Hant` to `zh-Hant-HK` but I'm not sure its a good idea, not sure its sustainable...
> [@hugomorg](https://github.com/hugomorg) I've been reflecting on tis a while and I think there is a reasonable compromise I can implement. > > 1. When resolving CLDR locales, and doing a...
> I spent the weekend mapping out how to do this and I've got a good plan. And I found some good test data trolling the CLDR repo. I just...