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

Incorrect date formatting in Italian #127

Closed
jsilland opened this Issue Aug 6, 2014 · 9 comments

Comments

Projects
None yet
3 participants
@jsilland

jsilland commented Aug 6, 2014

Time.now.to_datetime.localize(:it).to_date.to_medium_s
=> "06/ago/2014"

As per our Italian linguists, this is incorrect – The correct separator should be a space in this case

@KL-7

This comment has been minimized.

Show comment
Hide comment
@KL-7

KL-7 Aug 6, 2014

Contributor

This pattern comes directly from CLDR data over here, so if you're sure it's incorrect, you should submit a ticket for CLDR. Looks like they're using spaces for 'long' format, but slashes for 'medium' and 'short'.

Contributor

KL-7 commented Aug 6, 2014

This pattern comes directly from CLDR data over here, so if you're sure it's incorrect, you should submit a ticket for CLDR. Looks like they're using spaces for 'long' format, but slashes for 'medium' and 'short'.

@jsilland

This comment has been minimized.

Show comment
Hide comment
@jsilland

jsilland Aug 7, 2014

I reported the bug to CLDR. If you agree to keep this bug open, I can update it with their response when I receive it

jsilland commented Aug 7, 2014

I reported the bug to CLDR. If you agree to keep this bug open, I can update it with their response when I receive it

@KL-7

This comment has been minimized.

Show comment
Hide comment
@KL-7

KL-7 Aug 7, 2014

Contributor

We sure can keep the ticket open, but I should warn you that most likely the fix will get into twitter-cldr-rb only after a new version of CLDR with this fixed is released and twitter-cldr-rb is upgraded to that CLDR version. It'll take some time, but I'd rather not update our resources manually before that. If it's critical for your needs, I guess you can fork twitter-cldr-rb and apply the fix earlier.

Contributor

KL-7 commented Aug 7, 2014

We sure can keep the ticket open, but I should warn you that most likely the fix will get into twitter-cldr-rb only after a new version of CLDR with this fixed is released and twitter-cldr-rb is upgraded to that CLDR version. It'll take some time, but I'd rather not update our resources manually before that. If it's critical for your needs, I guess you can fork twitter-cldr-rb and apply the fix earlier.

@jsilland

This comment has been minimized.

Show comment
Hide comment
@jsilland

jsilland Aug 7, 2014

I fully recognize that fixing this issue will take a couple of release cycles on both ends, as well as for the CLDR folks to actually acknowledge the issue prior to that. In the meantime, we're mitigating the issue by switching to a different format in this particular use case.

With that said, CLDR's issue tracking appears to be fairly opaque (I was given no link to actually check on the status of the issue) and I would like for this to be publicly searchable and tracked, even if it takes place in a non-official binding of CLDR.

jsilland commented Aug 7, 2014

I fully recognize that fixing this issue will take a couple of release cycles on both ends, as well as for the CLDR folks to actually acknowledge the issue prior to that. In the meantime, we're mitigating the issue by switching to a different format in this particular use case.

With that said, CLDR's issue tracking appears to be fairly opaque (I was given no link to actually check on the status of the issue) and I would like for this to be publicly searchable and tracked, even if it takes place in a non-official binding of CLDR.

@KL-7

This comment has been minimized.

Show comment
Hide comment
@KL-7

KL-7 Aug 7, 2014

Contributor

I've never reported CLDR issues myself, but @camertron might know something about the process. It'd be great to link CLDR ticket here, so we can keep track of it. Did you report it through http://unicode.org/cldr/trac ? If so, maybe you can find it through one of the reports here http://unicode.org/cldr/trac/report?

Contributor

KL-7 commented Aug 7, 2014

I've never reported CLDR issues myself, but @camertron might know something about the process. It'd be great to link CLDR ticket here, so we can keep track of it. Did you report it through http://unicode.org/cldr/trac ? If so, maybe you can find it through one of the reports here http://unicode.org/cldr/trac/report?

@jsilland

This comment has been minimized.

Show comment
Hide comment
@jsilland

jsilland Aug 11, 2014

I originally had used another form which I had found after some amount of searching on the CLDR website. I have now reported this bug as http://unicode.org/cldr/trac/ticket/7800

I have a past working relationship with a couple of members of the Unicode consortium, I may try to reach out if this doesn't get traction in the near future.

jsilland commented Aug 11, 2014

I originally had used another form which I had found after some amount of searching on the CLDR website. I have now reported this bug as http://unicode.org/cldr/trac/ticket/7800

I have a past working relationship with a couple of members of the Unicode consortium, I may try to reach out if this doesn't get traction in the near future.

@camertron

This comment has been minimized.

Show comment
Hide comment
@camertron

camertron Sep 24, 2014

Collaborator

Looks like this has been fixed in CLDR v26, which was released September 18th. I'm hoping we can update this along with #129.

Collaborator

camertron commented Sep 24, 2014

Looks like this has been fixed in CLDR v26, which was released September 18th. I'm hoping we can update this along with #129.

@camertron

This comment has been minimized.

Show comment
Hide comment
@camertron

camertron Nov 5, 2014

Collaborator

This should be fixed now, can you verify, @jsilland?

Time.now.to_datetime.localize(:it).to_date.to_medium_s
=> "05 nov 2014"
Collaborator

camertron commented Nov 5, 2014

This should be fixed now, can you verify, @jsilland?

Time.now.to_datetime.localize(:it).to_date.to_medium_s
=> "05 nov 2014"
@KL-7

This comment has been minimized.

Show comment
Hide comment
@KL-7

KL-7 Nov 25, 2014

Contributor

Looks like this one is fixed. Thanks @camertron!

Contributor

KL-7 commented Nov 25, 2014

Looks like this one is fixed. Thanks @camertron!

@KL-7 KL-7 closed this Nov 25, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment