Skip to main content
thierryp53002420
Participant
March 9, 2020
Question

Encoding problem in search tab in CHM output

  • March 9, 2020
  • 2 replies
  • 334 views

Hi,

I am using Robohelp 2019.0.11 and I work on a project in french.

When I generate my project in a CHM output, the search tab seem to have an encoding problem.

 

Example :

My first topic is named "Première rubrique". When I search the word "rubrique", the search tab display my topic as "Premèire rubrique".

Also, when I search the word "Première", the CHM show a window with "No topic found". So I can't search word with accents and it is problematic with a french project.

 

 

Can I do something to fix this problem ?

Thanks in advance !

This topic has been closed for replies.

2 replies

Peter Grainge
Community Expert
Community Expert
March 9, 2020

In that case you must report it as a bug.

 

Please follow this link to report bugs or request features. https://tracker.adobe.com

 

Post the link to your bug report / feature request in this thread and others can vote for it. The more people who do so, the higher it gets prioritised.

 

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

It looks like someone had this problem before me and has already reported it. It seems I'll have to wait for the next update

Here is the link : https://tracker.adobe.com/#/view/RH-6554

 

Thanks again for your help.

Peter Grainge
Community Expert
Community Expert
March 9, 2020

I suggest you create a new project in Classic with the same title and see how the search goes in that. I am wondering if the issue is something the New UI is not handling. Let us know.

 

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

Thank you for your help.

 

I created a project then a topic with the same title in Robohelp Classic, and it seems that the problem doesn't exist with Classic.