Hello,
I have still Problems with the special german characters and the
LDAP-Transformer.
When I write
<map:serializer name="html" mime-type="text/html" src
="org.apache.cocoon.serialization.HTMLSerializer">
<doctype-public>-//W3C//DTD HTML 4.01 Transitional//EN</doctype-public>
<encoding>ISO-8859-1</encoding>
<omit-xml-declaration>yes</omit-xml-declaration>
</map:serializer>
nothing happens.
When I make in the xsp-page between <xsp:logic> a ldap-query, the
characters return fine. Why return the LDAP-Transformer false characters?
Thank you in advance
Katrin Seiffert
|---------+---------------------------->
| | Berin Loritsch |
| | <bloritsch@apache|
| | .org> |
| | |
| | 23.04.02 14:43 |
| | Bitte antworten |
| | an cocoon-users |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| An: [EMAIL PROTECTED]
|
| Kopie:
|
| Thema: Re: Antwort: Problem with special german characters and LDAP
-Transformer |
>------------------------------------------------------------------------------------------------------------------------------|
[EMAIL PROTECTED] wrote:
> Hi,
>
>
>>I use the LDAP-Transformer. It's works fine. But I have a Problem with
>>special german characters. I must use the character set "ISO-8859-1".
>>The Problem occurs only on LDAP-Transformer-Datas. On the normal
conversion
>>from xml to html using xslt occurs no Problems with special german
>>characters.
>>What can I do?
>
>
> We had a similar problem with our Oracle database when we used html
forms.
> Everything worked fine, when we typed data in the form and sent it to the
xsp
> page for processing.
> But when we read data from the database and used it to initialize the
form data,
> it got "encrypted".
> Our solution - which, in my opinion, is not really good - is to tell the
html
> serializer to generate output in the "ISO-8859-1" character set instead
of the
> normal "UTF-8" character set. Then all the data, which is serialized to
html
> stays in the "ISO-8859-1" character set, which has been read from the
database.
>
This is an issue with your database vendor not supporting other encoding
standards. Bear in mind that old Netscape 4.x browsers do not handle
UTF-8 encodings well at all. The newer browsers all do support it.
That said, Readers are supposed to make the conversions for you...
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
