[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Improving variable content in 2.0
Apologies, all — clearly I misread the part of the requirement (and Bob’s clarification) which showed the other, non-variable content in the wintitle. Lesson learned: always take the time to base examples on the actual content that someone provides! 😳
So, I see the point with <wintitle>, though is that the only semantic element that’s specialized from <keyword> and thus is constrained in this way? If so, would it be easier to make the DITA 2.0 <wintitle> a specialization of <ph> instead, just like <uicontrol>, which does allow a nested <keyword>?
On Jul 10, 2017, at 19:04, Joe Pairman <email@example.com> wrote:
I understand that the example given of the <text> element is one way to get the same variable value showing up within various inline elements — something that could be useful with the product name. I believe this is still covered with the use of linktext. I’ve added various inline elements in my sample topic, all referencing the same key, and they all pull in the linktext content:
<title>DITA Topic Map</title>
<linktext>Some text string</linktext>
<title>Test referencing linktext from wintitle</title>
Wintitle: <wintitle keyref="SomeKey"/>
Ph: <ph keyref="SomeKey"/>
Uicontrol: <uicontrol keyref="SomeKey"/>
Keyword: <keyword keyref="SomeKey"/>
With the <tm> element, if that were to be variable, again I’d suggest putting the keyref on the <tm> itself. Not that there’s anything wrong with using another nested element — I have used <keyword> and <text> in similar cases before, though of course they wouldn’t have worked in <wintitle> — but it just seems a bit neater to pull the variable text directly into whatever element I need locally. The <linktext> element is allowing that to happen.
On Jul 10, 2017, at 18:15, Bob Thomas <firstname.lastname@example.org> wrote:
But, of course, you can't because <tm> isn't allowed in wintitle. But, the idea is the same.
On Mon, Jul 10, 2017 at 11:09 AM, Bob Thomas <email@example.com> wrote:
+1 720 201 8260
Instant messaging: Gmail chat (firstname.lastname@example.org) or Skype
Time zone: Mountain (GMT-7)