DCR parsing error

I am creating some dcrs while generating a template. I am getting the following error when I am trying to edit the dcrs in CCI. I've checked the dcr and it's well formed. What can be the reason?

Root cause:
Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]:Invalid byte 1 of 1-byte UTF-8 sequence.

Details...

com.interwoven.ui.formspub.datacapture.EditDCRPredicate$ReadDCRException: Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]:Invalid byte 1 of 1-byte UTF-8 sequence.

Find more posts tagged with

Comments

gzevin

I am creating some dcrs while generating a template. I am getting the following error when I am trying to edit the dcrs in CCI. I've checked the dcr and it's well formed. What can be the reason?

Root cause:
Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]:Invalid byte 1 of 1-byte UTF-8 sequence.

Details...

com.interwoven.ui.formspub.datacapture.EditDCRPredicate$ReadDCRException: Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]:Invalid byte 1 of 1-byte UTF-8 sequence.

check your containers and items - are pathid's and locations set properly?

ISCBorisB

I am creating some dcrs while generating a template. I am getting the following error when I am trying to edit the dcrs in CCI. I've checked the dcr and it's well formed. What can be the reason?

Root cause:
Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]:Invalid byte 1 of 1-byte UTF-8 sequence.

Details...

com.interwoven.ui.formspub.datacapture.EditDCRPredicate$ReadDCRException: Couldn't parse DCR bytes into DOM [unable_to_parse_dcr ]:Invalid byte 1 of 1-byte UTF-8 sequence.

It is impossible to say exactly what happened without looking at the DCR in question

If I have to speculate, you are probably using some ISO-encoded single-byte symbols that
should be multi-bytes in UTF-8. That includes for example Yen/Euro signs, special letters (with
acute, umlaut, etc...) used in many European languages and so on. In short, any symbol that
has ISO hex encoding greater than 0x7F.

JoshProx

yeah boris....I checked my dcr and it was encoding issue for some of the characters. I am now using HTML::Entities::encode_entities to wrap the text where those characters are expected. Is there a better way to handle that?

ISCBorisB

Is there a better way to handle that?

What is *better* really depends on how you use the Data in your generated DCRs. Compare for example the difference in the following outputs

use HTML::Entities qw(
   encode_entities
   encode_entities_numeric
);
use Encode;

$input = qq(vis-à-vis Beyoncé's naïve\npapier-mâché résumé);
print "\n", encode_entities($input), "\n";
print "\n", encode_entities_numeric($input), "\n";
print "\n", encode_utf8($input), "\n";

JoshProx

If I use encode_utf8, I get the same error while editing the dcr. And also if I use the first two then characters are shown as encoded when I edit the dcr; i.e. I don't see the accenuated characters. Is there a way to display the accenuated characters when the user edits the dcr.

ISCBorisB

If I use encode_utf8, I get the same error while editing the dcr. And also if I use the first two then characters are shown as encoded when I edit the dcr; i.e. I don't see the accenuated characters. Is there a way to display the accenuated characters when the user edits the dcr.

Proper (read multi-byte) UTF-8 encoding is perfectly adequate for Displaying and Saving accentuated characters.
Screen-shot below illustrates the topic. It shows both DCR rendered with the DC Form and the same DCR in Editor's
Hex Mode. All that is plain vanilla TS, I did absolutely nothing special.

Without additional information we can not know what went wrong in your case. Perhaps you did not use Encode package
correctly (it is plenty more than just encode_utf8!), ignored conversion errors, did not set Source encoding correctly
and so on. Run perldoc Encode, read it and modify your scripts. If you have problems, post your code and source sample.