Hi, i18n team,
I know you have started work on D7 version of i18n module. However it seems nothing is done yet, as far as I see in github. Is there any chance this module would be ready to work with D7 next month or two? If no, could you give me some hints how could I make it work just with menus? I need to translate menus desperately... the content translation is done via "Content translation" module.

Comments

mgifford’s picture

yes, there doesn't seem to be any action since October 9th.

I added in the github version and got this error after enabling the 2 available multilingual modules:

Fatal error: Cannot redeclare i18n_node_language_list() (previously declared in /[...]/sites/all/modules/github/i18n/i18n_node/i18n_node.module:53) in /[...]/sites/all/modules/github/i18n/i18n_node/i18n_node.module on line 310
mishoboss’s picture

It seems there will be a long wait until we see D7 version of i18n...

Anyone knows any workaround to translate menus?

amirtaiar’s picture

subscribe

valderama’s picture

subscribing

criz’s picture

menu translations is imho the most missing feature for d7 multilanguage sites!

emagus’s picture

subscribing

spacereactor’s picture

Sadly I have to move back to drupal 6 because there isn't enough support to get internationalization to work with drupal 7. Very little attention is given to this important module. :(

steinmb’s picture

Still only the October 9th check in at GIThub. Anyone know what's happening?

mgifford’s picture

Ok, so who is going to pony up the resources to see that this gets done? Developers, cash, heck even blog posts thanking the countless hours that Jose, Gabor & others have put into setting this up for drupal over the years and all the work that's gone into getting the basics in core.

I agree that we need to have a plan & someone to step forward to do the initial upgrade. This may or may not be the team that did it in D6. I'm certainly willing to help test.

It would also be great if there was some thought now about what we want to see as part of core for D8.

das-peter’s picture

Subscribe
I did some work for strings, blocks & menu in my fork: https://github.com/das-peter/i18n

mgifford’s picture

Ok, that's great. I'm not familiar enough with how to use Git to merge in changes.

Is that just a clone and enhancement of Jose's work?

das-peter’s picture

@mgifford: Yes, basically it's just a copy of Jose's repo including all the versioning information. Github enables you to send a so called "Pull Request" - it's like creating a patch and send it to the other dev.
If Jose accepts the "Pull Request" he can merge my changes into his repo.
Besides that github offers nice tools to keep your fork in sync with the "master".

steinmb’s picture

Title: D7 port » D7 port of i18n

Renaming title, enable us to tell what project this is related to in views that only displays the issue title.

SilviaT’s picture

Title: D7 port of i18n » D7 port

Maybe this is a dumb question but why the development for D7 moved to Github?

juves’s picture

[deleted]

jose reyero’s picture

Well, we have a plan now, http://groups.drupal.org/node/111404

And btw, #583664: Planning Drupal 7 upgrade

@SilviaT,

Development is moving to Github with the idea of speeding it up. Besides cvs being old enough and difficult to work with specially if you want to rename folders (which is our case), last time I tried (with Drupal cvs) I got stuck with this more than once for days, http://drupal.org/node/912056

@steinmb,

We don't need to change the title. Or you can do the same for all the module's issues.

mgifford’s picture

Thanks Jose! This is great.

jose reyero’s picture

Status: Active » Fixed

The bulk of the upgrade is done, we need now testing and polishing, upgrade scripts, unit tests, etc.

Development is back on Drupal git btw.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.