The full package has a lot of modules. Some of them will be trimmed down as some features are already in Drupal core, some need to be fully reworked, and some may be dropped. I'm reorganizing the whole package. This is a rough plan or what I'm doing with them:
main/
- i18n: trim down and upgrade (move menu part into i18nmenu)
- translation: remove (node part already in core, move taxonomy part into i18ntaxonomy)
- i18nprofile: upgrade
- i18nblocks: upgrade, may be merged into the main i18n module
- i18nviews: upgrade, waiting for views upgrade
contrib/
- i18nmenu: upgrade and expand
- i18ntaxonomy: upgrade and expand
experimental/
- i18nstrings: full rework to use new core features
- i18ncontent: upgrade and merge with some other module
- i18nsync: upgrade, parts of it waiting for cck upgrade
- ttext: remove, translatable cck fields may be in the next cck version
And this will be the new layout (Adding modules and features as I'm upgrading them)
i18n
- Multilingual variables
- Extended language API
i18ntaxonomy
- Multilingual vocabularies
- Term localization
i18nblocks
- Language field for custom blocks
- Translatable block content and title
i18nstrings
- Now uses locale textgroups for different types of strings
- Some more advanced object oriented translation features coming
This is a work in progress, but there are some modules already upgraded that can be tried.
Comments
Comment #1
wahlau commentedi have Drupal 6 Beta 2 installed, and somehow head does not talk well with D6 beta 2. what should i do next? thanks.
Comment #2
Freso commented1) Subscribing
2) Not sure whether to file new bugs in relation to this on their own or here. But (for|right) now I post it here: After enabling i18n, content is shown only under current locale (ie. entries in Danish are shown only when locale is da and English entries are shown only when locale is en). This sounds like it works as it should, eh? Well, guess again. This doesn't just affect node[/*], pages such as admin/content/node and $node/translate are affected as well, which for one means that you can't see the nodes the current node is a translation of (or which nodes are translations of the current one).
Comment #3
murzI think this bug is a consequence of wrong working function i18n_db_rewrite_where(), which can't get right mode for selecting nodes and work with "simple" mode.
Because Drupal 6 beta 4 have all multilanguage functionality for my needs (and some functionality, that have dublicated i18n), but i18n module have a lot of ugly functionality for me, I decided to do a separated module lfilter.
But this module have many functions from cvs i18n module (i replace prefix from "i18n_" to "lfilter_") with some small changes. I think you can get it as example when writing a patch to i18n.
Discuss about module lfilter you can here.
Comment #4
Marc Bijl commentedJust subscribing ;)
Comment #5
jose reyero commentedDev release for Drupal 6 already available: 6.x-1.x-dev
Testers and feedback are really welcomed.
Note:
- A big part of the package has been completely reworked.
- Upgrade scripts need some love yet, please help testing them.
Comment #6
mohammed76hi.
first subscribing,
second, renamed the issue to help us identify it when out of context.
Comment #7
jose reyero commentedUpdating version
Comment #8
progfrog commentedInstalled Drupal 6.1
i18n-6.x-1.x-dev.tar.gz
views-6.x-2.0-alpha3.tar.gz
during creation of view, when a select Preview this error message is show
user warning: Unknown column 'node.language' in 'where clause' query: SELECT COUNT(*) FROM (SELECT node.nid AS nid, node_revisions.body AS node_revisions_body, node_revisions.format AS node_revisions_format, node.created AS node_created, node.status AS node_status, node_revisions.teaser AS node_revisions_teaser, node.title AS node_title, node.type AS node_type FROM node node LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid WHERE ((node.type in ('story'))) ) count_alias WHERE (node.language ='de' OR node.language ='' OR node.language IS NULL) in /var/www/drupal6/trunk/sites/all/modules/views/includes/view.inc on line 510.
I don't know if is due views module, or i18nviews
seems like inner query doesn't pick node.language
i will post this to views issues also
Comment #9
seanrSame here. It's not i18nviews, because Drupal 6 won't even allow me to install that (says its incompatible because the .info file hasn't been updated). What's the status of i18nviews?
Comment #10
seanrPosted a separate issue for that last item here: http://drupal.org/node/234945
Comment #11
jose reyero commentedAbout i18nviews, for now I'll be taking care only of these more critical compatibility issues, like that one, but not updating the module while views code is still 'moving' it will have to wait till there's at least a views-6-beta1 out there.
However, if someone wants to work on this before, patches for i18nviews will be welcomed and committed right away, the module is not working anyway, so... :-)
Comment #12
drewish commentedI'm running into an issue with the rewriting on some custom module's queries. When viewing a node with the language specifically set I get:
but when the node's language is set to neutral I get:
which won't find other English stories.
It seems like the problem is in
i18n_db_rewrite_where()when it callsi18n_selection_mode('params')but I'm not sure how to correct it.Comment #13
hongbo commentedchange
i18n_selection_mode('params')toi18n_get_lang()can fix the problem.See http://drupal.org/node/237401
Comment #14
ogi commentedsubscribe
Comment #15
designerbrent commentedSubscribing
Comment #16
jose reyero commentedI've been fixing some more issues today and it seems there are no more critical bugs so far, just a few minor ones, so I think we should be approaching a beta version.
In the meanwhile, besides all these bugs and support requests -which are useful- I'd like to hear also some good news of people having tested this version of the module and/or the upgrade scripts and being fine with them, if there are any (?)
As a side note, there's some i18n configuration data that is lost when upgrading to Drupal 6, like the menu items language that is gone when the Drupal core upgrade scripts drop that table so there's no chance to recover it later or the old switcher blocks that are not supported anymore (simply because we don't need them anymore)
Thus, after upgrading, you may need some manual reconfiguration. For now I'll just add it to the documentation.
Thanks for the feedback.
Comment #17
avangelist commentedSubscribe
Comment #18
gustavlarson commentedsubscribe
Comment #19
philipshu commentedI installed i18n and enabled all modules that came with it,
I translated my permanent links (menu) into English from Chinese by using translate interface,
when I use "language switcher" block the interface's language changes, but not the menu
I see people refers to the "translation" block
I don't see that in my block selection
Any ideas?
Comment #20
chipway commentedHi philipshu,
I had a D6 i18n dev working pretty well. But with the last updates Arpil 02 or MArch 25, I can no more use the alternate language.
Language switcher does nothing, and I have no more Language Translation bloc.
Anyy idea ??
Thank you.
Comment #21
chipway commentedSorry.
I put "Domain name only" as Language negotiation in Language configuration (now it woks with "Path prefix with language fallback").
May you did some thing like that ?
Comment #22
jose reyero commentedI've just fixed menu permissions for the latest core upgrade (Drupal 6.2).
The rest should work fine.
Comment #23
jose reyero commentedThis is mostly done, so just stay posted to module releases.