First thoughts, see Encode::Encoding, Creating (and using) a custom encoding., Re^2: Creating (and using) a custom encoding. (fudge :encoding(rot13))
Seconds thoughts, sub In[A-Z]\w+ · CPAN->grep
Encode-JP-Emoji-0.60/lib/Encode/JP/Emoji/Mapping.pm
Encode-InCharset-0.03/InCharset/8859_1.pm
Encode-JP-Mobile-0.30/lib/Encode/JP/Mobile.pm
Lingua-JA-Moji-0.36/lib/Lingua/JA/Moji.pm
Sub::CharacterProperties - Support for user-defined character properties
Encode::InCharset - defines \p{InCharset}
pod thoughts, =head1 NAME Thai - useful ch section should match package Regexp::Thai that is should be Module::Name - module description
name thoughts, say no to "Regexp::Thai", say no to Regexp, stick to Encode or Lingua ... consider vanity naming ... Encode::InCharset::Polygot::Thai, Encode::Th::PolygotProperties... whatever makes the most sense with how your contribution improves the situation regarding Thai (is it generically useful or just for your program?)
Maybe ask on http://prepan.org/
In reply to Re: Namespace/advice for new CPAN modules for Thai & Lao
by Anonymous Monk
in thread Namespace/advice for new CPAN modules for Thai & Lao
by Polyglot
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |