Hi All,
I had replied to the board and forgot to change the subject line, so this is continuing that topic. The short question is, how can I get the Subheading element's prefix text to appear as a full paragraph before the Description element's text? I've build a small sample for this discussion and was trying to get a full paragraph heading inserted before the contents of a text element, based off the parent elements name. Also, it took quite a while to figure out how to make a mixed content model not throw errors, and I still really do not understand how else that sequence could be structured. The SYSTEM and SPA elements insert the prefix text. However, I would think the structure should be: (<TEXT>,Description1&,Description2&)* I don't understand the need for the wrapper and termination, but that's what I found by trial and error. Separating the elements this way does not work. In the end, there will be many optional "Description" elements and they will have mixed order. Description1 and Description2 do not insert the Subheading prefix text. Further, it seems I would need to have the Subheading element before the <TEXT> element, since Subheading needs to be inserted before the Description element's text (or data). Below are the EDD and xml source data, which all validates and could be usable, except for the missing prefix Subheading. EDD Version is 12.0 Automatically create formats on import. Element (Container): File Valid as the highest-level element. General rule: File_Title, (SYSTEM?,SPA?) Element (Container): File_Title General rule: <TEXT> Text format rules In all contexts. Use paragraph format: Title Element (Container): SYSTEM General rule: (<TEXT>|Description1|Description2)* Prefix rules In all contexts. Prefix: SYSTEM Heading Text format rules In all contexts. Use paragraph format: ChapterHeading Element (Container): SPA General rule: (<TEXT>|Description1|Description2)* Prefix rules In all contexts. Prefix: SPA Heading Text format rules In all contexts. Use paragraph format: ChapterHeading Element (Container): Description1 General rule: (<TEXT>|Subheading)* Text format rules In all contexts. Use paragraph format: Indented4 Element (Container): Description2 General rule: (<TEXT>|Subheading)* Text format rules In all contexts. Use paragraph format: Indented4 Element (Container): Subheading General rule: <TEXT> Prefix rules If context is: Description1 Prefix: Insert Description1 Else, if context is: Prefix: Insert Description2 Text format rules In all contexts. Use paragraph format: Heading4 <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE File SYSTEM "file:///C:/FMStructure/Test.dtd" [ ]> <File> <File_Title>File Title</File_Title> <SYSTEM> <Description1>SYSTEM description1</Description1> <Description2>SYSTEM description2</Description2> </SYSTEM> <SPA> <Description1>SPA description1</Description1> <Description2>SPA description2</Description2> </SPA> </File> Thanks C2 ________________________________ From: Framers <framers-bounces+cuc2u=hotmail....@lists.frameusers.com> on behalf of framers-requ...@lists.frameusers.com <framers-requ...@lists.frameusers.com> Sent: Tuesday, August 28, 2018 1:02 PM To: framers@lists.frameusers.com Subject: Framers Digest, Vol 149, Issue 21 Send Framers mailing list submissions to framers@lists.frameusers.com To subscribe or unsubscribe, visit http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com You Framers Info Page - Adobe FrameMaker<http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com> lists.frameusers.com About the Framers email list. The purpose of this list is to share information about using Adobe Framemaker. We welcome experienced users, newcomers, and people simply wanting to know more about the software. can reach the person managing the list at framers-ow...@lists.frameusers.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Framers digest..." Today's Topics: 1. Re: FM 2017 Columns and Continued Lines (Wim Hooghwinkel - idtp) 2. FM2019 Doesn't Print to PDF (Corcoran, Susan) 3. Re: Framers Digest, Vol 149, Issue 20 (cuc tu) 4. Kudos for Adobe Support (Lea Rush) 5. Re: Framers Digest, Vol 149, Issue 20 (Roger Shuttleworth) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Aug 2018 22:24:51 +0200 From: Wim Hooghwinkel - idtp <w...@idtp.eu> To: framers@lists.frameusers.com Cc: julie.sigr...@airbornemx.com Subject: Re: [Framers] FM 2017 Columns and Continued Lines Message-ID: <16dfd6c2-321b-4c45-ae11-b73e1c80c...@idtp.eu> Content-Type: text/plain; charset=us-ascii Hi Julie, you could use a (one column) table for each Part Number and the belonging references. Put the Part Number paragraph in the table header (or table title) and add the table continued variable. This will be repeated at the top of each column where the table breaks. Vriendelijke groet / Kind regards, Wim Hooghwinkel FontoXML <http://www.fontoxml.com/> | DITAToo <http://www.ditatoo.com/> | FrameMaker <http://framemakerspecialist.nl/> | edc <http://www.easydoccontents.com/> | AEM <http://www.adobe.com/nl/products/xml-documentation-add-on-for-experience-manager.html> | MiramoPDF <https://www.miramo.com/english/overview/overview.html> Phone +31652036811 Skype wimhooghwinkel Twitter @idtp Web www.idtp.eu<http://www.idtp.eu> Check my LinkedIn <https://www.linkedin.com/in/hooghwinkel/> profile for latest updates - > Op 27 aug. 2018, om 22:02 heeft framers-requ...@lists.frameusers.com het > volgende geschreven: > > I work in Unstructured FrameMaker 2017 and have no background with > scripting or automating tasks. There may not be a simple solution, but > figured it couldn't hurt to ask. > > I have a file I've imported from Word that contains a Part Number and then > a list of chapter references for the part. The part number and chapter > reference each have their own paragraph tag. The page is set up as 3 > columns and whenever the chapter references break over to a new column the > client wants the part number repeated with (CONT) added. > > The file I'm working on is 60 pages long and I have an additional file > approx same size yet to do. I can set it up manually, but would have to > redo everytime something is added or deleted to the file. > > Is there any automated way of making this happen or is manually the only > solution? > > Thanks/Julie ------------------------------ Message: 2 Date: Tue, 28 Aug 2018 14:11:24 +0000 From: "Corcoran, Susan" <susan.corco...@honeywell.com> To: "framers@lists.frameusers.com" <framers@lists.frameusers.com> Subject: [Framers] FM2019 Doesn't Print to PDF Message-ID: <co2pr07mb2662b7b80952daa3e824301089...@co2pr07mb2662.namprd07.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi All, I'm playing with the trial version of FM2019 (on Win 10) and I have found that I can't publish to PDF properly. Using the Publish options, I can't specify RGB or CMYK, I can't specify my output file name, and even with all that, resulting pdfs are blank. When I try Save as PDF, I'm told to go to the Publish options. I had success by going back to the old method of printing to a ps file and distilling it, but I would think with the new Publish options that PDF output would be simpler. My gut tells me something's busted. Has anybody else seen these issues? Susan Corcoran -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 92 bytes Desc: image001.gif URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20180828/52c82446/attachment.gif> ------------------------------ Message: 3 Date: Tue, 28 Aug 2018 15:31:21 +0000 From: cuc tu <cu...@hotmail.com> To: "framers@lists.frameusers.com" <framers@lists.frameusers.com> Subject: Re: [Framers] Framers Digest, Vol 149, Issue 20 Message-ID: <mwhpr1801mb1888736bc5380eb28f0829fffd...@mwhpr1801mb1888.namprd18.prod.outlook.com> Content-Type: text/plain; charset="iso-8859-1" Howdy Framers, I am building a very simple structure, cut down further for this discussion. Some items I have not figured out: When importing element defs into the template: Elements that are defined but not referenced. The FM str dev guide mentions this one time as a capitalization mismatch (pg33 of the 2015 release), but I cannot see the problem. The elements are Subheading, Description2, SPA, SYSTEM, and File_Title. If I remove the Description2 element and references, then the unreferenced elements are Subheading, Description1, and File_Title. Some elements need a heading inserted as a paragraph, so I found an example for this in the dev guide, pg234. I'm not getting the prefix text inserted before the Description elements. Thanks for any assist. C2 ====================================================== <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE File SYSTEM "file:///C:/FMStructure/Test.dtd" []> <File> <File_Title>File Title</File_Title> <SYSTEM> <Description1>SYSTEM description1</Description1> <Description2>SYSTEM description2</Description2> </SYSTEM> <SPA> <Description1>SPA description1</Description1> <Description2>SPA description2</Description2> </SPA> </File> ====================================================== EDD Version is 12.0 Automatically create formats on import. Element (Container): File Valid as the highest-level element. General rule: <ANY> Element (Container): File_Title General rule: <TEXT> Text format rules In all contexts. Use paragraph format: Title Element (Container): SYSTEM General rule: <ANY> Prefix rules In all contexts. Prefix: SYSTEM Heading Text format rules In all contexts. Use paragraph format: ChapterHeading Element (Container): SPA General rule: <ANY> Prefix rules In all contexts. Prefix: SPA Heading Text format rules In all contexts. Use paragraph format: ChapterHeading Element (Container): Description1 General rule: <TEXT> Text format rules In all contexts. Use paragraph format: Indented4 Element (Container): Description2 General rule: <TEXT> Text format rules In all contexts. Use paragraph format: Indented4 Element (Container): Subheading General rule: <TEXT> Prefix rules If context is: Description1 Prefix: Insert Description1 Else, if context is: Prefix: Insert Description2 Text format rules In all contexts. Use paragraph format: Heading4 ====================================================== ------------------------------ Message: 4 Date: Tue, 28 Aug 2018 18:05:15 +0000 From: Lea Rush <l...@astoria-pacific.com> To: An email list for people using Adobe FrameMaker software. <framers@lists.frameusers.com> Subject: [Framers] Kudos for Adobe Support Message-ID: <060c2856105c5e4b91c3ba7a6933b8234df58...@ap-exch0.ap-exch.spire> Content-Type: text/plain; charset="iso-8859-1" Credit where credit is due. My computer was force-updated to the current build of Windows 10 last week, and the activation status for my beloved Frame8 was destroyed. I tried reactivation over the 'net, and it failed. I tried the activation phone number, and it was (not surprisingly) defunct. I finally called Adobe support. After a fair number of cache-file shenanigans and a new serial number, FM8 is working again. Many thanks to Vaibhav Vishwakarma for jumping through the many hoops needed to solve my problem. Lea Lea Rush Senior Software and Documentation Specialist Astoria-Pacific www.astoria-pacific.com<http://www.astoria-pacific.com/<http://www.astoria-pacific.com<http://www.astoria-pacific.com/>> P: 800-536-3111, +1-503-657-3010 Let us know how we're doing. Click here to take a brief survey<https://www.surveymonkey.com/r/service60>. Please consider the environment before printing this email. `?.??.???`?.?.???`?...? ><((((?>`?.??.???`?.?.???`?...?><((((?> https://www.surveymonkey.com/r/service60 NOTICE OF CONFIDENTIALITY This communication is from Astoria-Pacific and is intended to be confidential and solely for the use of the persons or entities addressed above. If you are not an intended recipient, be aware that the information contained herein may be protected from unauthorized use by privilege or law, and any copying, distribution, disclosure or other use of this information is prohibited. If you have received this communication in error, please contact the sender by return email or telephone (503) 657-3010 immediately, and delete or destroy all copies. Thank you for your cooperation. ------------------------------ Message: 5 Date: Tue, 28 Aug 2018 18:56:00 +0100 From: Roger Shuttleworth <shutti...@gmail.com> To: "An email list for people using Adobe FrameMaker software." <framers@lists.frameusers.com> Subject: Re: [Framers] Framers Digest, Vol 149, Issue 20 Message-ID: <e80bb1e0-f16c-437e-a29d-b9fa4f152...@gmail.com> Content-Type: text/plain; charset=UTF-8 Hi The unreferenced elements are ones that you have defined in your EDD but do not appear in the content model of any other element, and are not root level elements. Mismatched spelling can cause this, as element names are case-sensitive. But they may also be merely unused elsewhere in the EDD. Hope this helps. Roger ?Sent from BlueMail ? On 28 Aug 2018, 4:31 pm, at 4:31 pm, cuc tu <cu...@hotmail.com> wrote: >Howdy Framers, > >I am building a very simple structure, cut down further for this >discussion. Some items I have not figured out: > >When importing element defs into the template: Elements that are >defined but not referenced. The FM str dev guide mentions this one time >as a capitalization mismatch (pg33 of the 2015 release), but I cannot >see the problem. The elements are Subheading, Description2, SPA, >SYSTEM, and File_Title. If I remove the Description2 element and >references, then the unreferenced elements are Subheading, >Description1, and File_Title. > >Some elements need a heading inserted as a paragraph, so I found an >example for this in the dev guide, pg234. I'm not getting the prefix >text inserted before the Description elements. > >Thanks for any assist. >C2 > >====================================================== ><?xml version="1.0" encoding="UTF-8"?> ><!DOCTYPE File SYSTEM "file:///C:/FMStructure/Test.dtd" []> > ><File> ><File_Title>File Title</File_Title> ><SYSTEM> ><Description1>SYSTEM description1</Description1> ><Description2>SYSTEM description2</Description2> ></SYSTEM> ><SPA> ><Description1>SPA description1</Description1> ><Description2>SPA description2</Description2> ></SPA> ></File> >====================================================== >EDD Version is 12.0 >Automatically create formats on import. >Element (Container): File >Valid as the highest-level element. >General rule: <ANY> >Element (Container): File_Title >General rule: <TEXT> >Text format rules >In all contexts. >Use paragraph format: Title >Element (Container): SYSTEM >General rule: <ANY> >Prefix rules >In all contexts. >Prefix: SYSTEM Heading >Text format rules >In all contexts. >Use paragraph format: ChapterHeading >Element (Container): SPA >General rule: <ANY> >Prefix rules >In all contexts. >Prefix: SPA Heading >Text format rules >In all contexts. >Use paragraph format: ChapterHeading >Element (Container): Description1 >General rule: <TEXT> >Text format rules >In all contexts. >Use paragraph format: Indented4 >Element (Container): Description2 >General rule: <TEXT> >Text format rules >In all contexts. >Use paragraph format: Indented4 >Element (Container): Subheading >General rule: <TEXT> >Prefix rules >If context is: Description1 >Prefix: Insert Description1 >Else, if context is: >Prefix: Insert Description2 >Text format rules >In all contexts. >Use paragraph format: Heading4 >====================================================== > >_______________________________________________ > >This message is from the Framers mailing list > >Send messages to framers@lists.frameusers.com >Visit the list's homepage at http://www.frameusers.com >Archives located at >http://www.mail-archive.com/framers%40lists.frameusers.com/ >Subscribe and unsubscribe at >http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com >Send administrative questions to listad...@frameusers.com ------------------------------ Subject: Digest Footer _______________________________________________ This daily digest is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com ------------------------------ End of Framers Digest, Vol 149, Issue 21 **************************************** _______________________________________________ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com
