On Mon, Oct 1, 2018 at 4:15 PM Luis Gil de Bernabé <lgilbern...@apache.org> wrote:
> I have updated long ago the files from es, but i wasn't sure to commit > them as the FR file Lucien is saying. > So now i'm sure it could be done, i will add them to trunk (es > modification only) > > @Christophe JAILLET <christophe.jail...@wanadoo.fr> im not helpfull > here, but i vote +1 to update our build tool :) > rgd > Also +1 to a freshened build toolchain, or trusting the JDK (Open or otherwise) to provide the functionality. Very concerned about trusting utf-8 for anything that is expected to be console readable. Not as much the xml/html decorated contents, but the man pages and any text files concern me. I've been living in a utf-8 console for a very long time, but I don't expect my experience is typical. I'm also not keen on delivering 1%-3% more bytes over the wire where we can directly represent the contents in an ISO-8859 representation. That said, shifting to utf-8 also buys us the symbolic sets. Let's avoid the emoji's, but various bullets and highlight characters could drastically improve the readability of our docs. So on balance, utf-8 doesn't seem unreasonable, *unless* we expect most localized users will be reading the plain text of the file.
