Hi Gabor et. al,
I'm starting to play with the D6 beta 3 and I'm loving it. Hopefully I'll be able to contribute something, even if only use cases and a some patch review.
I am having trouble with a locale/internationalization issue. Is this a good place to post?
Having installed D6 beta 3, I ...
a) created a story node with some text in english,
b) enabled the locale and translation modules
c) enabled imported the D5 french localization of the site (which got the vast majority of interface strings),
d) did my own special ;-) version of a french version of my story node
e) went into my user 1 profile and switched my preferred language to French.
The problem (interesting feature?) is that now when I view the site, it's mostly in English even though French is specified as my user's language. However, whenever i view an 'edit' tab for the story node, the -interface- (including navigation menu) is translated into French. That's cool, but then I go back to the 'view' tab and i get the English translation again.
Have I done something wrong? Is this a caching issue?
regards!
p.s. the q=node summary page shows both versions of the story. i love the 'each translation as node' model along with the tnid column in the node table. i can see how this is going to work well with other modules.
Comments
oh oh!
Should the q=node summary page now just list content in a single language, but have a selector to pick from those languages with published content in them? And could this be a "patch newbie" patch that I could do?
http://www.sticksallison.com
http://www.sticksallison.com
listings are not filtered
Depending on your requirements, listings might require language based filtering or not. Eg. on a multilanguage blog, even though you have languages and a language switcher block, you'd like to list all entries (although those are not translations obviously). We found that some sites would like to switch the interface and content language independently. So while single node pages are switched language with the language switcher block, node listings are not. To have it work based on your own requirments, use i18n or localizer module (you would need menu, taxonomy, site settings, user profile fields, etc. translation anyway, which is not part of Drupal 6 core). Or alternatively, you can use views for listings. Now that Drupal 6 has the core concept of node languages, views will support filtering on them.
Saving language field for node working?
What i need is that, when you are in a given language interface (that's working moreless fine as fas as I know), when you create new content, the field "language" for this node should be set to the current language, but is set always to the default language (english).
Is it working ok?
What I need is simple, if you have the interface in a given language, let's say spanish, when you create a new node this field (language) in the node table should be set to spanish aswell.
How can I get to it?
Thanks
submit a bug report
This is a reasonable and simple "bug" report, if you submit to the issue queue: http://drupal.org/node/add/project_issue/drupal/bug We actually did not thought of this simple way to help users, and set the default language selection to empty on new nodes on purpose. What you suggest however could be a very simple usability enhancement, and I can fix this for you after you submit a bug report :)