1.3: Support heading for tasktroubleshooting element

Proposal 13096

EDIT: clarification added by @robander, May 4 2016: DITA 1.3 introduced <tasktroubleshooting> as a specialization of <section> within task topics.

We currently have the ability to add headings to task sections, using the args.gen.task.lbl parameter. This is supported for PDF and X/HTML (not sure about other formats). This feature request is a request to add headings for the new task section as well.

[shaneataylor]

@shudson310 I agree this would be very helpful, but wonder if troubleshooting section labels shouldn’t be controlled by a separate parameter, maybe a new args.gen.tbs.lbl?

Alternatively, maybe a new token-based args.gen.labels parameter would provide more flexibility, so users could specify (e.g.)

args.gen.labels = steps result condition remedy tasktroubleshooting

Also (and this might be my own quibble with the spec), when (almost always) the problem condition can be stated succinctly, I put it in <shortdesc> rather than <condition> to assist users who are scanning / searching troubleshooting topics to resolve a problem. I wonder what others think about:

• applying the Condition label to the short description if no <condition> is specified?
• processing <condition> as a <shortdesc> if no <shortdesc> exists?

[shudson310]

I expect that when args.gen.task.lbl is set to “yes”, that rendered troubleshooting topics would get labels for:

• Condition
• Cause
• Remedy

Also a label “Troubleshooting” for steptroubleshooting and tasktroubleshooting.