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

Special Characters in DCR

rahulkulkarni

I am generating DCR through WORKFLOW in external task ipl file .

The DCR Is genarating as per requirement. but while editing DCR it is showing an

Error 'Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]: Invalid byte 2

of 4-byte UTF-8 sequence'. I am facing this error only for some HTML file

generated DCR. Others DCR are Editing properly.

As per my understanding there might be some special character might be in my

HTML file, Can you Please let me know Hoe to remove this Special character in

PERL?

Find more posts tagged with

Comments

Adam Stoller

Can you Please let me know Hoe to remove this Special character in PERL?

If you show us the code you use to create the DCR, we can probably figure out what you're doing wrong.

Aghosh

Hi,

I Would suggest you go and try to generate the page without the workflow.i.e go the branch and edit the dcr and generate , i think there might be error with the datacapture.cfg or the data entered in the dcr. if workflow is working fine with other dcrs being generated then i think the wf is working fine.

twTest.rptdesign

Adam Stoller

Hi,

I Would suggest you go and try to generate the page without the workflow.i.e go the branch and edit the dcr and generate , i think there might be error with the datacapture.cfg or the data entered in the dcr. if workflow is working fine with other dcrs being generated then i think the wf is working fine.

I'm not sure if you're interpreting the original post correctly - though it would be understandable if you didn't.

The original post indicates that the DCR is the problem and the DCR is being generated - not that the DCR is okay and the page being generated from the DCR is a problem.

Based on my - literal - interpretation of the original post - the question (and answer) most likely lies in the code used to generate the DCR.

ISCBorisB

Based on my - literal - interpretation of the original post - the question (and answer) most likely lies in the code used to generate the DCR.

Another problem may be the content that has been used to create DCRs (Data feed, documents, whatever).

An error indicates invalid UTF-8 octets sequence. There are numerous reasons why that could happen.
For example, the original document may have had different (non UTF-8) encoding and DCR-building code
failed to correctly decode/encode in UTF-8, etc. MS Office documents with it's silly "Smart"(?!) quotes may also
cause problems of that nature. Documents that use "right side" ASCII encoding (bigger than 128) are
suspects and so on.