Multilanguage month support

subscribing

Very useful and necessary patch. Well to see it in following versions of Date

Subscribe

Subscribe

Subscribe

awsome!

+1

Subscribe

subscribe

subscribe

I subscribe and fully support.

+1 for that

Tested on Drupal 6.15 and Date 6.x-2.4. This patch corrects the writings of month names in Russian on a multilingual site with i18n installed.

Subscribing. This feature is needed.

Subscribe

Subscribe

Subs

Subscribe

Sub.

subscribe

Very important for me!

+1

subscribe

subscribe

Subscribe. Very useful!

subscribe

+1

+1

+1

Subscribing! Very needed patch.

subscribing

can this be expanded to allow different order of month/day/year dropdown selectlist depending on language? for example, if language A mm/dd/yy and if language B yy/mm/dd

t('!month-genitive |January|February|March|April|May|June|July|August|September|October|November|December', array('!month-name' => '')

should be

t('!month-genitive |January|February|March|April|May|June|July|August|September|October|November|December', array('!month-genitive' => '')

subscribing

subscribing

subscribing

Subscribing! Very needed patch.

Any chances this would be applied to the module Date?

+1.
3 months to commit...

Subscribing

Patch fixed according to #32 suggestion.

Come on, Date devs! This is a MUCH demanded feature among Russian, Ukrainian, Polish, Belorussian, Slovak, Slovenian, Czech, Bulgarian, Macedonian, Bosnian, Serbian, Croatian and Montenegrin users.

I hope that this patch will be inserted into the following release.

+1

tested and works great!
+1 for commit

Date module is unusable for me without this patch. Unfortunately there is some problem in 2.6 version - when editing node, month-genitive is default and can't save node without changing date.

but, does it work with views?

Does #44 indicate there is a problem with the patch? Please confirm that.

2 KarenS #46

I'm using patched Date on all my sites. Node editing is okay. Saving and displaying is okay. I believe that piotrly #44 should clarify his issue and provide steps to reproduce it.

For those who are upset that this is not yet committed -- read back through this issue -- everyone says 'subscribe' or '+1' but no one says they have tested it. Then we have a report that it needs work and it is changed and immediately marked ready to commit, but again no one reports that they have tested it until one report in #43 that it (which patch? the one with the fix in #32 or the original?) works. We also have a report in #44 that it does not work.

I see only three reports that it was tested, one is for a different patch and one is a report that it did not work.

Don't grumble that I haven't committed this, please do more than say '++'; Tell me that you have tested it and *which* thing you are testing and please someone confirm what is going on with the report that it didn't work.

Actually there's something else that needs to be tested in addition. I'm pretty sure this will work fine in English since that is the base language, but I suspect this may break languages that don't use month-genetive. I suspect we need a test for whether there is a non-English value in month-genetive before we use it to ensure that it doesn't pop back to English for languages that have nothing in that value. I'm not even sure of the best way to do this but you need to use something like French (where we have a good current translation that does not have that value populated) to be sure that the right value is returned for them.

KarenS, here's a live site in Russian with #40 patch: http://zhso.ru/

If you're still unsure it's working, i can clone the site for you and grant you editor permissions.

As for #44, the guy didn't supply his report with steps to reproduce. It's unclear what happened with his site and i don't experience his issue as well.

What about a French site? We need to confirm what happens on a French site that has no French values for genetive.If I read this right, it will end up with English values instead of French values if the pattern meets the criteria. See my comments in #51. You can wait for me to test and research if that it is a problem and try to find a fix if it does, or someone can check that out for me. If you want me to figure this out by myself, you may have a wait. If you're anxious to get this committed someone can test this for me.

Please understand that I have to not only know if it works right for you, I have to be sure it won't break things for anyone else.

subscribing

This patch still is not included to the module, right?

bora-89, not icluded. The maintainer wants it to be tested on a non-cyrillic site, like French.

need

Still waiting...

This patch solve month names in Date module, but same problem is in other modules and Drupal core. See format_date in common.inc, titles for argument with node creation month (when used with day argument) in Views, etc.

Still no support for 7.x? Also, this patch is not applied to 7.x branch.

I would gladly mark this as a bug and set its status to critical, but this is not the case. Drupal's internal weird dates processing, based on PHP's dates but with locale stuff cut off makes things so bad. I hate this, honestly.

I asked questions in #49, #50, and #51. No one has answered all of them. Nothing will happen to this patch until someone responds to those.

This does not apply to 7.x where multilingual is handled by core.

No response or follow-up after 4+ months at 'postponed (maintainer needs more info)'
Marking closed...

+1

+1000000000

Subscribe

+1

There is no point in subscribing 'cause this issue is closed.