A new custom port sounds like the right idea. The `reencode-input-port`
and ``reencode-output-port` implementations in
"collects/racket/port.rkt" are tied to byte converters, but they should
be the right idea and could be generalized to other conversion
functions. You might have to copy them for no
The more I read in section 4.5.4 the more it dawns on me that what I'm
after may not be possible without (a) a custom patched version of Racket
and/or (b) a custom patched version of libiconv. An alternative -- I think
-- would be a custom input port, but even that might require (a) and/or (b)
2 matches
Mail list logo