Hi, A couple years ago when we here last investigated this utf-8 related problems, it seemed that a solution was found, which _should_ work with different perls.
Today we should test this solutinon anew with 5.10 and maybe 5.14, after which it could be backported from our local branch to the current svn branch. Martin! Is it ok to take the latest svn snapshot as a base for these experiments and possible commits? All the best, Sergei On 08.02.2012 16:46, Martin Bartosch wrote: > Interesting problem, and I am not sure why this happens. Originally we > designed OpenXPKI to be fully UTF8-compliant. I also know that it was used by > our Russian friends to some success, and they also kept a keen eye on keeping > the code UTF8-aware. However, I remember Sergei writing to the list that some > problems occurred with later commits regarding UTF8 support. > It also seems to be an annoying truth that the semantics of handling UTF8 in > Perl has changed significantly, possibly breaking things in OpenXPKI. Sergei > once mentioned that the changes were so deep that fixing the behaviour was > not really possible without breaking backwards compatibility with pre 5.10 > releases. > > The problem you are seeing with the serialization is very likely the result > of the difference between bytes and characters when encoded in UTF8. I know > that this used to work before. > It might also point into the direction of a bug in Perl (5.10?) itself: ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
