FrameMaker 8 Table subheads

I am working with Structured FrameMaker 8. I need to redesign a table so that the rows in the table that display subheads are formatted differently from the table header. The table header has white text on a 100% blue background. The subheads need to be white text on a 30% blue background. The number of rows that appear under each subhead vary, and these rows need to have black text on a white background. How do I create the table subheads? The tables are created automatically when an xml file is imported into FrameMaker.
I am thinking that I can create the subhead 30% blue bar by creating a graphic on the reference page, and then applying it to a paragragh tag. The problem with this is that I can’t figure out how to offset the text so that it is centered vertically in the subhead bar.
Any suggestions will be appreciated.

Art,
let's try to keep things separated:
- I'm not sure *when* the fntcache.dat gets deleted, if you're using a corresponding batch file on STARTUP. To my best knowledge this might be too late, the previous fntcache.dat is already loaded.
- There is no mechanism that can be used to prevent a rebuild of this file, so the question based on "...not rebuilt..." is misleading. The fntcache.dat will be rebuilt in any case.
- The working solution is deleting the file on shutdown. On startup the system either reads no file (hear the system saying "ok, there's nothing I could read now, but I should repair this for future use) or an empty file (system says: "I can't believe this file is empty, I'll have to repair this, but I'm going to accept it for now"). The system does definitely *not* use all the information which (during the next steps of starting up) it will put into the fntcache.dat file in order to rebuild it.
In short words (without having any programmer's knowledge or insight into Windows mysteria), for me the startup process looks like this:
- Switch computer on
- boot and do whatever a PC does on startup
- read fntcache.dat
- rebuild fntcache.dat, if missing, but DON'T read it in again at this time
- continue doing, whatever a PC does...
You see, the trick is only working, because the rewritten fntcache.dat is NOT being read after rebuild. Keep your fingers crossed they don't "fix" this before the ugly FM/PDF bug is fixed.
Regards,
Bernd

Similar Messages

Line width on framemaker table

hi there... i've got an issue on generated the framemaker9 - pdf.
First, After generated to pdf, the table line width looks like not consistent. There are some thin and thick.. how must i do to get the table look nice with the all line is thin...
procedure that i use to build the table is ------> Custom ruling and shading - choose from table (apply ruling style)
Second - what is the difference between click or not at convert CMYK to RGB at settings in PDF Setup ? What exactly the function of convert CMYK to RGB ?

Sha,
If you have two separate questions, please create two posts. (Converting CMYK to RGB is the default behaviour of all previous versions of FrameMaker on Windows. Switching off this conversion is supposed to pass through the CMYK data when saving as PDF. Whether you need this or whether it works completely as you need it, you have to test.)
Regarding line widths: Have you printed the page?
Assuming your line with is set to be 0.5pt. With 72pt/inch and 25.4mm/inch you get a theoretical line width of 0.1764mm.
Your screen has a resolution of maybe 96ppi (pixel per inch) so each pixel has a width of 0.2645mm. You can see that with pixels so wide, you can not successfully show 0.1764mm in 100% zoom size. The software (e.g. Adobe Reader) tries its best, but sometimes fails. The human eye is very good at detecting patterns and recognizes even slight changes inside a pattern very easily.
Your printer may have a resolution of 600dpi (dot per inch) so each dot is as tiny as 0.0423mm. This time the printer may use about 4 dots to create the 0.5pt line, with a 1200dpi printer it could be 8 dots.
So in the end what you see is just a technological limitation. If the so-called "Retina" display makes its way into mass market with >300ppi resolution those effects will fade away...
- Michael

FrameMaker Table of Contents TOC Help Needed

I am working on a book using Frame Maker 8 and I am trying to generate a table of contents for the first time.
The book has several chapters, and I am able to generate a TOC with the Chapter titles without a problem.
Within the chapters, there are outlines. When I generate the TOC with the Heading1Start and Heading1 (marked with roman numerals in the body text), it works fine too.
But then when I add the Heading2Start and Heading 2 (marked with capital letters A, B, C in the body text), it generates the TOC list with only the headings and page numbers but without the capital letters for the paragraph numbers.
Basically, I'm getting something that looks like this:
Chapter 1 ....... 7
I. Overview ... 13
Introduction 13
when what I need is this:
Chapter 1 ....... 7
I. Overview ... 13
A. Introduction 13
How do I fix this?
I apologize if this is a simple topic of if the answer is elsewhere. I searched for an answer in a few places but did not find one.

have you used the <$paranum> building block on your TOC reference page?
I explain this and other building blocks on p.372 of my book. The <$paranum> functionality is the same in FM11 as in FM8.
-Matt
Matt R. Sullivan
co-author Publishing Fundamentals: Unstructured FrameMaker 11
P: 714.798.7596 | C: 714.585.2335 | [email protected]
@mattrsullivan LinkedIn facebook mattrsullivan.com

I can't fathom the reasoning behind ID CS5 tables. Can you help?

I can make ID CS5 tables work, but I don't understand how they work. I should mention that I'm a heavy FrameMaker user, so I'm sure I've got some faulty preconceptions.
In FrameMaker, I'm accustomed to using table styles to automate table formatting. All table formatting info -- e.g., text styles for table titles, headings, and body; rules; cell padding; etc -- is built into the table style and applied with a single click. The text styling information is drawn from preexisting paragraph styles that are associated with the table style. All very straightforward. But in InDesign, things seem a lot more complicated.
InDesign has Table Styles and Cell Styles. I'm unclear on the relationship between the two. You can specify ruling and shading styles in both. I don't understand this.
I've gotten more predictable results with Cell Styles, so I've built most of my formatting info into them. But Cell Styles aren't stand-alone entities. Even though you have to create them, then add them to the Table Style, they have to be associated with a preexisting paragraph style. This seems like a duplication of effort -- two separate styles (cell and paragraph) applying the same text formatting info. The Cell Style does include ruling and shading info, but that shouldn't be necessary since that information theoretically can be entered in the Table Style.
Also, using Cell Styles limits you to one paragraph style per cell. In some cases I need two -- data or text, followed by some bullet points. When this happens I've had to strip out the Cell Style and apply a paragraph style directly. Seems funky.
I don't want to get too deep into the weeds with specific puzzles I've encountered; suffice to say I don't understand how Table Styles and Cell Styles interact and how best to use them to create and format tables efficiently. Do any of you understand the thinking behind ID tables? Can you point to a source that explains it? There's got to be a system there, a set of coherent operating principles, but I haven't been able to discern them.
Sincere thanks,
--Donna Reynolds

semiwool wrote:
I'm not clear how you're able to automate the next-format behavior in FrameMaker. Are you saying that populating a FrameMaker table by importing text from a source, using the convert-to-table option does this because the incoming content has paragraph styles that match existing FrameMaker formats, and that you can't get this in InDesign? InDesign's import options are quite rich. If you need details, search Google for "InDesign text import options" without quotes.
My apologies. I must have done a poor job of explaining the problem, which is: If you apply a Cell Style to a cell, that cell will only permit one paragraph style. If you need to use two styles in the cell, you have to change the Cell Style to None, then do your formatting with a regular paragraph style.
These tables were imported as RTF, which has worked reasonably well. Actually, yesterday I was thinking about the discussion we had re: Frame > ID conversions. The first draft of the tutorial I worked up is done. If interested, I'd be happy to send a copy.
Many thanks for your assistance,
-dr
Try this:
* Create a small table, say four rows by four columns.
* Create a paragraph style named noStyle, based on No Style.
* Create a paragraph style with text color cyan, for the second paragraph in the cel; call it cyan. Leave Next Style as Same Style.
* Create a paragraph style with text color magenta, for the first paragraph in the cell; call it magenta. Set Next style to cyan.
* Create a cell style whose paragraph style is magenta.
* In a table cell, create two paragraphs that use the style noStyle.
* Copy the two paragraphs to another cell.
* In the first cell, apply the magenta style to the first paragraph.
* Select both paragraphs in the cell, or select the cell.
* In the paragraph styles panel, Right-Click the magenta style name.
* In the context menu that appears, click Apply "magenta" then Next Style. The first paragraph remains magenta, and the second paragraph changes to cyan.
* Select the second cell.
* Apply the cell style magentaCell. Both paragraphs are tagged with the magenta paragraph style.
* Select the cell and in the Paragraph Styles panel, Right-Click the paragraph style magenta, and select Apply "magenta," then Next Style. Like the two paragraphs selected in the cell that has no cell style applied, the first paragraph remains magenta, and the second paragraph changes to cyan.
* Copy two paragraphs tagged with noStyle and paste to all the cells in the table.
* Select the whole table.
* Apply the magenta paragraph style to all cells.
* * In the paragraph styles panel, Right-Click the magenta style name.
* In the context menu that appears, click Apply "magenta" then Next Style. The first paragraph remains magenta, and the second paragraph changes to cyan. All the cells have the first paragraph tagged magenta and the second tagged cyan.
* Undo these last steps until all cells have reverted to containing two noStyle paragraphs.
* Select the whole table and apply the magenta cell style.
* In the paragraph styles panel, Right-Click the magenta style name.
* In the context menu that appears, click Apply "magenta" then Next Style. The first paragraph remains magenta, and the second paragraph changes to cyan.
So, with or without cell styles, the Apply Next Style feature efficiently formats multiple-style table cells.
[EDIT] Yes, I'd like to see your tutorial. Click on my name in the sidebar to send a private message, if you don't have my email address already. Thanks for the offer.[/EDIT]
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices
Message was edited by: peter at knowhowpro

FrameMaker 11 file link broken when published out to RoboHelp 10

Hello
I have the Adobe Technical Communication Suite 4 and am trying to test publish a FrameMaker 11 file out through
the FrameMaker publish button to WebHelp (by way of RoboHelp 10).
In the FrameMaker 11, file, I have a link to a PDF that sits down in a subfolder. I have used the following approach:
1. Highlighted text in a FrameMaker table.
2. Chose Special>Hyptertext
3. From the Hypertext panel, I selected Message Client from the Command drop down menu
and in the syntax field I entered: message openfile Foldouts/Foldout1.pdf
4. I then tested the link in FrameMaker by using ALT and CTRL and it works.
5. Next, I saved the FrameMaker file as a PDF (File>Save As PDF) and tested the PDF. The PDF links work.
So with all that said, how come I can't select File>Publish>WebHelp and have the link information carry through to the WebHelp HTM output?
I tried this Publish option straight out of the box and it did not work. I also tried creating a custom RoboHelp template (.XPJ file) and it did not work.
I believe there is a PgfId marker that is generated when the Hyptertext is created in FrameMaker (using the process stated above), but that marker is not getting
translated into an HREF, once it gets published out through RoboHelp 10.
I also tried saving the FrameMaker 11 file directly as an HTML file using the FrameMaker 11 - File>Save As HTML process, but no links carried through
using that process either.
I do not know if this is a FrameMaker issue or a RoboHelp issue, so I am now posting this in both forums.
If someone could point me in the right direction, I would really appreciate it.
Are there certain steps one must do to preserve FrameMaker Hypertext links that get published out through RoboHelp 10 to WebHelp?
Thanks in advance for your suggestions.
Jim

I've deleted the other post as the question is being addressed here. Folks who use Fm only would not be able to help so this is the correct forum as Jeff as explained.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Table Problems (Cell Shading and Default Format from EDD and Template)

I have two problems related to tables using Structured FrameMaker (Version 10), whilst in-processing XML.
I've designed two different table formats in my Template; Format A with black shading - 30% for THead and 3% for row, and Format B with blue shading - 30% for THead and 3% for row.
If I create a structured document from scratch and insert a table, I get the required Black (30%) and Black (3%) shading.   If I then insert an informaltable, I get the required Blue (30%) and Blue (3%) shading.
Although I've given the two table types different default formats in the EDD - Format A for table and Format B for informaltable - when I open the XML file (normally) from within FrameMaker I notice that all the tables default to Format A (black shading).   When I then import my EDD table should stay as Format A and informaltable should change to Format I.   This doesn't happen; they all stay at Format A.
I can change informaltable by manually applying Format I, this worksI. Obviously, with long documents which might have hundreds of tables we can't afford the time and manpower to do such things one at a time by hand.
Do any of the Structure gurus have a fix for this, or can someone give me a hint of what I might be doing wrong?
The second, but related question was a general one.   I see that Adobe says
"Tables
FrameMaker table formats are only partially integrated with the structure model. The content of
a FrameMaker table is always fully structured, but the control over cell border ruling is limited and
there is no structure format control over cell shading."
I believe it could be useful to apply cell shading on an individual cell basis (although I'm not sure whether this is possible at the XML level - where someboddy might give an element an attribute of, say, shading (with options, such as, green, red, blue, yellow all at, say, 30%, with a default of red, for example.
I've seen that there has been mention of plugins to achieve cell shading in structure; does anyone have an experience with such things, more to the point, can anyone point me in the right direction?   I don't mind paying fo a solution which I can implement myself.
Any help or advice would be much appreciated.
Regards
Chris

Hi,
could you please provide some details on the EDD, RWR and some example XML?
My wild guess goes into the direction of the RWR not containing enough information that get written out into XML.
We're using table formatting with shaders too (using an attribute to control the specific formatting of each table) and it works like a charm in FM9 and FM11 when roundtripping.
The context rules are used in the table group (i.e. tgroup element). This might already solve the issue .
Cheers Alex

Table headings and column/row sizes

I have mapped my FM table format to a table style defined in my CSS. However, I have the following issues with the resulting RoboHelp tables:
I have a header row in the FrameMaker table, but the header doesn't come over into RH. All of the table rows are <td> instead of <th>. Therefore, the shading defined in my CSS for the table header row does not appear.
A bunch of inline formatting that I don't want is coming over, defining the table width and the row width and height. Here's an example:
<table class="formatA" cellspacing="0" width="600">
    <tr style="height: 18.00pt;">
        <td style="vertical-align: top; padding-left: 6.00pt; padding-top: 3.00pt;
             padding-right: 6.00pt; padding-bottom: 3.00pt;" width="198"><p>Report/Visualization</p></td>
        <td style="vertical-align: top; padding-left: 6.00pt; padding-top: 3.00pt;
             padding-right: 6.00pt; padding-bottom: 3.00pt;" width="402"><p>Description</p></td>
    </tr>
Is there any way to get RH to recognize table header rows?
Also, is there any way to prevent the size information from coming over? What I'd like is for the table width to be 100% and the cell widths and heights to be determined by their content (which would happen automatically if the inline formatting weren't added).
If there isn't a way to accomplish this, then I'd probably be better off not trying to map the table styles and just going with "Source". The sizes would still be fixed, but at least the shading would appear.

Forget FM for a moment. I think that if you create a table in RoboHelp using TH you will find RoboHelp simply does not understand TH.
The more people who report a bug or request a feature, the more likely it is to be actioned. Please follow this link.
http://www.Adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

FrameMaker to InDesign conversion?

I have FrameMaker 7.2 and InDesign CS3. I have a few book projects in FrameMaker that I would like to convert over to CS3. However, one of them has extensive (hundreds) of cross-references (footnotes, basically), and the other has been indexed. I don't mind losing formatting, since I figure I'll be creating a new format in InDesign anyway, but I do mind losing the cross-references and the indexing.
Is there a way to import my FrameMaker files into InDesign that will retain cross-references and indexing?
What I've tried:
I tried saving a test FrameMaker file as RTF, text, and MIF, but InDesign didn't recognize any of these formats. (Though text and RTF would lose my indexing and cross-references, I was trying to see if InDesign would recognize ANY format.)
I found a service online that charges rather steeply for converting from FrameMaker to InDesign, but that isn't an option.
Thanks in advance for any help that is offered.
regards,
Marina

semiwool wrote:
But that tool didn't work with our test files. At the request of the DTP Tools folks, I ftp'd two of our archives. They acknowledged receiving them, but I haven't heard anything since. I'm guessing that these files are too complex for their filter. I should explain that these files began life as design-y Quark files, which were later converted to FrameMaker. So there are a lot of design elements you might not often find in FrameMaker documents.
InDesign table styles and table cell styles are very smart and offer more formatting options than FrameMaker, but InDesign doesn't sort tables, and doesn't have the FrameMaker column-width settings like "make current column same width as column x," or "make selected column(s) as wide as its longest text line."
Here's where I get really confused: ID tables.
In FrameMaker, the Table Tag contains the information about rules. But when I build rule information into an ID Table Style, nothing happens. I get no rules at all unless I ALSO specify rules in the Cell Style. What am I missing here?
Also, this business of associating cell styles and paragraph styles seems like an unnecessary pain to me. What am I missing here?
Also, ID doesn't make a distinction between the title block and heading rows, which is a problem for us because each of these elements is formatted differently in our tables.
Also, ID doesn't have the "table continuation" variable.
Whew! 8-)
There's an InDesign table-sorting script (search Google) somewhere around, but I don't think anyone's yet created scripts for these other features.
As always, submit format feature requests at https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform. The more requests they receive, the better chance it will happen sometime in a future release.
HTH
Regards,
Peter
The DTP Tools' MIF Filter for InDesign commercial plug-in converts conditional text and cross-references.
It's not surprising that non-standard FrameMaker methods and techniques don't convert well with a tool designed for standard FrameMaker, so the workarounds to wrangle Quark originals into FrameMaker may be helpful to the DTP Tools folks to work with going forward. It's always OK to drop a note to follow-up on their progress with your files.
Yes, InDesign turns certain table properties over to cells. Not necessarily better or worse than FrameMaker, just different. One example is that FrameMaker's paragraph format Table Cell margin property is a Table Cell offset property in InDesign. That's consistent with InDesign's text frame offset property; FrameMaker has no text offset property within a text frame that corresponds to this InDesign property.
FrameMaker table formats save the paragraph formats in the first row of table cells. When you create a new FM table with a given format, the last-created table's number of header and body rows, and table columns, are the initial suggestions; the first row of cells has the saved paragraph formats, and so do the additional rows.
True, InDesign tables have no title element. Using the paragraph in which you create the table for the title text probably will do the same thing as your FrameMaker table titles. Search Google for "indesign table continuation variable" without quotes for tips on emulating them.
You'll get used to the fact that these two products are different. One major difference you'll probably see going forward, is that the familar basic FrameMaker tool set that you've grown used to, isn't going to change markedly, even as its user interface, interactive-media options, outputs and frameworks like XML, DITA, etc, do change; compare this to InDesign's steady growth in technical-publishing features, release-by-release. The more you make use of the feature request form, the more likely you'll see some of your requests come to a future release.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

Framemaker XML Output Issue

I have an issue with an attribute not being exported to XML from FM8.
Here is the excerpt from the DTD:
<!ELEMENT std.table.header (std.table.row+)>
<!ATTLIST std.table.header
cols CDATA #REQUIRED
rowsep CDATA "1"
>
The first issue I had was "cols" not showing up as an attribute in the Structured View. I solved with issue (with the help of MarttiP) by adding it to the EDD as shown below:
Element (Container): std.table.header
General rule: std.table.row+
Attribute list
Name: cols Integer Required
Now the issue I am having is on export of the XML, the "cols" attribute is not being exported and I am getting an error "required attribute 'cols' not provided". Any suggestions?

The std.table.header element will need to be mapped to a new table structure in FrameMaker. While FrameMaker handles CALS tables without the need for additional read/write rules, you will have to provide a full set of rules to create the correct FrameMaker table mapping.
The std.table.header is only a part of a table, it's used in many places as the header for a variety of non-CALS tables. For each of these tables you will need to define a new FrameMaker table structure. I'll attempt to provide the solution for the first of these special tables...
In the DTD the following structure is defined:
<!ELEMENTaal (title, std.table.header, (aal-category+ | aal-entry+))>
<!ATTLISTaal
%frameatt;
>
<!ELEMENTaal-category (title, aal-entry+)>
<!ATTLISTaal-category
%frameatt;
>
<!ELEMENTaal-entry (nsn+, dcpno, ui, qty)>
<!ATTLISTaal-entry
%bodyidatt;
>
The aal element is probably intended to be displayed as a table. The std.table.header must be fitted into a suitable structure for FrameMaker, for example:
In this example new FM table part elements have been added to the EDD to provide the required table structure. On import from XML FrameMaker will create the missing elements, Read/Write rules must be used to drop them on export. The table parts used in the example are:
Element name
FM element type
aal
Table
std.table.header.title
Table title
std.table.header
Table header
std.table.header.row
Table row
std.table.header.entry
Table cell
aal.table.body
Table body
aal-category
Table row
entry.title
Table cell
aal-entry
Table cell
nsn, dcpno, ui, qty
Container
You may ask whether it's worth putting this much effort into formatting data as tables, in this example maybe not, but there will be times when it's the only way to go.
One of the problem areas are elements that have to be defined as different FM element types depending on context. In this example aal/title has to be reneamed to std.table.header.title and aal-category/title is renamed to entry.title. I would use XSLT to transform the elements on XML import and export.
The easier alternative t all of this is to forget about using tables and format the data as simple lists.
I hope this has been useful.
Regards
Ian

Conversion Table Questions: problems converting tables to structured

I'm in the process of converting unstructed FM8 docs to structured docs using FM10 and DITA structure. Right now I'm trying to build a conversion table to structure the docs, but I'm having a lot of trouble with the tables. The main problem seems to be with the tgroup element since I can't figure out how to get the thead and tbody to wrap in the tgroup element.
Here is an example of one of the tables I'm trying to structure:
This is the Table section of the conversion table I've had the most success with:
And this is the result:
As you can see, the thead and tbody elements are not wrapped in tgroup and the structure is invalid. I've been playing around with the conversion table for several days now and can't seem to figure out how to fix this. If anyone has any suggestions, they would be greatly appreciated!
Thanks,
D'Arcy

D'Arcy,
Here are a few observations that might help:
1) The structure you use within FM (which is what the conversion table helps create) need not be exactly the same as the structure you use in XML.
2) Do not confuse the element named table with a FrameMaker table.
3) As Michael has pointed out, the CALS table model used by DITA is a five-level structure:
table
tgroup
    tbody
       row
         entry
while the FrameMaker table model has 4 levels:
table
tbody
    row
      cell
4) FrameMaker can map between the 5-level structure and the 4-level structure in one of two ways, controlled by the element definitions (usually specified in an EDD), the read/write rules, and the DTD:
a) The element named table can be a container while the element named tgroup is the actual table. This model has a closer correspondence between the FrameMaker and the DITA table structure. Michael has pointed out one of its biggest weaknesses. If a FrameMaker table (regardless of its element name) has a title, then FrameMaker repeats the title on each page of a multipage table. However, if the element named table is a container and the actual table is an element named tgroup, the title is a container preceding the table and this automatic repetition does not happen.
b) If you are sure that your tables will always consist of a single tgroup, you don't have to use the tgroup element within FrameMaker. Make the element named table a FrameMaker table and include the read/write rule:
element "tgroup" unwrap;
FrameMaker will recreate the tgroup element whenever you save a document as XML. This model allows you to make the table title a FrameMaker table. However, you cannot use the element named title as both a FrameMaker table title and a container. Typically, therefore, people use the element named title as a container that is the title of things like chapters and sections and use an element named something like tabletitle for the title of tables.
Read/write rules like:
element "title" is fm element:
element "title" is fm table title element "tabletitle"'
let you save your documents as XML with both title and tabletitle represented as <title> in XML. You'll need to use a custom client or XSLT to map the XML element named title to either title or tabletitle depending on whether the XML element occurs within a table or not.
5) Your conversion table had one row with T: in column 1 and another with T:Format A in column 1; one mapped to table and the other to tgroup. The row with T:Format A would apply to all tables with the specified format, the other row would apply to all tables with other formats. These conversion table rows do not define a relationship between table and tgroup. Map T: to table if you want the model in 4b) above and to tgroup if you want the model in 4a). In the latter case, use an additional row with:
title?, tgroup
in column 1 and table in column 2.
     --Lynne

Problem with text alignment in the panelheader

Hi,
We are using <af:panelheader> in our jspx file. We are using custom CSS for alignments. The text we are displaying inside this panel header is top-aligned by default. But we want to align this text to middle. In our custom CSS file, we tried with different options to align this text to middle(ex: vertical-align:text-bottom;caption-side: bottom;...). Please guide me on this like which option to use.
Our CSS code for panelheader is this:
.AFHeaderLevelOne,.x1x,H1.af_panelHeader,H1.x20,H1.af_showDetailHeader,H1.x21,.af_messages_header,.x24,.p_OraProductBrandingCompactText,.x5b,.PortletHeaderText,.x6n,.PortletHeading1,.x6o,.PortletSubHeaderText,.x6u,.portlet-section-header,.x73,.portlet-section-subheader,.x77,.portlet-table-header,.x7a,.portlet-table-subheader,.x7e {caption-side: bottom; background-color: rgb(233,233,209);vertical-align:text-bottom;white-space: nowrap; height: 37px; font-family:Tahoma;font-size:17px;color:#9c7200;margin-bottom:0px;margin-top:0px;font-weight:bold}
and panelHeader code inside jspx is this:
<afh:rowLayout id="rowLayout1" width="100%" >
<afh:cellFormat columnSpan="4" height="37">
<af:panelHeader text="Add Law Firm"/>
</afh:cellFormat>
</afh:rowLayout>
Thanks & Regards,
Yeshwanth.

Hi,
try
.AFHeaderAlias{vertical-align:text-bottom; white-space: nowrap; height: 37px; font-family:Tahoma;font-size:17px;color:#9c7200;margin-bottom:0px;margin-top:0px;font-weight:bold}
or
h1.x20{vertical-align:text-bottom; white-space: nowrap; height: 37px; font-family:Tahoma;font-size:17px;color:#9c7200;margin-bottom:0px;margin-top:0px;font-weight:bold}
both work
Frank

I can't import a Frame document that is longer than 2 pages

I've gradually cut down the size of a 70 page document until I got it to import at 2 pages. Have had this problem with other documents in this project but not to this extent. Usually just had to split into two files. After several attempts, it is not unusual for RH to crash.
The files have had all page numbers removed from cross-references.
There are no unresolved cross-references.
RH 8.0.2.208
Framemaker 7 (also tried a Frame 9 doc)

I believe I found the problem. I sometimes "stack" Framemaker tables, meaning their markers run together and aren't separated in any way. I was able to perform the RH import after I "unstacked" these tables.

How to withdraw a wrong open and save of a structured fm file in unstructured mode?

I opened a structured fm file wrongly in unstructured mode and saved it. When I opened this fm file again in structured mode, the structure view has been blank. Does anyone no how to withdraw this?

Dragon,
   To expand slightly on what Alex and Russ have said, whenever you delete content from a FrameMaker document and save the result, the deleted content is gone. It doesn't matter whether the deleted content is the element hierarchy or text and graphics in the document. A recent backup, whether a version of the file that you explicitly saved or one created by FrameMaker's automatic backup, is
   Alex mentioned that a conversion table might help recreate the document's element structure. His comment assumed that a conversion table was used somewhere in the history of this document. Whether or not that is the case, you can create a new conversion table specifically for this document. If you haven't looked at conversion tables yet, a conversion table is a FrameMaker table that describes how to use tagging in an unstructured document to create an equivalent structured document. How successfully it creates the desired structure depends very much on the nature of the tags used in the unstructured document and the desired element structure.
    --Lynne

Glossary tab doesn't display and Glossary pop ups don't work

TCS 3.5 (FrameMaker 10, RoboHelp HTML, version 9)
Windows XP version 5.1 sp3
Internet Explorer 8.0
My apologizes if this should be in a different forum. Also, from searching I have found that the problem is usually that the DLL has not been loaded -- I have done that. So I am at a loss. Thanks in advance for your help!
Problem: My .chm output does not have a Glossary tab and the Glossary text pop-ups in my topics do not work.
Background: Since I am new to TCS 3.5 I'm going to give my entire process. Quite frankly I'm not even sure if my entire process is correct.
Steps:
Before I began: I loaded the HHActiveX.dll. Here's the proof:
Create a blank project.
Import master page (File > Import > Master Page).
Load project settings (File > Project Settings > Import).
Link FrameMaker Book (File > Link > FrameMaker Document)
Configure Properties (Right-click the book file in RH and click Properties).
In Properties, select Convert FrameMaker Table of Contents and give a name.
In Properties, select Convert Glossary and give a name.
In Project Manager pod, right-click the Glossary topic (System Management GLO) and click Set as Default.
Update Project (File > Update > Update All).
Run Glossary Hotspot Wizard (when running wizard, select the glossary topic that was set as default in step 8)
Edit the UpdateMarkedGlossaryTerms.jsx script (change the GlossaryName variable to the Glossary topic created in step 8 and change the GlossaryStyle variable to TextPopUp)
Run Update Marked Glossary Terms script (In Script Explorer pod, right-click the UpdateMarkedGlossaryTerms.jsx script and click Run).
Run graphicinreferencepages.jsx script (this inserts my note graphics from FM reference pages)
Configure Microsoft HTML Help layout. Here's the properties file:
16. In the properties file I selected the Glossary topic that I had set as my default in step 8.
17. Click Save and generate.
Result: In the .chm file (and in View Selected Item in RH) when I click a glossary term in a topic, I get "This program cannot display the webpage". Also, the Glossary tab is not displayed.

Welcome to our community, Linda
In RoboHelp, if you open the Glossary pod (View > Pods > Glossary > Select Glossary) do you see terms and definitions listed there?
If not, that would explain it as the Glossary has no entries.
Assuming it does have entries, you may simply need to enable the tab by clicking View > Pods > Project Set-up. Expanding the Windows section in the pod and double-clicking your CHM window.
A CHM window looks like this:
If you don't see a CHM window, you will need to create one. If you do see a CHM window, double-click it. Then ensure the Glossary is enabled.
Keep us posted! Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

Non-Breaking Hyphen in MIF String ?

I'm using a spreadsheet (LibreOffice Calc) to generate the MIF for a Framemaker table: Paste in lines of tab-separated part_numbers and descriptors, copy out raw MIF that opens in Frame as a 3-column table with callout#, part_number and descriptor, each having a unique Xref Marker with marker text based on the p/n & descriptor. It works (including escaping any Frame-special chars in the descriptors), except for one extra feature I'd like to have.
I'd like to make all dashes in the part-numbers into non-breaking hyphens (\x15). Using the Calc function SUBSTITUTE, I can change any character to any arbitrary string. Part numbers may have zero or more dashes.
So for raw string 123-456A, where "-" is an NBH, I'd generate:
<ParaLine <String `123-456A'>
According to the MIF(7) reference, either of these MIFs should work:
<ParaLine <String `123\x15456A'>
<ParaLine <String `123<Char HardHyphen>456A'>
They don't.
They both throw a parsing error on open in Frame.
This doesn't work either:
<ParaLine <String `123\\x15456A'>
It ends up as a literal \x15 in the final table.
This Calc function doesn't work either (where decimal 21 is hex 15):
=SUBSTITUTE($RawData.A3;"-";"CHAR(21)")
The character doesn't survive copy and paste through a plaintext editor, even if a raw 0x15 is valid MIF (which it may not be).
This is FM7.1 Unix, so I can't use the Unicode code point for an NBH (this is the suggest route for MIF8 or later).
The following MIF is valid, but may require more parsing of my strings than I care to invest in:
<String `123'><Char HardHyphen><String `456A'>
I could use:
=SUBSTITUTE($RawData.A3;"-";"'><Char HardHyphen><String `")
If I were sure that no partnumbers began or ended with a dash.
Any other ideas?

<String `123\x15456A'> parse fail
<String `123 \x15 456A'> nbh, but leading space (fail)
<String `123\x15 456A'> nbh, no spaces, works perfectly, thank you
Amusingly, if you re-save the same document as MIF, Frame(7) re-codes the nbh as:
<String `123'>
<Char HardHyphen>
<String `456A'>
... as does MIF9, saving as MIF9,
even though the MIF9 reference says that as of MIF8, HardHyphen and 9 of its pals are no longer represented by name - use the UTF-8 code points. I'm guessing that intended policy change had some unintended results.

FrameMaker 8 Table subheads

Similar Messages

Maybe you are looking for