Clean install of 6.1
enable Greek language
enable translation for stories
translate one menu ITEM to Greek (just to be sure when I am in Greek section)
enable the language selection block
write a story in English
translate story in Greek
visit frontpage (both stories appear)
Change selection of language to Greek from the language block (el/node)
but all stories are still shown (1 Greek and 1 English)

Is that the normal behaviour ?

according to this handbook page
http://drupal.org/handbook/modules/translation
(last paragraph)

Use the language switcher block provided by locale module to allow users to select a language. If available, both the site interface and site content are presented in the language selected.

language selection block should do content filtering by language

The issue seems similar to
http://drupal.org/node/72884 (this is from 2006)

Comments

chx’s picture

chx commented
Status: Active » Closed (won't fix)

translate one menu ITEM to Greek <= this is not supported. Menu is not i18n'able with core only.

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented

Sorry But I don't understand what you are saying !!

My point was not whether the menu was translatable (which it was) but whether the content should obey the language selection (from the block)

jpewert’s picture

jpewert commented

So how do you internationalize menus in Drupal 6? Is there a module or do you have to set up different menus? If so, how do I tell Drupal which menu to display depending on the current language?

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented

chx and jpewert

The drupal 6 menus are apparently translatable using JUST CORE
here is what I did step by step

1. clean install of 6.1

2. Enable Locale and Content Translation

3. admin/settings/language/ad > Greek (It will work for Any Language)

4. admin/settings/language/configure Path Prefix Only

5. admin/build/block Enable Language Switcher

6.
admin/content/node-type/story
WorkFlow settings
Multilingual support
Enabled with translation

7.
node/add/story Create a story in English
And translate that story to Greek
node/1/translate

8.
Visit Front page
(Both English and Greek Stories visible)

From the language block choose Greek
(Both English and Greek Stories visible)

9.
admin/build/translate/search > search for Administer
Translate the string
(One string is enough to know which language the system is displaying)

10.
step 4. again
Path prefix with language fallback

11.
step 8. again
(Both English and Greek Stories visible,
menu translation for "Administer" displays correctly)

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented
Category: bug » feature
Status: Closed (won't fix) » Active

Just figured it out

You do need
http://drupal.org/project/i18n
to be able to display only the language selected (from the language selection block)

(admin/settings/i18n > content selection mode: only current language)

Still it seems to me like a feature that should be in core !!!

Menus and content can be translated and language can be chosen
but content can't be chosen ??

It would be nice to be in core.

ar-jan’s picture

ar-jan commented
Title: Language selection does not filter Language content ?? » Language selection does not filter Language content

I have exactly the same problem. Basically I did the same thing on a fresh Drupa 6.1 install, except I am using "Domain names only" as the criterium for selecting the language: mysite.org for English, and mysite.nl for Dutch. But content which is available in both languages appears also in both languages instead of in the selected language.

Giorgos, did you install i18n module? It seems to be in development stage for Drupal 6.1, did it work for you already?

I agree that this should be core functionality, isn't that just what the Locale & Content Translation Modules are meant to do?

I'm a first time user of Drupal so please comment, thanks.

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented

ngochakana,

as I commented on #5
i18n does what is Needed (even though it should be in core)

being in dev state I don't consider a problem as long as it does what you want
(it only means that it was not tested thoroughly)
and its a simple thing that you want from i18n module.

Check in for any new releases and update it when they are out
in your installation you can enable "update status"
and check in "admin/reports/updates" for any updates

ar-jan’s picture

ar-jan commented

OK, thanks. I've installed the i18n Module as well, however I'm still experiencing some problems. I've posted the description of my problems here.
P.S. Yes, I changed my name :)

strellman’s picture

strellman commented
Title: Language selection does not filter Language content » Language selection requires i18n
Version: 6.1 » 6.2
Category: feature » support

Thanks for your comment!

You do need http://drupal.org/project/i18n
to be able to display only the language selected (from the language selection block)

It seems the documentation indicates i18n is just for d5 in some places, ie. Internationalization (i18n): Building multilingual sites http://drupal.org/node/133977

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented
Version: 6.2 » 7.x-dev
Category: support » feature

Sorry
But why was this changed to a support request ?

I am proposing this as a feature that is implemented elsewhere
And I strongly feel it should be in Core

I find it counterintuitive to have to install a module just
to use a simple feature (selecting content of just one language)
since Drupal already Supports multiple languages content

Why don't we let a developer decide if they are actually going to move
the functionality from i18n to core ??

If they say no I will be OK with it.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (duplicate)

I think we better follow up here #197051: Content selection modes by language for multilaguage sites