Thanks! Hi,

When trying to use the character 'ë' -- encoded as ë -- in my xml
response
I get the error message "Reference to undefined entity 'euml'".

Does anyone have an idea what triggers this problem and more important
how to solve it?

Thanx!

Sounds like an encoding issue (decoded char does not exist for the 
encoding you are using). Try specifying UTF-8.

Ken

Hi,

Where do I need to specify UTF-8?

Cheers

Your response should start with something like:

<xml version="1.0" encoding="iso-8859-1"?>

change it to:

<xml version="1.0" encoding="UTF-8"?>

Up till now I have never specified this.
Is this in the manual?

Going to try it...

Thanks for the clue

I needed to make sure that the following components had compatible 
character sets:
1. mysql datbase      : Collation -->latin1_general_ci
2. php   htmlentities : htmlentities( $string, ENT_NOQUOTES, 
'iso-8859-1')
3. start rico response with : <?xml version="1.0" 
encoding="iso-8859-1"?>
(do not forget the first question mark (?) )

Now it works.

Cheers

I'm seeing this same problem using Live Grid Plus.

I'm using JSF on the server side and the h:outputText component is
encoding using the latin1 entities.

The AJAX response looks something like

<?xml version="1.0" encoding="UTF-8"?>
<ajax-response>
  <response type="object" id="data_grid_updater">
    <rows update_ui="true">
      <tr>
        <td><div>2c9081cb13987e8401139893e9f50736</div></td>
        <td><div>ABCDEFG</div></td>
        <td><div>First</div></td>
        <td><div>Last</div></td>
        <td><div>Administraci&oacute;n de Cr&eacute;ditos</div></td>
        <td><div>7/5/07 5:50 PM</div></td>
      </tr>
    </rows>
  </response>
</ajax-response>

I was able to fix this in Firefox by adding a DOCTYPE:

  <!DOCTYPE ajax-response PUBLIC
          "-//W3C//DTD XHTML 1.0 Transitional//EN"
          "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

between the "<?xml ..." line and the "<ajax-response>".

I'm not happy with this fix because 1) I'm not sure why it worked, and
2) this does not resolve the problem in IE.

Does anyone have any suggestions for how to make the XML parser in IE
accept these entities?