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
Should work with utf-8 characters #14031
Comments
From krajserg@gmail.comHello, I'm very happy to see this prompt handles arrows and other traversing the input string. However, often we need to enter Unicode characters (encoded as utf-8 of course). Currently you just get a ? for each character that makes up the character in utf-8. |
From @khwilliamsonOn Sun Aug 17 11:34:26 2014, krajserg@gmail.com wrote:
You haven't included enough information for anyone to understand what the problem is? What prompt are you referring to? You don't mention what program you are running. If it is perl, we need the output of 'perl -v' to better understand the situation. Please give a step-by-step procedure of how to reproduce the problem -- |
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Thu Aug 21 14:00:54 2014, khw wrote:
We haven't heard back from the original poster in a month. I recommend that we close this ticket in 7 days unless we get further input. Thank you very much. -- |
From krajserg@gmail.comOn Thu Aug 21 14:00:54 2014, khw wrote:
➜ ~ perl -v This is perl 5, version 14, subversion 2 (v5.14.2) built for i486-linux-gnu-thread-multi-64int Copyright 1987-2011, Larry Wall Perl may be copied only under the terms of either the Artistic License or the Complete documentation for Perl, including FAQ lists, should be found on ➜ ~ locale [CODE] Enter utf8 symbol: жузель in fact, it turns out: Enter utf8 symbol: ?????? In debian after installing the package libterm-readline-gnu-perl problem is gone |
From @cpansproutOn Thu Sep 18 09:21:26 2014, krajserg@gmail.com wrote:
It would be useful to know which ReadLine backend it was using. If you could uninstall the package temporarily and add: warn "ReadLine library is ", $term->ReadLine; to your code, the output would be helpful in figuring out why the question marks were showing up. (I cannot reproduce the problem on Mac OS X with the default Stub implementation.) -- Father Chrysostomos |
From @khwilliamsonOn Mon Oct 27 16:04:12 2014, sprout wrote:
Again, it has been a very long time without a response from the OP, who said the problem goes away after installing libterm-readline-gnu-perl I'm taking this ticket, and if in a month nothing further has been heard, I'll close it. |
From @khwilliamsonClosing this ticket as per the previous message, after a month with no further communication |
@khwilliamson - Status changed from 'open' to 'rejected' |
From @SmylersFather Chrysostomos via RT writes:
I'm not the original poster, but I can reproduce the problem on Ubuntu Does it still make sense for Term::ReadLine (which is upstream blead) Term::ReadLine::Perl has 32 open bugs (not including this one), and its Term::ReadLine (which is upstream blead) currently looks for back ends If ::Perl were removed from that list, what would break? Whom would it Smylers * For what it's worth, aptitude why libterm-readline-perl-perl reveals Anybody wanting to play along, here's the code as a one-liner: $ PERL_RL=Perl perl -MTerm::ReadLine -wE 'Term::ReadLine->new($0)->readline(q[Enter UTF-8 symbol: ])' Typing a non-Ascii character displays a � instead. However, typing -- |
From @andk
> Term::ReadLine (which is upstream blead) currently looks for back ends > If ::Perl were removed from that list, what would break? Whom would it ::Perl adds at least cursor movement. In the example you posted I can -- |
Migrated from rt.perl.org#122551 (status was 'rejected')
Searchable as RT122551$
The text was updated successfully, but these errors were encountered: