Overrides a necessary evil?
Hi, all! I realize this dilemma is opinion-based, but here goes: In structured FrameMaker, in theory there shouldn't be any overrides, right? They should have all been accounted for when devising the structure. So everyone (at least in theory) should be writing/formatting the same way. What about page breaks? I understand the widow/orphan capabilities, but sometimes it still looks awkward - it would look better (and reads better) to move a whole section to the next page. Any opinions either way? Or any good reasons why one is better than the other? Thanks for the input! Kristy Kristy Nolan Publications Specialist Ground Ops Publications DAL-3TR Southwest Airlines Dallas, TX 75235 ___ 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: Overrides a necessary evil?
If you need it that badly, then you can write page breaks into your structure, so that it's not an override. Set up an attribute on any elements that could require a page break (Headings, for example) and write in a context rule that applies a page break if you set the attribute to a certain value. Gary In my opinion, I think most would agree, page breaks are just about the only acceptable override in non-structured documents. As you point out, sometimes you need to fix awkward breaks. This e-mail, and any attachments are strictly confidential and intended for the addressee(s) only. The content may also contain legal, professional or other privileged information. If you are not the intended recipient, please notify the sender immediately, by return of email, and then delete the e-mail and any attachments. You should not disclose, copy or take any action in reliance on this transmission. Please ensure you have adequate virus protection before you open or detach any documents from this transmission. Advantica, Inc. is a company incorporated in Delaware with its headquarters at 600 Bent Creek Blvd., Suite 100, Mechanicsburg, PA 17050 U.S.A. Advantica Ltd. is a company registered in England and Wales with company No. 3294136 and registered office at Holywell Park, New Ashby Road, Loughborough, Leicestershire, LE11 3GR, United Kingdom. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ 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: Overrides a necessary evil?
Hi Kristy, I get around the pagination issue in my structured documents by adding a pagination attribute to my section elements that includes the choices Top_Of_Page and Top_Of_Column. This allows me to start any section at the top of a page or column if necessary. Context-based formatting rules in the EDD detect the value of the pagination attribute and set the pagination properties of the corresponding heading paragraph accordingly. You can use this technique to gain fine control over any layout-specific properties in structured documents. I also find this technique useful to swap out the graphical icons associated with warnings, cautions, notes, and tips. I also use this technique to control alignment in table cells. I have also added attributes to the root element of a chapter to toggle branding-specific color schemes throughout the entire document. Best regards, Martin Martin R. Smith www.golehtek.com ___ 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.
Overrides a necessary evil?
Hi, all! I realize this dilemma is opinion-based, but here goes: In structured FrameMaker, in theory there shouldn't be any overrides, right? They should have all been "accounted for" when devising the structure. So everyone (at least in theory) should be writing/formatting the same way. What about page breaks? I understand the widow/orphan capabilities, but sometimes it still looks awkward - it would look better (and reads better) to move a whole section to the next page. Any opinions either way? Or any good reasons why one is better than the other? Thanks for the input! Kristy Kristy Nolan Publications Specialist Ground Ops Publications DAL-3TR Southwest Airlines Dallas, TX 75235
Overrides a necessary evil?
Kristy, In my opinion, I think most would agree, page breaks are just about the only acceptable override in non-structured documents. As you point out, sometimes you need to fix awkward breaks. I don't work with structured documents a lot, but I think the printed layout gets compromised somewhat because it is so difficult to control from within the structure. Clint Clinton Owen | Senior Technical Writer | Crane Aerospace & Electronics | +1 425-743-8674 | F: +1 425-743-8113 -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Kristy Nolan Sent: Wednesday, July 09, 2008 1:39 PM To: framers at lists.frameusers.com Subject: Overrides a necessary evil? Hi, all! I realize this dilemma is opinion-based, but here goes: In structured FrameMaker, in theory there shouldn't be any overrides, right? They should have all been "accounted for" when devising the structure. So everyone (at least in theory) should be writing/formatting the same way. What about page breaks? I understand the widow/orphan capabilities, but sometimes it still looks awkward - it would look better (and reads better) to move a whole section to the next page. Any opinions either way? Or any good reasons why one is better than the other? Thanks for the input! Kristy Kristy Nolan Publications Specialist Ground Ops Publications DAL-3TR Southwest Airlines Dallas, TX 75235 ___ You are currently subscribed to Framers as Clint.Owen at craneaerospace.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/clint.owen%40craneae rospace.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info. We value your opinion! How may we serve you better? Please click the survey link to tell us how we are doing. http://www.craneae.com/surveys/satisfaction.htm Your feedback is of the utmost importance to us. Thank you for your time. >>>>>>>>>> Crane Aerospace & Electronics Confidentiality Statement <<<<<<<<<< The information contained in this email message may be privileged and is confidential information intended only for the use of the recipient, or any employee or agent responsible to deliver it to the intended recipient. Any unauthorized use, distribution or copying of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately and destroy the original message and all attachments from your electronic files. This e-mail message has been scanned and cleared by MailMarshal
Overrides a necessary evil?
If you need it that badly, then you can write page breaks into your structure, so that it's not an override. Set up an attribute on any elements that could require a page break (Headings, for example) and write in a context rule that applies a page break if you set the attribute to a certain value. Gary > In my opinion, I think most would agree, page breaks are just about the > only acceptable override in non-structured documents. As you point out, > sometimes you need to fix awkward breaks. This e-mail, and any attachments are strictly confidential and intended for the addressee(s) only. The content may also contain legal, professional or other privileged information. If you are not the intended recipient, please notify the sender immediately, by return of email, and then delete the e-mail and any attachments. You should not disclose, copy or take any action in reliance on this transmission. Please ensure you have adequate virus protection before you open or detach any documents from this transmission. Advantica, Inc. is a company incorporated in Delaware with its headquarters at 600 Bent Creek Blvd., Suite 100, Mechanicsburg, PA 17050 U.S.A. Advantica Ltd. is a company registered in England and Wales with company No. 3294136 and registered office at Holywell Park, New Ashby Road, Loughborough, Leicestershire, LE11 3GR, United Kingdom. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Overrides a necessary evil?
Hi Kristy, I get around the pagination issue in my structured documents by adding a "pagination" attribute to my section elements that includes the choices Top_Of_Page and Top_Of_Column. This allows me to start any section at the top of a page or column if necessary. Context-based formatting rules in the EDD detect the value of the pagination attribute and set the pagination properties of the corresponding heading paragraph accordingly. You can use this technique to gain fine control over any layout-specific properties in structured documents. I also find this technique useful to swap out the graphical icons associated with warnings, cautions, notes, and tips. I also use this technique to control alignment in table cells. I have also added attributes to the root element of a chapter to toggle branding-specific color schemes throughout the entire document. Best regards, Martin Martin R. Smith www.golehtek.com
