Bug in Visual Format in TS 6.7.1 - SP1??

Okay, we are testing to see if SP1 makes it through our testing and I've hit something that doesn't seem quite right to me.

Solaris 10
TS 6.7.1 - SP1

The visualformatconfig.xml file has changed between 671 and 671SP1 and one of the many changes in the file is one where the default value for the character encoding is set to "utf-8" instead of "entityname".

The client I am working with expects that the characters such as é will be encoded within the html as é and not as a literal value.

So I changed the value for the character encoding from "utf-8" to "entityname" like so:

[html]

object="true" mswordfilter="true">

[/html]

Now whenever I type in é into my visualformat box, I get the following error:

[html]
Transform Error C00CE002 (-1072898046)

Reference to undefined entity 'eacute'.

Internal filter XSLT
XML
********************************************************************************

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

test

********************************************************************************

eWebEditPro v5.1.0.41
2007-10-12 1:37:13 PM

[/html]

I close the box and I see that my characters have been properly enconded. This happens for even such characters such as spaces. (same error message as above but replace the following message with the one that follows it:

* Reference to undefined entity 'eacute'.
* Reference to undefined entity 'nbsp'.

I am using the Out of the box visualformat config that comes with TS 671-SP1 and have not made any other changes to it other than the character encoding.

Thoughts?

Thoughts?

Find more posts tagged with

Comments

FurnaceFace

okay... It was a lovely way to spend 1.5 hours but I finally managed to get SP1 and VisualFormat to work the way we used to have it.

My bad for not fully trying all iterations of reverse changes that were done to SP1. I thought I would at least follow up in case anyone else follows in my footsteps.

Further down in the visualformatconfig.xml file, you will find the setting "viewas" - the previous default settings have changed as well (as stated on page 105 of the TS forms publisher dev guide) and I had to change them all back to the same settings that were there in TS 6.7.1 to get the character encoding of "entityname" to work properly.

Apologies for wasting bandwidth... The inhouse creation of a "best practices" document for upgrading from TS 6.7.1 to TS 6.7.1-SP1 continues... Smiley Wink

Enjoy your weekend.
/FF

Kev

We have exactly the same problem, is there any chance that you could detail the changes that you made to "viewas"?

Do you mean this "viewas" bit?

< viewas view="wysiwyg" publish="xhtml" mode="body" unicode="false">
...
< /viewas>

Thanks

Kev

Migrateduser

Did the suggested changes. Still same issue. Any other catch in this?

Kev

I guess that no one is going to answer us kadiyala. :-(

FurnaceFace

Hi Kev,

Sorry for not getting back earlier, to be honest, the client went in a completely different direction with the encoding and we ended up fiddling with the visuaformatconfig.xml settings quite a bit.

Try changing the unicode value to true. That was the only value we changed in the ViewAs section.

hope that helps,
/FF

DougD

The character encoding should be "utf-8", not "entityname".

Migrateduser

I was getting a similar validation error. I decided that the simplest approach would be to go back to the default config and then start migrating my changes over one by one rather than trying to update my old config file.

moulikk

Any others faced a similar issue and have a resolution?

I have all tried all the above possible solutions. No success.

Kev

We have changed one line of our code from:

<clean charencode="entityname" cr="cr" lf="lf" preferfonttag="false" reducetags="true">

to:

<clean charencode="entityname" cr="cr" lf="lf" showonsize="5000" preferfonttag="false" reducetags="true" showdonemsg="true" prompt="true" hideobject="true" mswordfilter="true">

and it seemed to work.