+1
—Scott
From: Éric Sirois <>
Date: Tuesday, February 21, 2017 at 10:07 AM
To: Scott Hudson <>, "" <>
Subject: RE: [dita] RE: Overall fixes for bookmap for 2.0
Yeah, we have run into a similar situation with glossref (it doesn’t behave like the other ref type elements). Maybe that’s another small proposal we can fix for 2.0.
Éric Sirois
DITA Toolsmith
IXIASOFT
825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
/www.ixiasoft.com
From: Scott Hudson [mailto:]
Sent: February 21, 2017 12:06 PM
To: Éric Sirois <>;
Subject: Re: [dita] RE: Overall fixes for bookmap for 2.0
Well, the most annoying thing IMO is that even if the keys resolve, they won’t show up in output unless you specifically set print=“yes”. I’ve run into this a ton with term/abbreviated-form.
—Scott
From: <> on behalf of Éric Sirois <>
Date: Tuesday, February 21, 2017 at 10:03 AM
To: Éric Sirois <>, "" <>
Subject: [dita] RE: Overall fixes for bookmap for 2.0
Specifically looking to allow Keydefs in a more natural position in the map versus the first instance were topicref is allowed in the current content model. Are there other things that we have ignored about bookmaps
in DITA 1.3?
Éric Sirois
DITA Toolsmith
IXIASOFT
825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
/www.ixiasoft.com
From: [mailto:]
On Behalf Of Éric Sirois
Sent: February 21, 2017 11:33 AM
To:
Subject: [dita] Overall fixes for bookmap for 2.0
Hi,
We have a number of clients that have hit some limitations for keyref and ditavalref in bookmaps. I would like to work on a proposal that would address those limitations in DITA 2.0. Would it be possible to create
a project entry in the DITA 2.0 project?
Kind regards,
Éric Sirois
DITA Toolsmith
IXIASOFT
825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
/www.ixiasoft.com
