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; } } }

getting error for the é character

sabya

I am saving categories name which have a character é in it. I save these in a .meta file.Now when I am trying to read the same in a datacapture.cfg through a .ipl file I am getting error. the character é gets converted to a junk box character. I am using encoding="UTF-8" . I need to fic this very urgently. please help.

Find more posts tagged with

Comments

Samir_Friend

I am saving categories name which have a character é in it. I save these in a .meta file.Now when I am trying to read the same in a datacapture.cfg through a .ipl file I am getting error. the character é gets converted to a junk box character. I am using encoding="UTF-8" . I need to fic this very urgently. please help.

Does the IPL file also gives you a junk character after reading it from the .meta file? OR what is the IPL output?

sabya

samir , the ipl file returns me properly.

Samir_Friend

Can you post your DCT and IPL code

sabya

please do find the files attached

Samir_Friend

Since it is not considering your XML as well-formed(An & char is usually the culprit since your char is represented by é ) try using this:


use HTML::Entities;
.
.
.
.
$option_list .= qq(......);
$option_list = HTML::Entities::decode($option_list);

Now Print the option_list

If it doesn't help you might need to get the numeric encoding of the special characters in the IPLs output first.

sabya

its not working. and I have to use UTF-8 for encoding.please let me know any solution keeping these into consideration.also find the attachment where i have taken a screenshot of the error.

Samir_Friend

This is not an error, it's a misrepresentation. You should have attached the snapshot in your original post so that people don't confuse it with an error in your datacapture xml.

Anyways, I can think of these two things at the moment:

1. It could be a browser issue, so that you may need to change the encoding of your browser to see it correctly.
2. If 1. is not true, use HTML::Entities package functions to encode your default ISO-8859-1 output into UTF-8 and then try decoding it similarly using UTF-8 in your IPL just before printing onto the datacapture.cfg

Let us know your findings.

ISCBorisB

its not working. and I have to use UTF-8 for encoding.please let me know any solution keeping these into consideration.also find the attachment where i have taken a screenshot of the error.

Your inline emits ISO-8859-1 output and then you are viewing it in UTF-8 DC Form rendition.

Single byte é is an invalid UTF-8 character so the browser shows it as a little square. Modify inline
to output correct UTF-8 encoding

sabya

boris, if you have any code which i can try putting inline and check.please let me know.

ISCBorisB

boris, if you have any code which i can try putting inline and check.please let me know.

If I were you I would've tried to fix the issue without any code changes, simply by fixing an
encoding of this "meta" file of yours to valid UTF-8.

If you can not do it (eg, "meta" is used for something else, etc) take a look at [post=142748]this[/post] sample.
Note that there I illustrate UTF-8 => Latin1 conversion, you will need it the other way around