Did RH 9.02 patch break something...???

Report · Feb 15, 2012

Yesterday we upgraded to Version 9.0.2. Today my stylesheets don't work.

I rely very heavily on stylesheets because my company has two divisions with two separate brandings. Every day I have to import the same document to two separate projects, and apply the appropriate stylesheet so it publishes in the right colors for that division.

I tested multiple Word documents, multiple projects and multiple stylesheets. As soon as you apply ANY stylesheet, the topic loses all formatting. That means I have to manually apply the styles to every line of text.

Is there a quick fix to this that will get me through today? I have topics I need to publish.

Thanks

Report · Feb 15, 2012

Hi,

This is the first I heard of this, so if it's related to the patch, it most certainly isn't common.

In order to give us a better estimation of the problem, could you please answer a few questions:

Could you describe the proces you use more precisely? Do you import word documents? Do you link them?
Do you also use RoboHelp topics that do not originate from a Word document?
When you apply a style sheet and the formatting disappears, is the link to your style sheet placed in the <head> section of the file?
Is the contents of the CSS somehow truncated?
Is the loss of styles in the WYSIWYG only, or does it persist when you generate different SSLs?
What happens when you assign a style sheet in the SSL settings?

Greet,

Willam

Report · Feb 15, 2012

Thanks for replying. I was just now reporting it as a bug.

In Word, apply custom styles to a document.
Create two stylesheets for Robohelp that replicate those Word styles, but have different colors for the heading styles. Place them in each applicable Robohelp project folder.
Import the document.
Right click the topic name in the Topic List, and click Appearance.
Select the appropriate stylesheet and click OK.
Usually it's Voila! and everything formats perfectly. Today there is NO style to ANY text - even the font reverts to no margins, Times New Roman 10pt. It keeps character formatting, so things I bolded in Word stayed bolded. But that's it. I have used the same stylesheets for months, and made no changes to it yesterday, when it was working.

The loss of styles persists after you compile. However, they display correctly in the Styles and Formatting pod. When I highlight text in the window and apply the styles from the Styles pod, they update as they should, but the process is 100% manual.

I have no topics that don't originate in Word.

Here's one of the stylesheets:

/*Created with Adobe RoboHelp 9.*/

p.WD_Normal {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: .5in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

}

span.WD_Hyperlink {

color: #0000ff;

text-underline: single;

text-decoration: underline;

}

span.WD_HyperlinkFollowed {

color: #800080;

text-underline: single;

text-decoration: underline;

}

p.WD_DocumentMap {

margin-top: 0in;

margin-right: 0in;

margin-bottom: .0001pt;

margin-left: .5in;

font-size: 8.0pt;

font-family: Tahoma, sans-serif;

color: #262626;

}

p.WD_Acetate {

margin-top: 0in;

margin-right: 0in;

margin-bottom: .0001pt;

margin-left: .5in;

font-size: 8.0pt;

font-family: Tahoma, sans-serif;

color: #262626;

}

p.WD_Bullet1 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

text-indent: -.25in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

margin-left: 0.75in;

}

p.WD_Bullet2 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

text-indent: -0.23in;

margin-left: 0.98in;

}

p.WD_Bullet3 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

text-indent: -12px;

margin-left: 108px;

}

p.WD_Subtopic {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: .5in;

font-size: 14.0pt;

font-family: Calibri, sans-serif;

font-weight: bold;

font-style: italic;

color: #00003f;

}

p.WD_ChangeDate {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: .5in;

font-size: 9.0pt;

font-family: Calibri, sans-serif;

font-weight: bold;

font-style: italic;

color: #00003f;

}

p.WD_Note {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 6.0pt;

margin-left: 27.0pt;

text-indent: -27.0pt;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

}

p.WD_Note1 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: 45.0pt;

text-indent: -27.0pt;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

font-weight: bold;

}

p.WD_Note2 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: 1.25in;

text-indent: -.5in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

}

p.WD_Note3 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: 1.5in;

text-indent: -.5in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

}

p.WD_Number1 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

text-indent: -.25in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

margin-left: 0.75in;

}

p.WD_Number2 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: 1.0in;

text-indent: -.25in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

}

p.WD_Number3 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

margin-left: 120px;

text-indent: -24px;

}

p.WD_para1 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 6.0pt;

margin-left: .75in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

}

p.WD_Paragraph {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 12.0pt;

margin-left: .5in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #000000;

}

p.WD_ParaIntro {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 6.0pt;

margin-left: .5in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #000000;

}

p.WD_Process {

margin-top: 0in;

margin-bottom: 3.0pt;

margin-left: .5in;

font-size: 16.0pt;

font-family: Calibri, sans-serif;

font-weight: bold;

margin-right: 58px;

text-align: justify;

color: #4c89bc;

}

p.WD_Subtopic1 {

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: .5in;

background: #C9C9C9;

font-size: 12.0pt;

font-family: Calibri, sans-serif;

font-weight: bold;

color: #00003f;

margin-top: .1in;

}

p.WD_Subtopic2 {

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: .5in;

background: #ffffff;

font-size: 12.0pt;

font-family: Calibri, sans-serif;

font-weight: bold;

color: #4c89bc;

margin-top: 0.1in;

}

p.WD_Topic {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 3.0pt;

margin-left: .5in;

border: none;

padding: 0in;

font-size: 18.0pt;

font-family: Calibri, sans-serif;

font-weight: bold;

color: #000000;

}

span.WD_NoteChar {

font-family: Calibri, sans-serif;

color: #262626;

}

p.WD_Important {

margin-top: 6.0pt;

margin-right: 0in;

margin-bottom: 6.0pt;

margin-left: .5in;

border: none;

padding: 0in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #262626;

}

p.WD_NoFormatting {

margin: 0in;

margin-bottom: .0001pt;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #000000;

margin-left: 0.5pt;

}

p.WD_Para2 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 6.0pt;

margin-left: 1.0in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #000000;

}

p.WD_Para3 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 6.0pt;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #000000;

margin-left: 108px;

}

span.WD_BalloonTextChar {

font-family: Tahoma, sans-serif;

color: #262626;

}

span.WD_HTMLPreformattedChar {

font-family: "Courier New";

}

p.WD_Image {

margin-top: 6.0pt;

margin-right: 0in;

margin-bottom: 6.0pt;

margin-left: .75in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #000000;

}

span.WD_DocumentMapChar {

font-family: Tahoma, sans-serif;

color: #262626;

}

p.WD_Normal1 {

margin-top: 0in;

margin-right: 0in;

margin-bottom: 6.0pt;

margin-left: .5in;

border: none;

padding: 0in;

font-size: 11.0pt;

font-family: Calibri, sans-serif;

color: #000000;

}

span.WD_TopicChar {

font-family: Calibri, sans-serif;

color: #000000;

font-weight: bold;

}

span.WD_ParagraphChar {

font-family: Calibri, sans-serif;

color: #000000;

}

span.WD_Number1Char {

font-family: Calibri, sans-serif;

color: #262626;

}

span.WD_ProcessChar {

font-family: Calibri, sans-serif;

font-weight: bold;

font-style: italic;

color: #4c89bc;

}

span.WD_ChangeDateChar {

font-family: Calibri, sans-serif;

color: #595959;

font-weight: bold;

font-style: italic;

}

span.WD_para1Char {

font-family: Calibri, sans-serif;

color: #262626;

}

OL {

margin-top: 0px;

margin-bottom: 0px;

}

UL {

margin-top: 0px;

margin-bottom: 0px;

}

rh-list.MSWordList2 {

x-level-count: 3;

x-lvl-1-text-indent: -24px;

x-lvl-1-type: bullet001;

x-lvl-1-format: "<x>";

x-lvl-2-format: "<x>";

x-lvl-2-text-indent: -24px;

x-lvl-2-type: bullet002;

x-lvl-3-format: "<x>";

x-lvl-3-text-indent: -24px;

x-lvl-3-type: bullet003;

}

rh-list.MSWordList1 {

x-level-count: 2;

x-lvl-1-text-indent: -24px;

x-lvl-1-margin: 24px;

x-lvl-1-type: decimal;

x-lvl-1-format: "<x>.";

x-lvl-2-format: "<x>";

x-lvl-2-text-indent: -24px;

x-lvl-2-type: bullet004;

x-lvl-2-margin: 72px;

}

rh-list.MSWordList0 {

x-level-count: 3;

x-lvl-1-text-indent: -24px;

x-lvl-1-type: decimal;

x-lvl-1-format: "<x>.";

x-lvl-2-format: "<x>.";

x-lvl-2-text-indent: -24px;

x-lvl-2-type: lower-alpha;

x-lvl-2-margin: 120px;

x-lvl-3-format: "<x>.";

x-lvl-3-text-indent: -12px;

x-lvl-3-type: lower-roman;

}

rh-seq.bullet002 {

x-count: 1;

x-1: o;

x-font: Courier New;

}

rh-seq.bullet003 {

x-count: 1;

x-1: ;

x-font: Wingdings;

}

rh-seq.bullet004 {

x-count: 1;

x-1: ;

x-font: Wingdings;

}

rh-seq.bullet001 {

x-count: 1;

x-1: ;

x-font: Symbol;

}

p.Paragraph {

}

Report · Feb 15, 2012

Just to add to what Willam has covered...

What version did you upgrade from?

Have you looked at the Importing topics on my site? I describe there how to get a good import with RoboHelp 902.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Report · Feb 15, 2012

My reply crossed with your update. Those WD styles confirm you do need to take a look at my site.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Report · Feb 15, 2012

Thanks, but it seems to be addressing Word document preparation, and I have hundreds and hundreds of documents I cannot go back and "prepare" for the import process, which worked until yesterday. Is there a short answer to how I fix this?

Report · Feb 15, 2012

Here's what I figured out. When you import Word documents into the new version, it maps over your Word styles with the name you assigned them in Word. In earlier versions it added WD_ to the beginning of the style name.

So, what I learned from testing is, I can fix this by going into the stylesheet and removing WD_ from the beginning of all the style names, but that removes the formatting from documents I imported into the earlier version because the styles in those topics are still named WD_. Or, I can go into Word and rename all my styles "WD_StyleName", and keep the existing stylesheets in Robohelp - but that's a really inelegant fix.

Or, I can create a new stylesheet that contains both the old names and the new names for all of the styles. That might work.

So I called Adobe tech support, and I reported it as a bug, both on the phone and from the website. He sat and watched me go through the process a number of times. There doesn't appear to be a way to map the old style names to the new style names within Robohelp, which leaves me with the task of modifying my stylesheets, and reapplying them to all of my projects.

The first thing I said to him was, "You don't make changes this big for just a patch. I could understand it, if this was Robohelp 10..." I mean, patches are supposed to be invisible. By the end of the discussion, he agreed with me. It's an awful lot of workaround for something that's just supposed to fix a couple of bugs. He wrote up a report on it. We'll see if they figure out a fix.

Thanks guys.

Report · Feb 15, 2012

I doubt there will be a fix as 902 was the fix for something that was broken and that you were working around.

After the import you are changing the topics from the CSS created when you import to your existing CSS. Why not leave the existing imports as they are linked to say styles1.css. Create a copy of styles1.css and call it styles2.css. Link future imports to that.

Does that not work for you?

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Report · Feb 15, 2012

Unfortunately, they've changed the branding colors at this company three times since I've worked here. And there are two divisions. And they just hired a new president who might like a different color or a different online help design...I need to be able to know that one change fixes everything all across the board.

What I did was open the stylesheet in Notepad, and copy/paste the content to the bottom of the file. Then I went through the styles I had just pasted and removed WD_ from all of them, and saved the file. The stylesheet now has two versions of every style, one with and one without a preceding WD_. I tested it, and it worked fine. That only took a couple of minutes. Now I have to open all the projects and apply that stylesheet to all of them.

Thanks!

Report · Feb 15, 2012

PS. The simple way to apply new stylesheets is to just go to the C:\Robohelp directory, copy the one that you changed, then paste it into the directories for all your other projects. You don't need to reapply it to the individual topics because they pull from whatever stylesheet file is in that folder. So, the total fix took about 10 minutes, once I thought it through. Not as big a disaster as I had anticipated!

Adobe Community

Did RH 9.02 patch break something...???