[Viewer 6.18.1] Inconsistent rendering of none english chars Issue

[tkinte]

Hi.

Non english chars are not consistent and correctly rendred from page to page. The isue appears in many new views. As illustration, please see the attachments


Best regards,

Tshitshi

[tkinte]

Impacted views list

• View: Application Capability Catalogue by Name

• View: Application Catalogue

• View: Business Capability Catalogue Table

• View: Business Process Catalogue as Table

• View: Business Capability Dashboard

• View: Business Capability Catalogue by Name

• View: Application Dashboard

• View: Application Catalogue (Table)

• View: Application Landscape

• View: Application Rationalisation Analysis

• View: Application Reference Model

• View: Business Process RTO/RPO Mapping

• View: Business Capability Tree

etc...

[JohnM]

Hi,

We had a couple of similar tickets recently, but couldn't recreate the issue. Do you have a repository (test/dummy data) you could share that has the issue?

Thanks

John

[tkinte]

Hi John,

OK. Will prepare a repo for test.
Could you help find the demorepo.zip on the current site. The https://enterprise-architecture.org/dow ... morepo.zip is broken.
Will use that repo to prepare a test repo.

Best regards

Tshitshi

Hi,

We had a couple of similar tickets recently, but couldn't recreate the issue. Do you have a repository (test/dummy data) you could share that has the issue?

Thanks

John

[iapaza]

Hello,
I have same issue, I had reported this a few days ago.
Please, We hope your answer as soon as possible.

Christian.

[neil.walsh]

Hi Tshitshi,

You can use this repository:

https://essential-cdn.s3-eu-west-2.amaz ... emo_os.zip

Cheers

Neil

[tkinte]

Hi Neil.

Please find the adapted repo with visual result of tests on the following github repo
https://github.com/ezzle/essential-proj ... er_6181.md

Best regards

Tshitshi

Hi Tshitshi,

You can use this repository:

https://essential-cdn.s3-eu-west-2.amaz ... emo_os.zip

Cheers

Neil

[neil.walsh]

Hi,

We have tested today with a variety of operating systems and browsers and cannot replicate the issue you are seeing. For us, the special characters always render correctly.

We have tested
Windows 11/ Chrome
Windows 11 / Edge
Windows 11 / Firefox
Windows 10/ Chrome
Windows 10 / Edge
Windows 10 / Firefox
Windows 10 / Opera
macOS 13 / Chrome
macOS 13 / Safari
macOS 13 / Edge
macOS 13 / Firefox

Can we get a little more detail on your current setup which might help us narrow down the issue?

What operating system and what version (Windows 10, macOS 13, Ubuntu 18, etc)
Which browser and what version (Chrome 114, Edge 113, Firefox 111, etc)
What is the default language of your machine?

Do you get the issue across all browsers on your machine? I.e. is Chrome different to Edge.
Have you experienced any similar language issues with other websites or apps?

Let me know and we'll see what we can find.

Thanks

Neil

[tkinte]

Hi Neil,

Tested on

Windows Server 2022 Standard Version 21H2 Build 20348.1726
Chrome Version 114.0.5735.110 (Build officiel) (64 bits)
Microsoft Edge Version 114.0.1823.43 (Official build) (64-bit)
Language : English (Windows) + Dutch (Apps & Web)

Windows 10 Entreprise Version 22H2 Build 19045.2965
Chrome Version 114.0.5735.110 (Build officiel) (64 bits)
Microsoft Edge Version 114.0.1823.43 (Version officielle) (64 bits)
Firefox 102.10.0esr (64 bits)
Français (Belgique)

I think the error is unlikely to be machine related. The same instance is displayed correctly by one report and incorrectly by another report: Same machine, same OS, same Browsers, same instance, only the reports change. Indeed If I take the Application Capability instance for example, the same characters are correctly displayed by the old "application/core_al_app_cap_summary.xsl" report, but incorrectly by the new "application%2Fcore_al_app_cap_list_by_name_filtered.xsl" report (Note! the name includes a space).




Best regards,

Tshitshi

Hi,

We have tested today with a variety of operating systems and browsers and cannot replicate the issue you are seeing. For us, the special characters always render correctly.

We have tested
Windows 11/ Chrome
Windows 11 / Edge
Windows 11 / Firefox
Windows 10/ Chrome
Windows 10 / Edge
Windows 10 / Firefox
Windows 10 / Opera
macOS 13 / Chrome
macOS 13 / Safari
macOS 13 / Edge
macOS 13 / Firefox

Can we get a little more detail on your current setup which might help us narrow down the issue?

What operating system and what version (Windows 10, macOS 13, Ubuntu 18, etc)
Which browser and what version (Chrome 114, Edge 113, Firefox 111, etc)
What is the default language of your machine?

Do you get the issue across all browsers on your machine? I.e. is Chrome different to Edge.
Have you experienced any similar language issues with other websites or apps?

Let me know and we'll see what we can find.

Thanks

Neil

[JohnM]

Quick update - We are still looking into this - we can't replicate so are trying a few other options

[JohnM]

Hi Tshitshi,

Apologies for this, we're still unable to replicate. Can you open this file and send us a screenshot back of what you get for a row with odd data.

Thanks

core_bl_bus_cap_list_as_table_filtered_chars.xsl.zip

[tkinte]

Hi Tshitshi,

Apologies for this, we're still unable to replicate. Can you open this file and send us a screenshot back of what you get for a row with odd data.

Thanks
core_bl_bus_cap_list_as_table_filtered_chars.xsl.zip

Hi John.

Same issue as you can see

[tkinte]

Not Same issue from https://neon.essentialintelligence.com/ Demo viewer 3

httpsneon.essentialintelligence.com.png

Similar issues
viewtopic.php?f=21&t=2945

viewtopic.php?f=21&t=2940

Best regards

Tshitshi

[JohnM]

Hi Tshitshi,

Thanks, that's helped narrow down where the issue is for us.

John

[JohnM]

Can you try something, please. In the enterprise/api folder find the core_api_el_bus_cap_to_app_mart_caps.xsl file and do a global replace of <xsl:with-param name="isForJSONAPI" select="true()"/> with <xsl:with-param name="isForJSONAPI" select="false()"/>

in the Integration/api folder find core_api_import_business_capabilities.xsl. and do the same. Then publish, open the view (give the caches a chance to finish). The view should fail, refresh the page, then open the console and you should see an error something like

Screenshot 2023-06-20 at 09.47.43.png

.

Click the link on the right-hand side, which should show you the error in the JSON and then send us a screenshot of the JSON where the error is.

Set your selects to true() on the APIs after this.

Thanks

[JohnM]

Also, we suspect it is related to Tomcat encoding. Can you open your web.xml in tomcat and uncomment this section:

<filter>
<filter-name>setCharacterEncodingFilter</filter-name>
<filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
<init-param>
<param-name>encoding</param-name>
<param-value>UTF-8</param-value>
</init-param>
<async-supported>true</async-supported>
</filter>

restart Tomcat and publish then see what it does

[tkinte]

Hi .
Error Message

Code: Select all

Uncaught SyntaxError: JSON.parse: expected ',' or '}' after property value in object at line 4 column 47 of the JSON data
    onreadystatechange http://finvmeafivued01.finbel.intra:8080/essential_viewer_6181/report?XML=reportXML.xml&PAGEXSL=&PMA=&XSL=business/core_bl_bus_cap_list_as_table_filtered_chars.xsl&LABEL=Business Capability Catalogue chars&&targetReportId=&targetMenuShortName=&cl=en-gb:1267

Screenshots





Best regards,

Tshitshi

[/code]

Can you try something, please. In the enterprise/api folder find the core_api_el_bus_cap_to_app_mart_caps.xsl file and do a global replace of <xsl:with-param name="isForJSONAPI" select="true()"/> with <xsl:with-param name="isForJSONAPI" select="false()"/>

in the Integration/api folder find core_api_import_business_capabilities.xsl. and do the same. Then publish, open the view (give the caches a chance to finish). The view should fail, refresh the page, then open the console and you should see an error something like Screenshot 2023-06-20 at 09.47.43.png.

Click the link on the right-hand side, which should show you the error in the JSON and then send us a screenshot of the JSON where the error is.

Set your selects to true() on the APIs after this.

Thanks

[tkinte]

Hi John

Seems OK. But I see the isue persists on the other machine. May be a local cache issue.

Will do more testing and let you know.




Best regards

Tshitshi

Also, we suspect it is related to Tomcat encoding. Can you open your web.xml in tomcat and uncomment this section:

<filter>
<filter-name>setCharacterEncodingFilter</filter-name>
<filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
<init-param>
<param-name>encoding</param-name>
<param-value>UTF-8</param-value>
</init-param>
<async-supported>true</async-supported>
</filter>

restart Tomcat and publish then see what it does

[neil.walsh]

Hi,
Just to add a little more to the investigations here....

from the command line can you try running the following

Code: Select all

java -XshowSettings

You should see something like

Code: Select all

file.encoding = UTF-8

Additionally, you could try modifying the connector in the Tomcat server.xml file (typically in the tomcat/conf/ directory) to include the URI encoding

Code: Select all

<Connector port="8080" 
           protocol="HTTP/1.1"
           connectionTimeout="20000"
           URIEncoding="UTF-8"
           redirectPort="8443"/>

Finally, just to document the web.xml change suggested above. In the Tomcat web.xml (typically in the tomcat/conf/ directory), uncomment the filter and the filter mapping for UTF8 support.

Code: Select all

<!-- A filter that sets character encoding that is used to decode -->
 <!-- parameters in a POST request -->
 <filter>
        <filter-name>setCharacterEncodingFilter</filter-name>
        <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
        <init-param>
            <param-name>encoding</param-name>
            <param-value>UTF-8</param-value>
        </init-param>
 </filter>

  <!-- The mapping for the Set Character Encoding Filter -->
  <filter-mapping>
        <filter-name>setCharacterEncodingFilter</filter-name>
        <url-pattern>/*</url-pattern>
  </filter-mapping>

Let us know if this helps in any way

Thanks

Neil

[tkinte]

Hi John and Neil.

Green light

Tests OK.

I had to set the java's file.enconding to utf-8 on the Tomcat and Protégé Server Machines.

https://genrocket.freshdesk.com/support ... g-to-utf-8

Thank you very much for the support.

Best regards,

Tshitshi

Hi,
Just to add a little more to the investigations here....

from the command line can you try running the following

Code: Select all

java -XshowSettings

You should see something like

Code: Select all

file.encoding = UTF-8

Additionally, you could try modifying the connector in the Tomcat server.xml file (typically in the tomcat/conf/ directory) to include the URI encoding

Code: Select all

<Connector port="8080" 
           protocol="HTTP/1.1"
           connectionTimeout="20000"
           URIEncoding="UTF-8"
           redirectPort="8443"/>

Finally, just to document the web.xml change suggested above. In the Tomcat web.xml (typically in the tomcat/conf/ directory), uncomment the filter and the filter mapping for UTF8 support.

Code: Select all

<!-- A filter that sets character encoding that is used to decode -->
 <!-- parameters in a POST request -->
 <filter>
        <filter-name>setCharacterEncodingFilter</filter-name>
        <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
        <init-param>
            <param-name>encoding</param-name>
            <param-value>UTF-8</param-value>
        </init-param>
 </filter>

  <!-- The mapping for the Set Character Encoding Filter -->
  <filter-mapping>
        <filter-name>setCharacterEncodingFilter</filter-name>
        <url-pattern>/*</url-pattern>
  </filter-mapping>

Let us know if this helps in any way

Thanks

Neil

[JohnM]

Thanks for your help in resolving this Tshitshi.

John