As we know, when Flare builds a Word target, it parsimoniously (or infuriatingly, depending on your viewpoint) never creates a new Word style when it can reuse an identical one it has already created.
Sometimes (I’ll leave out the explanation why) I want to force Flare to create separate Word styles for “identical†CSS styles.
One way I can do this is by subtle changes to font color. Visually, #000001 is hard to distinguish from #000000, but it’s enough for Flare to generate a new Word style.
But this is somewhat unappealing.
Can anyone suggest a better use of CSS, that would force Flare to create separate Word styles while keeping the visual appearance (as near as damn it) the same?
I’m betting there is something really simple that I’ve overlooked.
Fooling Flare into generating separate Word styles
-
Paul Griffiths
- Sr. Propeller Head
- Posts: 262
- Joined: Wed Apr 18, 2007 2:25 am
- Location: Nottingham, UK
-
wclass
- Propellus Maximus
- Posts: 1238
- Joined: Mon Feb 27, 2006 5:56 am
- Location: Melbourne, Australia
Re: Fooling Flare into generating separate Word styles
This looks like the return of a bug I had reported back in 2008 (with v4), but I'm pretty sure it was fixed then. Unfortunately, I can't access the release notes for v5 so I can't give more details.
My issue: I had created styles for "buttons" and for "screens" and for "fields" and all happened to be bold. I wanted to maintain separate styles because sometimes I wanted items highlighted with a color as well. When I exported to Word and tried to search for anything with the "button" style, none existed, which was a problem for me.
Sorry I don't have a workaround for you, but I will be resubmitting the bug report.
My issue: I had created styles for "buttons" and for "screens" and for "fields" and all happened to be bold. I wanted to maintain separate styles because sometimes I wanted items highlighted with a color as well. When I exported to Word and tried to search for anything with the "button" style, none existed, which was a problem for me.
Sorry I don't have a workaround for you, but I will be resubmitting the bug report.
Margaret Hassall - Melbourne