Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

German umlauts rendering as ?'s (AEM 6.4.5)

Avatar

Avatar
Level 1
salcap1
Level 1

Likes

0 likes

Total Posts

5 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
salcap1
Level 1

Likes

0 likes

Total Posts

5 posts

Correct Reply

0 solutions
View profile
salcap1
Level 1

29-03-2021

Hi all,

 

I've been working on this issue for a few days now. Honestly just going for a 'sounding-board' type method here to see if anyone's comments spur an idea.

 

I have inherited a project with the idea of redesigning and upgrading as time goes on. Everything is going fairly swell except for German text rendering. In my local machine I can edit components that have been created with RTE's in their dialog that are sling:resourceSuperType from the Text v2 Core Component and successfully save and render German umaluts (ä ö ü...). 

 

When installing the code to a Stage environment, these same components render the umlauts as ?'s. Now, I checked the JCR nodes and they do in fact still save the authored content with the correct umlauts. There appears to be something happening between retrieving from the JCR and rendering on the page. Keep in mind that the Stage environment is a pretty bare environment. I would have thought it to be exactly identical to my local AEM environment but it appears not.

 

Another weird behavior...we also have a Development AEM environment and when I install the code there, the umlauts DO render correctly. It appears to only be the Stage where I have an issue. I have referenced content packages, bundles, OSGI configs to attempt to find a difference between these environments with no luck.

 

I did perform Language Translation for Language Copies on the Stage environment but I'm 99% sure I performed that action locally also.

 

To summarize, I believe I have 3 identical environments with identical code and one of them is not rendering umlauts correctly while all of them properly save the umlauts to the JCR.

 

Any ideas are appreciated!

 

Supporting Images:

GOOD:

Screen Shot 2021-03-29 at 6.09.23 PM.png

 BAD:

Screen Shot 2021-03-29 at 6.09.15 PM.png

Related Packages:

AEM Service Pack 6.4.5

Core Components v2.3.0

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

30-03-2021

Hi,

 

interesting one 🙂 Can you check the LOCALE of the underlying system and the user? Also cross-check that the mbean java.lang:Runtime shows the same statements regarding locale.

 

Cheers,

J?rg 🙂

Answers (1)

Answers (1)

Avatar

Avatar
Validate 25
MVP
Singaiah_Chintalapudi
MVP

Likes

131 likes

Total Posts

234 posts

Correct Reply

39 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Validate 25
MVP
Singaiah_Chintalapudi
MVP

Likes

131 likes

Total Posts

234 posts

Correct Reply

39 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile
Singaiah_Chintalapudi
MVP

29-03-2021

Check the encoding config on AEM and see if that helps:

 

Go to Apache Sling Request Parameter Handling OSGI config and change the Default Parameter Encoding to "UTF-8" and see if this helps.