Behavior regarding conkeyref before keydef
Hey Everyone, This is a fairly explainable situation and not causing major problems but I'm curious if there is a way to get around it. Here's the scenario: 1. I have a map with a conkeyref in the mainbooktitle. Then in the front matter I define the keydef: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap/dtd/bookmap.dtd"> <bookmap format="ditamap" id="bookmap_User_Manual_Previ_Color"> <booktitle> <mainbooktitle><ph conkeyref="productinfo/prodname"/></mainbooktitle> </booktitle> <frontmatter> <keydef format="dita" href="user/ProductVariables.xml" keys="productinfo" processing-role="resource-only" type="topic"/> When I first load this map in Oxygen it loads the map title before it reads the keydef which results in a warning: System ID: C:\dita\products\vitek2systems\EN\Vitek2Systems_User_Manual.ditamap Severity: warning Description: [Document]:Could not resolve the target for key reference "productinfo/prodname" Screenshot: http://i.imgur.com/bXnnE.png If I open the map and make any change (Hit space, hit backspace, hit save) it then reads the title correctly. Is there another place I can define my keydef to avoid this? Or any other workaround? Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.
Hi Matt, We know about this bug and we plan to address it in a future version. You will be notified when this happens. Basically right now the keys are collected in the DITA Map after the conrefs (or topicrefs) are resolved so when the conkeyref is first encountered there are not yet any keys collected. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 7/31/2012 5:24 PM, KAATMAN Matthew wrote:
Hey Everyone,
This is a fairly explainable situation and not causing major problems but I'm curious if there is a way to get around it.
Here's the scenario: 1. I have a map with a conkeyref in the mainbooktitle. Then in the front matter I define the keydef: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap/dtd/bookmap.dtd"> <bookmap format="ditamap" id="bookmap_User_Manual_Previ_Color"> <booktitle> <mainbooktitle><ph conkeyref="productinfo/prodname"/></mainbooktitle> </booktitle> <frontmatter> <keydef format="dita" href="user/ProductVariables.xml" keys="productinfo" processing-role="resource-only" type="topic"/>
When I first load this map in Oxygen it loads the map title before it reads the keydef which results in a warning: System ID: C:\dita\products\vitek2systems\EN\Vitek2Systems_User_Manual.ditamap Severity: warning Description: [Document]:Could not resolve the target for key reference "productinfo/prodname" Screenshot: http://i.imgur.com/bXnnE.png
If I open the map and make any change (Hit space, hit backspace, hit save) it then reads the title correctly.
Is there another place I can define my keydef to avoid this? Or any other workaround?
Thanks! Matt
AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
On Tue, 31 Jul 2012 17:35:38 +0300, Oxygen XML Editor Support <support@oxygenxml.com> wrote:
We know about this bug and we plan to address it in a future version. You will be notified when this happens. Basically right now the keys are collected in the DITA Map after the conrefs (or topicrefs) are resolved so when the conkeyref is first encountered there are not yet any keys collected.
As you've realized, that's not the best order of processing. FYI, DITA2Go does it this way: 1. Parse original maps, including maps referenced from topicrefs and maprefs. Filter conditions during parse. 2. Kesolve keydefs in the parsed maps. 3. Resolve keyrefs to maps, including conkeyrefs. 4. Parse maps that used keyrefs and conkeyrefs. 5. Process conrefs between maps and from topics to maps (the OP's case). 6. Parse topics referenced in the maps. 7. Process conrefs between topics and from maps to topics. 8. Process autonumbers, generated lists, links, and xrefs, in that order. 9. Set page sequence. 10. Process related links. HTH! -- Jeremy H. Griffith <jeremy@omsys.com> DITA2Go site: http://www.dita2go.com/
Thanks Radu, Along the same lines, if you have multiple maps loaded and they're all using conkeyrefs before the keys are collected, sometimes you can see the keys displayed from map in the next map. Let me know if you need me to prepare an example but I suspect you already know about this as well. Thanks! Matt -----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Oxygen XML Editor Support Sent: Tuesday, July 31, 2012 9:36 AM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] Behavior regarding conkeyref before keydef Hi Matt, We know about this bug and we plan to address it in a future version. You will be notified when this happens. Basically right now the keys are collected in the DITA Map after the conrefs (or topicrefs) are resolved so when the conkeyref is first encountered there are not yet any keys collected. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 7/31/2012 5:24 PM, KAATMAN Matthew wrote:
Hey Everyone,
This is a fairly explainable situation and not causing major problems but I'm curious if there is a way to get around it.
Here's the scenario: 1. I have a map with a conkeyref in the mainbooktitle. Then in the front matter I define the keydef: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap/dtd/bookmap.dtd"> <bookmap format="ditamap" id="bookmap_User_Manual_Previ_Color"> <booktitle> <mainbooktitle><ph conkeyref="productinfo/prodname"/></mainbooktitle> </booktitle> <frontmatter> <keydef format="dita" href="user/ProductVariables.xml" keys="productinfo" processing-role="resource-only" type="topic"/>
When I first load this map in Oxygen it loads the map title before it reads the keydef which results in a warning: System ID: C:\dita\products\vitek2systems\EN\Vitek2Systems_User_Manual.ditamap Severity: warning Description: [Document]:Could not resolve the target for key reference "productinfo/prodname" Screenshot: http://i.imgur.com/bXnnE.png
If I open the map and make any change (Hit space, hit backspace, hit save) it then reads the title correctly.
Is there another place I can define my keydef to avoid this? Or any other workaround?
Thanks! Matt
AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.
Hi Matt, Can you please send us the samples that reproduce this problem? Thank you and regards, Mihaela Mihaela Calotescu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 8/1/2012 7:35 PM, KAATMAN Matthew wrote:
Thanks Radu,
Along the same lines, if you have multiple maps loaded and they're all using conkeyrefs before the keys are collected, sometimes you can see the keys displayed from map in the next map.
Let me know if you need me to prepare an example but I suspect you already know about this as well.
Thanks! Matt
-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Oxygen XML Editor Support Sent: Tuesday, July 31, 2012 9:36 AM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] Behavior regarding conkeyref before keydef
Hi Matt,
We know about this bug and we plan to address it in a future version. You will be notified when this happens. Basically right now the keys are collected in the DITA Map after the conrefs (or topicrefs) are resolved so when the conkeyref is first encountered there are not yet any keys collected.
Regards, Radu
Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 7/31/2012 5:24 PM, KAATMAN Matthew wrote:
Hey Everyone,
This is a fairly explainable situation and not causing major problems but I'm curious if there is a way to get around it.
Here's the scenario: 1. I have a map with a conkeyref in the mainbooktitle. Then in the front matter I define the keydef: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap/dtd/bookmap.dtd"> <bookmap format="ditamap" id="bookmap_User_Manual_Previ_Color"> <booktitle> <mainbooktitle><ph conkeyref="productinfo/prodname"/></mainbooktitle> </booktitle> <frontmatter> <keydef format="dita" href="user/ProductVariables.xml" keys="productinfo" processing-role="resource-only" type="topic"/>
When I first load this map in Oxygen it loads the map title before it reads the keydef which results in a warning: System ID: C:\dita\products\vitek2systems\EN\Vitek2Systems_User_Manual.ditamap Severity: warning Description: [Document]:Could not resolve the target for key reference "productinfo/prodname" Screenshot: http://i.imgur.com/bXnnE.png
If I open the map and make any change (Hit space, hit backspace, hit save) it then reads the title correctly.
Is there another place I can define my keydef to avoid this? Or any other workaround?
Thanks! Matt
AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (4)
-
Jeremy H. Griffith -
KAATMAN Matthew -
Oxygen XML Editor Support -
oXygen XML Editor Support