[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Fwd: [dita-comment] Interaction of "processing" and "translation" attribute
As a rule, translation agencies prefer that variable text that is essentially static (units of measurement, product names, corporate names, and such). Terms that will have to be parsed for different languages will be problematic or, in some cases, impossible to translate without flattening any variable text (say, for example, when a single term is used in different syntactic roles—nominative, accusative, etc.).
That said, some companies might have business rules to address such considerations, so it’s perhaps overkill to *never* allow resources to be translated.
Content Architect | Healthwise
208.331.6917 (office) | 208.345.1897 (fax)
Healthwise helps people make better health decisions.
For discussion on Tuesday, 20 June.
I think the tools vendor is making an incorrect assumption that resource-only items (for example, items referenced by <keydef> elements) should not be translated.
Others? And will our decision here trigger a need for an item in errata 02?
Dear DITA TC,
Could you please clarify?
Thank you and best regards,
-- This publicly archived list offers a means to provide input to the OASIS Darwin Information Typing Architecture (DITA) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: email@example.com Unsubscribe: firstname.lastname@example.org List help: email@example.com List archive: http://lists.oasis-open.org/archives/dita-comment/ Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita Join OASIS: http://www.oasis-open.org/join/
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php