Item438: replace horrid UTF8 regex's and replace with Encode
Current State: Closed
Released In: 2.0.0
Target Release: major
Applies To: Engine
I'm just wondering (and apparently I'm not the only one), why we're using a regexp where we could directly use Encode.
I know Encode is another module to require, thus another piece of code that gets loaded, but anyway some modules already require it (such as Wysiwyg).
To my humble opinion, if we want to go UTF-8, we will have to use some proper tool to do it, and thus Encode seems the appropriate choice.
Re-inventing the wheel using regexp can work, but...
Also, Encode uses XS, thus is much quicker than a regexp to achieve the same.
: Adding Encode as a required CPAN module
Encode was first released with perl 5.007003 (patchlevel perl/15039, released on 2002-03-05)
But according to people using it, it makes no sense doing UTF-8 with anything older than perl 5.8.3.
switching to Encode is a very sane sounding thing
- 12 Dec 2008
Just for the record, I've contacted RichardDonkin
for inputs on this.
My plan is to re-write most encodings (Check Item 5437
), using Encode, for all encoding issues.
But first I need input from the big players
- 12 Dec 2008
Got input from SvenDowideit
, thus I can start working on it.
Planning this for 1.1 anyway, so first bug fixes for 1.0
- 15 Dec 2008
No commits against 1.1.0 - bumping this up to a major release.
- 13 Mar 2011
Fixed in unicode core.
- 19 May 2015