DITA and XMetaL Discussion
XMetaL Community Forum › DITA and XMetaL Discussion › Authoring a System Message Lookup Table in a DITA Reference Topic
-
Jeff Haas June 3, 2010 at 10:23 am
Authoring a System Message Lookup Table in a DITA Reference Topic
June 3, 2010 at 10:23 amParticipants 1Replies 2Last Activity 12 years, 8 months agoRather than creating individual topics for system messages, I'm attempting to author a system message lookup table in one DITA reference topic. In XMetaL 6.0, the default reference topic creates a basic table using elements proptypehd/proptype, propvaluehd/propvalue, and propdeschd/propdesc. However, I'm hoping to customize or replace that table with a table that contains the following properties:
– Country
– Language
– Message Set Number
– Message Number
– Message Text
– Message Severity
– Long DescriptionShould I modify the existing table or create a table of my own? Should I re-use the provided elements or work with other elements such as “Software Elements” msgblock, msgnum, and msgph? Can this be done in a standard DITA reference topic or is some kind of specialization required?
Assuming I succeed in authoring such a table, will a user interface call be able identify a specific system messsage in the lookup table, extract the Message Text from raw, untransformed XML/DITA, and populate the appropriate user interface control with it?
Thanks for any help you can provide.
Derek Read June 10, 2010 at 12:28 am
Reply to: Authoring a System Message Lookup Table in a DITA Reference Topic
June 10, 2010 at 12:28 amWhat does this need to end up looking like in your final output?
Do any of these items (country, language, etc) need to pull in external data via conref or something (image, text, etc)?
Do any of these items need to link to something (with that link being a link-like thing such as in HTML output for example)?
Trying to get my head around what you are trying to do here.
Jeff Haas June 10, 2010 at 1:06 am
Reply to: Authoring a System Message Lookup Table in a DITA Reference Topic
June 10, 2010 at 1:06 amThanks for your reply.
I solved this problem by deleting the default properties table from the reference topic and creating my own normal table. Basically, I'm not performing the transform myself but providing raw XML/DITA to Development for them to populate standard user assistance controls in the user interface with data from my topics.
-
AuthorPosts
- You must be logged in to reply to this topic.