Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for locales in format #153

Closed
antoyo opened this issue May 19, 2017 · 4 comments · Fixed by #453
Closed

Add support for locales in format #153

antoyo opened this issue May 19, 2017 · 4 comments · Fixed by #453

Comments

@antoyo
Copy link

antoyo commented May 19, 2017

Hello.
It would be nice to be able to format a date in other languages than english.
Thanks to add this feature.

@Cobrand
Copy link

Cobrand commented May 22, 2017

I don't think it will be implemented directly in Chrono's core, however it could easily implemented as an optional feature (in the Rust sense), or even as another crate entirely. The latter would make much more sense, as it would be exactly like chrono-humanize did.

@lifthrasiir
Copy link
Contributor

In addition to being out of scope, date and time localization is about as difficult as time zone, because we may have to handle different chronologies at that point (e.g. Japanese era names or Islamic calendar). We probably have to delegate the entire jobs to something like rust-locale.

@hjmallon
Copy link

Coming from C/C++ it seems confusing to have a non locale-aware function called strftime. C languages and Python seem to translate day/month/etc names automatically along with preferred ordering and (in C) Japanese eras etc.

A few of these issues talk about a separate crate or fluent. Does anyone know where/if this functionality is supported or is aiming to be supported?

@cecton
Copy link
Contributor

cecton commented Dec 11, 2019

I updated #199 with a proposal for this issue.

@cecton cecton mentioned this issue Jul 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants