Generate 2 DCR from one form

MMar_Ojuel

Hi all,

We're developping a bilingual application. We need to store the content in every language in different rows in a database, being the primary key of the table the code of the content and the language. We are not sure about the way to make it: we're thinking about create a single DCT with the fields for every language, and after saving it create 2 separate DCR, one for each language, and after submitting store them in the DB.
Is this possible? If so, where can we find documentation about how to perform it?

Thank you in advance,

Adam Stoller

Hi all, We're developping a bilingual application. We need to store the content in every language in different rows in a database, being the primary key of the table the code of the content and the language. We are not sure about the way to make it: we're thinking about create a single DCT with the fields for every language, and after saving it create 2 separate DCR, one for each language, and after submitting store them in the DB. Is this possible? If so, where can we find documentation about how to perform it? Thank you in advance,

A single populated DCT creates a single populated DCR - there is no provision (as far as I know) to take a single populated DCT and have it produce multiple DCRs (and if you can figure out a hack to do so, you're probably going to have a maintenance nightmare down the road)

IMO - it is generally better to have a DCT that defines a single set of fields (one language) with distinct DCRs for each language, and use a well thought-out directory structure to support it. E.g.: within a given branch (workarea, staging, edition):

/content/xx_YY/some/dir/some/file.html
/templatedata/category/data-type/data/some/dir/some/file.xml

Where xx_YY is a language_LOCALE specification (e.g.: en_US, es_US, es_ES, en_UK, etc.) where (in most cases that I've dealt with) the DCRs are originated in English (en_US) and then sent to some translation service provider - when they are returned from the translator, the results are stored in one of the other language_LOCALE directories (based on what they were translated into).
The consistency of directory structure and file naming greatly facilitates programmatic automation.

Beyond that - it's up to you to determine how your organization works and how to best meet their needs.

If content originates in different languages - it becomes a bit trickier, but can still be done.

Putting all the language variations into a single DCT/DCR is, IMO, a mistake - if for no other reason than scalability (consider having to constantly extend the number of fields within the DCT to support more and more languages / locales)