perl.unicode...Re: how to request for a new module by Darren Duncan- March 27, 2008 Bayanzul,Go read http:cpan.orgmodules04pause.html and it should tell you or introduce you to everything you need to know. Read the whole thing (it isn&39;t very long).-- Darren Duncanbayanzul lodoysamba wrote:> Dear all,> > I have a question about submitting a new module to CPAN. How can one submit a module to CPAN> What is the procedure for it Is there any qualification for submitting a module> > Currently we are interested in developing a new module for converting Unicode...http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3155.html how to request for a new module by bayanzul lodoysamba- March 27, 2008 Dear all,I have a question about submitting a new module to CPAN. How can one submit a module to CPANWhat is the procedure for it Is there any qualification for submitting a moduleCurrently we are interested in developing a new module for converting Unicode strings in traditional mongolian script into different formats.It will include functions that perform convertions between: Basic Character Set <-> Presentation Set & Ligatures Basic Character Set <->...http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3154.html Re: Pack and Unpack are Broken for > 0x7FFF_FFFF (in 5.10.0) by Chris Hall- March 16, 2008 On Sun, 16 Mar 2008 I wrote>I thought &39;C&39; worked on Octets Which is what 5.8.8 appears to be>doing, but not 5.10.0.I apologise... I should have read the perldelta.I now understand that: in v5.8.8 one would say unpack(&39;C&39;, ...) and get the underlying octets, if the string was a &39;wide&39; (UTF8) string. in v5.10.0 this is no longer possible, C in a &39;wide&39; string returns the wide character value. in v5.10.0, in unpack &39;C&39; and &39;W&39; are the same..http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3153.html Re: Pack and Unpack are Broken for > 0x7FFF_FFFF (in 5.10.0) by Chris Hall- March 16, 2008 On Sun, 16 Mar 2008 I wrote....>Consider:>> use warnings ;>> sub sp > my ($v) = _ ;>> my $p = pack(&39;U&39;, $v) ;> my t = unpack(&39;C&39;, $p) ;>> printf &39;x%04X_%04X: &39;, ($v >> 16), $v & 0xFFFF ;> print map sprintf(&39;x%02X&39;, $_), t ;> print "n" ;> ;... > sp(0x7FFF_FFFF) ;...>v5.8.8 result:>> x7FFF_FFFD: xFDxBFxBFxBFxBFxBD...>v5.10.0 result:>> x7FFF_FFFD: x7FFFFFFDI didn&39;t.http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3152.html Pack and Unpack are Broken for > 0x7FFF_FFFF (in 5.10.0) by Chris Hall- March 16, 2008 More confusion about the valid range of characters in Perl.Both v5.8.8 and v5.10.0 Perl will pack(&39;U&39;, $v) for values of $v whichare > 0x7FFF_FFFF. The result is the (non-standard) Perl utf8 encodingfor such characters.v5.8.8 Perl will unpack a string containing the non-standard encoding.v5.10.0 Perl will not.Consider: use warnings ; sub sp my ($v) = _ ; my $p = pack(&39;U&39;, $v) ; my t = unpack(&39;C&39;, $p) ; printf &39;x%04X_%04X: &39;, ($v >> 16), $v &..http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3151.html Re: UTF-8 (strict) appears borken by Chris Hall- March 15, 2008 I have prepared a bug report, as below.I don&39;t want to waste everybody&39;s time if this is thought to be a feature......so if anyone thinks this is not a bug, please shout (soon).Thanks,Chris-----------------------------------------------------------------Please enter your report hereEncode::encode(&39;UTF-8&39;, $foo) and Encode::decode(&39;UTF-8&39;, $bar) detect theUnicode &39;non-character&39; U+FFFF and treat it as an error.There are 65 other Unicode non-characters: U+FFFE ...http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3150.html Re: utf8::valid and x14_000 - x1F_0000 by Chris Hall- March 13, 2008 On Wed, 12 Mar 2008 Juerd Waalboer wrote>Chris Hall skribis 2008-03-12 20:49 (+0000):>> a. are you saying that characters in Perl are Unicode >Yes. They are called Unicode, at least. This has my preference for>explanation and documentation.>> b. or are you agreeing that characters in Perl take values>> 0..0x7FFF_FFFF (or beyond), which are generally interpreted as>> UCS, where required and possible >This too. This is the more technically...http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3149.html UTF-8 (strict) appears borken by Chris Hall- March 12, 2008 1. &39;Ill-formed&39; UTF-8=====================The Unicode Standard specifies that any UTF-8 sequence that does notcorrespond to this table is &39;ill-formed&39;: Code Points 1st Byte 2nd Byte 3rd Byte 4th Byte -------------------+----------+----------+----------+----------+ U+0000..U+007F 00..7F -- -- -- U+0080..U+07FF C2..DF 80..BF -- -- U+0800..U+0FFF E0 A0..BF 80..BF -- U+1000..U+CFFF .http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3148.html Re: utf8::valid and x14_000 - x1F_0000 by Juerd Waalboer- March 12, 2008 Chris Hall skribis 2008-03-12 20:49 (+0000):> a. are you saying that characters in Perl are Unicode Yes. They are called Unicode, at least. This has my preference forexplanation and documentation.> b. or are you agreeing that characters in Perl take values> 0..0x7FFF_FFFF (or beyond), which are generally interpreted as> UCS, where required and possible This too. This is the more technically accurate explanation, and has mypreference for implementation.> If (a) then..http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3147.html Re: utf8::valid and x14_000 - x1F_0000 by Chris Hall- March 12, 2008 On Wed, 12 Mar 2008 Juerd Waalboer wrote>Chris Hall skribis 2008-03-12 13:20 (+0000):....>> String literals are represented by UCS code points. Which>> reinforces the feeling that characters in Perl are Unicode.>Yes!OK. For the avoidance of doubt: a. are you saying that characters in Perl are Unicode b. or are you agreeing that characters in Perl take values 0..0x7FFF_FFFF (or beyond), which are generally interpreted as UCS, where required and...http://www.nntp.perl.org/group/perl.unicode/2008/03/msg3146.html |