Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

How do I get keydef to support Italics?


How do I get keydef to support Italics?

We have a model name that has an Italicized letter in it. How do I get the keydef to support italics?




You might need to provide an example of your problem, and why italics are not working.

The third line says M155E4, the E needs to be in italics. If I ctrl+I the letter, I get a A20294 Requested formating is not allowed in this context message at the bottom of the screen.




Hi Bryon--

I think your problem doesn't really have anything to do with keydefs, but rather it's because you're trying to insert inline formatting in a <keyword> element, where it is not allowed. You will probably either have to modify your schema, or live without italics in your keywords metadata.


Thanks Clay, I have found this file smamap.mod, if I add the %univ-atts to the keyref should it work.


=================================================== -->

<!--                    COMMON ATTLIST SETS                        -->

<!-- ============================================================= -->

<!-- Currently: same as topicref, minus @query -->

<!ENTITY % chapter-atts

            'navtitle   CDATA                             #IMPLIED

             href       CDATA                             #IMPLIED

             keyref     CDATA                             #IMPLIED


             copy-to    CDATA                             #IMPLIED


                        CDATA                             #IMPLIED


             %univ-atts;'                                            >

Hi Bryon,

Hacking the smamap definitions in this way may break DITA for you, and also means you now have to maintain a customized version of the SMA code and roll it out to all users. Specializing DITA properly is a little involved but does allow specializations to be portable. The process is documented here: (Element Domain Specialization is what allows new elements to be defined and "subclassed" from an ancestor element)

Unfortunately, making a definition of an element e.g. <keyword> more expansive like you would need to do is not permitted via specialization. You can only make definitions more restrictive. Do you have to use <keyword>? If not, try finding another element that is more appropriate for formatted text (keyword is intended for text strings only). For example <ph> allows ful formatting. This might be a good starting point:



5-Regular Member

Hey Bryon,

Did adding the keyref to the entity work as you expected?

Let the Community know if any more is needed.  Thanks!

Top Tags