What if I don't want it to use that Encode interface? I just want it to
be a module on its own.
Any good reason for doing so? This goes against two expectations set up by
CPAN precedent:
• All modules that deal with encoding/decoding are compatible with Encode.
• All modules in the Encode
On Mon, Nov 8, 2010 at 10:56 PM, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 da...@cpan.org wrote:
What if I don't want it to use that Encode interface? I just want it to
be a module on its own.
Any good reason for doing so? This goes against two expectations set up by
CPAN precedent:
• All modules that deal with
On Sat, Nov 6, 2010 at 5:00 AM, Shlomi Fish shlo...@iglu.org.il wrote:
Hi Tzadik,
Well, I suggest it would be Encode-Hebrew-$Something :
http://search.cpan.org/dist/Encode-Arabic/
I don't see why it should be incorporated into an existing module, because
it's not of general interest.
I did some painstaking reverse engineering in order to convert files that
use an old DOS Hebrew encoding (including vowels and points... this is
beyond ISO-8859-8 and Windows-1255 which are unpointed consonants only, with
no vowels) into Unicode. I was never able to find any information online
