[ https://forge.continuent.org/jira/browse/SEQUOIA-911?page=comments#action_13702 ]
Marc Herbert commented on SEQUOIA-911: -------------------------------------- The best way to fix this seems to use a new InputStreamReader() + encapsulate the JLine object so to NOT even create one at all in non-JLine mode. Check the code for details. > Add console support for exotic locales > -------------------------------------- > > Key: SEQUOIA-911 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-911 > Project: Sequoia > Type: Bug > Components: CLI Console > Versions: Sequoia 3.0 beta2, Sequoia 3.0 beta1, Sequoia 2.10.4, Sequoia > 2.10.3, Sequoia 2.10.2, Sequoia 2.10.1, Sequoia 2.10, Sequoia 2.9 > Reporter: Marc Herbert > Priority: Minor > > > The new Console.readLineBypassJLine() implemented to add unicode support > (SEQUOIA-887) may detect spurious newlines and thus corrupt user entry when > the terminal locale is using some exotic multibyte-encoding. > All unibyte encodings and UTF-8 are SAFE (cause UTF-8 is cunning) > Please note that readLineBypassJLine() is currently used only in > non-interactive ("-f") mode: this locale limitation > applies only in non-interactive mode. > Interactive mode (=JLine) support for multibytes characters is very different > and actually even worst than that, see SEQUOIA-887. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://forge.continuent.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Sequoia mailing list Sequoia@lists.forge.continuent.org https://forge.continuent.org/mailman/listinfo/sequoia
