Hi,

does anybody know if it's safe to use the 4.6 i18n module with the 4.7 Beata 2? If not is there a 4.7 version of i18n yet? I couldn't find one anywhere.

Thx, Felix

Comments

kiev1.org’s picture

In CVS i18n lays for 4.7 but it is not ended
I can not find in it the button "create translation "
help

kiev1.org’s picture

the working module of i18n is finally got for Drupal-4.7

http://drupal.htdogs.ru/files/i18n.zip

( http://drupal.htdogs.ru/node/263 )

for the use it is necessary to enable multilingual support in necessary content-type:
admin->settings->content_types
(my_site/admin/settings/content-types/story)

mandclu’s picture

Thanks so much for posting this, since I'm not able to access CVS at the moment (some kind of Python error). The files you posted, however, don't seem to include a patches folder, and while I was able to activate the module, I haven't yet seen the option to add translations for any content.

Any thoughts?

profix898’s picture

I CAN access cvs, but even there the patches folder is empty!
So where are the patches? Are they no longer needed?
Any hope for an 'official' 4.7 release of the module with README and
INSTALL updated? I think they are not synced with the code at the
moment, right?
How can we create multi-language content with your modified
version of the module? There is no 'create translation' link like it
was in 4.6!

kiev1.org’s picture

> So where are the patches? Are they no longer needed?

It is not needed for 4.7 patches

what to add translation - it is necessary to enable multilingual support in necessary content-type:
admin->settings->content_types
(for a node translation is work, for other did not try)

it is necessary to check up the module from CVS - fully possibly that he is already ready for Drupal 4.7 ...

David Lesieur’s picture

I did some tests, and only part of the i18n module works with 4.7 (HEAD).

Language selection works, translating variables works, but translating content (nodes or terms) does not. Porting to the new Forms API is not finished (among other things).

jose reyero’s picture

I know there are some people waiting for i18n module for 4.7 but,

there are still some bugs and issues in Drupal core, that I'll have to wait for to produce an usable version of i18n

So the news is: there wont be i18n 4.7 before Drupal 4.7

And for now, I think the best way to invest our time is to help fixing bugs in Drupal core -which is what I'm doing at the moment.

Cheers!

3B’s picture

Jose ... i'm starving waiting 4.7 and sequent i18n ... :-(((
:-)

i'm actually running www.lc8.org ... a 2 years old i18n website ... i'm waiting new version of i18n

i do agree with you about precedence in spending time on drupal core ... but ... i need to launch the new version that is only waiting i18n 4.7 ... so ... :-|

many thanks for you efforts!

Marc Bijl’s picture

- http://drupal.org/node/37855#comment-96486

It's about the CVS version. As the comment above says, it should work with 4.7, although bugs might still be possible. So testers are wanted and comments will be very much appreciated...

Latest info can be found here:
- http://drupal.org/cvs?file=/modules/i18n/i18n.module

CVS downloads can be found here:
- http://cvs.drupal.org/viewcvs/drupal/contributions/modules/i18n

___________________
discover new oceans
lose sight of the shore

rondev’s picture

I should launch a new multi language site within one month. What drupal release should I use. 4.6 now and I will have to spend long times to upgrade. Or 4.7 and it will possible to use the i18n soon. That is my dilemna.
Thanx,
Ronan

Marc Bijl’s picture

- http://drupal.org/node/42957#comment-118390

I would say: try drupal 4.7 with i18n CVS and help Jose as much as you can by testing reporting the few minor bugs that possibly might appear. Besides, this will make a later upgrade unnecessary (:

Just my $0.02 ...

___________________
discover new oceans
lose sight of the shore

3B’s picture

absolutely ... i'm running drupal 4.7.0 with cvs version of i18n+translations ... and it works really great (except an ancient and know problem with taxo translations)

just my 0.02 € :-)

Marc Bijl’s picture

Hi Alberto,

Sounds cool mate! However, I've got a question then: do you use primary links/menus, and, if yes, did you get them working? I don't mean: did you get them translated, but did you get them pointing to the right nodes (in the right languages)? As you can read in this post, and all that I wrote in the same topic later, I'm still struggling with that part of i18n :\

Would love to see how others managed to get this thing done :)

Cheers,
Marc

___________________
discover new oceans
lose sight of the shore

3B’s picture

hi Marc,
actually i've not implemented a menu because i did not decided how to run it ... the solution, if i'm correct is to create urls WITHOUT language prefixes ... e.g. same url for all (unique menu item) ... drupal/i18n will recognize user prefferred languange and drove the user to the correct language version ...

example of "un-languaged" menu link: ?q=node/40 and not ?q=it/node/40 or ?q=en/node/40 or as i18n like ... so on for each language

hope to be clear enough
let me know

P.S. i've put a look at your site ... very nice layout indee! my best compliments!

Marc Bijl’s picture

Had some e-mail contact with Jose and now I've got them running; neat stuff!

Will try and post an explanation later today at:
- http://drupal.org/node/63691

___________________
discover new oceans
lose sight of the shore