search

IMAmuseum / tap-cms

Authoring tools for the TAP mobile application software platform, built on top of Drupal. Learn more about the project at TAPintoMuseums.org.
https://github.com/IMAmuseum/tap-cms/wiki
GNU General Public License v3.0
24 stars 8 forks source link

Investigate & Implement Multi-lingual support #5

Open kjaebker opened 12 years ago

kjaebker commented 12 years ago

Determine how we can handle exporting multi-lingual data into TourML.

billbostick commented 12 years ago

Some of my notes regarding multi-lingual support that I'd like to discuss in the next huddle...

Traditionally, multi-lingual content support in Drupal has been achieved via a scheme whereby multiple nodes were created, one in each of the installed languages, that were then loosely affiliated as a 'content set' that was understood to represent different language versions of the same content. This is the method employed by the i18n project: http://drupal.org/project/i18n.

With the introduction of field-able entities in D7, a significant effort is underway to support multi-lingual content as a single node. D7 has core support for this feature, but no user interface with which to manage entity translations. This functionality is currently provided via the Entity Translation module: http://drupal.org/project/entity_translation. Because node titles are not yet entities, node title translation also requires the Title module: http://drupal.org/project/title.

The following articles summarize the pros and cons of each approach:

We'll need to determine which of these methods to use. My inclination is to go with the D7 approach of assigning languages per field. Seeking feedback.

kjaebker commented 12 years ago

After reading through many of those posts I think you are right, the D7 approach of translatable fields sounds like the way to go.

One thing we thought of to get around the title translation limitation was to add an additional field for title and rename the current title field to Administrative Title. That way the title could be customized for the Tour and the drupal title could be used for administering the tour data.

hannolans commented 11 years ago

This seems already fixed with entity translation in the newest release