Hi: Take it easy! This is a standard problem when you start to using Cocoon. :-D
What I am trying to said is that only putting the header is not enough. Just for reference. I use spanish and I had the same problem as you we I started with Cocoon. I dont use Windows anymore. But I can recommend you jEdit. (http://www.jEdit.org) to write XML stuff. In jEdit you have "buffer options" that allow you to define the character encoding for your saved files. That means How the file will be encoded BEFORE is saved into the hard disk. Of course the headers are importants too. Please feel free to ask if you have more questions. ;-) Best Regards, Antonio Gallardo > I am not shure what you mean, but i added to the header of all xsp and > xsl document the same encoding sceme! > > -----Ursprüngliche Nachricht----- > Von: Antonio Gallardo [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 7. März 2003 14:27 > An: [EMAIL PROTECTED] > Betreff: Re: AW: encoding and xsp > > > Hi! > > Please note that you must be sure that you are using the correct > encoding to save your files. > > Antonio Gallardo. > > > >> hi, >> >> thanks for your hints. i tried it, but it still does not work. i was >> not sure, if you mean to specifiy it within the <map:components>, or >> <map:pipelines> i did it in both. i also specified it within in the >> jdbc connection. but no success. >> >> Is it necessary to specify main sitemap, or is it also possible to put >> it into the sub-sitemap? >> >> here is how i added it: >> >> <map:components> >> <map:generators default="file"> >> <encoding>ISO-8859-1</encoding> >> </map:generators> >> </map:components> .... i did the same for the serializer and >> transformer. >> >> and ... >> >> <map:match pattern="**.html"> >> <map:generate type="serverpages" src="reg/docs/{1}.xsp"> >> <encoding>ISO-8859-1</encoding> >> </map:generate> >> <map:transform src="reg/stylesheets/anmeldung.xsl"> >> <encoding>ISO-8859-1</encoding> >> </map:transform> >> <map:serialize> >> <encoding>ISO-8859-1</encoding> >> </map:serialize> >> </map:match> >> >> if i read through the outputtet html, there is still a tag like: >> >> <META http-equiv="Content-Type" content="text/html; charset=UTF-8"> >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: Andres, Judith [mailto:[EMAIL PROTECTED] >> Gesendet: Freitag, 7. März 2003 09:42 >> An: [EMAIL PROTECTED] >> Betreff: AW: encoding and xsp >> >> >> Try specifying an encoding inside the serializer declaration in your >> sitemap: >> >> <map:serializer ...> >> <encoding>ISO-8859-1</encoding> >> </map:serializer> >> >> HTH Judith >> >> >> -----Ursprüngliche Nachricht----- >> Von: boessem [mailto:[EMAIL PROTECTED] >> Gesendet: Freitag, 7. März 2003 09:39 >> An: Cocoon-Users >> Betreff: encoding and xsp >> >> >> hi, >> >> i do not understand why the encoding works different for words i use >> wihtin the xsp document and words i get via the url. >> >> an example: >> >> I have got a form, where students should be able to apply for a >> specific exame. wihtin this form (a xsp document) there are some >> explainations of how to use the form and what to fill in. characters >> within these sentences like ä,ö,ü etc. are getting >> transformed into html perfectly. (so no trouble). >> >> but: >> >> i have got text fields where students are able to fill in their names. >> so if a name uses characters like ä,ö,ü etc. these names are >> transformed inot funny characters like e.g. Bößem into >> Bößem . >> >> i tried to solve this problem, by adding to the header of the xsp and >> xsl document the encoding sceme, like <?xml version="1.0" >> encoding="ISO-8859-1"?>, but still the same problem. >> >> does anyone know how to solve this problem. >> >> thanks and regards > > > > > --------------------------------------------------------------------- To > unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To > unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
