inserting utf-8 characters into a field in the meta tab causes utf-8
exceptions on trunk, but works fine on 1.2. note, both have page
serialized as utf-8 and form-encoding set to utf-8
i tracked it down to
usecases.js:29 and added some logging code:
PoolThread-3 DEBUG flow - usecases.js::executeUsecase() value is =
[�?ой�?и в п�?блика�?и�? ]
the code is:
var value = flowHelper.getRequest(cocoon).get(name);
earlier, in the request debug, both lenya 1.2 and 1.4 give:
21090 2005-06-05 16:19:30,323 [PoolThread-4] DEBUG
core.cocoon.debug():586 - DEBUGGING INFORMATION:
PARAM: 'properties.save.meta.description' VALUES: '[????? ? ??????????]'
and
PoolThread-4 DEBUG core.cocoon - DEBUGGING INFORMATION:
PARAM: 'description' VALUES: '[ddy ????????]'
so it looks like the FOM doesn't access the cocoon request object in the
same way as xsp, or the FOM doesn't do the encoding tricks as described
in http://wiki.apache.org/cocoon/RequestParameterEncoding
can someone confirm / deny on trunk whether they are seeing the same
problems?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
