Long Section Names

Log Out | Topics | Search Moderators | Register | Edit Profile

Author Message Christopher Borcsok Senior Member Username: ckb Post Number: 6 Registered: 06-2013 Posted on Sunday, August 11, 2013 - 05:21 pm:    PageFormat question: how to address the really really long section names that are especially prevalent in Divisions 21 to 28? If I follow CSC PageFormat, some client project names can be long too, and screw up my word doc headers where tab characters tend to hit each other. Jeffrey Wilson CSI CCS Senior Member Username: wilsonconsulting Post Number: 106 Registered: 03-2006 Posted on Monday, August 12, 2013 - 10:28 am:    I handle long names by wrapping to a 2nd line in the section title (which appears only on 1st page) and using a shortened version in footers since that is a reference for the reader's convenience -- not necessarily the full identity for the section. For project identification that involves more than a single line, I simply adjust all footers to accommodate it. I avoid headers, placing all info in footers. I find use of both a header & footer distracting when reading specs -- which I suppose defies PageFormat. David E Lorenzini Senior Member Username: deloren Post Number: 145 Registered: 04-2000 Posted on Monday, August 12, 2013 - 11:32 am:    Christopher Some of the recommendations in PageFormat are slightly different for CSC than those adopted for CSI. CSC prefers to include the Section number and Section title in the header and omit those items in the body before Part 1. There are six items designated in the header and two in the footer. I can see where you might have a problem with long section names in conjunction with long project names. Also, CSC chose a PageFormat header that does not include a Project Location. PageFormat for CSI recommends that header and footer information be separated into two categories to make the work of updating them for each project more efficient. The project information that has to change for each project is located in the header where it is the easiest to change. The Section information that does not change for each project is located in the footer. My answer to your question is to reorganize where you locate your project and Section information so that they do not conflict with each other. Take a look at PageFormat pages PF.14 and PF.15 to see if you might find a solution there. David Lorenzini, FCSI, CCS Architectural Resources Co. Christopher Borcsok Senior Member Username: ckb Post Number: 7 Registered: 06-2013 Posted on Monday, August 12, 2013 - 09:36 pm:    In order to maximize speed of reusing specs, and for some of the custom macros I've written (including my table of contents generator), I have used a field code in MS Word (specifically "Title") to store the Section Name, and I use "Subject" likewise for the Section Number. Another macro I've written basically "inserts" the content of another word file ("Header.docx" and "Footer.docx") which includes all the project specific header data, and the fields, which when updated adopt the section name in the individual section. I've tried using tables in the headers, but this causes more problems due to the way Word actually treats tables internally. Unfortunately, I don't know of a way to work this with a deliberate carriage return within the field, unless I unlink the field after updating... Or I could break the section name for these purposes across several fields... I'll need to think about this approach. What are the odds of CSC revising their PageFormat to address this incidental oversight (Section Names in MF'95 were always shorter), or shortening some of the standard section names? David E Lorenzini Senior Member Username: deloren Post Number: 146 Registered: 04-2000 Posted on Monday, August 12, 2013 - 09:50 pm:    Since you are inserting a file into the header, you could customize the file so a long title pairs with a short project number to fit long section names. If you want the title to break over two lines, you could use hard spaces in the title except where you want it to break. David Lorenzini, FCSI, CCS Architectural Resources Co.