Add LICENSE
Upstream changes:
2014-08-15 Sean M. Burke sburke@cpan.org
* RELEASE 1.22. (The dev release works, so this is a version bump.)
* See notes for 2014-07-25, because this is the first public release
with significant changes since 2001!
2014-07-25 Sean M. Burke sburke@cpan.org
* !DEVELOPER RELEASE!
* !Release 1.20_01!
* Many bugfixes. Thanks especially to Tomaolc!
* Yet more *.t files added for improved sanity checking.
* Shuffling around the internals of Unidecode.pm
* Putting in some vacuous 0x__.pm files where
previously there would just be a load failure
Upstream changes:
2014-06-30 Sean M. Burke sburke@cpan.org
* Release 1.01 -- first official Unidecode release since 2001!!!
* There are no real changes since the 2014-06-23 developer
release. I'm just making this all official now.
2014-06-23 Sean M. Burke sburke@cpan.org
* !DEVELOPER RELEASE!
* Release 1.00_03
* Now asserting that we need at least Perl 5.8.0
An automated test system that tried running the t/*.t
under a 5.6.2 spewed all kinds of crazy error messages.
Hence the bump-up.
So, I added assertions for the version.
* I added some tests for more basic sanity assertions.
2014-06-17 Sean M. Burke sburke@cpan.org
v1.00_02 - Not released. Just internal rearranging.
2014-06-13 Sean M. Burke sburke@cpan.org
* !DEVELOPER RELEASE!
* Release 1.00(_01!)- so many years later, finally we bump up to 1.*!
* My documentation is now BRILLIANT.
* Minor bugfixes.
* Some code comments for clarity.
* A modern test suite.
* A proper release will follow in a few days.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
It often happens that you have non-Roman text data in Unicode, but you can't
display it -- usually because you're trying to show it to a user via an
application that doesn't support Unicode, or because the fonts you need aren't
accessible. You could represent the Unicode characters as "???????" or
"\15BA\15A0\1610...", but that's nearly useless to the user who actually wants
to read what the text says.
What Text::Unidecode provides is a function, unidecode(...) that takes Unicode
data and tries to represent it in US-ASCII characters (i.e., the universally
displayable characters between 0x00 and 0x7F). The representation is almost
always an attempt at transliteration -- i.e., conveying, in Roman letters, the
pronunciation expressed by the text in some other writing system.
