What i say ( and sorry for not explained it very well ).. Is that , when i see xml files ( xreg, jetspeed content and so on ) in JetSpeed prior to first run, they have ISO-8859-1 encoding.., and after a first run, they all are changed to UTF-8..,
I wonder if Castor ( that if i remember well is the XML persistence layer ) is the piece that changes the encoding.... Saludos , Ignacio J. Ortega > -----Mensaje original----- > De: Santiago Gala [mailto:[EMAIL PROTECTED]] > Enviado el: lunes 8 de octubre de 2001 17:27 > Para: [EMAIL PROTECTED] > Asunto: Re: XML changing encodings > > > Ignacio J. Ortega wrote: > > >Hola a todos: > > > >I've noted that every xml file in jetspeed, as is it in CVS has > >ISO-8859-2 encoding, and after first run, they are changed > to UTF-8, is > >not a big problem, and everything continues to run smoothly > ( with some > >glitches i will try to patch) .. > > > Isn't it ISO-8859-1? I imagined it was due to the fact that some XML > files include the "�" in Raph�el. > > It is important to have the right encoding if we have non-US-ASCII > characters in XML files. UTF-8 seems to be a very reasonable encoding, > as it is valid for all Unicode characters, including European, Arabic, > Hebrew, Asian, etc. > > The problem is that it brings its own issues, specially since file > system encoding defaults to different values depending on > country/locale > of the server installation. > > > > > > >Can this lead to future problems?, can be done in a more consistent > >way?, that is, all xml in UTF-8 in CVS or correct the encoding in > >Castor.. > > > Which castor generated XML files are there in CVS? do you > mean in the dist? > > > > >i'm a newbie and i really dont know how to do it nor if > Castor is really > >the sin here..if somebody can point me in the right direction i will > >contribute some patch for this.. > > > WRT the disk cache, everything in there is stored in UTF-8 > encoding, to > avoid having to deal with the mixture between HTTP headers > and <?xml ... > declarations to parse the encoding. Also, UTF-8 is the default XML > encoding, but we are free to use other encodings if it is > done consistently. > > > > > > > > >Saludos , > >Ignacio J. Ortega > > > > >--------------------------------------------------------------------- > >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]
