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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Translated pages showing Wrong Special Characters in page properties

ArunaSurukunta
Level 5
Level 5

 

 

Hi All,

 

I am facing issues with translated content after coming back from Translated services, AEM is showing content as mentioned below screenshot.

 

We are creating pages in language master and sending them for translations to translate the content. Once the content pages are back from translation servers, in AEM  page properties showing below.

Please help me on how to resolve this issue.

translationCapture.png

1 Accepted Solution
BrianKasingli
Correct answer by
Community Advisor
Community Advisor

annyreddy, you might need your translator to NOT encode special symbols and characters, as your example shows, the Granite UI dialogues will not decode the ended.

Once your data is written in AEM with regular symbols and characters, Making sure your pages are encoded in UTF-8 , your symbols and special characters should be played property to the end uses. If you cant do this, then maybe you would probably need to create something custom to run when translations are written into AEM; Decode all the ended. Checkout this tool here for encoding/decoding special symbols and characters, https://www.web2generators.com/html-based-tools/online-html-entities-encoder-and-decoder

 

<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>

 

View solution in original post

2 Replies
BrianKasingli
Correct answer by
Community Advisor
Community Advisor

annyreddy, you might need your translator to NOT encode special symbols and characters, as your example shows, the Granite UI dialogues will not decode the ended.

Once your data is written in AEM with regular symbols and characters, Making sure your pages are encoded in UTF-8 , your symbols and special characters should be played property to the end uses. If you cant do this, then maybe you would probably need to create something custom to run when translations are written into AEM; Decode all the ended. Checkout this tool here for encoding/decoding special symbols and characters, https://www.web2generators.com/html-based-tools/online-html-entities-encoder-and-decoder

 

<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>

 

View solution in original post

narayanj2824445
Level 1
Level 1

@ArunaSurukunta What exactly worked for you the translator or page encoding?