Has the font problem already been solved?

[hadjira]

Is there a new solution for the well known "Times New Roman" problem (fonts shifting into this style when compiling) ? The long discussion with 120 contributions did not contain a solution for me: I uninstalled all security updates of the last few months that could have caused the problem, even more, one by one, I downloaded the dll file from the Adobe homepage but nothing changed.
For instance, I applied a radical solution, because I couldn't continue to work under these conditions:
I deleted all Times New Roman fonts from my windows system, RoboHelp has now no chance to convert my fonts into Times. But that can't really be a definite solution, can it?

[Peter Grainge]

No point in starting a new thread. It just starts to split up any additional information that may be found.

I don't think I have seen any RH6 users report this problem but that is not to say it was fixed there. It could simply be that few RoboHelp for Word users upgraded. I'll make some enquiries about RH6.

Interesting solution. Did you try renaming the fonts to say My Times New Roman to see if that allowed you to keep the fonts while avoiding this issue?

[hadjira]

I didn't try renaming the fonts, I have now another problem: All signs like - and " appear as vertical bars in help file (in preview and after compilation).
It just can't be, that people are forced to update for quite a lot money to RoboHelp 6 because RoboHelp 5 doesn't work properly any more!!!
One could think that the software was consciously infiltrated by errors to make people buy the updates. The problems began just before the release of RoboHelp 6 - what a coincidence !!!

Sorry, but I'm becoming really angry ... this "little" problem made me lose a lot of time!

[Peter Grainge]

I didn't say RH6 was the solution, simply that I had not seen any RH6 users complain of this problem. In fact I have been told that nothing was different in RH6.

Also bear in mind that the problem has arisen because of updates Microsoft introduced so it is not linked to the new version of RoboHelp, confirmed by the fact that the fix was not changed in that version so there would be no reason to upgrade just for this.

I don't know why you are having this new problem but I don't think it is necessary to insinuate that Adobe have done anything malicious. Vertical bars usually appear when HTML does not understand something but that is usually in the code.

Can you create this problem in a new project?

Save the anger until you know this is a RoboHelp problem rather than something in your project. At this point, that could be the case.

[Guest]

As a matter of interest, which version of word are you using? Have you imported the word documents, or have you cut and paste?

Brian

[hadjira]

I'm using Office 2003. My collegue working with office 2000 never had those problems.

I have a large number of projects, most of them already existed when we used RoboHelp 4 and older versions of MS Office. Old an new projects show the same problems: imported ones, documents written by myself in an new project, texts I copied......
I installed a test version of RH 6 and restored my Times N.R. font in my windows registry... also with RH6 the font is converted (in the preview and after compilation). The signs (-"(...) appear all right with times new Roman. When I delete Times New Roman, Arial is taken but instead of the signs I only have the large vertical bars.
What I don't understand: MS updates seemed to cause it, but uninstalling the updates doesn't change anything.

I think I'll format my whole machine, reinstall Windows and return to Office 2000, then reinstall RH.

And never ever execute a Security update!!!!

[Peter Grainge]

Before you stick your PC in a bowl of bleach, try turning off Smart Tags in Word 2003. Just a hunch.

[hadjira]

Thanks for the hunch, but it doesn't help.

The bowl of bleach is a good idea ;-)
But I think I'll rather reinstall office and RH.... and pray!

[Peter Grainge]

Come on guys, lets all pray for Hadjira.

[Guest]

hadjira,

Check out the article in this link. There is a known problem with word that fits what you are describing.

Hope this helps, I should have checked the word forums sooner

Brian