Re: Insufficiencies in JEP: 400: UTF-8 by Default

2021-03-31 Thread Roger Riggs
Hi Anthony, A draft of updates to the Process API is in the works and covers improving the ease of use and providing Readers and Writers.  Note that if process output is redirected to a file, it does not interpose on the byte streams and is not in a position to affect the character set used

Re: Insufficiencies in JEP: 400: UTF-8 by Default

2021-03-30 Thread Anthony Vanelverdinghe
Hi Alan As Marco mentioned, another use case is sub-process stdin/stdout/stderr. In my particular instance, I'm starting a Process which has its output redirected to a file. It uses the platform's default encoding for writing to stdout. So when I want to read its output from the file at some

Insufficiencies in JEP: 400: UTF-8 by Default

2021-03-14 Thread Marco
Hi all, the JEP generally paints the picture that using the OS charset would be incorrect or useless, it is however the right and perfectly valid choice for communicating with other local programs where no other charset was specified. It is the same as UTF-8 most of the time, but not always

Re: Insufficiencies in JEP: 400: UTF-8 by Default

2021-03-14 Thread Alan Bateman
On 14/03/2021 11:00, Marco wrote: : IMO Charset should provide standardized getters for the OS charset and the console charset. The latter being different has been a long standing issue on Windows where the codepage differs between its CLI and regular environments. OpenJDK has the necessary