cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Nagels <nick.nag...@med.kuleuven.be>
Subject Re: Forms encoding problem
Date Wed, 08 Feb 2006 11:36:04 GMT
As the first statement

<map:pipelines>
<map:pipeline>
	<map:act type="set-encoding">
		<map:parameter name="form-encoding" value="UTF-8"/>
	</map:act>

This is the action it uses:

	<map:action name="set-encoding" 
src="org.apache.cocoon.acting.SetCharacterEncodingAction"/>

Hope this helps.		

Nick Nagels
IT Specialist @ KULeuven for EuroGenTest
Tel. +0032 16 33 01 43
Herestraat 49 bus 602
B-3000 Leuven
MSN Messenger: nick.nagels@med.kuleuven.ac.be


Derek Hohls wrote:
> Nick
>  
> Thanks - where exactly in the pipeline did you insert this?
>  
> Derek
> 
>>>> nick.nagels@med.kuleuven.be 2006/02/08 11:56:39 AM >>>
> This helped me a lot.
> 
> <map:act type="set-encoding">
> <map:parameter name="form-encoding" value="UTF-8"/>
> </map:act>
> 
> Greets
> 
> Nick Nagels
> IT Specialist @ KULeuven for EuroGenTest
> 
> 
> 
> Derek Hohls wrote:
>> Antonio
>>
>> I guess I did - strange that it happens only on the one
>> server.. maybe UNIX less "forgiving" than Linux.
>>
>> Is there a "default" encoding that Cocoon makes use of?
>> IOW, if I import or reuse stylesheets from Cocoon samples
>> etc. will I expect to see these in UTF-8? Can I simply omit
>> the encoding parameter from *all* my files and set a default
>> for the entire project (in the sitemap, for example). That
>> way I could avoid the "mixing" problem you refer to.
>>
>> Or if this is all spelt out in great detail, somewhere, I'd like
>> to go and read up about it...
>>
>> Thanks
>> Derek
>>
>>
>>>>> antonio.fiol@gmail.com 2006/02/08 09:36:44 AM >>>
>> 2006/2/8, Derek Hohls < dhohls@csir.co.za >:
>>> PS Is there any good reason to prefer ISO-8859-1 over
>>> UTF-8 ... these seem to be used interchangeably, but I
>>> guess they are not?
>>
>> They are different.
>>
>> If your app only uses "latin" characters, you could use one or the
>> other. Otherwise, you should use UTF-8.
>>
>> But beware that mixing is not good, especially if you mix them in the
>> same document. Both encodings encode the same characters in very
>> different ways (except for standard ASCII, which happens to be encoded
>> the same). If you mix, you may run into trouble. You probably already
>> ran into trouble. ;-)
>>
>> --
>> Antonio
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org 
>> For additional commands, e-mail: users-help@cocoon.apache.org 
>>
>>
>>
>>
> 
> Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org 
> For additional commands, e-mail: users-help@cocoon.apache.org 
> 
> 
> 
> 

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message