version of Cache::Memcached that works on 5.6.1
Otherwise I'd guess that your least worse choice to progress is to locally
fork Cache::Memcached and remove the code in it which requires Encode.
Nicholas Clark
' and
then to restore the previous IO layers.
Is there a way to determine the IO layers applying to a filehandle
just from the filehandle itself?
I think you want PerlIO::get_layers($fh)
I'm not sure where it's documented.
Nicholas Clark
. I guess that one
needs to loop over all characters in the string, and verify that if
$char eq lc $char then also $char ne uc $char. (But one could first
short circuit the common pass case with the test above)
Nicholas Clark
::Collate with 5.8.8 (or earlier) and are currently using DUCET 4.1.0
So it wouldn't be a great idea.
Nicholas Clark
that 5.8.9 will ship with Unicode 5.0.0 data
Nicholas Clark
that it's ISO-8859-1.
Definitely buggy. Not possible to change without breaking backward
compatibility.
Nicholas Clark
conversion of real
data, certainly for data outside of ISO-8859-1 and UTF-8, and I've never used
I18N::Langinfo. I hope that someone else on this list can give a decent
answer.
Nicholas Clark
use utf8; Unicode word characters
can also be used in identifiers.
I doubt that this will change in perl 5, because the parser is written in C,
and so it would be very hard work to replace it with something that was fully
Unicode aware.
Nicholas Clark
character?
I don't know.
And if the test is only checking for invariant characters below 127, it
doesn't strike me as a very thorough test.
Nicholas Clark
On Wed, Aug 10, 2005 at 02:11:45PM +0530, Sastry wrote:
On 8/9/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Tue, Aug 09, 2005 at 10:58:48AM +0530, Sastry wrote:
$enc_string = encode(iso-8859-16, $string);
So $enc_string should be a single byte, 97, everywhere.
Can you suggest some
On Tue, Aug 09, 2005 at 10:58:48AM +0530, Sastry wrote:
Hi
I get 73 printed on EBCDIC platform. I think it is supposed to print
129 as it is the numeric equivalent of 'a'.
-Sastry
On 8/8/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On your EBCDIC platform, what does this give
* this change makes things work?
Nicholas Clark
that change, how does your build fail? How do the errors differ?
Nicholas Clark
if ((uv == 0xfe || uv == 0xff)
!(flags UTF8_ALLOW_FE_FF)) {
warning = UTF8_WARN_FE_FF;
goto malformed;
}
#endif
Is that second call to NATIVE_TO_UTF still present in your modified code?
Nicholas Clark
On Fri, Jun 10, 2005 at 12:02:27PM +0100, Nicholas Clark wrote:
It would be better if you sent 1 e-mail to both perl-unicode.perl.org
and perl5-porters@perl.org to ask a given question, rather than two.
It would help if I got the address correct.
(or avoided using the format used in DNS zone
that attempts to solve the other problems will be hindered
by errors introduced by these bugs.
Nicholas Clark
UTF8 rather than the default,
then you get a 2 byte file output.
Nicholas Clark
before doing things with the PV.
Nicholas Clark
authors have also fixed bugs.
Nicholas Clark
that you need to file a report, as we're now aware of it.
Jarkko managed to cut the test case down to something very small, but we
can't manage to make a fix that doesn't break regexps in something else,
seemingly completely unrelated.
Nicholas Clark
On Tue, Jun 29, 2004 at 06:49:16PM +0100, Richard Jolly wrote:
Script
Could you resend the script/data test case as an attachment please?
It's been mangled by the format flowed on your mailer and currently I'm
getting errors which suggest that I can't undo that damage.
Thanks
Nicholas
On Wed, Jun 30, 2004 at 10:15:13PM +0100, Richard Jolly wrote:
On 30 Jun 2004, at 17:52, Nicholas Clark wrote:
On Tue, Jun 29, 2004 at 06:49:16PM +0100, Richard Jolly wrote:
Script
Could you resend the script/data test case as an attachment please?
Attached.
Thanks.
Looks like
a workable solution, volunteer to actually do it and I think
that everyone will be happy.
My only thought is should the API be full SVs, or char pointer plus utf8/not
flag? (possibly as 1 bit in a flags word)
Nicholas Clark
it into the maintenance branch, but I intend to,
so unless it causes really really strange errors (very unlikely) it will
be in 5.8.5. (Which in turn will be in mid July)
Nicholas Clark
as http://search.cpan.org/author/ILYAZ/if-0.0101/
In the core since 5.8.0
Nicholas Clark
these variables on RedHat systemwide, so I don't
know how to change them.
My personal opinion is that it was premature of RedHat to make RedHat 8.0
*default* to using UTF8 locales, given the general state of UTF8 support
in most programs running on Linux. Others may disagree.
Nicholas Clark
is there something that the perl development community needs to do
(or change) that would avoid this in future?
Nicholas Clark
--
Befunge better than perl? http://www.perl.org/advocacy/spoofathon/
On Sun, Nov 03, 2002 at 11:13:25PM +, Nicholas Clark wrote:
Currently the appended patch passes all regression tests on FreeBSD on
bleadperl. However, having experimented I know that the new -O function it
provides is buggy in some way, as running -O on the Chinese encodings gives
suggested that allowing optional arguments would induce
serious slowdown. (by implication even when no optional arguments are used)
Nicholas Clark
PS shameless plug for optimising your perl code talk:
http://www.ccl4.org/~nick/P/Fast_Enough/
5.8.0 support
in 5.8.0 is much better than 5.6.1, and it also fixes many of the bugs
still present in 5.6.1. (Nothing is perfect - a few new bugs have been
reported in 5.8.0, but generally it does seem stable and of good quality)
Nicholas Clark
--
Even better than the real thing:http://nms
::Collate in the box, hit go, top
of the returned list)
CPAN's usually a the best place to start when looking for anything perl.
Nicholas Clark
metachars cause the regexp to think
in ASCII, and unicode scalars are treated as a series of bytes.
5.8.0 fixes this problem - regexps just work there. Modulo unknown bugs)
Nicholas Clark
--
Even better than the real thing:http://nms-cgi.sourceforge.net/
On Tue, Aug 06, 2002 at 10:36:09PM +0900, SADAHIRO Tomoyuki wrote:
On Mon, 5 Aug 2002 22:17:10 +0100
Nicholas Clark [EMAIL PROTECTED] wrote:
I'm trying to backport ExtUtils::Constant from 5.8.0 to work on perl pre
5.8.0. Currently ExtUtils::Constant is using utf8::encode and utf8
of the dark side.
M-x flyspell-mode
Definitely part of the dark side because here it defaults to American.
And then refuses to start because I don't have American dictionaries
installed. ispell has no problem just running and finding the correct
dictionaries.
Nicholas Clark
--
Even better than the real
the different encoding systems are forced to jump through, when one
only knows languages which use the Roman alphabet and therefore has
had no direct experience of anything other than ASCII and ISO 8859-1.
But it's more important to get Encode working well than spend time on this
right now.
Nicholas Clark
On Wed, Feb 06, 2002 at 09:59:44AM +, Nick Ing-Simmons wrote:
Nicholas Clark [EMAIL PROTECTED] writes:
On Tue, Feb 05, 2002 at 04:29:34PM +, Nick Ing-Simmons wrote:
If I throw jis208.enc into the pot, then without -O it is 12s
and with -O approx 4 minutes for a trivial saving
the configure question?
Try harder to compress CJK encodings (this will slow your build considerably)?
[no]
Unless we find a more efficient algorithm to search for common substrings.
Nicholas Clark
--
EMCFT http://www.ccl4.org/~nick/CV.html
best however you config things]. Or am I barking up the wrong tree?
Nicholas Clark
--
EMCFT http://www.ccl4.org/~nick/CV.html
38 matches
Mail list logo
