Drupal for multiple languages, part two: content types configuration

In the first article of this series, we configured Drupal core. Now we have to configure all the content types.

This site has four different content types: page, project, partner (this is for internal use) and article. Those articles are the blog posts. I am not using the blog module here, a blog is just a bunch of articles sorted by date, you don't need the blog module for that.

Anyway, Let's focus on our subject: configuring the content types to work in multiple languages.

Configuring pages

Go to Administer > Content Management > Content types > Pages > Edit. Go to the bottom of the page. You'll find a section named "multilanguage options", configure it like in the screenshot:

The options on this content type are very permissive. Require language means that any node of this type we create must have a language selected, so this node exists in just one language. Not being required means that a node can be language neutral, which means that this node exists as is in all languages. You don't usually want this, but in this particular case I needed the possibility of creating language neutral pages.

Creating the content

Now that our content type is configured, we can create new content. When you create a new node, you can see something new in the form:

That's where you select the language for the content you're just creating.

But there is one thing left. We should have a way to tell Drupal something like: "this node is the translation to Spanish of this other node in English". How do we do that?

Creating the translations

Besides the "view" and "edit tabs, thre's now a third one: Translate. This is where we create translations for our nodes, or assign other nodes as translations of the one we're looking at.

See? there you can add a translation or assign a node as translation or another node.

Easy for us, but some people would find this a bit complicated. For some people, it's easy to create just one node, with fields for different languages, like "title (english)", "title (spanish)" and so on.

In the third article of this series, I'll show you how to reuse one node's content to create all language versions at the same time.

Comments
Lauris (not verified) on Tue, 06/01/2010 - 19:26

I can't find the creating the translations part. with the screenshot above. How can i reach this? please help me(A)

nachenko on Tue, 06/01/2010 - 21:14

To view the translations area as seen in the screenshot, the module must me properly installed and configured. You must also activate other helper modules that come with i18n: Content type translation, CCK Translation, Translation Overview, Synchronize translations. Check the part one of this article series to be sure the module is properly configured, then check the configuration of the content type you want to translate.

See first screenshot on this article.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <pre> <code> <ul> <ol> <li> <dl> <dt> <dd> <p> <img> <h2> <h3> <blockquote>
  • Lines and paragraphs break automatically.