Using Attributes on the Reference Page
Hi Randall, I don't think there was anything in the olden days that stopped working on later versions. I would suggest that you look at FrameScript as a way to automate adding the required leading zeros. If you can spell out your exact requirements, I can help you determine what is possible with FrameScript. I looked at this problem some time ago for a mil-spec client, and we were able to come up with a FrameScript solution that would largely automate the process. Let's face it: FrameMaker is a great publishing platform, but sometimes it needs help to overcome some of its limitations. This is not the kind of task you want to maintain by hand, especially when it may be possible to automate it inexpensively. If you want to pursue this further, please contact me off-list. Thank you very much. Rick Quatro Carmen Publishing Inc. 585-659-8267 rick at frameexpert.com www.frameexpert.com http://www.frameexpert.com/peace/ FM Pilgrims: We are trying to perfect some standard TOC and Index features in the Reference pages and are having "issues" with things that apparently used to work in 6.xx and don't appear to work anymore with Structured 7.2: This is a MIL SPEC 40051-2 project, which requires a 4-digit work package number element () for each file, from 0001 to approx 0400+. The leading zeroes are crucial, as the spec requires four-digits to appear on the page, page number, TOC, and Index. Problem: We cannot get Frame 7.2 to recognize the coding to pick up the attribute , which sets the number of zeroes to 3 for WPs 1 to 9, 2 for WPs 10 to 99, and the default 1 for WPs 100 and up. It should work, but it does. We believe it worked on older versions of FM that we used in the past, but it won't work now. (We suspect some unannounced tinkering by Adobe that has had unintended consequences...) Looks like we are forced to drop the whole attribute idea and just use the system variable <$chapnum> to generate the work package number and basically treat it like text so that it retains the leading zeroes, which would normally be truncated by FM. But, that means essentially hard-keying values into each file, which is a step backwards, in my mind, from what FM should be able to do for us automatically. 1. What changed between 6.xx and 7.2 to make attributes a no-go on the Reference page? 2. What is everyone else who does 40051-2 compliant mil spec pubs doing for in each package? Is there another obvious approach I am missing? 3. Am I being completely addled or was there really a way to do this in the "olden days"? TIA! Randall C. Reed Senior Technical Writer Technical Publications Total Life Cycle Support Force Protection Industries, Inc. (o) 843-574-3899 (c) 843-906-5522
Using Attributes on the Reference Page
2009-12-11-05T14:20Z Randall - I have no interest in Carmen publishing other than being a satisfied customer. Early this year, we were using FrameMaker 7.1p116 (unstructured) on a project to conform to US DOD MIL-STD 40051-2. We ran into the same problem and contacted Rick Quatro of Carmen Publishing. He produced a FrameScript script for us: SetWorkPackageNumbering.fsl. Worked like a charm. We're now working on a project to conform to US DOD MIL-HDBK 2361C (AB) and MIL-STD 40051-2 and such. I recommend you contact him and ask him to adapt the above script to work with both unstructured and structured files. If he adapts it, we'd be interested in getting the updated version. Rick's contact information follows. / Rick Quatro rick at frameexpert.com 585-659-8267 / Also, I invite and encourage you to report the problem and request the feature as I did through: http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform Good luck and regards, Dave Stamm Publications Specialist, Senior Staff General Dynamics C4 Systems, Inc. Battle Management Systems Division 1700 Magnavox Way, Suite 200 We'll hit your targets from here.(tm) Fort Wayne, Indiana 46804-1552 US tel: 260-434-9620 fax: 260.434.9606 dave.stamm at gdc4s.com http://www.gdc4s.com/ This message and / or attachments may include information subject to GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message. -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Randall C. Reed Sent: 2009-December-11-Friday 08:41 To: framers at lists.frameusers.com Subject: Using Attributes on the Reference Page Importance: High FM Pilgrims: We are trying to perfect some standard TOC and Index features in the Reference pages and are having "issues" with things that apparently used to work in 6.xx and don't appear to work anymore with Structured 7.2: This is a MIL SPEC 40051-2 project, which requires a 4-digit work package number element () for each file, from 0001 to approx 0400+. The leading zeroes are crucial, as the spec requires four-digits to appear on the page, page number, TOC, and Index. Problem: We cannot get Frame 7.2 to recognize the coding to pick up the attribute , which sets the number of zeroes to 3 for WPs 1 to 9, 2 for WPs 10 to 99, and the default 1 for WPs 100 and up. It should work, but it does. We believe it worked on older versions of FM that we used in the past, but it won't work now. (We suspect some unannounced tinkering by Adobe that has had unintended consequences...) Looks like we are forced to drop the whole attribute idea and just use the system variable <$chapnum> to generate the work package number and basically treat it like text so that it retains the leading zeroes, which would normally be truncated by FM. But, that means essentially hard-keying values into each file, which is a step backwards, in my mind, from what FM should be able to do for us automatically. 1. What changed between 6.xx and 7.2 to make attributes a no-go on the Reference page? 2. What is everyone else who does 40051-2 compliant mil spec pubs doing for in each package? Is there another obvious approach I am missing? 3. Am I being completely addled or was there really a way to do this in the "olden days"? TIA! Randall C. Reed Senior Technical Writer Technical Publications Total Life Cycle Support Force Protection Industries, Inc. (o) 843-574-3899 (c) 843-906-5522 This e-mail is intended solely for the person or entity to which it is addressed and may contain legally privileged and CONFIDENTIAL INFORMATION intended solely for viewing by the addressee. If you are not the intended recipient, you should immediately stop reading this message and delete it from your system. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. Please notify the Helpdesk at helpdesk at forceprotection.net if you have received this message in error. This material contains confidential and proprietary information of Force Protection, Inc. and its subsidiaries. Copying this material or disclosing such information to others without the Company's prior consent is prohibited. This material also contains technical data relating to a "Defense Article" within the meaning of the International Traffic in Arms Regulations (22 CFR Part 120). The transfer or disc
Using Attributes on the Reference Page
FM Pilgrims: We are trying to perfect some standard TOC and Index features in the Reference pages and are having "issues" with things that apparently used to work in 6.xx and don't appear to work anymore with Structured 7.2: This is a MIL SPEC 40051-2 project, which requires a 4-digit work package number element () for each file, from 0001 to approx 0400+. The leading zeroes are crucial, as the spec requires four-digits to appear on the page, page number, TOC, and Index. Problem: We cannot get Frame 7.2 to recognize the coding to pick up the attribute , which sets the number of zeroes to 3 for WPs 1 to 9, 2 for WPs 10 to 99, and the default 1 for WPs 100 and up. It should work, but it does. We believe it worked on older versions of FM that we used in the past, but it won't work now. (We suspect some unannounced tinkering by Adobe that has had unintended consequences...) Looks like we are forced to drop the whole attribute idea and just use the system variable <$chapnum> to generate the work package number and basically treat it like text so that it retains the leading zeroes, which would normally be truncated by FM. But, that means essentially hard-keying values into each file, which is a step backwards, in my mind, from what FM should be able to do for us automatically. 1. What changed between 6.xx and 7.2 to make attributes a no-go on the Reference page? 2. What is everyone else who does 40051-2 compliant mil spec pubs doing for in each package? Is there another obvious approach I am missing? 3. Am I being completely addled or was there really a way to do this in the "olden days"? TIA! Randall C. Reed Senior Technical Writer Technical Publications Total Life Cycle Support Force Protection Industries, Inc. (o) 843-574-3899 (c) 843-906-5522 This e-mail is intended solely for the person or entity to which it is addressed and may contain legally privileged and CONFIDENTIAL INFORMATION intended solely for viewing by the addressee. If you are not the intended recipient, you should immediately stop reading this message and delete it from your system. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. Please notify the Helpdesk at helpdesk at forceprotection.net if you have received this message in error. This material contains confidential and proprietary information of Force Protection, Inc. and its subsidiaries. Copying this material or disclosing such information to others without the Company's prior consent is prohibited. This material also contains technical data relating to a "Defense Article" within the meaning of the International Traffic in Arms Regulations (22 CFR Part 120). The transfer or disclosure of this information to any non-U.S. person or company without an export license approved by the United States Department of State, Directorate of Defense Trade Controls is prohibited under federal law.
RE: Using Attributes on the Reference Page
Hi Randall, I don't think there was anything in the olden days that stopped working on later versions. I would suggest that you look at FrameScript as a way to automate adding the required leading zeros. If you can spell out your exact requirements, I can help you determine what is possible with FrameScript. I looked at this problem some time ago for a mil-spec client, and we were able to come up with a FrameScript solution that would largely automate the process. Let's face it: FrameMaker is a great publishing platform, but sometimes it needs help to overcome some of its limitations. This is not the kind of task you want to maintain by hand, especially when it may be possible to automate it inexpensively. If you want to pursue this further, please contact me off-list. Thank you very much. Rick Quatro Carmen Publishing Inc. 585-659-8267 r...@frameexpert.com www.frameexpert.com http://www.frameexpert.com/peace/ FM Pilgrims: We are trying to perfect some standard TOC and Index features in the Reference pages and are having "issues" with things that apparently used to work in 6.xx and don't appear to work anymore with Structured 7.2: This is a MIL SPEC 40051-2 project, which requires a 4-digit work package number element () for each file, from 0001 to approx 0400+. The leading zeroes are crucial, as the spec requires four-digits to appear on the page, page number, TOC, and Index. Problem: We cannot get Frame 7.2 to recognize the coding to pick up the attribute , which sets the number of zeroes to 3 for WPs 1 to 9, 2 for WPs 10 to 99, and the default 1 for WPs 100 and up. It should work, but it does. We believe it worked on older versions of FM that we used in the past, but it won't work now. (We suspect some unannounced tinkering by Adobe that has had unintended consequences...) Looks like we are forced to drop the whole attribute idea and just use the system variable <$chapnum> to generate the work package number and basically treat it like text so that it retains the leading zeroes, which would normally be truncated by FM. But, that means essentially hard-keying values into each file, which is a step backwards, in my mind, from what FM should be able to do for us automatically. 1. What changed between 6.xx and 7.2 to make attributes a no-go on the Reference page? 2. What is everyone else who does 40051-2 compliant mil spec pubs doing for in each package? Is there another obvious approach I am missing? 3. Am I being completely addled or was there really a way to do this in the "olden days"? TIA! Randall C. Reed Senior Technical Writer Technical Publications Total Life Cycle Support Force Protection Industries, Inc. (o) 843-574-3899 (c) 843-906-5522 ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: Using Attributes on the Reference Page
2009-12-11-05T14:20Z Randall - I have no interest in Carmen publishing other than being a satisfied customer. Early this year, we were using FrameMaker 7.1p116 (unstructured) on a project to conform to US DOD MIL-STD 40051-2. We ran into the same problem and contacted Rick Quatro of Carmen Publishing. He produced a FrameScript script for us: SetWorkPackageNumbering.fsl. Worked like a charm. We're now working on a project to conform to US DOD MIL-HDBK 2361C (AB) and MIL-STD 40051-2 and such. I recommend you contact him and ask him to adapt the above script to work with both unstructured and structured files. If he adapts it, we'd be interested in getting the updated version. Rick's contact information follows. / Rick Quatro r...@frameexpert.com 585-659-8267 / Also, I invite and encourage you to report the problem and request the feature as I did through: http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform Good luck and regards, Dave Stamm Publications Specialist, Senior Staff General Dynamics C4 Systems, Inc. Battle Management Systems Division 1700 Magnavox Way, Suite 200 We'll hit your targets from here.(tm) Fort Wayne, Indiana 46804-1552 US tel: 260-434-9620 fax: 260.434.9606 dave.st...@gdc4s.com http://www.gdc4s.com/ This message and / or attachments may include information subject to GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message. -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Randall C. Reed Sent: 2009-December-11-Friday 08:41 To: framers@lists.frameusers.com Subject: Using Attributes on the Reference Page Importance: High FM Pilgrims: We are trying to perfect some standard TOC and Index features in the Reference pages and are having "issues" with things that apparently used to work in 6.xx and don't appear to work anymore with Structured 7.2: This is a MIL SPEC 40051-2 project, which requires a 4-digit work package number element () for each file, from 0001 to approx 0400+. The leading zeroes are crucial, as the spec requires four-digits to appear on the page, page number, TOC, and Index. Problem: We cannot get Frame 7.2 to recognize the coding to pick up the attribute , which sets the number of zeroes to 3 for WPs 1 to 9, 2 for WPs 10 to 99, and the default 1 for WPs 100 and up. It should work, but it does. We believe it worked on older versions of FM that we used in the past, but it won't work now. (We suspect some unannounced tinkering by Adobe that has had unintended consequences...) Looks like we are forced to drop the whole attribute idea and just use the system variable <$chapnum> to generate the work package number and basically treat it like text so that it retains the leading zeroes, which would normally be truncated by FM. But, that means essentially hard-keying values into each file, which is a step backwards, in my mind, from what FM should be able to do for us automatically. 1. What changed between 6.xx and 7.2 to make attributes a no-go on the Reference page? 2. What is everyone else who does 40051-2 compliant mil spec pubs doing for in each package? Is there another obvious approach I am missing? 3. Am I being completely addled or was there really a way to do this in the "olden days"? TIA! Randall C. Reed Senior Technical Writer Technical Publications Total Life Cycle Support Force Protection Industries, Inc. (o) 843-574-3899 (c) 843-906-5522 This e-mail is intended solely for the person or entity to which it is addressed and may contain legally privileged and CONFIDENTIAL INFORMATION intended solely for viewing by the addressee. If you are not the intended recipient, you should immediately stop reading this message and delete it from your system. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. Please notify the Helpdesk at helpd...@forceprotection.net if you have received this message in error. This material contains confidential and proprietary information of Force Protection, Inc. and its subsidiaries. Copying this material or disclosing such information to others without the Company's prior consent is prohibited. This material also contains technical data relating to a "Defense Article" within the meaning of the International Traffic in Arms Regulations (22 CFR Part 120). The transfer or disclosure
Using Attributes on the Reference Page
FM Pilgrims: We are trying to perfect some standard TOC and Index features in the Reference pages and are having "issues" with things that apparently used to work in 6.xx and don't appear to work anymore with Structured 7.2: This is a MIL SPEC 40051-2 project, which requires a 4-digit work package number element () for each file, from 0001 to approx 0400+. The leading zeroes are crucial, as the spec requires four-digits to appear on the page, page number, TOC, and Index. Problem: We cannot get Frame 7.2 to recognize the coding to pick up the attribute , which sets the number of zeroes to 3 for WPs 1 to 9, 2 for WPs 10 to 99, and the default 1 for WPs 100 and up. It should work, but it does. We believe it worked on older versions of FM that we used in the past, but it won't work now. (We suspect some unannounced tinkering by Adobe that has had unintended consequences...) Looks like we are forced to drop the whole attribute idea and just use the system variable <$chapnum> to generate the work package number and basically treat it like text so that it retains the leading zeroes, which would normally be truncated by FM. But, that means essentially hard-keying values into each file, which is a step backwards, in my mind, from what FM should be able to do for us automatically. 1. What changed between 6.xx and 7.2 to make attributes a no-go on the Reference page? 2. What is everyone else who does 40051-2 compliant mil spec pubs doing for in each package? Is there another obvious approach I am missing? 3. Am I being completely addled or was there really a way to do this in the "olden days"? TIA! Randall C. Reed Senior Technical Writer Technical Publications Total Life Cycle Support Force Protection Industries, Inc. (o) 843-574-3899 (c) 843-906-5522 This e-mail is intended solely for the person or entity to which it is addressed and may contain legally privileged and CONFIDENTIAL INFORMATION intended solely for viewing by the addressee. If you are not the intended recipient, you should immediately stop reading this message and delete it from your system. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. Please notify the Helpdesk at helpd...@forceprotection.net if you have received this message in error. This material contains confidential and proprietary information of Force Protection, Inc. and its subsidiaries. Copying this material or disclosing such information to others without the Company's prior consent is prohibited. This material also contains technical data relating to a "Defense Article" within the meaning of the International Traffic in Arms Regulations (22 CFR Part 120). The transfer or disclosure of this information to any non-U.S. person or company without an export license approved by the United States Department of State, Directorate of Defense Trade Controls is prohibited under federal law. ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
