summaryrefslogtreecommitdiff
path: root/lib/utf8_heavy.pl
Commit message (Expand)AuthorAgeFilesLines
* Unicode categories continue:Jarkko Hietaniemi2001-10-191-6/+13
* Document the problem with the swash_fetch() API that affectsJarkko Hietaniemi2001-10-161-0/+1
* Rewrite mktables from scratch.Jarkko Hietaniemi2001-10-131-29/+64
* Enable more debugging.Jarkko Hietaniemi2001-10-091-5/+5
* Unicode properties saga continues.Jarkko Hietaniemi2001-10-041-1/+1
* Yet more Unicode properties.Jarkko Hietaniemi2001-10-041-3/+4
* Unicode properties: fix L& (the #12319 didn't allow L&,Jarkko Hietaniemi2001-10-031-2/+2
* Unicode properties: support \p{(?:Is)?L&} as an alias for \pL.Jarkko Hietaniemi2001-10-031-7/+8
* Further tweaks to the Unicode properties.Jarkko Hietaniemi2001-10-011-0/+1
* Cleanup utf8_heavy; allow dropping the In prefix fromJarkko Hietaniemi2001-09-301-41/+43
* #12272 wasn't right, it introduced an extra ().Jarkko Hietaniemi2001-09-301-1/+1
* Nasty recursion trap if one would match Unicode.Jarkko Hietaniemi2001-09-291-1/+1
* More leniency to the \p and \P: now can have whitespaceJarkko Hietaniemi2001-09-291-1/+1
* Allow for more flexibility in the \p{In...} names, nowJarkko Hietaniemi2001-09-291-4/+13
* Rename lib/unicode files to lib/unicore to avoidJarkko Hietaniemi2001-08-091-1/+1
* More \p{In...} testing, combined with \N{...}.Jarkko Hietaniemi2001-06-081-2/+3
* Salvage bits and pieces from the experimental 'utf8 everywhere'Jarkko Hietaniemi2001-05-311-1/+3
* Re: [ID 20010528.004] dual bug under utf8: $@ has UTF8 flag and \s+ does not ...Hugo van der Sanden2001-05-301-2/+0
* Additional safeguard against $@ getting trampled; idea from Hugo.Jarkko Hietaniemi2001-05-291-5/+10
* At least a partial fix for 20010528.004.Jarkko Hietaniemi2001-05-291-1/+1
* Explain the \p{} and \P{} error message better andJarkko Hietaniemi2001-04-281-1/+1
* Add a level of indirection to the implementation of \p{InFoo}Jarkko Hietaniemi2001-04-281-1/+8
* use warnings rather than fiddling with $^W (from Paul Marquess)Gurusamy Sarathy2000-02-021-1/+1
* tr///d does not seem to workLarry Wall1998-10-231-2/+1
* fix intolerance of SWASHes for blank linesGisle Aas1998-08-081-33/+31
* kill bogus warning from -we 'use utf8; $_="\x{FF}"'Gisle Aas1998-08-081-3/+3
* Here are the long-expected Unicode/UTF-8 modifications.Larry Wall1998-07-241-0/+224