DITA 1.1 elements with translation properties

This contains a list of all DITA 1.1 elements, divided up by module. It describes which are block elements and which are inline, and lists which elements should be translated by default. After review, this list will be merged with the already approved list of 1.0 elements.

Notes on the tables below

topic elements

Element name Specialized from Block/Inline (presentation) Block/Inline (translation) Translatable content? Translatable attributes?
abstract N/A block 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  
foreign N/A block3 block3 no4  
index-base N/A block***1 block yes  
unknown N/A block block no  

glossary elements

Element name Specialized from Inherits everything from ancestor? Block/Inline (presentation) Block/Inline (translation) Translatable content? Translatable attributes?
glossdef abstract yes block block yes  
glossentry topic yes block block yes  

indexing-d elements (indexing domain)

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***1 block yes  
index-sort-as index-base yes block***1 block yes  

xnal-d elements (XNAL domain)

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.

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  

bookmap elements

The bookmap specialization contains many phrase-based elements inside the bookmeta. These are metadata, and should not be translated.

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
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  
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 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 block vs. inline designation for the foreign element is likely to change for some specializations
4 The desc, object, and image elements inside <foreign> should still be translatable; they provide an alternative display if the foreign content cannot be processed