A

Anonymous

Question

Wrong font in One Source

Forum|Forum|20 years ago
June 6, 2006
28 replies
22996 views

I used OneSource to create printed documentation. Although nearly all the font in a section is ARIEL, when converted, a few words showed up in what appears to be SYMBOL or some other font. I cannot find a reason for this, as the fault is listed as ARIEL in the original RoboHelp document. Any ideas?

RH for Word

This topic has been closed for replies.

Show previous replies

Peter Grainge

Community Expert

No because Word 2003 is not compatible with X4. This problem is only on Word 2003.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

A

Anonymous

Sure it's compatible - I use version X4.1 with MS Word 2003.

Karen

A

Anonymous

Hello Limestone Springs,

The above TechNote has been updated with a newer patch that resolves both the original issue along with the issue you mentioned.

Thank you,

Bobby Walker
Technical Support
Adobe Systems Incorporated

A

Anonymous

The TechNote refers to version X5; will this patch work for version X4.1 also?

Thanks, Karen

A

Anonymous

Thank you Adobe TS,

I tried the update and it has solve the problems I was having with all Security Updates installed.

Limestone Springs

A

Anonymous

Hello everyone,

We have released an update to address this issue. Please see http://www.adobe.com/go/799a6b49 for details.

Thank you,

Bobby Walker
Technical Support
Adobe Systems Incorporated

A

Anonymous

Adobe TS

I approved the new update too quickly. My test project worked fine with correct fonts being displayed. When I started working on other projects I found a major problem for me. I use a lot of sub & super script characters in most of my projects. RoboHelp has never been able to handles these using the nornal "Word - Format - Font " method. The work around was to use the Arial Sub and Arial Super (True Type) font character sets when a subscript or superscript character was needed. The new update, evidently, does not handles these font character sets.

Example: When an Arial Sub font character is encountered, all text following the character is changed to something like a subscripted "wingding" font.

So, I still can not use the fix you provided.

Thanks,
Limestone Springs

A

Anonymous

To those required to have security updates on your work computers,

My company installed the updates today, which brought back all the problems associated with these security updates. Peter Grainge's Snippet 51 - Solution 1 worked as expected. If you use this simple "fool the update" procedure, remember to replace your Winword_Update.exe with the new, security updated Winword.exe. This will allow you to have the latest security update protection when you are not using RoboHelp for Word.

Limestone Springs

M

MSCaroline

Known Participant

Follow-up to my previous post: removed KB923094 (installed 10/12/06), which seems to have solved the problem. Just in case any of y'all run into the same issue.

M

MSCaroline

Known Participant

Anybody finding this problem (specifically, output being generated in the wrong font) returning? I uninstalled KB917334 quite a while ago, and everything has been fine since then. But this morning, I'm running into the same problem all over again. I can only assume that it is coming from one of the updates downloaded/installed last night. I did double-check to make sure that Auto Update didn't try to sneak 917334 back in despite my telling it never to mention that update in my presence again. It seems to have obeyed me on that one, so that's not the problem....

K

Karla_T

Participating Frequently

No rotten tomatoes from me! You are right, of course. However, with another deadline looming, it seems easier to insert a few manual page breaks than to take on something new. (The same old story, right?)

I will make a resolution to try the RH HTML editor right after our next product release.

Captiv8r

Legend

LOL, once you get accustomed to it, you will be surprised at how much you don't miss Word! The interface actually is a bit Word like.

Cheers... Rick

K

Karla_T

Participating Frequently

Limestone Springs,

Thanks so much for the update. I am somewhat reluctant to try your suggestion (using an older version of Winword.exe), because it seems like we're trying to trick the computer and our IT department into thinking that we're in compliance, when we would not be. (In fact, I have alerted my IT department of the whole problem, so I wouldn't do this without their blessing.)

However.... it may be a useful thing to do temporarily when compiling WinHelp. You could do something like the following: uninstall the patch, save off the old Winword.exe, then reinstall the patch. The new Winword.exe would be used at all times, but just before compiling, you could "overwrite" the new with the old. Then, after compiling, put the new version back. It may be a bit of a maintenance nightmare -- making sure to keep track of the two different files while renaming and overwriting, but it seems like a viable workaround that accomplishes the needed fix for RoboHelp while not being in a state of permanent noncompliance with the IT folks. Hope this makes sense...

It may work for me because I do very little with Winhelp, and the "wrong font" issue has had a limited impact so far.

My most urgent problem is when I take the same project and produce a .chm file; I get the "font dump" issue. However, today I saw (on Peter Grainge's site) a suggestion for a delightfully simple workaround: put a manual page break at the beginning of each Word doc, and the font dump problem disappears! Since most of what I deliver now is just a .chm file, this workaround is perfect for me. Big sigh of relief....!

(An earlier suggestion was to put a "dummy" help topic at the beginning of each doc file, but I didn't like this because a user could stumble across these topics in the .chm if they did a search on the word "arial" or some other font name that was in the dump list.)

I will keep hoping that Adobe (Macromedia) comes through with a real fix soon.

Thanks again.

Karla

Captiv8r

Legend

Hi Karla

quote:

Since most of what I deliver now is just a .chm file

I guess it would be just rubbing salt in a very deep wound then to suggest that you are long overdue to step away from the nasty old Word editor, bite the bullet and move into the world of RoboHelp HTML? (Keep in mind that beginning with Vista, Microsoft is pulling all support for things WinHelp.)

(Rick backs away slowly looking in all directions for boots, rotten tomatoes, bullets, bricks and whatnot being hurled at him)

Cheers all... Rick

K

Karla_T

Participating Frequently

Any news from Microsoft Support regarding the promised "hotfix?" The problem persists for me and is a fairly serious annoyance. I have a large help project (1100+ topics, 50 Word docs) that requires lots of updating and maintenance.

An update from Peter Grainge or from Limestone Springs would be appreciated.

As an aside, I have now experienced both versions of the issue. When I compile WinHelp I see the "wrong font" (all Times New Roman) problem; when generating a .chm file from the same project I see the "font dump" problem.

It also seems to be unique to XP SP2; others at my company who have otherwise-identical configurations but are not yet at SP2 do not have the problem.

A

Anonymous

Karla T
The news from Microsoft is not promising. They sent me a fix for the "wrong font" problem, but in the meantime I noticed my second problem associated with the security update. The "placeMain" window appearred and would not go away. When I asked Microsoft about finalizing the font fix and mentioned the second problem, they replied with five paragraphs of garbage impling that the fix would not be done due to the effects it could have on "code stability". I have sent the information from Microsoft to Peter so he can nudge Macromedia into action. It looks like Macromedia will have to correct the compatability problems in RoboHelp. Microsoft also clued me in to the fact that the new release of Word (Word 12) will probably also break RoboHelp. So, the ball is in Macromedia's court to update Robohelp or find another editor besides Word.
Now the good news for you and me. I have you same problem at work as you. We are required to have the Microsoft Security Updates on our computer. Since Microsoft's font fix required a modification in Winword.exe, I uninstalled the security update that is causing the problem. This replaced Windword.exe with the old one that work with RoboHelp. I then made a copy of the old Winword.exe, and rebooted my computer to let the security update reinstall. I replaced the updated Winword.exe with the old one I copied (original) and Robohelp works fine. I rebooted the computer and Winword.exe was not over-written (HURRR..RAY!!!), so the computer thinks the security update is installed and RoboHelp is fixed. This should keep us going until Macromedia comes through with an update.

Thanks,
Limestone Springs

Captiv8r

Legend

LOL, is this like the longest thread in history?

Just a simple note. Macromedia is no more. It's all Adobe now. Had it still been Macromedia, I'd have said "good luck in seeing it ever get fixed". But Adobe seems intent on developing RoboHelp further.

I know Peter is off on holiday this week. I also know he has done all he can to bring this to the attention of the good folks at Adobe. So please know it's not falling into a big black hole somewhere.

Sincerely... Rick

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded