[
https://issues.apache.org/jira/browse/CASSANDRA-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107797#comment-15107797
]
Stefania commented on CASSANDRA-11030:
--------------------------------------
Looking at the 2.2. patch:
* At [line
737|https://github.com/apache/cassandra/compare/cassandra-2.2...pauloricardomg:2.2-11030#diff-1cce67f7d76864f07aaf4d986d6fc051R737]
why use {{sys.stdout.encoding}} rather than {{self.encoding}} or {{encoding}}?
* At [line
767|https://github.com/apache/cassandra/compare/cassandra-2.2...pauloricardomg:2.2-11030#diff-1cce67f7d76864f07aaf4d986d6fc051R767]
is the list of encodings complete, can they ever be specified as upper case?
* Can you rebase on trunk to make sure the [pep8 compliance
failure|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-11030-dtest/lastCompletedBuild/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_pep8_compliance/]
is not related?
Else it LGTM.
I also only have Windows 7; [~JoshuaMcKenzie] are you running on Windows 10 by
any chance?
> utf-8 characters incorrectly displayed/inserted on cqlsh on Windows
> -------------------------------------------------------------------
>
> Key: CASSANDRA-11030
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11030
> Project: Cassandra
> Issue Type: Bug
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Minor
> Labels: cqlsh, windows
>
> {noformat}
> C:\Users\Paulo\Repositories\cassandra [2.2-10948 +6 ~1 -0 !]> .\bin\cqlsh.bat
> --encoding utf-8
> Connected to test at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.4-SNAPSHOT | CQL spec 3.3.1 | Native protocol v4]
> Use HELP for help.
> cqlsh> INSERT INTO bla.test (bla ) VALUES ('não') ;
> cqlsh> select * from bla.test;
> bla
> -----
> n?o
> (1 rows)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
