Paragraph style not appearing in styles window?

[TechnicalDisaster]

Kind of an odd-ball issue.

Here is my bulleted list style:

Code: Select all

p.INDENTList_Bullets,
p.INDENTList_Bullets_Keep_With
{
	color: #000;
	list-style-type: disc;
	display: list-item;
	font-family: Arial, Sans-Serif;
	font-size: 80%;
	font-weight: 400;
	margin: 7pt 0 0 1.75in;
	padding: 3pt;
	text-align: Left;
	text-indent: 0;
	vertical-align: baseline;
}

Content I import from Frame use this style correctly, but the style does not appear in the styles window.

I don't understand how the Flare context sensitive style windows work. I have 3 styles windows:
Paragraph styles - appears when my cursor is in a paragraph
List styles - appears when my cursor is in a ol or ul list style
Random window I can't access - contains a ton of styles from the Frame to Flare conversion. <---I need to access this window.

Am I crazy?

[lacastle]

the "random window" may be coming when you double-click on a word? those are character styles.
how do you know it's there if you can't access it? are you trying to keep your Frame styles and style names? didn't you match them to existing Flare styles in the import process?

by the way, why did you create a paragraph bullet list and not just modify the li/ul/ol styles?

[TechnicalDisaster]

I think I got it squared away. You're not allowed to map Frame list styles to ol and ul styles in Flare - they have to come in as <p> styles. I made a CSS goof.

I fixed the issue by removing:

Code: Select all

list-style-type: disc;
   display: list-item;

from the stylesheet and created the bullet using the mc-autonumber format.

Now the style appears where it is suppose to.

[i-tietz]

You're not allowed to map Frame list styles to ol and ul styles in Flare - they have to come in as <p> styles.

HONESTLY??? NO KIDDING???
What nonsens is that? Can anybody else verify this?

[NorthEast]

You're not allowed to map Frame list styles to ol and ul styles in Flare - they have to come in as <p> styles.

HONESTLY??? NO KIDDING???
What nonsens is that? Can anybody else verify this?

Yes, Flare has never been able to map FM styles to ol/ul/li tags.

You can map them to paragraph styles with autonumber formatting; that's the easiest solution, if you don't mind using autonumber lists.

When I converted our projects, I wanted to use normal lists (ol/ul tags), so I had to bite the bullet and manually reformat all my lists.

[lacastle]

When I converted our projects, I wanted to use normal lists (ol/ul tags), so I had to bite the bullet and manually reformat all my lists.

I knew i was going to have to edit all my imported manuals anyway, so i also manually formatted all my lists (just imported them as p styles).

[TechnicalDisaster]

Due to our release schedule, we will be using <p> styles after the conversion and then make it a backlog project to manually convert to <ol> and <ul> styles.

[i-tietz]

Due to our release schedule, we will be using <p> styles after the conversion and then make it a backlog project to manually convert to <ol> and <ul> styles.

Goodness - "manually convert"!!!
We are thinking of importing all our manuals into Flare - that's more than 3.000 pages!!! How long is this going to take?
And Flare cannot even do the Find&Replace with Regular Expressions!
I still cannot believe it ... *shaking my head* ... has anyone placed an enhancement request?

[TechnicalDisaster]

We have around 20,000 pages to convert (first 6,000 already completed!). I dump the html files into Notepad++ to use regular expressions. I expect with 20 writers it will take 8-10 hours per guide. We'll have everything done in about 2 weeks.

[i-tietz]

We have around 20,000 pages to convert (first 6,000 already completed!). I dump the html files into Notepad++ to use regular expressions. I expect with 20 writers it will take 8-10 hours per guide. We'll have everything done in about 2 weeks.

Ah - yes, if every author knows his way with RE ... but in our department I'm the only one.

[TechnicalDisaster]

We have around 20,000 pages to convert (first 6,000 already completed!). I dump the html files into Notepad++ to use regular expressions. I expect with 20 writers it will take 8-10 hours per guide. We'll have everything done in about 2 weeks.

Ah - yes, if every author knows his way with RE ... but in our department I'm the only one.

You can't create some instructions for your writers to follow?

[NorthEast]

Due to our release schedule, we will be using <p> styles after the conversion and then make it a backlog project to manually convert to <ol> and <ul> styles.

Goodness - "manually convert"!!!
We are thinking of importing all our manuals into Flare - that's more than 3.000 pages!!! How long is this going to take?
And Flare cannot even do the Find&Replace with Regular Expressions!
I still cannot believe it ... *shaking my head* ... has anyone placed an enhancement request?

I guess you'd have to weigh up how important it is to have HTML lists; if you don't mind autonumber lists then you don't have a problem.

It would be great if you could map FM lists to HTML lists. I suspect that it would be more difficult to implement though, as list styles in FM are effectively set up in the same was as autonumber lists in Flare; they're not structured like an HTML list.

[i-tietz]

With the necessary precision so nobody makes serious mistakes - writing a "how to" probably takes as long as doing it myself. That's the experience from writing a how-to for importing our RoboHelp projects and do the refinishing.

[LTinker68]

I guess you'd have to weigh up how important it is to have HTML lists; if you don't mind autonumber lists then you don't have a problem.

There are definite advantages to using one over the other. A lot of people use a mix of the two. They use HTML lists for simple lists that you won't cross-reference to and don't need to have fancy numbering. If you want to xref to a list item (e.g., "see step 3") or have fancier numbering for your list items (e.g., A.1.b), then go with paragraphs with auto-numbering.