UTF-8 encoded octets to ->decode

[nick]

As I 1/2 expected Encode:XS::decode had same problems with input 
that was UTF-8 encoded (e.g. literal string in scope of UTF-8 even 
after passing through =??Q?'s regular expression.

Attached patch seems to fix it.

(Posted via an unusual route though)



patch
Description: Binary data

Call for Papers: IUC23 (23rd Internationalization and Unicode Conference)

[Richard Ishida]

>>  Call for Papers!  <

  Twenty-third Internationalization and Unicode Conference (IUC23)
   Unicode, Internationalization, the Web: The Global Connection
Week of March 24-28, 2003
 Prague, Czech Republic

  Send in your submission now!  <<<

Submissions due: November 15, 2002
   Notification date: November 29, 2002
   Completed papers due: January 6, 2003
  (in electronic form and camera-ready paper form)

  Just 4 weeks to go!  <<<

The Internationalization & Unicode Conference is the premier technical
conference worldwide for both software and Web internationalization. The
conference (renamed from "Unicode Conference" to more accurately reflect
its content) features tutorials, lectures, and panel discussions that
provide coverage of standards, best practices, and recent advances in
the globalization of software and the Internet. Attendees benefit from
the wide range of basic to advanced topics and the opportunities for
dialog and idea exchange with experts in the field. The conference runs
multiple sessions simultaneously to maximize the value provided.

New technologies, innovative Internet applications, and the evolving
Unicode Standard bring new challenges along with their new capabilities.
This technical conference will explore the opportunities created by the
latest advances and how to leverage them for global users, as well as
potential pitfalls to be aware of, and problem areas that need further
research. There will also be demonstrations of best practices for
designing applications that can accommodate any language.

We invite you to submit papers that relate to Unicode or any aspect of
software and Web Internationalization. You can view the programs of
previous conferences at:
http://www.unicode.org/unicode/conference/about-conf.html


CONFERENCE ATTENDEES

Conference attendees are generally involved in either the development
and deployment of Unicode software, or the globalization of software and
the Internet. They include managers, software engineers, systems
analysts, font designers, graphic designers, content developers, web
designers, web administrators, technical writers, and product marketing
personnel.

THEME & TOPICS

International computing is the overall theme of the Conference.
Presentations should be geared towards a technical audience.  Topics of
interest include, but are not limited to, the following (within the
context of Unicode, internationalization or localizability):

- Internationalization issues with new technologies
- XML and Web protocols
- The World Wide Web (WWW)
- Security concerns e.g. Avoiding the spoofing of UTF-8 data
- Impact of new encoding standards
- Implementing Unicode: Practical and political hurdles
- Implementing new features of recent versions of Unicode
- Evaluations (case studies, usability studies)
- Natural language processing
- Algorithms (e.g. normalization, collation, bidirectional)
- Programming languages and libraries (Java, Perl, et al)
- Optimizing performance of systems and applications
- Search engines
- Library and archival concerns
- Portable devices
- Migrating legacy applications
- Cross platform issues
- Printing and imaging
- Operating systems
- Databases
- Large scale networks
- Government applications
- Testing applications
- Business models for software development (e.g. Open source)

We invite you to submit papers which define tomorrow's computing,
demonstrate best practices in  computing today, or articulate problems
that must be solved before further advances can occur.


SESSIONS

The Conference Program will provide a wide range of sessions including:
- Keynote presentations
- Workshops/Tutorials
- Technical presentations
- Panel sessions

All sessions except the Workshops/Tutorials will be of 40 minute
duration.  In some cases, two consecutive 40 minute program slots may be
devoted to a single session.

The Workshops/Tutorials will each last approximately three hours.  They
should be designed to stimulate discussion and participation, using
slides and demonstrations.


PUBLICATIONS

If your paper is accepted, your details will be included in the
Conference brochure and Web pages and the paper itself will appear on a
Conference CD, with an optional printed book of Conference Proceedings.


CONFERENCE LANGUAGE

The Conference language is English.  All submissions, papers and
presentations should be provided in English.


SUBMISSIONS

Submissions MUST contain:

1. An abstract of 150-250 words, consisting of statement of purpose,
paper description, and your conclusions or final summary.  Also, if this
is a paper for an intermediate or advanced audience, please specify what
assumptions you are making about the attendees' prior knowledge.

2. A brief biography.

3. The details listed belo

[Encode] 1.80 released

[Dan Kogai]

Hugo and porters,

  I have released Encode 1.80 despite the fact I just released 1.79 
less than 24 hours ago.

Whole:
	http://www.dan.co.jp/~dankogai/Encode-1.80.tar.gz
	and CPAN

Change is very small; it just includes a patch from NI-XS.

$Revision: 1.80 $ $Date: 2002/10/21 20:39:09 $
! Encode.xs t/mime-header.t
  Even more patches from NI-XS regarding Encode::utf8->decode().
  And one more test to t/mime-header.t to prove it
  Message-Id: <[EMAIL PROTECTED]>

Still I decided to go for 1.80 because I reckon you are yet to commit 
the latest Encode to bleedperl.  If you haven't work on it that's fine; 
just skip 1.7? and go straight to 1.80.  Apologies and thanks.

Dan the Encode Maintainer.

[Encode] 1.79 released

[Dan Kogai]

porters,

I have decided to release Encode 1.79 so soon after 1.78 with two 
reasons.

Whole:
	http://www.dan.co.jp/~dankogai/Encode-1.79.tar.gz
	and CPAN

=head1 reasons

=over

=item 1

The latest patch to Encode.(pm|xs) by Nick In-XS to relocate 
Encode::utf8 from .pm to .xs has introduced a minor bug that was 
revealed in t/mime-header.t.  It was due to the fact that 
Encode::utf8->decode() attempts to decode even when the argument is 
already flagged as utf8 string.  Encode 1.78 fixed the problem by 
mending lib/Encode/MIME/Header.pm but Nick In-XS has sent me a patch to 
Encode.xs.

=item 2

M$ version of the mapping in cp949 (Korean) and cp950 (Trad. Chinese) 
was obsolete, resulting   U+20AC (EURO SIGN) and U+00AE (REGISTERED 
SIGN) missing.  This time Moriyama-san has tested them against 
conversions via Win32 API and verified that they all matches now (at 
leased those marked as round-trippable).

=back

=head2 grumbles

Frankly, I am f.*ing tired of hearing about any M$-related char map 
issues.  This is to close the cp9?? cases altogether.  From now on I 
will happily ignore any claims saying 'cp??? seems to be wrong' unless 
M$ fixes their web pages ( 
http://www.microsoft.com/typography/unicode/cscp.htm -- it's gone!) and 
THE ATTITUDE (no news on the shutdown of the page above was released to 
the community).  I have just had enough, m'kay?

=head1 Changes

$Revision: 1.79 $ $Date: 2002/10/21 06:05:37 $
! Encode.xs
  Further patches from NI-XS.  Encode::utf8->decode() now checks the
  value of utf8 flag of the argument.  As a result, the fix to
  lib/Encode/MIME/Header.pm is no longer neccessary but since it did
  no harm (even speedwise) I'll leave it unreverted.
! ucm/cp949.ucm ucm/cp950.ucm
  U+20AC EURO SIGN
  U+00AE REGISTERED SIGN
  were missing as a result of 1.78. Discovered by Moriyama-san.
  Moriyama-san has also developed a test script that compares
  (en|de)coded results to the corresponding Win32 API result and
  all cp9?? maps are now verified.
  Message-Id: <[EMAIL PROTECTED]>

=head1 AUTHOR

Dan the Encode Maintainer

Text::Iconv compiled on Win32, linked dynamically to libiconv

[Robert Allerstorfer]

Hi,

in order to use Autrijus' Encode::compat on Win32, I would like to
compile Text::Iconv dynamically linked to libiconv.dll (GNU libiconv,
separately compiled). But, I couldn't find instructions on the net yet
on how to do that. Did anybody do this successfully? Any help is
appreciated.

best,
rob.