By ssb-1 on

Hi folks,

I'm planning a multilanguage corporate brochure + blog website (Drupal 6) for one of my clients. Website frontend will be available in eight languages though backend only in English. The reason for that desision is to avoid the trouble of translating the whole Drupal 6.0 in all eight languages. Besides that, only a single person will have access to backend.
BTW the website will not make use of blog module, just pages, stories, search and contact;

Is there any list of the strings used in frontend of Drupal 6.0 or other resource that will help me to accomplish such a task?

Any other ideas are welcomed.

Regards.

⋅ Categories: Drupal 6.x

Comments

davemybes’s picture

davemybes commented

At the moment, you can have multiple languages in Drupal6 (beta2) and it all seems to work nicely (good job Gabor). However, if you want to have a page with English only content, then click a button to see the same content in French, it won't do it for you. You need to have a third party module to help with this - i18n , localizer or even Views - none of which are ready for Drupal6 yet.

There is a language switcher block, but it only translates the interface, and doesn't switch content from one language to another. Each node has a language link below it that will switch between languages.

If you can wait for Drupal 6 to be officially released (and for the other modules too), do so, otherwise, you'll have to use Drupal 5.3 + i18n/localizer.
______________________________________________________________________________________________________
mybesinformatik.com - Drupal website development

______________________________________________________________________________________________________

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Unfortunately (for your use case), if "Save" appears on the frontend and on the backend, it will be translated on the frontend and on the backend just as well. So you might be able to have a list of strings which appear on the frontend, but that would quite a bit overlap with the strings displayed on the backend. The definition of the frontend and backend also differs from site to site. On a brochure site for example, the content creation forms are backend, on a community site, they are frontend.

ssb-1’s picture

ssb-1 commented

Thanksfully the specific brochure website will be used by anonymous users only and administrated by a closed team. So, I think it's easier to set English as the prefered language for admins and translate only those strings that will be displayed on public pages. This way, logged-in users (admins) will always use English and visitors will be able to choose user interface language from a list.

Thank you both for the answers!