Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
On July 27, 2020 2:12:45 AM CDT, Stefan Eissing <stefan.eiss...@greenbytes.de>
wrote:
Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri <drugg...@apache.org>:
Hi, all;
FYI, I came across an unexpected set of diffs when rebuilding docs
before tagging this morning. Haven't forgotten about T&R, but would
like to figure out the origin of the docs changes (likely my
environment). I've started a conversation on docs@ about what I'm
seeing.
Sorry about your troubles. Do we need to look for someone else doing
the RMing or what's your status?
Hi, Stefen;
I'm still good to go. I just need clarity on what encoding behavior we expect
in the docs. More info is on docs@. Either way works for me... just need to
know what the consensus is.
On 2020/07/22 23:32:05, Daniel Ruggeri <dan...@bitnebula.com> wrote:rance :))
Hi, all;
It's been a while since we've rolled a release and gotten
fixes/etc in our community's hands. Apologies for not suggesting this
sooner. How about a T&R Friday? That will let vote run through the
weekend.
--
Daniel Ruggeri
Hi,
I don't have access to my PC these days (side effect from being on
vacation in the south of France :)), however, have a look at r1878788 on
trunk which should fixed once and for all the issue.
This commit switches the en doc files into utf8 which works great with
older and newer versions of Java.
To be consistent with the other language, the files themselves should be
renamed to have a trailing .utf8, as explained in the commit description.
I've not done it on trunk because it is painful (at least for me) to
synch all the news .utf8 files with svn. If s.o. feels like making the
change, please do.
CJ
