[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Antwort: Re: [dita-comment] Interaction of "processing" and "translation" attribute
i.A. Stefan Eike
Technischer Redakteur
- Schulung -
DAKOSY Datenkommunikationssystem AG
Mattentwiete 2, 20457 Hamburg
http://www.dakosy.de
Phone | + 49 40 370 03 - 507 |
Fax | + 49 40 370 03 - 370 |
mailto:eike@dakosy.de |
-----------------------------------------------------------------
Sitz der Gesellschaft: Hamburg, HRB 78314
Aufsichtsrat: Dr. Johann Killinger (Vors.)
Vorstand: Dieter Spark, Ulrich Wrage
-----------------------------------------------------------------
Von:
Kristen James Eberlein
<kris@eberleinconsulting.com>
An:
dita-comment@lists.oasis-open.org
Datum:
20.06.2017 20:56
Betreff:
Re: [dita-comment]
Interaction of "processing" and "translation" attribute
The DITA TC discussed your e-mail today. The TC was unanimous in agreeing that the DITA tool vendor was interpreting the DITA specification incorrectly.
Resources referenced by <keydef> elements most certainly MUST be translated. This includes the content of topics, or text contained within a <topicmeta> element.
The defaulted presence of processing-role="resource-only" on a <keydef> element only indicates that the topic referenced should not be part of the navigational structure.
Unless elements have translate="no" specified, the content is intended to be translated.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
On 6/1/2017 9:40 AM, Stefan Eike wrote:
Dear DITA TC,
I'm unsure about the interaction of the "processing" and the
"translation" attributes. I had a discussion with one of our
DITA tool vendors, and we interprete the specification differently.
Consider a <keydef>:
<keydef keys="foo" href="">
We have many <keydef> elements like this in our docs. We use <keydef>
elements to point to "database topics". These topics should not
be rendered in the output, but these database topics contain reusable textual
elements (like <ph> or <dlentry>), that are conkeyrefed into
rendered topics. A <keydef> element implicitely sets processing-role="resource-only".
So for us, topics referenced with <keydef> should be translated,
because they might contain text.
Our DITA tool vendor says, a <keydef> is resource-only and resource-only
"things" should not be translated. I assumed, that the "resource-only"
would not affect translations. I could not find a statement in the specs
that determines that. I expected, that, by default, a <keydef> should
be processed like any other element, so it should be "translated",
unless translate="no" is set.
So I expected, that, if I'd like to avoid the translation of a <keydef>
referenced topic, I would explicitely need to write:
<keydef keys="foo" href="" translate="no"/>
Could you please clarify?
Thank you and best regards,
Stefan Eike
-- 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:
dita-comment-subscribe@lists.oasis-open.org
Unsubscribe: dita-comment-unsubscribe@lists.oasis-open.org
List help: dita-comment-help@lists.oasis-open.org
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/
-- 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:
dita-comment-subscribe@lists.oasis-open.org Unsubscribe: dita-comment-unsubscribe@lists.oasis-open.org
List help: dita-comment-help@lists.oasis-open.org 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/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]