[ https://issues.apache.org/jira/browse/KARAF-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325288#comment-17325288 ]
Vassil Zorev edited comment on KARAF-6849 at 4/19/21, 7:59 PM: --------------------------------------------------------------- Hi JB. Had a look a bit at the ShellTable to try to come up with a fix, but there are too many variables for me :( In general this seems to depend on the encoding of the standard out and the forceAscii flag. That's as far as i got.. My best guess would be to use DEFAULT_SEPARATOR_NO_FORMAT also in case the standard out does not support unicode (in windows in my tests), not sure if that was the intention there. Also please let me know if such discussions should happen in another place.. Regards was (Author: vassilz): Hi JB. Had a look a bit at the ShellTable to try to come up with a fix, but there are too many variables for me :( In general this seems to depend on the encoding of the standard out and the forceAscii flag. That's as far as i got.. My best guess would be to use DEFAULT_SEPARATOR_NO_FORMAT also in case the standard out does not support unicode (in windows in my tests), not sure if that was the intention there. > ShellTable no format rendering is not the same on Windows and Unix > ------------------------------------------------------------------ > > Key: KARAF-6849 > URL: https://issues.apache.org/jira/browse/KARAF-6849 > Project: Karaf > Issue Type: Bug > Components: karaf > Reporter: Jean-Baptiste Onofré > Priority: Major > > The shell table output with no format enabled is not exactly the same on Unix > and Windows. > On Windows, we have: > {code:java} > karaf@root()> feature:version-list --no-format foo > 1.0.0 | | mvn:foo/features/1.0.0/xml{code} > On Unix, we have: > {code:java} > karaf@root()> feature:version-list --no-format foo > 1.0.0 mvn:foo/features/1.0.0/xml {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)