----- Original Message ----- From: "Thorsten Scherler" <[EMAIL PROTECTED]> To: <dev@forrest.apache.org> Sent: Sunday, January 22, 2006 8:35 PM Subject: Re: character entities
| El sáb, 21-01-2006 a las 22:41 +0800, Gav.... escribió: | > I wrote earlier :- | > | > | P.S- | > | | > | Creating an empty hook has the side effect of a self closing div - | > obviously | > | inlvalid and messes | > | up the rest of the page. | > | | > | e.g. | > | | > | <forrest:hook name="headlines"></forrest:hook> | > | creates | > | <div id="headlines /> | > | instead of | > | <div id="headlines"></div> | > | | > | > This made me have a look around, and as a side-effect found an old | > thread regarding this back in July 2005, just before my time I think. | > | > The discussion also brought up   and its possible side effects | > of creating  . | | Yeah, I am running into the same problem ATM. You can see it online at | http://lenya.zones.apache.org/ "Today:Â..." (I am looking right now to | fix that, so the site may be fixed if you visit it) | | On my local machine that does not happen. I have run into a similar | problem with cocoon on a job I did a while ago. The problem was lying in | the server configuration, now I just looked on our zones server: | Sun Microsystems Inc. SunOS 5.10 Generic January 2005 | -bash-3.00$ locale | LANG= | LC_CTYPE="C" | LC_NUMERIC="C" | LC_TIME="C" | LC_COLLATE="C" | LC_MONETARY="C" | LC_MESSAGES="C" | LC_ALL= | | The locale is not UTF-8! | | Doing "locale" on my machine gives: | LANG=es_ES.UTF-8 | LC_CTYPE="es_ES.UTF-8" | LC_NUMERIC="es_ES.UTF-8" | LC_TIME="es_ES.UTF-8" | LC_COLLATE="es_ES.UTF-8" | LC_MONETARY="es_ES.UTF-8" | LC_MESSAGES="es_ES.UTF-8" | LC_PAPER="es_ES.UTF-8" | LC_NAME="es_ES.UTF-8" | LC_ADDRESS="es_ES.UTF-8" | LC_TELEPHONE="es_ES.UTF-8" | LC_MEASUREMENT="es_ES.UTF-8" | LC_IDENTIFICATION="es_ES.UTF-8" | LC_ALL= | | That is UTF-8! | | The solution back on the job was setting the language to de_DE.UTF-8 | before starting the tomcat server. | | > | > I am seeing  a lot lately and so think the problem is still not solved. | | Yeah, we need to find the root cause of this problem. I guess it is | lying in the "locale". | | > For instance it is the result of siteinfo-last-published.ft. | > | > Last Published: 01/21/2006 17:53:37 | > | > This line is created from the contract here :- | > | > <xsl:template name="siteinfo-last-published-body"> | > <script type="text/javascript">document.write("<i18n:text >Last | > Published:</i18n:text> " + document.lastModified);</script> | > </xsl:template> | > | > I have a theory. | > | > in the code the   is right next to a " (quote). The entity number for " | > (quote) is " | > | > I had a crazy thought that maybe they were adding together somehow. | > (160+34=194) | > | >   + " =  | > | > Guess what  is equal to , yup :- | > | >  | | Jeje, nice theory, but I have an example where you do not combine   | with " and still the described behavior can be seen. | | <forrest:hook class="breadtrail"> | <forrest:contract name="genericMarkup"> | <forrest:properties contract="genericMarkup"> | <forrest:property name="genericMarkup"> | <strong> </strong> | </forrest:property> | </forrest:properties> | </forrest:contract> | </forrest:hook> Yes, it was a theory, it was late also. What does a strong space look like :) | | | > | > Anyway, in the example contract code above, removing   and putting a | > real space in there cures it and the space | > is preserved no problem as it is enclosed between the quotes. | > | > I copied the contract to my /pili/html/ directory and it now renders | > correctly. | > | > Have I missed something here or was it that simple ? | > | | Actually regarding http://www.html-world.de/program/html_sz.php | Unicode: | XML:   | Result: space | | We are using the right code for spaces. I guess you need to set the | locale to UTF-8 on the server (before starting httpd), since forrest is | rendering it on lenya.zones just fine but the httpd is delivering the | content with "Â". I am not disputing that   is a space, my argument and what my solution above was that you need not employ   all the time - especially when text is surrounded by quotes. The example text is :- ("<i18n:text >Last Published:</i18n:text> " + document.lastModified); The   is there to put a space between the : and the date produced by document.lastModified. I do not see a reason for using   in this case the same as there is no   between the words 'Last' and 'Published' What works for me is :- ("<i18n:text >Last Published:</i18n:text> " + document.lastModified); That 'space' is legal and universal, it is enclosed in quotes and so will get converted correctly no matter how the locale is set on the server. Also for some, there will definatly be problems in getting their web server locale changed. I can change my locale on my server no problem, however apache.minitutorials.com and some of my other sites are remotely hosted by different ISPs, I doubt they will change on my say so. I guess this to be true of many Forrest users. Gav... -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.14.22/239 - Release Date: 24/01/2006
