Closed (fixed)
Project:
Internationalization
Version:
7.x-1.x-dev
Component:
Compatibility
Priority:
Major
Category:
Feature request
Assigned:
Reporter:
Created:
24 Nov 2010 at 14:26 UTC
Updated:
2 Apr 2011 at 12:11 UTC
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
Comment #1
mgiffordyes, 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:
Comment #2
mishoboss commentedIt seems there will be a long wait until we see D7 version of i18n...
Anyone knows any workaround to translate menus?
Comment #3
amirtaiar commentedsubscribe
Comment #4
valderama commentedsubscribing
Comment #5
crizmenu translations is imho the most missing feature for d7 multilanguage sites!
Comment #6
emagus commentedsubscribing
Comment #7
spacereactor commentedSadly 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. :(
Comment #8
steinmb commentedStill only the October 9th check in at GIThub. Anyone know what's happening?
Comment #9
mgiffordOk, 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.
Comment #10
das-peter commentedSubscribe
I did some work for strings, blocks & menu in my fork: https://github.com/das-peter/i18n
Comment #11
mgiffordOk, 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?
Comment #12
das-peter commented@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".
Comment #13
steinmb commentedRenaming title, enable us to tell what project this is related to in views that only displays the issue title.
Comment #14
SilviaT commentedMaybe this is a dumb question but why the development for D7 moved to Github?
Comment #15
juves commented[deleted]
Comment #16
jose reyero commentedWell, 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.
Comment #17
mgiffordThanks Jose! This is great.
Comment #18
jose reyero commentedThe bulk of the upgrade is done, we need now testing and polishing, upgrade scripts, unit tests, etc.
Development is back on Drupal git btw.