ansaurus

Question

Answer 1

A:

Don't use the <?xml ... ?> construct (I can't remember its proper name). Use a DOCTYPE:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=ISO-8859-1"/>
    ...
</head>
...
</html>

Matt Ball 2009-11-18 19:03:39

Processing Instruction?

Vincent Ramdhanie 2009-11-18 19:04:32

That's the one.

Matt Ball 2009-11-18 19:13:39

I have removed <?xml ...?> from the jsp page, included the DOCTYPE. Page renders but still → shows up as a question mark. Did not solve the problem.

m_a_khan 2009-11-18 19:36:24

Try using HTML rather than XHTML if you want to use the `→` entity. Also try using `→` instead of `→`.

Matt Ball 2009-11-18 20:00:10

It's an ‘XML Declaration’, which technically isn't a Processing Instruction even though it looks like one. You probably don't need an XML Declaration (because XML is UTF-8 by default; HTML still needs the meta) and shouldn't use it in HTML-compatible-XHTML as IE will go into quirks mode.

bobince 2009-11-18 20:12:48

Answer 2

+1 A:

The page stops rendering and throws XML parsing error such as "semi colon expected somewhere in my javascript" or "processing instruction not found" etc etc.

That will happen if you declare XHTML as XML instead of "HTML with XML syntax". Indeed get rid of that XML declaration. If you can, I'd go a step further and just use HTML as real HTML, i.e. use <!doctype html> or any other HTML strict doctype. Also see http://hsivonen.iki.fi/doctype/.

<% request.setCharacterEncoding("UTF-8"); %>

First detail is that the request.setCharacterEncoding("UTF-8") is way superfluous. At this stage it's already too late to set that. Second detail is that you're using scriptlets for that. I recommend not to do so. Use taglibs/EL where appropriate. If that's not possible, then the code logic actually belongs in a Java class, either directly or indirectly in a Servlet or Filter class.

Removing "charset=utf-8" from response.setContentType makes the page render. The only problem is that → shows up as a questin mark "?"

The response.setContentType(..) is superfluous if you already set it as a <meta> tag in the HTML <head> which is imho much cleaner.

Finally you also need to set the response character encoding (that's different from setting the content type!) as follows:

<%@ page pageEncoding="UTF-8" %>

This by the way also implicitly creates a <meta> tag for the content-type. More background information and hints can be found here.

Hope this helps.

BalusC 2009-11-18 19:15:04

Removed request.setCharacterEndocding, included <meta .... > under <head>, page renders but → still shows up as question mark.

m_a_khan 2009-11-18 19:37:30

I've edited my answer how to set response encoding properly.

BalusC 2009-11-18 20:31:55

porneL 2009-11-18 21:05:16

Answer 3

A:

You probably have code like this:

<script type="text/javascript"> if (a && b) </script>

which is forbidden in XHTML mode, but required in text/html mode. You'll find explanation of this problem in Sending XHTML as text/html Considered Harmful.

And code like:

<a href="foo?bar&baz">

is not allowed in any version of HTML or XHTML. It must always be written as:

<a href="foo?bar&amp;baz">

Apparently you're not generating page using XML serializer (it wouldn't let you create invalid entities or improperly encoded characters), therefore I suggest that you use HTML 4 Strict or HTML5-as- text/html instead, which are more appropriate for hand-coded markup.

porneL 2009-11-18 21:17:06

ansaurus

tags:

views:

answers:

Displaying xhtml content in a jsp page

related questions