Re: Problem with indent

[Joerg Heinicke]

g[R]eK wrote:
Hi J.Pietschmann,

JP> Try
JP>    <indent>yes</indent>
It isn't working, the output is same :-(
Of course it changes nothing with encoding, you wrote "Problem with indent" 
in the mail subject.

                               <encoding>UTF-8</encoding>
JP> This should be the default.


And in output I have some chars encoded as entities. How Can
JP>  > I force Cocoon to encode my language (polish) chars

correctly?


JP> What is "correctly? If you mean you don't want to have
JP> HTML entities: you can't (unless you are willing to pull
JP> some tricks which take some time to explain)
Look:

<table class="footer">
<tbody>
<tr>
<td>
        Some footer... bla bla
Zaż&oacute;łcić gęsią jaźń</td>
</tr>
</tbody>
</table>
This is what I get from cocoon HTML Serializer, but I want to have this:
<table class="footer">
<tbody>
<tr>
<td>
        Some footer... bla bla
Zażółcić gęsią jaźń</td>
</tr>
</tbody>
</table>
The difference is enity '&oacute;'. Interesting is that the cocoon is encoding some of my 
language letters (like 'ę',
'ż') correctly. That is to say, it is encoded as char not as entity.
I know that I often mix the identifiers/correct names, but I will try to 
explain:
&oacute; is only another representation of ó. &oacute; is the character 
entity, while ó is the character. But they represent the same character and 
a browser correctly parsing the HTML should show both in the same way. But 
there is no problem if Cocoon delivers the HTML in the above way.

Now remains the question, why the browser isn't doing this. Do you have a 
<meta> tag specifying the encoding 'UTF-8' in your HTML code? If yes, is the 
browser not UTF-8 aware? Or does it prefer the encoding specified in the 
response header and this is different or/and wrong?

I think Mozilla is a very good browser to test this. On a page you can have 
a look at the properties of the page via 'view page info' in context menu, 
view/page info in the main menu or ctrl + i via keyboard. There is written 
as which encoding the page was recognized. Furthermore you can force Mozilla 
to show the page in another encoding to see the effects, what happens if 
it's recognized correctly (or not).

Little question... When I start cocoon, I have this text:
'server.properties not found, using command line or default properites'
Is it important?
I don't think, that it is important. server.properties could overwrite the 
mentioned default properties.

Regards,

Joerg

--

System Development
VIRBUS AG
Fon  +49(0)341-979-7419
Fax  +49(0)341-979-7409
[EMAIL PROTECTED]
www.virbus.de
CeBIT 2003 vom 12. bis zum 19. März in Hannover

VIRBUS stellt gemeinsam mit der IBM-Tochter IT-Services and Solutions
GmbH aus.
Lassen Sie sich überraschen von den neuen, umfassenden Möglichkeiten im
Internet-gestützten Zahlungsverkehr.
Besuchen Sie uns: Halle 3, Stand D55.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]