nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

HTML Entities in Visual format

ramam77

Hi,

When I enter danish characters (ø,å)in my visual format, in the WYSIWYG its appearing properly . But HTML mode (Source View) converts these to their HTML equivalent(å). If i take the value of that field using formapi , I get the html equivalent characters not the original danish characters. How can i decode these to the original the danish characters .
Is there any setting in the visual format need to be done or it has to be done through form api. Please advice.

TS version 6.1
Regards,
Nirmala

Find more posts tagged with

Comments

Migrateduser

I used to have the same problem and I had to translate them back to their original characters with FormAPI. If someone knows of a way to configure this setting within eWedbEditPro, please share!

Johnny

Does it help if you set the encoding to utf-8 in the vfe config?

Migrateduser

Hi Nirmala,

The VFE allows you to render the accented characters properly. As pointed out by Johnny, you can use utf-8 encoding in VFE configuration file.

But there is a catch, for utf-8 to work properly, the rendering must be done only once or else the character would be doubly parsed and then it will be treated as 2 characters instead of one.

You can try out utf-8 first, but if that does not work out properly, try to modify

[color=black] charencode="utf-8" cr="cr" lf="lf" showonsize="5000" preferfonttag="false" reducetags="true">[/color]

to

[color=black] charencode="entityname" cr="cr" lf="lf" showonsize="5000" preferfonttag="false" reducetags="true">[/color]

I hope this will be able to solve all your problems and for the current html pages you can open the DCRs and use

1. Right click on VFE fiels --> select clean source

1. modifying the content in VFE auto forces a clean source.

This will allow you to solve the problem, I faced this issue on Production server and was able to resolve it.

-Rahul.

niks

Hi,

If you were able to solve it through Form API , Could You please share the code, even I am facing the same problem

Regards,
Niks

Migrateduser

Hi Nicks,

this problem occurs if the TS database is unable to store the utf-8 encoding properly and sometimes render the utf-8 characters as a combination of two characters due to 16 bit.

As pointed out, the Visual Format Editor which uses ewebeditpro could be used to solve these issues. In the visualformatconfig.xml file you can change the "charencode" attributes value to entityname. this will allow the accented character to be stored as a named character in database and since all older browsers support the entityname, the problem will vanish away.

-Rahul.