This content has been marked as final.
Show 5 replies
-
1. Re: Invalid byte 2 of 3-byte UTF-8 sequence
jobb Mar 9, 2009 7:35 AM (in response to jobb)Sorry, but problems with UTF-8 chars concerning also this site. All special chars on this page are transformed to unreadeble labels
What I tried to show was number chars from http://www.w3schools.com/tags/ref_entities.asp (Entity number) æ -
2. Re: Invalid byte 2 of 3-byte UTF-8 sequence
nbelaevski Mar 9, 2009 8:02 AM (in response to jobb)Hello,
Have you tried this:<?xml version="1.0" encoding="UTF-8"?>
? -
3. Re: Invalid byte 2 of 3-byte UTF-8 sequence
jobb Mar 9, 2009 8:03 AM (in response to jobb)Yes, the same problem
-
4. Re: Invalid byte 2 of 3-byte UTF-8 sequence
jobb Mar 9, 2009 10:09 AM (in response to jobb)I have checked more about extended character set. In addition to norwegian and other languages, characters like or even expression like
<h:commandLink rendered="#{orderdetailMBean.orderHasAssets && orderLineWrapper.downloadURL != ''}">
gives a parsing error (the last one : The entity name must immediately follow the '&' in the entity reference).
The question is how to setup/parametrize the parser to avoid this?
One workaround is to use boundle and propeties file with all texts. But what to do with el expressions including && ? -
5. Re: Invalid byte 2 of 3-byte UTF-8 sequence
nbelaevski Mar 9, 2009 12:19 PM (in response to jobb)"jobb@miroko.net" wrote:
I have checked more about extended character set. In addition to norwegian and other languages, characters like  or even expression like<h:commandLink rendered="#{orderdetailMBean.orderHasAssets && orderLineWrapper.downloadURL != ''}">
gives a parsing error (the last one : The entity name must immediately follow the '&' in the entity reference).
The question is how to setup/parametrize the parser to avoid this?
One workaround is to use boundle and propeties file with all texts. But what to do with el expressions including && ?
Facelets view file should be a syntactically correct XML file. Use "AND" or&&