Problem while displaying '<' in report

[Shankar_24684]

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

i have to display this line with yellow background in my report .

 

Can anyone please help out in doing the same?

 

Thanks in advance,

Shankar.S

[svenn]

Look up Unicode. Use the Unicode value for < and >.

[redwine]

Shankar,

 

you can try using the following html entity names for the "less than" and "greater than" symbols:

 

< ... type &lt;

> ... type &gt;

 

for other special symbols see this url:

http://www.w3schools.com/html/html_entities.asp

 

 

let us know how it goes

 

edwin

[thiego]

It doesnt work if you mix "<" or ">" with another html tag (eg <font size =3> </font>)

I had the same error..

In my case, i was trying to use < or > with bold.

"<" and ">" are interpreted as a html tag creating the following error:

"ERROR [sTDERR] [Fatal Error] :3:2: The content of elements must consist of well-formed character data or markup."

[thiego]

and i've tried to use the unicode.. it doenst work too! the same error..

 

Post edited by: thiego, at: 2007/06/05 12:49

Post edited by: thiego, at: 2007/06/05 12:50

[redwine]

thiego,

 

you can't use the GREATER THAN and LESS THAN characters directly in the fields... you have to use the html character entity for those two characters and other characters such as the ampersand. refer to my previous post in this thread. i have placed a link to w3schools in case you want to learn about how to display other special characters.

 

honestly, i am not sure if iReport/JasperReports has a feature that filters special characters and translates them into their printable form.... that would be cool if they had that. anyway, if you need to display text taken from a datasource (text that you don't intend to scan completely for special symbols), the only solution that i know of is to create an application (java or other language) that will scan the text for special characters and convert the special characters into their corresponding character entities.

 

i'm sure someone out there already has a fix for this... or at least has an idea of how to work around this issue.

 

hth

 

 

edwin