Autonumber Format. 01, 02, 03...

Hello ,
Simple question; can you format numbering in the Paragraph Design, Autonumber Format to count 01, 02, 03... 10, 11 etc.?

bowen192 wrote:
Hello ,
Simple question; can you format numbering in the Paragraph Design, Autonumber Format to count 01, 02, 03... 10, 11 etc.?
You might be able to fake it with a new paragraph format whose numbering prefix contains the text character zero, and the number counter (placeholder) that begins at 1; use it for numbers below 10. Use a separate paragraph format whose numbering sequence begins at 10, and continues from the previous paragraph (9).
This might take some fiddling.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

Similar Messages

Autonumber formats change after topics are linked across projects

We are going from Robohelp HTML x5.0.2 to Robohelp HTML 8.0.2.208, so there is obviously a huge learning curve that we are working through. We generate to WebHelp and merge 15 projects into a published master. Our users view the output on our intranet using Internet Explorer 7.
We loved the autonumber format feature in version 8 (particularly the additional bullet styles available and no longer needing to manually renumber steps when something was inserted or deleted), but have run into a problem.
The autonumber items work fine in the projects and when generated and published into the merged master, but when we need to add a link from a topic in one project to a topic in another project it changes the bullets and numbering.
Example:
We have a topic in Project A that references a topic in Project B (both projects are part of the merged master).
We insert a link in the Project A topic to the topic in Project B (using Insert Hyperlink - Link To - File). Everything in both A and B look fine at this point.
We preview the topic Project A by clicking on "View Selected Item" (eyeglasses) and then click on the link we inserted to validate it works. This causes the topic in project B to now have stutter-text for bullets and numbers (i.e., what used to say "1. Step" now says "1. 1. Step"). As more links are added to that topic, it adds more bullets and numbers to the linked topic:
1. 1. 1. Procedure
● ● ● Bullet
o o o Bullet2
§ § § Bullet3
□ □ □ Bullet4
This does not happen when adding links to topics that are in the same project, only when linking to topics that are in another project.
All of our topics are created directly in RoboHelp; we do not import files from Word, FrameMaker, etc. Each of our projects has the same style sheet (we created 1 CSS file and copied it into each project so that they were all identical).
All of our version 8 projects were created from scratch in version 8, and we have been importing our version 5 topics one by one (and deleting the version 5 styles assigned to them), then applying the applicable version 8 style to each line. We have attempted creating brand new topics in version 8 to make sure no old legacy version 5 code imported from an old project was causing the issue, and it still happens. We have tried manually cleaning up the HTML code for the topic and it happens again once a cross-project link is added back to that topic. We also tried the "Convert RoboHelp edited topics to HTML" to try to get around the XHTML restrictions and it still happened to everything that was an autonumber format, so it appears the issue is something with that one of these. We created styles for each autonumber format we wanted to use (using the options available for Paragraph styles in the Robohelp Style editor), this is a sample of one of them:
p.Bullet {
 list-style: rh-list;
 x-list-class: rl-p-Bullet;
 x-list-level: 1;
rh-list.rl-p-Bullet {
 x-level-count: 1;
 x-lvl-1-format: "<x>";
 x-lvl-1-type: disc;
While it would be really great to have the additional features of the autonumber format, it may not be a viable option for us since it is only available on the paragraph level and Robohelp 8 does not appear to play well with bullets and numbers in anything other than the list level. I'm thinking I may need to abandon our current style sheet that uses autonumbering and start over with a new style sheet using only the limited bullets and numbering available on the list level (or possibly go old-school and just use the bullet and number toolbar buttons to add formatting to normal text). We are about 8,000 topics into our conversion of 40,000. Any suggestions are greatly appreciated. Thanks!

I'd love to send you the test projects I set up, but unfortunately my company has blocked that ability. I created brand new blank projects in Robohelp 8 using the default style sheet with an autonumber bullet and numbered step added and nothing else. I thought this bare-minimum approach would be the best way to make sure it wasn't something we had set up incorrectly that on our end. I used the default First Topics in each project and added numbered and bullet texts using the style sheet to Project 1 and then added a link to that topic in Project 2. I didn't even generate the projects and I still had the issue when I previewed the Project 2 topic and clicked the link.
I've attached a copy of the info on the topic in Project 1 and the code behind the scenes for it below:
First Topic
1. 1. 1. Procedure
o o o Bullet
o o o Bullet
2. 2. 2. Procedure
Code before link in Project 2:
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>Procedure<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>Procedure<?rh-list_end ?>
</body>
</html>
Code after link in Project 2 was added and clicked:
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>1.     Procedure<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>2.     Procedure
Code after link in Project 2 clicked a second time:
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>1.     1.     Procedure<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Bullet" ?>o       o       Bullet<?rh-list_end ?>
<?rh-list_start level="1" an="1" class="rl-p-Procedure" ?>2.     2.     Procedure
Logically there is no reason that clicking on a link that is outside of the project should be able to recode the topic being displayed, but it is.

Need help with Autonumber Format

We are using unstructured FrameMaker 12 on a Windows 7 platform (64 bit).
We need to number questions in an FAQs section, that includes the "Q" in bold followed by a colon that is not in bold.
This is what the new paragraph style needs to do:
1.[tab][bold]Q[Default ¶ Font]:[tab]What happens when XYZ?
[tab][bold]A[Default ¶ Font]:[tab]This is what happens.
We would like for the number and "Q:" to appear automatically and be formatted correctly with the new paragraph style, so all we have to do is type the question. (We would prefer not to use "Q##:" because it would require a unique indentation distance in the template.)
The "A:" should also be indented and formatted correctly.
Both the "Q:" and the "A:" would wrap around to the same indentation for long text strings.
Can anyone provide the "building blocks" that can make this happen? Is this possible?
I tried to search for the answer in this forum and on the Web. I apologize if this is answered somewhere already.
Thanks in advance.
Tim

This is certainly possible! assuming I've understood the question correctly, of course …
All you need is a pair of paragraph formats, one for the questions and one for the answers, and a character format for the labels. Set the paragraph properties so that the numbering can be outdented, and set the numbering properties to add Q (or A, depending) followed by a sequence indicator and a tab. Here's a screenshot of how I'd do it for the questions.
And here's a bit more explanation of how the Autonumber format works its magic …
the Q: at the very start is the series label, and the colon is an essential part of the definition. By including a series label, you can set up different series; for example to number tables and figures separately.
after the series label, Q {space} is the text that will be included before the counter; <n+> is the building block for a numeric counter that will increment by 1; the full stop after the building block is another piece of text, and \t is a tab character.
the character format identifies a, well, character format that is applied to anything generated by the autonumbering; the format I've used just happens to be set to light grey.
This already gives an idea of how elegant FM numbering can be. Icing on the cake in this case is that thanks to the series label you can also display the current value of the counter for the answer. The autonumber format I've used for answers is Q:A <n>.\t
the Q: is the same series label
A{space} is the text, and <n> is the building block for 'current value of counter identified by this series label'
If your document simply alternates single-paragraph questions and single-paragraph answers, you can save yourself time by using the Next Paragraph Tag option to follow questions by answers and vice versa. You'll be amazed by how quickly you'll have your Q&A ready :-}

Multiple character formats in a paragraph format

Hi. I've searched the general discussion and did not find this issue.
I have one paragraph format called Bomb that consists of a Wingding character (M) in the Numbering tab that prints a little black bomb in a side head. I combine with format with two other paragraph formats called Caution and Warning. These formats are in column and use a red, bold autonumber (CAUTION, WARNING) followed by a couple of spaces--the text goes immediately after the spaces.
My bosses now want the bomb symbol and the CAUTION/WARNING word in the side head, with the text in column. I can't see how to combine that Wingding character with the regular Verdana word. I had to do something similar with my Note format, except that I put the word "note" by itself as a side head and created a format to follow it called NoteAft for the text.This way, I have a line with the Note format, followed by a paragraph return, then the NoteAft format for the text.
I'd rather not have to use three formats to replace the existing two for Caution/Warning, so I hope y'all can help me figure out how to handle this thing.
I appreciate your suggestions! BTW, I'm using FM 7.2 but will want to switch over to 9.0 when my bosses agree.
Dimi Everette

OK, I managed to answer my own question!
Bomb para format: tab at 0.2 cm (not sure that's required...), Next Para tag is CAUTION; default font is Verdana; Run-In Head with no default punctuation; Numbering tab has Autonumber format checked, M in text field with Wingdings char format; defaults for Advanced and Table Cell tabs.
I press Return and CAUTION appears.
CAUTION para format: no tabs, Next Para is NoteAft; default font is Verdana; Side Head--Alignment: First Baseline; Numbering tab has Autonumber format checked, CAUTION in text field with RedBold char format; defaults for Advanced and Table Cell tabs.
I press Return and type the text of the CAUTION in the NoteAft style.
I'm going to change that Para tag to BombCaution and create another para tag with for BombWarning and be set! Of course this won't work unless your master page uses a column with room for side heads.
If you know of something more elegant, please pass it along.
Dimi

Autonumber bug in headings following a procedure

Hoping someone has an answer to this...
I'm on Frame 11 (11.0.0.380) on Windows 7.
I'm running into a strange issue with headings that are autonumbered. Everything works as expected... until I include a proccedure that has autonumbered steps and sub-steps. The heading immediately following the procedure renumbers from the beginning. The image below shows an example. There are three headings, which are numbered correctly. Then I inserted a subheading with a procedure and the heading below it has incorrect numbering. This only happens in headings that follow a procedure.
The autonumbers for the paragraphs are:
Heading1: <$chapnum>.<n+>
Heading2: <$chapnum>.<n>.<n+>
Numbered: S:<n+>/\t
NumberedCont1 (sub-step): <a=1>.\t
Is there something incorrectly set up in the autonumber format or is this a bug?

Take a look at this. http://help.adobe.com/en_US/FrameMaker/9.0/Using/WSF176D8C8-8133-4860-88E3-AF69262623F0.ht ml
The problem is in this paragraph with this numbering:
NumberedCont1 (sub-step): <a=1>.\t
You reset the numbering of the main paragraph back to 1, when you used the <a=1> tag since you did not preface it with S:.

Autonumbering Text in FM Converted to Bullet in RH

Running RH 7.02. In FM, my Caution paragraph style has
"CAUTION: " entered in the Autonumber Format field on the Numbering
tab, so that when I select the style in the document, the word
magically appears before I enter the actual caution statement.
When converted to RH, "CAUTION: " is replaced with a bullet.
What have I done wrong?

Sorry for the late response. I only visit the forums when I'm
having trouble with something. Here is a css example. All the
styles within your RoboHelp doc should be mapped to a single css
stylesheet for this to work. For instructions on how to do this see
part 3 of the "Adobe Technical Communication Suite: Getting Started
series" at:
http://www.adobe.com/devnet/robohelp/
Your image will be the screenshot of the word CAUTION.
P.Caution {
margin-right: 0.000pt;
text-align: left;
text-indent: 0.000pt;
margin-bottom: 8pt;
word-spacing: 0.250em;
font-style: normal;
font-weight: normal;
color: #000000;
letter-spacing: 0.00em;
font-size: 8pt;
font-family: Verdana, sans-serif;
margin-top: 2pt;
margin-left: 30pt;
display: list-item;
list-style-image: url(bullet_caution.gif);
text-decoration: none;
}

Table and Figure Autonumbering

I am currently using FrameMaker 8.0 and having a problem with the autonumbering of my tables and figures.
Is there a way to have these as seperate numbering but still referencing the Chapter number?
E.g. CHAPTER 1
Table 1.1
Figure 1.1
Figure 1.2
Table 1.2
CHAPTER 2
Figure 2.1
Table 2.1
Figure 2.2
Table 2.2
Thanks in advanced!
Skye

Skye,
If your chapters are separate files, then you should be using the
$chapnum variable and control that at the book level.
If all of your chapters are in a single file, then you have to define
your autonumber sequences to use the matrix method and have the
chapter number paratag reset the sub-ordinate paratag autonumbers.
This is explained in the "Using multiple counters in an autonumber
format" section of the Help file.
The first method is the easiest to use and maintain.

Making a forced return part of an autonumber

I want to format my chapters so that the number and the title are on different
lines, like this:
Chapter 4
Really Interesting Stuff
The forced line break after the chapter number should really be part of the
autonumber format, but I can't find a way to make FM6 (the version I'm running)
insert one. Adding a "\r" at the end of the autonumber format has no effect.
My current approach is to manually insert a forced line break at the beginning
of the title text, but this is a hack. Is there a better way? Googling around
hasn't yielded anything helpful.
I'm running FM6 on WinXP.
Thanks,
Scott

I tried Peter Meyer's method of connecting two text frames, and it worked beautifully for the document and the TOC. However, when I generated a PDF through PostScript and Distiller, for the bookmarks, I got duplicated numbers for the chapters, as in:
1 1 Introduction
2 2 Getting Started
3 3 Using the Interface
I can manually delete the extra numbers in the bookmarks, but I haven't found a way to prevent them from being generated.
Does anyone know how to get around this? Apparently, Acrobat thinks the two text frames require two numbers. Is this an Acrobat bug? Any ideas.
Thanks for any help on this.
Susan Self

Autonumbering for task levels - EDD question

Hello all,
In our current unstructured documents, we have a style that handles what we call "major" steps, which are tasks that can be by themselves or most often are no as they are normally in just one context. I could use <substeps> but the numbering scheme is reset, and these major steps normally involve a multitude of steps, not just one or two token sub-steps. Our major step is formatted like a heading, and there is a prefix of Step1 and StepN. We curently handle this using the Autonumber format in the paragraph designer (in our unstructured environ). In our structured DITA environment, I would like to retain that style since it is very popular with our users.
I am thinking that a change in the EDD is all I need as I could change the autonumber format based on a context. My question is, can I use a combination of {first}, etc ..rules with the ELEMENT < ELEMENT rule? My structure example appears below:
<task>
 <title>
 <shortdesc>
 <task>
With that second-level <task> being the MAJOR step. The highest level task is the MAIN user task, and would only required a <title> and <shortdesc>.
The Context rule "task < task" works for the first major step, but I need to handle the subsequent najor steps.
Any help or even an alternate way to handle this is greatly appreciated.
Thanks much
Tom

Tom,
Sorry my response did not make it through. Thanks for letting me know. Here is what I wrote:
My question is, can I use a combination of {first}, etc ..rules with the ELEMENT < ELEMENT rule?
Tom,
Yes, you can combine sibling and ancestor specifications. For example:
 x{first}
tests whether the current element is a child of an x that itself is the first child of its parent.
 {first} < x
tests whether the current element is the first child of an x. You can repeat the sibling specification after each ancestor listed:
 x{first} < y{first}
tests whether the current element is a child of of an x that is the first child of a y that is the first child of its parent. You can include wildcards in the ancestor chains, but you cannot test siblings of a wildcard:
 x{first} < * < y{first}
tests whether the current element is a child of an x that is the first child of its parent and that has an ancestor named y that is the first child of its parent. The y can be a more remote ancestor than the parent of the x. However:
 x < *{first} < y
does not work.
The Context rule "task < task" works for the first major step, but I need to handle the subsequent najor steps.
 task < task
tests whether the current element is a child of a task that itself is the child of a task. Whether either task is first is irrelevant. One mistake that is easy to make when writing such specifications is to use
task < task
instead of
task < * < task
These expressions differ because the first one requires there to be no intervening ancestors between the two tasks while the second one permits them.
Another easy mistake is to forget that the order of tests in a context rule is important. Suppose you
test
If context is: task
Else, if context is: task < task
Else, if context is: task < task < task
The else-if clauses will never fire because any element that is within three levels of task elements is also within two levels of task elements and any element that is within two levels is also within one level. Thus, any context that satisfies either else-if also satisfies the if. The if is used because it is first.
 --Lynne

Strange Autonumbering Problems

Hello Help, I have an autonumbering problem and I am stumped. There must be a simple solution. So I have four heading levels (Chapter.H1.H2.H3), and I need to have numbered headings. I have the following autonumber formats. H1 - <$chapnum>.<n+> H2 - <$chapnum>.<n>.<n+> H3 - <$chapnum>.<n>.<n>.<n+> Everything should be fine, right? Well, it works in most of my chapters, but in others it fails. The typical failure looks like: 3.2 3.2.1 3.0.1 (where it should be 3.3.1) Then I get 3.0.1 many times, suddenly a 3.2.1 and on and on, and it seems to be random. I believe that my autonumbering format is correct, but that the numbering must obviously be continued. A journey to Format > Document > Numbering has been unsuccessful. When I created the document, I copied and pasted from previous headings, and I can´t help but think I´ve found a bug in the software. Any help you guys can provide would be much appreciated. Thanks, Robert

> Frame gets confused about the value of <n> when the string is not labeled, > because it does not know which counter to go to in order to find the correct > value of <n>. I don't think that a call to "void Confuse()" is part of the source code for FM :-) It's actually quite easy: all numbering that is labelled with a series label "X:" becomes independent of all other numbering series. All numbering that is *not* labelled is considered to be part of the same single, un-labelled series, also independent of all other numbering series. Within a numbering series, any number of numbering positions (fields) can be defined. When a paragraph doesn't specify all the numbering positions, the remaining positions are reset to zero. For example: A numbering string of "<n>.<n>.<n+>" may result in 1.2.3. Then, a numbering string of "<n+>" increments the first position to 2 and resets the other to zero (2.0.0). (Only the first number is displayed) The next numbering string of "<n>.<n>.<n+>" will then result in 2.0.1. A numbering string of "<n+>< >< >" increments the first position to 3 and leaves the other two as is (but doesn't display them), i.e. 3.0.1. You only need to specify "< =0>" if you want to reset some positions, but not all the rest of the positions. You may still *want* to specify "< =0>" for all positions to make the numbering strings consistent and clearer (or not :-) -- /Thomas Michanek

Header autonumbering help needed

I am using FrameMaker v7.1p114 and I would like to create headings and subheadings within book chapters that have auto numbering such as the following assuming that this is Chapter 5:
5.1 Main heading 1
5.1.1 Sub heading 1
5.1.2 Sub heading 2
5.2 Main heading 2
5.2.1 Sub heading 1
5.2.2 Sub heading 2
I believe that I have the main heading figured out by using a paragraph format that uses the autonumber format as follows: <$chapnum>.<n+>iu
However, in order to get the desired autonumbered sub heading, what is a good method? One method that should work, but that requires me to create a lot of paragraph definitions, and that is not a completely autonumbered solution is as follows:
* create as many paragraph definitions as sub headings needed
* just put the <n+> on the end
For example, I could create a subheading #1 as: <$chapnum>.<n=1>.<n+>
a subheading #2 as: <$chapnum>.<n=2>.<n+>
a subheading #3 as: <$chapnum>.<n=3>.<n+>
The problem is that if I insert/move one of the sub headed sections, I would have to manually change the paragraph format and then go through the document and correct any text referenences that mention the specific section that now has a new sub heading number.

I used Dan's paper to create a test file in about 10 minutes and believe that I have come up with a solution. I crated 3 paragraph definitions and the code is as follows:
5.1 main 1-1 H:<$chapnum>.<n+>< =0>
5.1.1 sub 1-1-1 H:<$chapnum>.<n>.<n+>< =0>
5.1.1.1 sub 1-1-1-1 H:<$chapnum>.<n>.<n>.<n+>< =0>
5.1.1.2 sub 1-1-1-2
5.1.2 sub 1-1-2
5.1.3 sub 1-1-3
5.1.1.3.1 sub 1-1-3-1
5.1.3.2 sub 1-1-3-2
5.2 main 2
5.2.1 sub 1-2-1
5.2.1.1 sub 1-2-1-1
5.2.1.2 sub 1-2-1-2
I should have been using FrameMaker years ago .

How to automate the adding of check-box along with each numbered item in Framemaker file ?

I tried using the wingdings font as check-box. But I don't want to use it manually every time. I want to have it as a style part of my procedure style (numbering style). I need the check-box along with each numbered item. Whenever I apply my numbering style in FM, I should get something like:
" <checkbox> 1. <text> "

Use "N:\u2751\ <n+>.\ " for the autonumber format.
"N" Use counter N
"\u2751" One of many checkboxes available in Unicode
"<n+>" increment the counter
"." ordinary period
"\ " non-breaking space
This assumes that you are on FM8 or later, and your Unicode font has that glyph code point populated (Arial Unicode MS does if your font doesn't).
Don't use WingDings (or Zaph Dingbats) anymore. Using codepage overlays has any number of issues, and these two sets of legacy codepage dingbats don't even match each other.

Conversion from word problems with images

Hi ,
I managed to make a conversion table to structure the documents of out company.I am having a proble with images.I am importing the word file to our template with a custom EDD document.When the import finishes I am having all images at almost correct places.The issue is when i apply the custom conversion table all the images at anchored at insertion point.The correct position would be at below current line.I am stuck and I can not find a solution to this.
My EDD is as follows:
EDD Version is 12.0
Structured Application: ReportPlain
F:\FramemakerBooks\Part B -Section 3.fm
April 14, 2014
Element (Container): Author
General rule: <TEXT>
Text format rules
In all contexts.
Use paragraph format: ReportAuthor
Element (Container): Emphasis
General rule: <TEXTONLY>
Text format rules
In all contexts.
Text range.
Use character format: Emphasis
Element (Equation): Equation
Element (Container): EquationPara
General rule: Equation
Text format rules
Element paragraph format: Equation
Element (Container): Extract
General rule: (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef)*
Attribute list
Name: ID Unique ID Optional
Text format rules
In all contexts.
Use paragraph format: Extract
Element (Container): Figure
General rule: (<TEXT> | Frame)*
Attribute list
Name: ID Unique ID Optional
Name: XRefLabel String Optional
Default: Figure
Name: Imported Choice Optional
Choices: Yes, No
Default: No
Text format rules
In all contexts.
Use paragraph format: Figure
Element (Footnote): Footnote
General rule: <TEXT>
Text format rules
In all contexts.
Use paragraph format: Footnote
If context is: * < Table
Use paragraph format: TableFootnote
Element (Graphic): GRAPHIC
Initial graphic element format
In all contexts.
Insert anchored frame.
Anchored Frame Object Style:FiguredCentered
Element (Graphic): Frame
Initial graphic element format
If context is: Figure[Imported = "Yes"]
Insert imported graphic file.
Else
Insert anchored frame.
Element (Container): Head
General rule: <TEXT>
Text format rules
Count ancestors named: Section
If level is: 1
Context label: H1
Use paragraph format: Heading1
Else, if level is: 2
Context label: H2
Use paragraph format: Heading2
Else, if level is: 3
Context label: H3
Use paragraph format: Heading3
Else, if level is: 4
Context label: H4
Use paragraph format: Heading4
Else, if level is: 5
Context label: H5
Use paragraph format: HeadingRunIn
Else
Numbering properties
Autonumber format:
If context is: {first} < Report
Use paragraph format: ReportTitle
Else, if context is: HeadingRunIn
Use paragraph format: HeadingRunIn
Element (Container): HeadingRunIn
General rule: Head, Para+
Element (Container): Item
General rule: (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef | Para)*
Format rules for first paragraph in element
If context is: List[Type = "Plain"]
No additional formatting.
Else, if context is: List[Type = "Bulleted"]
Use paragraph format: Bulleted clean
Else, if context is: {first}
Use paragraph format: Numbered1
Else
Use paragraph format: Numbered
Element (Container): List
General rule: Item+
Attribute list
Name: ID Unique ID Optional
Name: Type Choice Optional
Choices: Plain, Bulleted, Numbered
Default: Bulleted
Automatic insertions
Automatically insert child: Item
Element (Container): Para
General rule: (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef | Footnote | Table )*
Attribute list
Name: ID Unique ID Optional
Text format rules
If context is: {after Head }
Use paragraph format: Body
Else, if context is: {after List}
Use paragraph format: BodyAfterHead
Else
Use paragraph format: Body
Element (Container): Part
Valid as the highest-level element.
General rule: (Para | Footnote | Table | Section )*
Attribute list
Name: ID Unique ID Optional
Control flags: Read-only
Automatic insertions
Automatically insert child: Head
Text format rules
Element paragraph format: Body
Element (Container): Purpose
General rule: <TEXT>
Text format rules
Element paragraph format: ReportPurpose
Element (Container): Section
General rule: (Section,Head |Section | Para | List | Table | Figure | HeadingRunIn )*
Attribute list
Name: ID Unique ID Optional
Name: XRefLabel String Optional
Default: Section
Automatic insertions
Automatically insert child: Head
Element (Container): Subscript
General rule: <TEXTONLY>
Text format rules
In all contexts.
Text range.
Font properties
Superscript/Subscript: Subscript
Element (Container): Superscript
General rule: <TEXTONLY>
Text format rules
In all contexts.
Text range.
Font properties
Superscript/Subscript: Superscript
Element (Table): Table
General rule: TableTitle?, TableHead?, TableBody
Attribute list
Name: ID Unique ID Optional
Control flags: Read-only
Name: XRefLabel String Optional
Default: Table
Control flags: Read-only
Initial table format
In all contexts.
Table format: Format A
Element (Table Body): TableBody
General rule: TableRow+
Element (Table Cell): TableCell
General rule: (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef | Frame| Para)*
Text format rules
Element paragraph format: Bodycell
Element (Table Heading): TableHead
General rule: TableHeadRow+
Element (Table Cell): TableHeadCell
General rule: <TEXT>
Element (Table Row): TableHeadRow
General rule: TableHeadCell+
Element (Table Row): TableRow
General rule: TableCell+
Element (Table Title): TableTitle
General rule: <TEXT>
Text format rules
Element paragraph format: TableTitle
Element (Container): Term
General rule: <TEXTONLY>
Text format rules
In all contexts.
Text range.
Use character format: Emphasis
Element (CrossReference): XRef
Attribute list
Name: IDRef ID Reference Required
Control flags: Read-only
Limit values for format change list properties
First indent
Maximum: 39.0"
Minimum: 0.0"
Left indent
Maximum: 39.0"
Minimum: 0.0"
Right indent
Maximum: 39.0"
Minimum: 0.0"
Space above
Maximum: 32767.0 pt
Minimum: -32767.0 pt
Space below
Maximum: 32767.0 pt
Minimum: -32767.0 pt
Line spacing
Maximum: 32767.0 pt
Minimum: -32767.0 pt
Tab stop position
Maximum: 39.0"
Minimum: 0.0"
Font size
Maximum: 400.0 pt
Minimum: 2.0 pt
Spread
Maximum: 1000.0%
Minimum: -1000.0%
Stretch
Maximum: 1000.0%
Minimum: 10.0%
Cell margins
Top
Maximum: 32767.0 pt
Minimum: 0.0 pt
Bottom
Maximum: 32767.0 pt
Minimum: 0.0 pt
Left
Maximum: 32767.0 pt
Minimum: 0.0 pt
Right
Maximum: 32767.0 pt
Minimum: 0.0 pt
And my conversion table is:
Wrap this object or objects In this element With this qualifier
TC: TableCell
P:Body Para
P:Normal Para
P:Heading 5 Head head5
E:Head[head5],(Para | Frame | List | Table )* Section section5
P:Heading 4 Head head4
E:Head[head4],(Para | Frame | List | Table | [section5])* Section section4
P:Heading 3 Head head3
Head[head3],(Para | List | Frame | Table | [section4])* Section section3
P:Heading 2 Head head2
Head[head2],(Para | List | Frame | Table | [section3])* Section section2
P:Heading 1 Head head1
Head[head1],(Para | List | Frame | Table | [section2])* Section section
T:Table Table (promote)
TT: TableTitle
TH: TableHead
TB: TableBody
TF: FOOTING
TR: TableRow
RE:RootElement Part
P:List Paragraph Item
Item+ List
G: GRAPHIC(promote)
RE:RootElement Part
I am almost done with the template"Application"I just need to place the pictures in the correct position.Can anyone point me to the right direction?
Thanks a lot in advance

Dimitris,
 I know you originally posted this question on the general FrameMaker forum. I suggest below that you post a follow-up question there.
 The structure-based part of the issue is that neither a conversion table nor an EDD can change properties of an existing anchored frame. It seems that when you open your Word document in FrameMaker, the graphics come in positioned at the insertion point. That doesn't change when you apply the conversion table. Your EDD does specify object style FiguredCentered as the initial format for GRAPHIC elements. The keyword here is "initial". The EDD can indicate a style for new anchored frames that are created by inserting an element. It does not allow you to change existing anchored frames.
So the real problem is how to make a global change to all existing anchored frames (either assigning an object style or changing the position to Below Current Line) so that you don't have to change them one at a time. I am not aware of a way to do so with existing FrameMaker commands. You could use a script or plug-in, or save the document as MIF and make a global change with a text editor in the MIF file. You might ask on the general FrameMaker forum if someone there knows an easier approach.
 --Lynne

FM import to RH: lists

Technical Communication Suite, RoboHelp HTML, WebHelp
I'm importing FM8 book into RH7 HTML.
I've done some research and I see that conversion of lists
between FM source files and RH HTML is very problematic. I'm
confused and haven't been able to resolve my particular problem
through research.
My FM bullet parragraph tag looks like:
Indent First: 18pt
Indent Left: 28pt
tab stop: 28pt L
Autonumber format:
\t
Everything lines up perfectly in FM and when saved as PDF.
When import to RH, I DO NOT select "Convert AutoNumber to
HTML list". In RH the first line is indented too much. The HTML
looks like this:
• 
The three spaces ( ) indents too
much; two spaces ( ) not enough.
One solution I'm considering is to search for
 
And replace with:
 
Manipulating the font size of a single space gets me darn
close. However, this solution is inelegant, time consuming, and
possibly prone to error in a large document (I'm working with 300+
pages). And it doesn't work well with numbered lists that go into
double digets.
Can anyone point me in the right direction?
Thanks,
Stan

If you have simple bullets and steps,
"Convert AutoNumber to HTML List" may work for you.
If you have nested lists (such as steps with bullets, bullets
with sub bullets)
the nested lists become entangled, and also tangle up
headings that follow, preventing topic breaks.
When you look at the HTML code, you can see the problems. The
</UL> (end of list) gets misplaced for the various nested
lists.
"Convert AutoNumber to HTML List" does not work for my
application.
darbyzz,
Here's what I did to make my bullets and steps work out.
- I did not use Convert AutoNumber to HTML List.
- I set up a secondary FM template, just for RoboHelp, and
use it just for my help files.
In this template, I don't use indents before the first level
bullets.
For second level lists, I use a format that includes an
empty place holder (as advised by Jain).
example: a:< ><a+>.\t
I also use a specific tag to reset a list to number 1 (I
found that was necessary).
- When mapping in RoboHelp, I left my first-level list tags
to Source,
- I map my second-level list tags to BodyLevel1, which, in
its default state,
is indented just enough for my needs.
This works pretty well for me, not perfectly, but I've
settled.

How to number Figure Titles continously across book files

Currently in our book files, the Figure Titles restart at 1 in each book file. We would like them to number continously throughout the whole book, so that if there are 3 figures in chapter 1, the first figure in chapter 2 automatically starts at 4 (and if figures are added or deleted, the numbers update automatically when you generate the book).
Is this possible to do or are we forced to number our figures with a chapter preface (first chapter figures are 1.1, 1.2, etc., second chapter figures are 2.1, 2.2, etc.)

It's very possible and easy.
1. Assign a "series label" to the paragraph format that holds the autonumber
for your figures. I use "F:" for figures. For example, "F:Fig. <n+>.\sn" is
the autonumber format I use. It gives a result such as "Fig. 3. " (I also
assign a bold character format to the autonumber format, to separate it from
the caption text.)
2. In the book file, select the files you want to be affected, right click
and choose "Numbering." On the Paragraph tab, set "Continue Numbering from
Previous Paragraph in Book."
3. Edit> Update Book to see the result.
4. Done!
Series labels come in really handy. Some use separate series labels for
tables, photos, charts, etc., but that can become confusing to readers very
quickly. (Table 1 follows Plate 6?). It's easier and clearer to use a single
series label for all illustrative elements.
Mike Wickham

Autonumber Format. 01, 02, 03...

Similar Messages

Maybe you are looking for