Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8352916

`stdout/err.encoding` in non-interactive environment

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: P4 P4
    • tbd
    • None
    • core-libs
    • None
    • generic
    • generic

      Currently `stdout/err.encoding` system properties are derived from host specific way, i.e., the value from nl_langinfo() on Unix and GetConsoleOutputCP() on Windows is used if the Java runtime is connected to a terminal. If the runtime is not connected to a terminal, e.g. redirecting to a file or pipe, it falls back to `native.encoding`. In those cases, using the default charset (`file.encoding`) would be desirable, considering all other IO apis now use the default charset.

            naoto Naoto Sato
            naoto Naoto Sato
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: