New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fallback (replacement char) with encode() vs binmode/open #8950
Comments
From nospam-abuse@bloodgate.comCreated by nospam-abuse@bloodgate.comMoin, consider the three programs below. They take an UTF-8 text containing * it doesn't seem possible to say what replacement char is uses, '?' I believe this is a bug, all three programs should work like encode.pl: # perl encode.pl encode.pl: ##################################################################### binmode.pl: ##################################################################### open.pl: ##################################################################### All the best, Tels Perl Info
|
From @JuerdTels skribis 2007-06-26 22:51 (-0700):
It's possible, but not entirely obvious: juerd@nano:~$ perl -MEncode -le'print encode latin1 => "foo\x{0420}bar\x{e9}", sub { "%" }' | hexdump -C
They seem to be using FB_PERLQQ for CHECK. The documentation says: When the layer is pushed, the current value of This doesn't seem to work. juerd waalboer: perl hacker <juerd@juerd.nl> <http://juerd.nl/sig> |
The RT System itself - Status changed from 'new' to 'open' |
These now print \x{...} for all characters not representable in 8859-1 |
Migrated from rt.perl.org#43390 (status was 'open')
Searchable as RT43390$
The text was updated successfully, but these errors were encountered: