Non-normative information : Element-by-element recommendations for translators
WebWorks  
Element-by-element recommendations for translators
(Non-normative) This topic contains a list of all OASIS DITA elements. It includes recommendations on how to present the element type to translators, whether the element contents are likely to be suitable for translation, and whether the element has attributes whose values are likely to be suitable for translation. Examples of content that is not suitable for translation include code fragments and mailing addresses.
Since the distinction between block and inline elements is ultimately controlled by the container of the element and the processing associated with it, the same element may be a block in one context and an inline element in another. Specializing document types may vary this behavior according to the needs of the document type being created, and the distinctions given below are provided only as a guide to known behavior with the base DITA document types.
Notes on the tables below
• For specializations, the second column gives the ancestor element, and the third column gives a quick yes/no guide to indicate whether all behavior is inherited. If something is not inherited, the change will appear in bold.
• For any specialization not listed below, the suggested default is to fall back to the closest listed ancestor.
• The block/inline presentation column indicates whether the element is formatted as a single block.
• The block/inline translation column indicates whether the element represents a complete translatable segment. For example, the element <cmd> is presented inline with other elements, but represents a complete translation segment.
• Items marked as block*** are blocks on their own, but may appear in the middle of a segment. They should not break the flow of the current segment. These are considered "subflow" elements for translation. We recommend that, when possible, these elements should only be placed at sentence boundaries to aid in translation.
• For all elements, the translate attribute will override the suggested default translation setting. So, a translation setting of "yes" or "no" in the table below does not guarantee that an element will always, or never, be translated.
• If an element has translatable attributes, they are listed in the last column. Note that the spectitle and specentry attributes are described with a footnote.
• The keyword element (as well as specializations of keyword) is an inline, phrase-like element when it appears in the body of a document. It may also appear in the keywords element in topicmeta (for maps) or in the prolog (for topic). When it appears in the <keywords> element, each keyword represents an individual segment, and is not part of a larger segment; in that location, keyword can be considered a "subflow" element.
topic elements
Element name
Specialized from
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
abstract
N/A
block
block
yes
alt 1
N/A
block***2
block
yes
audience
N/A
block (metadata)
block
yes
author
N/A
block (metadata)
block
yes
body
N/A
block
block
yes
bodydiv (new in DITA 1.2)
N/A
block
block
yes
boolean
N/A
inline
inline
n/a
brand
N/A
block (metadata)
block
yes
category
N/A
block (metadata)
block
yes
cite
N/A
inline
inline
yes
colspec
N/A
n/a
n/a
n/a
component
N/A
block (metadata)
block
yes
copyrholder
N/A
block (metadata)
block
yes
copyright
N/A
block (metadata)
block
yes
copyryear
N/A
block (metadata)
block
yes
created
N/A
block (metadata)
block
yes
critdates
N/A
block (metadata)
block
yes
data
N/A
N/A (metadata)
block
no (likely to change for some specializations)
data-about
N/A
N/A (metadata)
block
no
dd
N/A
block
block
yes
ddhd
N/A
block
block
yes
desc
N/A
block
block
yes
dl
N/A
block
block
yes
@spectitle3
dlentry
N/A
block
block
yes
dlhead
N/A
block
block
yes
draft-comment
N/A
block***4
block
no
dt
N/A
block
block
yes
dthd
N/A
block
block
yes
entry
N/A
block
block
yes
example
N/A
block
block
yes
@spectitle5
featnum
N/A
block (metadata)
block
yes
fig
N/A
block
block
yes
@spectitle6
figgroup
N/A
block
block
yes
fn
N/A
block***7
block
yes
foreign 8
N/A
block9
block10
no11
image
N/A
block when @placement= break, otherwise inline
block when @placement= break, otherwise inline
yes
@alt12
index-base
N/A
block***13
block
yes
index-sort-as (new in DITA 1.2)
N/A
block***xref
block
yes
indexterm
N/A
block***14
block
yes
indextermref
N/A
inline
n/a
n/a
itemgroup
N/A
inline
inline
yes
keyword
N/A
inline
inline (except when within <keywords> – see note above the table)
yes
keywords
N/A
block
block
yes
li
N/A
block
block
yes
lines
N/A
block
block
yes
@spectitle15
link
N/A
block
block
yes
linkinfo
N/A
block
block
yes
linklist
N/A
block
block
yes
@spectitle16
linkpool
N/A
block
block
yes
linktext
N/A
block
block
yes
lq
N/A
block
block
yes
@reftitle
metadata
N/A
block (metadata)
block
yes
navtitle
N/A
block
block
yes
no-topic-nesting
N/A
n/a
n/a
n/a
note
N/A
block
block
yes
@othertype, @spectitle17
object
N/A
block
block
yes
@standby
ol
N/A
block
block
yes
@spectitle18
othermeta
N/A
block (metadata)
block
yes
@content
p
N/A
block
block
yes
param
N/A
block
block
n/a
permissions
N/A
block (metadata)
block
yes
ph
N/A
inline
inline
yes
platform
N/A
block (metadata)
block
yes
pre
N/A
block
block
yes
@spectitle19
prodinfo
N/A
block (metadata)
block
yes
prodname
N/A
block (metadata)
block
yes
prognum
N/A
block (metadata)
block
yes
prolog
N/A
block (metadata)
block
yes
publisher
N/A
block (metadata)
block
yes
q
N/A
inline
inline
yes
related-links
N/A
block
block
yes
required-cleanup
N/A
block***20
block
no
resourceid
N/A
block (metadata)
block
yes
revised
N/A
block (metadata)
block
yes
row
N/A
block
block
yes
searchtitle
N/A
block
block
yes
section
N/A
block
block
yes
@spectitle21
sectiondiv (new in DITA 1.2)
N/A
block
block
yes
series
N/A
block (metadata)
block
yes
shortdesc
N/A
block
block
yes
simpletable
N/A
block
block
yes
@spectitle22
sl
N/A
block
block
yes
@spectitle23
sli
N/A
block
block
yes
source
N/A
block (metadata)
block
yes
state
N/A
inline
inline
yes
@value
stentry
N/A
block
block
yes
@specentry24
sthead
N/A
block
block
yes
strow
N/A
block
block
yes
table
N/A
block
block
yes
tbody
N/A
block
block
yes
term
N/A
inline
inline
yes
text (new in DITA 1.2)
N/A
inline
inline
yes
tgroup
N/A
block
block
yes
thead
N/A
block
block
yes
title
N/A
block
block
yes
titlealts
N/A
block
block
yes
tm
N/A
inline
inline
yes
topic
N/A
block
block
yes
ul
N/A
block
block
yes
@spectitle25
unknown (new in DITA 1.1)
N/A
block
block
no
vrm
N/A
block (metadata)
block
yes
vrmlist
N/A
block (metadata)
block
yes
xref
N/A
inline
inline
yes
1 The use of the alt attribute is deprecated in favor of the alt element.

2 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

3 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

4 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

5 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

6 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

7 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

8 The block vs. inline designation for the foreign element is likely to change for some specializations.

9 The block vs. inline designation for the foreign element is likely to change for some specializations.

10 The block vs. inline designation for the foreign element is likely to change for some specializations.

11 The desc, object, and image elements inside <foreign> should still be translatable; they provide an alternative display if the foreign content cannot be processed.

12 The use of the alt attribute is deprecated in favor of the alt element.

13 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

14 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

15 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

16 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

17 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

18 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

19 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

20 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

21 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

22 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

23 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

24 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

25 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

map elements
As of DITA 1.2, the @navtitle attribute is deprecated, for translation purposes, in favor of the new <navtitle> element. The <navtitle> element is also available in topics, and is included in the topic table above.
Element name
Specialized from
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
anchor
N/A
n/a
n/a
n/a
linktext
N/A
block
block
yes
map
N/A
block
block
yes
@title 1
navref
N/A
n/a
n/a
n/a
relcell
N/A
block
block
yes
relcolspec
N/A
block
block
yes
relheader
N/A
block
block
yes
relrow
N/A
block
block
yes
reltable
N/A
block
block
yes
searchtitle
N/A
block
block
yes
shortdesc
N/A
block
block
yes
topicmeta
N/A
block
block
yes
topicref
N/A
block
block
yes
@navtitle
1 (deprecated as of DITA 1.2 for translation purposes)

bookmap elements (new in DITA 1.1)
The bookmap specialization contains many phrase-based elements inside the bookmeta. These are metadata, and should not be translated.
As of DITA 1.2, the @navtitle attribute is deprecated, for translation purposes, in favor of the new <navtitle> element.
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
abbrevlist
topicref
yes
block
block
yes
@navtitle
amendments
topicref
yes
block
block
yes
@navtitle
appendix
topicref
yes
block
block
yes
@navtitle
approved
data
yes
block
block
no
backmatter
topicref
yes
block
block
yes
bibliolist
topicref
yes
block
block
yes
@navtitle
bookabstract
topicref
yes
block
block
yes
@navtitle
bookchangehistory
data
yes
block
block
no
bookevent
data
yes
block
block
no
bookeventtype
data
yes
block
block
no
bookid
data
yes
block
block
no
booklibrary
ph
yes
inline
inline
yes
booklist
topicref
yes
block
block
yes
@navtitle
booklists
topicref
yes
block
block
yes
bookmap
map
no
block
block
yes
removed title attribute
bookmeta
topicmeta
yes
block
block
yes
booknumber
data
yes
block
block
no
bookowner
data
yes
block
block
no
bookpartno
data
yes
block
block
no
bookrestriction
data
yes
block
block
no
bookrights
data
yes
block
block
no
booktitle
title
yes
block
block
yes
booktitlealt
ph
yes
inline
inline
yes
chapter
topicref
yes
block
block
yes
@navtitle
colophon
topicref
yes
block
block
yes
@navtitle
completed
ph
no
inline
inline
no
copyrfirst
data
yes
block
block
no
copyrlast
data
yes
block
block
no
day
ph
no
inline
inline
no
dedication
topicref
yes
block
block
yes
@navtitle
draftintro
topicref
yes
block
block
yes
@navtitle
edited
data
yes
block
block
no
edition
data
yes
block
block
no
figurelist
topicref
yes
block
block
yes
@navtitle
frontmatter
topicref
yes
block
block
yes
@navtitle
glossarylist
topicref
yes
block
block
yes
@navtitle
indexlist
topicref
yes
block
block
yes
@navtitle
isbn
data
yes
block
block
no
mainbooktitle
ph
yes
inline
inline
yes
maintainer
data
yes
block
block
no
month
ph
no
inline
inline
no
notices
topicref
yes
block
block
yes
@navtitle
organization
data
yes
block
block
no
part
topicref
yes
block
block
yes
@navtitle
person
data
yes
block
block
no
preface
topicref
yes
block
block
yes
@navtitle
printlocation
data
yes
block
block
no
published
data
yes
block
block
no
publisherinformation
publisher
yes
block
block
yes
publishtype
data
yes
block
block
no
reviewed
data
yes
block
block
no
revisionid
ph
no
inline
inline
no
started
ph
no
inline
inline
no
summary
ph
yes
inline
inline
yes
tablelist
topicref
yes
block
block
yes
@navtitle
tested
data
yes
block
block
no
toc
topicref
yes
block
block
yes
@navtitle
trademarklist
topicref
yes
block
block
yes
@navtitle
volume
data
yes
block
block
no
year
ph
no
inline
inline
no
concept elements
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
conbody
body
yes
block
block
yes
conbodydiv (new in DITA 1.2)
bodydiv
yes
block
block
yes
concept
topic
yes
block
block
yes
glossentry elements (new in DITA 1.1)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
glossAbbreviation (new in DITA 1.2)
title
yes
block
block
yes
glossAcronym (new in DITA 1.2)
title
yes
block
block
yes
glossAlt (new in DITA 1.2)
section
yes
block
block
yes
removes @spectitle
glossAlternateFor (new in DITA 1.2)
xref
yes
inline
n/a (empty element)
n/a
glossbody (new in DITA 1.2)
body, conbody
yes
block
block
yes
glossdef
abstract
yes
block
block
yes
glossentry
topic, concept
yes
block
block
yes
glossPartOfSpeech (new in DITA 1.2)
data
yes
N/A (metadata)
block
no
glossProperty (new in DITA 1.2)
data
yes
N/A (metadata)
block
no
glossScopeNote (new in DITA 1.2)
note
yes
block
block
yes
@othertype
glossShortForm (new in DITA 1.2)
title
yes
block
block
yes
glossStatus (new in DITA 1.2)
data
yes
N/A (metadata)
block
no
glossSurfaceForm (new in DITA 1.2)
p
yes
block
block
yes
glossSymbol (new in DITA 1.2)
image
yes
block when @placement= break, otherwise inline
block when @placement= break, otherwise inline
yes
removes @alt
glossSynonym (new in DITA 1.2)
title
yes
block
block
yes
glossterm (new in DITA 1.2)
title
yes
block
block
yes
glossUsage (new in DITA 1.2)
note
yes
block
block
yes
@othertype (removes @spectitle)
reference elements
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
propdesc
stentry
yes
block
block
yes
@specentry1
propdeschd
stentry
yes
block
block
yes
@specentry2
properties
simpletable
yes
block
block
yes
@spectitle3
property
strow
yes
block
block
yes
prophead
sthead
yes
block
block
yes
proptype
stentry
yes
block
block
yes
@specentry4
proptypehd
stentry
yes
block
block
yes
@specentry5
propvalue
stentry
yes
block
block
yes
@specentry6
propvaluehd
stentry
yes
block
block
yes
@specentry7
refbody
body
yes
block
block
yes
refbodydiv (new in DITA 1.2)
bodydiv
yes
block
block
yes
reference
topic
yes
block
block
yes
refsyn
section
yes
block
block
yes
@spectitle8
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

2 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

3 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

4 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

5 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

6 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

7 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

8 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

task elements
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
chdesc
stentry
yes
block
block
yes
@specentry1
chdeschd
stentry
yes
block
block
yes
@specentry2
chhead
sthead
yes
block
block
yes
choice
li
yes
block
block
yes
choices
ul
yes
block
block
yes
removes @spectitle
choicetable
simpletable
yes
block
block
yes
@spectitle3
choption
stentry
yes
block
block
yes
@specentry4
choptionhd
stentry
yes
block
block
yes
@specentry5
chrow
strow
yes
block
block
yes
cmd
ph
NO
inline
block
yes
context
section
yes
block
block
yes
removes @spectitle
info
itemgroup
NO
inline
block
yes
postreq
section
yes
block
block
yes
removes @spectitle
prereq
section
yes
block
block
yes
removes @spectitle
result
section
yes
block
block
yes
removes @spectitle
step
li
yes
block
block
yes
stepresult
itemgroup
NO
inline
block
yes
steps
ol
yes
block
block
yes
removes @spectitle
steps-informal (new in DITA 1.2)
section
yes
block
block
yes
removes @spectitle
steps-unordered
ul
yes
block
block
yes
removes @spectitle
stepsection (new in DITA 1.2)
li
yes
block
block
yes
stepxmp
itemgroup
NO
inline
block
yes
substep
li
yes
block
block
yes
substeps
ol
yes
block
block
yes
removes @spectitle
task
topic
yes
block
block
yes
taskbody
body
yes
block
block
yes
tutorialinfo
itemgroup
NO
inline
block
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

2 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

3 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

4 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

5 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

hi-d elements (highlight domain)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
b
ph
yes
inline
inline
yes
i
ph
yes
inline
inline
yes
sub
ph
yes
inline
inline
yes
sup
ph
yes
inline
inline
yes
tt
ph
yes
inline
inline
yes
u
ph
yes
inline
inline
yes
indexing-d elements (indexing domain) (new in DITA 1.1)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
index-see
index-base
yes
block***1
block
yes
index-see-also
index-base
yes
block***2
block
yes
index-sort-as
index-base
yes
block***3
block
yes
1 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

2 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

3 This element is considered a "subflow" element for translation. If it is located in the middle of a translation segment, it should not be translated as part of that segment. For example, indexterm, fn, and draft-comment may divide a sentence in two, but should be treated as blocks, and should not interrupt the sentence.

pr-d elements (programming domain)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
apiname
keyword
yes
inline
inline
yes
codeblock
pre
yes
block
block
yes
@spectitle1
codeph
ph
yes
inline
inline
yes
coderef (new in DITA 1.2)
xref
yes
inline
N/A (empty element)
N/A
delim
ph
yes
inline
inline
yes
fragment
figgroup
yes
block
block
yes
fragref
xref
yes
inline
inline
yes
groupchoice
figgroup
yes
block
block
yes
groupcomp
figgroup
yes
block
block
yes
groupseq
figgroup
yes
block
block
yes
kwd
keyword
yes
inline
inline
yes
oper
ph
yes
inline
inline
yes
option
keyword
yes
inline
inline
yes
parml
dl
yes
block
block
yes
@spectitle2
parmname
keyword
yes
inline
inline
yes
pd
dd
yes
block
block
yes
plentry
dlentry
yes
block
block
yes
pt
dt
yes
block
block
yes
repsep
ph
yes
inline
inline
yes
sep
ph
yes
inline
inline
yes
synblk
figgroup
yes
block
block
yes
synnote
fn
yes
block
block
yes
synnoteref
xref
yes
inline
inline
yes
synph
ph
yes
inline
inline
yes
syntaxdiagram
fig
yes
block
block
yes
removes @spectitle
var
ph
yes
inline
inline
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

2 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

sw-d elements (software domain)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
cmdname
keyword
yes
inline
inline
yes
filepath
ph
yes
inline
inline
yes
msgblock
pre
yes
block
block
yes
@spectitle1
msgnum
keyword
yes
inline
inline
yes
msgph
ph
yes
inline
inline
yes
systemoutput
ph
yes
inline
inline
yes
userinput
ph
yes
inline
inline
yes
varname
keyword
yes
inline
inline
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

ui-d elements (UI domain)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
menucascade
ph
yes
inline
inline
yes
screen
pre
yes
block
block
yes
@spectitle1
shortcut
keyword
yes
inline
inline
yes
uicontrol
ph
yes
inline
inline
yes
wintitle
keyword
yes
inline
inline
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

ut-d elements (Utilities domain)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
area
figgroup
yes
block
block
yes
coords
ph
NO
inline
inline
no
imagemap
fig
yes
block
block
yes (can contain translatable alternate text)
@spectitle1
shape
keyword
NO
inline
inline
no
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

mapgroup-d elements (mapgroup domain)
As of DITA 1.2, the @navtitle attribute is deprecated, for translation purposes, in favor of the new <navtitle> element.
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
anchorref (new in DITA 1.2)
topicref
yes
block
block
yes
@navtitle
keydef (new in DITA 1.2)
topicref
yes
block
block
yes
@navtitle
mapref (new in DITA 1.2)
topicref
yes
block
block
yes
@navtitle
topicgroup
topicref
yes
block
block
yes
@navtitle
topichead
topicref
yes
block
block
yes
@navtitle
topicset (new in DITA 1.2)
topicref
yes
block
block
yes
@navtitle
topicsetref (new in DITA 1.2)
topicref
yes
block
block
yes
@navtitle
xnal-d elements (XNAL domain) (new in DITA 1.1)
The XNAL information is all metadata, so it generally does not need to be translated. Exceptions may be needed when selections from this metadata are used for display purposes. The standard behavior may need to change based on local business rules. For example, in some cases it may be appropriate to translate the honorific, country, or organizationname elements.
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
addressdetails
ph
no
block
block
no
administrativearea
ph
no
block
block
no
authorinformation
author
no
block
block
no
contactnumber
data
no
block
block
no
contactnumbers
data
no
block
block
no
country
ph
no
block
block
no
emailaddress
data
no
block
block
no
emailaddresses
data
no
block
block
no
firstname
data
no
block
block
no
generationidentifier
data
no
block
block
no
honorific
data
no
block
block
no
lastname
data
no
block
block
no
locality
ph
no
block
block
no
localityname
ph
no
block
block
no
middlename
data
no
block
block
no
namedetails
data
no
block
block
no
organizationinfo
data
no
block
block
no
organizationname
ph
no
block
block
no
organizationnamedetails
ph
no
block
block
no
otherinfo
data
no
block
block
no
personinfo
data
no
block
block
no
personname
data
no
block
block
no
postalcode
ph
no
block
block
no
thoroughfare
ph
no
block
block
no
url
data
no
block
block
no
urls
data
no
block
block
no
Delayed Conref Resolution domain elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
anchorid
keyword
no
N/A (metadata)
n/a
no
anchorkey
keyword
no
N/A (metadata)
n/a
no
exportanchors
keywords
no
N/A (metadata)
n/a
no
Hazard Statement Domain (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
consequence
li
yes
block
block
yes
hazardstatement
note
yes
block
block
yes
@othertype, @spectitle1
hazardsymbol
image
yes
block when @placement= break, otherwise inline
block when @placement= break, otherwise inline
yes
removes @alt
howtoavoid
li
yes
block
block
yes
messagepanel
ul
yes
block
block
yes
@spectitle2
typeofhazard
li
yes
block
block
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

2 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

glossgroup elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
glossgroup
topic
yes
block
block
yes
glossref domain elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
glossref
topicref
yes
block
block
yes
@navtitle
abbreviated-form domain elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
abbreviated-form
term
yes
inline
N/A empty element
N/A
task requirements domain (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
closereqs
section, postreq
yes
block
block
yes
esttime
li
yes
block
block
yes
noconds
li
yes
block
block
yes
nosafety
li
yes
block
block
yes
nospares
data
yes
N/A (metadata)
block
no
nosupeq
data
yes
N/A (metadata)
block
no
nosupply
data
yes
N/A (metadata)
block
no
perscat
li
yes
block
block
yes
perskill
li
yes
block
block
yes
personnel
li
yes
block
block
yes
prelreqs
section, prereq
yes
block
block
yes
reqcond
li
yes
block
block
yes
reqconds
ol
yes
block
block
yes
reqcontp
li
yes
block
block
yes
reqpers
ol
yes
block
block
yes
safecond
li
yes
block
block
yes
safety
ol
yes
block
block
yes
spare
li
yes
block
block
yes
spares
p
yes
block
block
yes
sparesli
ul
yes
block
block
yes
@spectitle1
supeqli
ul
yes
block
block
yes
@spectitle2
supequi
li
yes
block
block
yes
supequip
p
yes
block
block
yes
supplies
p
yes
block
block
yes
supply
li
yes
block
block
yes
supplyli
ul
yes
block
block
yes
@spectitle3
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

2 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

3 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

classification domain elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
subjectCell
relcell
yes
block
block
yes
subjectref
topicref
yes
block
block
yes
@navtitle
topicapply
topicref
yes
block
block
yes
@navtitle
topicCell
relcell
yes
block
block
yes
topicsubject
topicref
yes
block
block
yes
@navtitle
topicSubjectHeader
relrow
yes
block
block
yes
topicSubjectRow
relrow
yes
block
block
yes
topicSubjectTable
reltable
yes
block
block
yes
subject scheme elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
attributedef
data
yes
N/A (metadata
block
no
defaultSubject
topicref
yes
block
block
yes
@navtitle
elementdef
data
yes
N/A (metadata)
block
no
enumerationdef
topicref
yes
block
block
yes
@navtitle
hasInstance
topicref
yes
block
block
yes
@navtitle
hasKind
topicref
yes
block
block
yes
@navtitle
hasNarrower
topicref
yes
block
block
yes
@navtitle
hasPart
topicref
yes
block
block
yes
@navtitle
hasRelated
topicref
yes
block
block
yes
@navtitle
relatedSubjects
topicref
yes
block
block
yes
@navtitle
subjectdef
topicref
yes
block
block
yes
@navtitle
subjectHead
topicref
yes
block
block
yes
@navtitle
subjectHeadMeta
topicmeta
yes
block
block
yes
schemeref
topicref
yes
block
block
yes
@navtitle
subjectRel
relrow
yes
block
block
yes
subjectRelHeader
relrow
yes
block
block
yes
subjectRelTable
reltable
yes
block
block
yes
subjectRole
relcell
yes
block
block
yes
subjectScheme
map
yes
block
block
yes
removes @title
learningAssessment elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
learningAssessment
topic, learningBase
yes
block
block
yes
learningAssessmentbody
body, learningBasebody
yes
block
block
yes
learning base elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
lcAudience
section
yes
block
block
yes
@spectitle1
lcChallenge
section
yes
block
block
yes
@spectitle2
lcDuration
section
yes
block
block
yes
@spectitle3
lcInstruction
section
yes
block
block
yes
@spectitle4
lcInteraction
section
yes
block
block
yes
@spectitle5
lcInteractionBase
section
yes
block
block
yes
@spectitle6
lcIntro
section
yes
block
block
yes
@spectitle7
lcNextSteps
section
yes
block
block
yes
@spectitle8
lcObjective
li
yes
block
block
yes
lcObjectives
section
yes
block
block
yes
@spectitle9
lcObjectivesGroup
ul
yes
block
block
yes
lcObjectivesStem
ph
yes
inline
inline
yes
lcPrereqs
section
yes
block
block
yes
@spectitle10
lcResources
section
yes
block
block
yes
@spectitle11
lcReview
section
yes
block
block
yes
@spectitle12
lcSummary
section
yes
block
block
yes
@spectitle13
lcTime
data
yes
inline
inline
no
learningBase
topic
yes
block
block
yes
learningBasebody
body
yes
block
block
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

2 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

3 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

4 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

5 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

6 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

7 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

8 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

9 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

10 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

11 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

12 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

13 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

learningContent elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
learningContent
topic, learningBase
yes
block
block
yes
learningContentbody
body, learningBasebody
yes
block
block
yes
learningOverview elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
learningOverview
topic, learningBase
yes
block
block
yes
learningOverviewbody
body, learningBasebody
yes
block
block
yes
learningSummary elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
learningSummary
topic, learningBase
yes
block
block
yes
learningSummarybody
body, learningBasebody
yes
block
block
yes
learningPlan elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
lcAge
p
yes
block
block
yes
lcAssessment
p
yes
block
block
yes
lcAttitude
p
yes
block
block
yes
lcBackground
p
yes
block
block
yes
lcCIN
fig
yes
block
block
yes
@spectitle1
lcClassroom
fig
yes
block
block
yes
@spectitle2
lcClient
fig
yes
block
block
yes
@spectitle3
lcConstraints
fig
yes
block
block
yes
@spectitle4
lcDelivDate
fig
yes
block
block
yes
@spectitle5
lcDelivery
p
yes
block
block
yes
lcDownloadTime
fig
yes
block
block
yes
@spectitle6
lcEdLevel
p
yes
block
block
yes
lcFileSizeLimitations
fig
yes
block
block
yes
@spectitle7
lcGapAnalysis
section
yes
block
block
yes
@spectitle8
lcGapItem
fig
yes
block
block
yes
@spectitle9
lcGapItemDelta
p
yes
block
block
yes
lcGeneralDescription
p
yes
block
block
yes
lcGoals
p
yes
block
block
yes
lcGraphics
fig
yes
block
block
yes
@spectitle10
lcHandouts
fig
yes
block
block
yes
@spectitle11
lcIntervention
section
yes
block
block
yes
@spectitle12
lcInterventionItem
fig
yes
block
block
yes
@spectitle13
lcJtaItem
p
yes
block
block
yes
lcKnowledge
p
yes
block
block
yes
lcLearnStrat
p
yes
block
block
yes
lcLMS
fig
yes
block
block
yes
@spectitle14
lcModDate
fig
yes
block
block
yes
@spectitle15
lcMotivation
p
yes
block
block
yes
lcNeeds
p
yes
block
block
yes
lcNeedsAnalysis
section
yes
block
block
yes
@spectitle16
lcNoLMS
fig
yes
block
block
yes
@spectitle17
lcOJT
fig
yes
block
block
yes
@spectitle18
lcOrganizational
fig
yes
block
block
yes
@spectitle19
lcOrgConstraints
p
yes
block
block
yes
lcPlanAudience
fig
yes
block
block
yes
@spectitle20
lcPlanDescrip
fig
yes
block
block
yes
@spectitle21
lcPlanObjective
p
yes
block
block
yes
lcPlanPrereqs
fig
yes
block
block
yes
@spectitle22
lcPlanResources
p
yes
block
block
yes
lcPlanSubject
fig
yes
block
block
yes
@spectitle23
lcPlanTitle
fig
yes
block
block
yes
@spectitle24
lcPlayers
fig
yes
block
block
yes
@spectitle25
lcProcesses
p
yes
block
block
yes
lcProject
section
yes
block
block
yes
@spectitle26
lcResolution
fig
yes
block
block
yes
@spectitle27
lcSecurity
fig
yes
block
block
yes
@spectitle28
lcSkills
p
yes
block
block
yes
lcSpecChars
p
yes
block
block
yes
lcTask
fig
yes
block
block
yes
@spectitle29
lcTaskItem
p
yes
block
block
yes
lcTechnical
section
yes
block
block
yes
@spectitle30
lcValues
p
yes
block
block
yes
lcViewers
fig
yes
block
block
yes
@spectitle31
lcW3C
fig
yes
block
block
yes
@spectitle32
lcWorkEnv
fig
yes
block
block
yes
@spectitle33
lcWorkEnvDescription
p
yes
block
block
yes
learningPlan
topic, learningBase
yes
block
block
yes
learningPlanbody
body, learningBasebody
yes
block
block
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

2 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

3 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

4 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

5 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

6 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

7 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

8 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

9 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

10 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

11 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

12 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

13 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

14 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

15 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

16 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

17 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

18 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

19 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

20 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

21 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

22 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

23 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

24 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

25 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

26 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

27 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

28 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

29 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

30 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

31 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

32 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

33 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

learning map domain elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
learningContentRef
topicref
yes
block
block
yes
@navtitle
learningGroup
topicref
yes
block
block
yes
@navtitle
learningObject
topicref
yes
block
block
yes
@navtitle
learningOverviewRef
topicref
yes
block
block
yes
@navtitle
learningPlanRef
topicref
yes
block
block
yes
@navtitle
learningPostAssessmentRef
topicref
yes
block
block
yes
@navtitle
learningPreAssessmentRef
topicref
yes
block
block
yes
@navtitle
learningSummaryRef
topicref
yes
block
block
yes
@navtitle
learning domain elements (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
lcAnswerContent
p
yes
block
block
yes
lcAnswerOption
li
yes
block
block
yes
lcAnswerOptionGroup
ul
yes
block
block
yes
lcArea
figgroup
yes
block
block
yes
lcAreaCoords
ph
NO
inline
inline
no
lcAreaShape
keyword
NO
inline
inline
no
lcAsset
p
yes
block
block
yes
lcCorrectResponse
data
yes
N/A
block
no
lcFeedback
p
yes
block
block
yes
lcFeedbackCorrect
p
yes
block
block
yes
lcFeedbackIncorrect
p
yes
block
block
yes
lcHotspot
fig
yes
block
block
yes
lcHotspotMap
figgroup
yes
block
block
yes
lcInstructornote
note
yes
block
block
yes
@spectitle1
lcItem
stentry
yes
block
block
yes
removes @specentry
lcMatching
fig
yes
block
block
yes
lcMatchingItem
stentry
yes
block
block
yes
removes @specentry
lcMatchingItemFeedback
stentry
yes
block
block
yes
removes @specentry
lcMatchTable
simpletable
yes
block
block
yes
removes @spectitle
lcMatchingHeader
sthead
yes
block
block
yes
lcMatchingPair
strow
yes
block
block
yes
lcMultipleSelect
fig
yes
block
block
yes
lcOpenAnswer
p
yes
block
block
yes
lcOpenQuestion
fig
yes
block
block
yes
lcQuestion
p
yes
block
block
yes
lcQuestionBase
p
yes
block
block
yes
lcSequence
data
yes
N/A
block
no
lcSequenceOption
li
yes
block
block
yes
lcSequenceOptionGroup
ol
yes
block
block
yes
lcSequencing
fig
yes
block
block
yes
lcSingleSelect
fig
yes
block
block
yes
lcTrueFalse
fig
yes
block
block
yes
1 The spectitle and specentry attributes can contain translatable text. The direct use of fixed-in-the-DTD text by tools is discouraged, in favor of using the value as a lookup string to find the translation outside of the file, using accepted localization methods for generated text.

learning metadata domain (new in DITA 1.2)
Element name
Specialized from
Inherits everything from ancestor?
Block/Inline (presentation)
Block/Inline (translation)
Translatable content?
Translatable attributes?
lcLom
metadata
yes
block
block
yes
lomAggregationLevel
data
yes
N/A
block
no
lomContext
data
yes
N/A
block
no
lomCoverage
data
yes
N/A
block
no
lomDifficulty
data
yes
N/A
block
no
lomInstallationRemarks
data
yes
N/A
block
no
lomIntendedUserRole
data
yes
N/A
block
no
lomInteractivityLevel
data
yes
N/A
block
no
lomInteractivityType
data
yes
N/A
block
no
lomLearningResourceType
data
yes
N/A
block
no
lomOtherPlatformRequirements
data
yes
N/A
block
no
lomSemanticDensity
data
yes
N/A
block
no
lomStructure
data
yes
N/A
block
no
lomTechRequirement
data
yes
N/A
block
no
lomTypicalAgeRange
data
yes
N/A
block
no
lomTypicalLearningTime
data
yes
N/A
block
no
DITAVAL elements
The DITAVAL elements are not specialized, and are not rendered on their own, so related columns are dropped from this table. There are no translatable attributes in the DITAVAL element set.
As of DITA 1.2, the only element that directly contains text for translation is <alt-text>.
Element name
Block/Inline (translation)
Translatable content?
alt-text
block
yes
endflag
block
yes (inside nested elements)
prop
block
yes (inside nested elements)
revprop
block
yes (inside nested elements)
startflag
block
yes (inside nested elements)
style-conflict
block
N/A (empty element)
val
block
yes (inside nested elements)