[CAMPMAN-45] Words with diacritics in static page Created: 29/Jun/23  Updated: 22/Sep/23  Resolved: 21/Sep/23

Status: Closed
Project: Campaign Manager
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Mykola Assignee: Teresa Miyar
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Win10 x64


Issue Links:
Problem/Incident
causes INCUBATOR-40 CAMPMAN-45 Words with diacritics in s... Closed
is caused by CAMPMAN-48 Update documentation no light modules... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Work Started:

 Description   

Steps to reproduce

  1. Import static page with polish text (checked in both modes: UTF-8 and CP437)
  2. Choose index.html in HTML Bridge page template
  3. Open page

Expected results

Polish text is showing without errors

Actual results

Polish text have question mark or random symbols in places where diacritics was

Workaround

Development notes

Looks like on MacOS it's working ok

campaign-importer 3.0.8
magnolia dx core 6.2.29



 Comments   
Comment by Teresa Miyar [ 28/Jul/23 ]

Hi,

Could you send a sample file for testing and also check the file.encoding value and all the other language valuesin about config like this https://demo.magnolia-cms.com/.magnolia/admincentral#app:about:config

Comment by Teresa Miyar [ 28/Jul/23 ]

Hi,

Update:

If it works on Mac and Not on windows then probably the issue could be cleared with:

JVM_SUPPORT_RECOMMENDED_ARGS="-Dfile.encoding=utf-8 -Dsun.jnu.encoding=utf-8"
Comment by Teresa Miyar [ 12/Sep/23 ]

Hi,
Did the JVM args fixed your issue?

Comment by Mykola [ 14/Sep/23 ]

Hi,
Sorry for the late response
yes, looks like it worked
am I understand it correctly, that JVM args are making impact because files are not simply loaded but reproduced in the Resources workspace?

Comment by Teresa Miyar [ 15/Sep/23 ]

Hi,

No, the resource files are displayed there, when you modify one directly in the resources workspace, then, it makes a copy and you will have the original file in your light module or war file and the one the overrides it in the resources workspace.
What handles the encoding is the request/response processing, that is, when reading the file to deliver it to the end user.

Comment by Mykola [ 16/Sep/23 ]

I'm not shure about original file in light module/war, cause when using Campaign importer we don't have original files there - we just importing static files from users PC to Magnolia (into resources workspace)
but  I understand request/response part
thank you

Comment by Teresa Miyar [ 21/Sep/23 ]

You can either create/upload files in the resources workspace or create a light module to pick them up and have the possibility to override them in the resources, you can find more information in the following link https://docs.magnolia-cms.com/product-docs/6.2/Modules/Light-modules.html
I will proceed to close this ticket now.

Comment by Mykola [ 21/Sep/23 ]

Yes, you can add files in resources or light module, what I meant was that Campaign publisher module and it's app doesn't work with light modules - it's only for static files imported from pc to resources workspace and not to the source code.

sure, we can close this issue
maybe worth updating the docs

Comment by Teresa Miyar [ 22/Sep/23 ]

Ok, I understand now, thank you, we will update the docs.

Generated at Sun Feb 11 23:55:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.