GlossSee and GlossSeeAlso
Alan Houser wrote: > Hi Marcus, > > This sounds like expected behavior. The rendering engine (FrameMaker) > generates the text of the cross-reference from the content of the target > GlossEntry. The GlossSee XML element exported from FrameMaker will have > no content. > I fear my post was not clear enough. If I use Frame to open an XML document containing a Glossee element Frame fails to create a cross reference inside the element. However, if I insert such an element into the document - along side the empty elment created when the xml file was read - Frame does insert a xref. Which suggests that I have correctly defined the element in the edd. I could simply work round this using Xref elements, which are prefectly valid and work fine. However, I am sure that using the correct elements would help anyone else who has to cope with the xml files. Marcus
GlossSee and GlossSeeAlso
Lynne A. Price wrote: > Marcus, > There is nothing special about elements with these names. Are the > empty elements in the XML document cross-references? Have you specified > a cross-reference format either in an attribute or in a read/write rule? > --Lynne > > I have a All context rule specifying the Xref format - as opposed to x-ref where I have a context rule that looks at the role to choose the x-ref format. However apart from that the two entries in the edd are identical. If I add a new element to an existing doc it works fine. As far as i can see all the resulting inserted element has all the same attributes as the one created when it read the xml file. It is just that the element created when the xml file is read does not contain a frame xref. Marcus
GlossSee and GlossSeeAlso
Is there any know issues with importing these XML elements. I have set them up in the EDD as Xref elements - and when I insert a new element into an existing Frame document it works as a cross reference. However, if I open an XML document I get an emplty element - even though the otherterm attribute is correct. Any ideas Marcus ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: GlossSee and GlossSeeAlso
Lynne A. Price wrote: Marcus, There is nothing special about elements with these names. Are the empty elements in the XML document cross-references? Have you specified a cross-reference format either in an attribute or in a read/write rule? --Lynne I have a All context rule specifying the Xref format - as opposed to x-ref where I have a context rule that looks at the role to choose the x-ref format. However apart from that the two entries in the edd are identical. If I add a new element to an existing doc it works fine. As far as i can see all the resulting inserted element has all the same attributes as the one created when it read the xml file. It is just that the element created when the xml file is read does not contain a frame xref. Marcus ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: GlossSee and GlossSeeAlso
At 04:05 PM 7/13/2006, Marcus Streets wrote: It is just that the element created when the xml file is read does not contain a frame xref. Marcus, Does your DTD declare the element as EMPTY? If not, you need a r/w rule that indicates it is a cross-reference. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training [EMAIL PROTECTED]http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
GlossSee and GlossSeeAlso
Is there any know issues with importing these XML elements. I have set them up in the EDD as Xref elements - and when I insert a new element into an existing Frame document it works as a cross reference. However, if I open an XML document I get an emplty element - even though the otherterm attribute is correct. Any ideas Marcus
GlossSee and GlossSeeAlso
At 04:05 PM 7/13/2006, Marcus Streets wrote: >It is just that the element created when the xml file is read does not >contain a frame xref. Marcus, Does your DTD declare the element as ? If not, you need a r/w rule that indicates it is a cross-reference. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training lprice at txstruct.comhttp://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284
