There isn't anything to test this with (I did say 'very rough'). Please
read
Encode.pm. Mainly I'm interested hearing comments whether this is a good
interface, something that could be used to replace Unicode::Map8 (lots of
table-driven conversions, for 8-bit legacy character sets), and when we
feel up
to it, Unicode::Map (lot of algorithmic conversions, for Eastern Asian
encodings). AFAIU, the current user interface of ::Map8 isn't what we
want?
Two comments:
1. Is there any chance of a null mapping to convert a string containing
UTF8 but not marked to one so marked, and vice versa?
2. Work is under way to revise UTR#22 which is an XML language for
describing encoding conversions. The changes will allow for context based
mappings. The revisions are scheduled to go before the November UTC
meeting. So, while what is there isn't the whole story, there should be
something pretty soon (He says in anticipation).
I realise this has nothing to do with the interface, but it may be of
interest to those working on the mapping code.
Martin Hosken
