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.
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
Re: Frame + XML
Steve Rickaby wrote: At 15:11 +0100 4/7/06, Marcus Streets wrote: How do I tell Frame that an element is an inline and should not be put into a new paragraph but only have character level formatting? Give it a text format rule of 'Text range'. For example: Element (Container): Emphasis General rule:TEXT Exclusions: Graphic Text format rules In all contexts. Text range. Use character format: Emphasis Here the element and the character format have the same name. I find this less confusing, but I'm like that. FrameMaker 7.0 is fine unless you either hit one of the bugs that were fixed in 7.1 (no idea what they were) or need the XML smarts introduced in 7.2. OK I am not going mad - just going mad. I was wondering why this was not working - I had a capitalisation problem - the element was being imported as function not Function. 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.
Frame + XML
I am using Frame 7.0 - I know I need to upgrade. I ma having problems with my EDD. How do I tell Frame that an element is an inline and should not be put into a new paragraph but only have character level formatting? Marcus
Frame + XML
Steve Rickaby wrote: > At 15:11 +0100 4/7/06, Marcus Streets wrote: > >> How do I tell Frame that an element is an inline and should not be put >> into a new paragraph but only have character level formatting? > > Give it a text format rule of 'Text range'. For example: > >> Element (Container): Emphasis >> General rule: >> Exclusions: Graphic >> Text format rules >> In all contexts. >> Text range. >> Use character format: Emphasis > > Here the element and the character format have the same name. I find this > less confusing, but I'm like that. > > FrameMaker 7.0 is fine unless you either hit one of the bugs that were fixed > in 7.1 (no idea what they were) or need the XML smarts introduced in 7.2. OK I am not going mad - just going mad. I was wondering why this was not working - I had a capitalisation problem - the element was being imported as function not Function. Marcus
SourceSafe??? Recommendations needed.
Vorndran, Charles P wrote: > Loren, > > SourceSafe will certainly handle the file types you mentioned and > virtually any others that you didn't. The characteristic of most > version control systems of this type is that they're really designed to > store text files efficiently, and binary files, like those that you > mentioned, are an afterthought. With text files, only the differences > are stored after the initial creation, and you can compare any two > versions and visually see the differences. With binary files, the > system must store the complete file for each new version because there > is no way for them to identify the differences. This makes storage of > binary file versions a lot bulkier than storage of text files versions. > Source safe will compare two binary files and only tell you that they > are different, no more. Keep in mind that these source control systems > were really designed for developers to use to store their ascii source > code files. > > Microsoft introduced Team System about a year ago. It's designed to > handle more concurrent users and has more features. SourceSafe does > have limitations in the concurrent user area but we have about 20 or 30 > developers on a Sourcesafe system and don't seem to have a problem, but > then they're not all accessing the system at the same time. I suspect > that with Team System, Microsoft might retire Source Safe in the future, > but I haven't seen anything in that regard. > > Other systems to look at are: > ClearCase from Rational/IBM is an excellent tool for this and > handles many users. > Documentum is a document storage system, based on Oracle. The > desktop client gives the look and feel of using Windows Explorer, with > all the drag 'n drop, copy, etc features that Windows users are > accustomed to. > At the low end of the price range there's CVS and its intended > replacement, SubVersion. These, again are designed for text files but > they will handle binaries, and their low price may make them very > attractive, if you have the recommended Linux or Unix server(s) to > support it. > CVS very long in the tooth and unless you have developers who are wedded to it - do not go there - for binary files it really does nto help you. SubVersion is a little newer and shinier. Though personally I like the look of git - another such tool developed for tracking changes in the Linux kernel source. This is excellent if you have a large number of developers. One question - why are you checking FM files into source control. Could you track XML source for your FM documents. XML being text is much better suited to tracking by source code systems - and will take up a lot less disk. You will still want to have your templates under source code control as binary files - but hopefully these change less often than the content. If you check in Frame files you are storing a copy of the template information every single time you commit. This can chew up your storage space fairly quickly. Marcus
