Nicholas and Porters
Since 5.8.7 became RC1, I have released Encode 2.10, hoping it will be in 5.8.7. It has long been bleed and I got not bug report related to new features.
=head1 Availability
http://www.dan.co.jp/~dankogai/cpan/Encode-2.10.tar.gz and CPAN
=head1 Synopsis
The major change is the introduction of utf-8-strict, which implements UTF-8 as defined by unicode.org (whereas "utf8" in perl is much more liberal).
=head1 Changes
$Revision: 2.10 $ $Date: 2005/05/16 18:46:36 $ ! Encode.pm fixed decode_utf8() accordingly to RT#8872 http://rt.cpan.org/NoAuth/Bug.html?id=8872 ! Encode.xs AUTHORS s/SvIVX/SvIV_set/ by Steve Peters. Message-Id: <[EMAIL PROTECTED]> ! AUTHORS GAAS was missing! ! Encode.pm New Pod section: "UTF-8 vs utf8"; explains utf-8-strict + t/utf8strict.t Tests utf-8-strict, accordingly to UTF-8 decoder capability and stress test" by Markus Kuhn http://smontagu.damowmow.com/utf8test.html Note that malformed and overlong sequences are not test here because perl already does that for you, utf-8-strict or not. ! Encode.pm Encode/encode.h t/fallback.t Addressed "encode(..., Encode::LEAVE_SRC) does not work". Now FB_(PERLQQ|HTMLCREF|XMLCREF) implies LEAVE_SRC so you can (en|de)code constant strings with these fallbacks. http://rt.cpan.org/NoAuth/Bug.html?id=8736 ! Encode.pm Encode.xs lib/Encode/Alias.pm t/Aliases.t Make Encode.pm support the real UTF-8, by GAAS Message-Id: <[EMAIL PROTECTED]> Message-Id: <[EMAIL PROTECTED]> ! Encode.pm Encode.xs post-2.09 comment patches from GAAS applied. Message-Id: <[EMAIL PROTECTED]> Message-Id: <[EMAIL PROTECTED]>
=AUTHOR
Dan the Maintainer Thereof
