On Dec 05, 2004, at 10:56, Dan Kogai wrote:
Thanks, applied in my repository. New tests and documentation fix in
progress. When I am done w/ that, I will release Encode-2.0901 on my
web (not CPAN yet). When cross-checks by porters are done I will
release Encode-2.10.
I have made 2.0901 available as follows:
http://www.dan.co.jp/~dankogai/Encode-2.0901.tar.gz
Here are changes:
! 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: <lrfz2mcngd(_dot_)fsf(_at_)caliper(_dot_)activestate(_dot_)com>
! Encode.pm Encode.xs
post-2.09 comment patches from GAAS applied.
Message-Id: <lroehacz6q(_dot_)fsf(_at_)caliper(_dot_)activestate(_dot_)com>
Message-Id: <lrk6rycymu(_dot_)fsf(_at_)caliper(_dot_)activestate(_dot_)com>
No test suites on utf-8-strict is added yet; as I reported in the
message below it takes patches to perl core to check U+10FFFF and
above.
From: dankogai(_at_)dan(_dot_)co(_dot_)jp
Subject: real UTF-8 vs. utf8n_to_uvuni()
Date: December 05, 2004 11:58:54 JST
To: perl5-porters(_at_)perl(_dot_)org,
gisle(_at_)ActiveState(_dot_)com
Cc: perl-unicode(_at_)perl(_dot_)org
Message-Id:
<9966DB32-4669-11D9-BBC7-000A95DBB50A(_at_)dan(_dot_)co(_dot_)jp>
Dan the Encode Maintainer