On Tue, 9 Sep 2008 06:48:49 -0700
"Gershon Joseph (gerjosep)" <> wrote:
> Here is the issue:
>
> Some elements, particularly <note>, are not translated to all target
> languages. Many notes (e.g. warning statements required to meet a
> specific country or region's legal requirements) apply only to a
> specific set of target languages.
>
> At present, DITA supports an on/off switch via @translate.
>
> I would like us to propose a solution for the case where authors need to
> specify a set of target languages. I feel this would be best achieved
> either by extending the definition of @translation to have the values
> "yes | no | group" (I'm sure we can find a better word than "group") and
> add another attribute that lists the target languages, or leave
> @translate alone and simply add a new attribute that lists the target
> languages (in which case, if the attribute is not set the default is to
> translate to all target languages). I'd anticipate a space-separated
> list of language/locale values, such as "it_IT fr_FR fr_CA".
Hi Gershon,
I would leave the "translate" attribute as is (yes | no) and extend
the audiences filter mechanism instead.
Regards,
Rodolfo
--
Rodolfo M. Raya <>
http://www.maxprograms.com
