All markup content that shows up in the output must be subject to the same translations policies regardless of its source. Otherwise, you have a publishing environment that is only suitable for rendering the source language. If the vendor wants to market such a tool then their interpretation would make sense.
Best Regards,
Bob Thomas
On Sat, Jun 17, 2017 at 7:21 AM, Kristen James Eberlein <> wrote:
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?
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
-------- Forwarded Message --------
Subject:
[dita-comment] Interaction of "processing" and
"translation" attribute
Date:
Thu, 1 Jun 2017 15:40:03 +0200 (CEST)
From:
Stefan Eike <>
To:
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:
Unsubscribe:
List help:
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
--
Bob Thomas
+1 720 201 8260
Skype: bob.thomas.colorado
Instant messaging: Gmail chat () or Skype
Time zone: Mountain (GMT-7)
