Highlighted

Problem with substring search with German umlauts RH2019.0.12 new UI HTML5 output

Engaged ,
Apr 30, 2020

Copy link to clipboard

Copied

Hi all,

I have a problem with the substring search in the HTML5 output. I am using RH2019.0.12 new UI, but the problem also occured with update 11. The search settings for my output are as follows:

Use topic description = true

Enable auto complete = true

Auto correct search query = false

Show definitions from glossary = true

Enable substring search = true

Add special characters for search = false

Generate XML sitemap = false

 

In my output, I have several topics containing the word "Primäreinzelkosten". If I search for "primär", I only get results containing exactly the word "primär", but not the "primäreinzelkosten". If I search for "primä", I get no results at all. If I search for "prim", I get all topics containing "primär", "primäreinzelkosten" and "primrose" or whatever. So the substring search seems to have a problem with the "ä". The substring search works as expected for example when searching for topics containing the word "Kostenblock". They are found whether I search for "koste", "kosten", or "kostenb".

 

My project language is set to German, my output language is also set to German. I tried outputs with the following Encoding settings: Default Encoding, Westeurope(ISO), UTF-16, UTF-8 without BOM. I also tried the outputs in different browsers (Chrome, Edge, Firefox). No matter what, I do not get any results when searching for "primä".

 

Does anyone know if there are further settings that I can check in order to make this work? Or is this a bug? In this case, I will create a bug regort.

 

Thanks and regards
Karin

Views

154

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Problem with substring search with German umlauts RH2019.0.12 new UI HTML5 output

Engaged ,
Apr 30, 2020

Copy link to clipboard

Copied

Hi all,

I have a problem with the substring search in the HTML5 output. I am using RH2019.0.12 new UI, but the problem also occured with update 11. The search settings for my output are as follows:

Use topic description = true

Enable auto complete = true

Auto correct search query = false

Show definitions from glossary = true

Enable substring search = true

Add special characters for search = false

Generate XML sitemap = false

 

In my output, I have several topics containing the word "Primäreinzelkosten". If I search for "primär", I only get results containing exactly the word "primär", but not the "primäreinzelkosten". If I search for "primä", I get no results at all. If I search for "prim", I get all topics containing "primär", "primäreinzelkosten" and "primrose" or whatever. So the substring search seems to have a problem with the "ä". The substring search works as expected for example when searching for topics containing the word "Kostenblock". They are found whether I search for "koste", "kosten", or "kostenb".

 

My project language is set to German, my output language is also set to German. I tried outputs with the following Encoding settings: Default Encoding, Westeurope(ISO), UTF-16, UTF-8 without BOM. I also tried the outputs in different browsers (Chrome, Edge, Firefox). No matter what, I do not get any results when searching for "primä".

 

Does anyone know if there are further settings that I can check in order to make this work? Or is this a bug? In this case, I will create a bug regort.

 

Thanks and regards
Karin

Views

155

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Apr 30, 2020 0
Adobe Community Professional ,
Apr 30, 2020

Copy link to clipboard

Copied

I'm thinking of the old CHM format that has issues if not used on a machine with the same language operating system.

 

Are you testing on a machine with German as the OS. I'm doubtful with this format but worth a try.

 

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 30, 2020 0
Engaged ,
Apr 30, 2020

Copy link to clipboard

Copied

Hi Peter, 

yes, my machine runs a German OS.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 30, 2020 0
Adobe Community Professional ,
Apr 30, 2020

Copy link to clipboard

Copied

Try techcomm@adobe.com first. 

 

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 30, 2020 0
Adobe Community Professional ,
Apr 30, 2020

Copy link to clipboard

Copied

I just tried putting both the words below in separate topics and generated with both a frameless and a responsive skin. Worked both times.

 

image.png

 

Try in a test project and see what you get.

 

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 30, 2020 0
Engaged ,
May 03, 2020

Copy link to clipboard

Copied

Hi Peter,

I just ran the test, same issue with a brand new project and default skin Azure Blue:

 

 Umlaut1.pngUmlaut2.pngUmlaut3.png

 

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 03, 2020 0