Do you it’s worth logging a jira case? It’s a bug with symptoms that are visible beyond the Calcite site and current release, so I think a Jira would help document it.
Is it possible to fix the 1.36 doc? I don’t believe so. And actually I think it’s rather a neat curiosity, so we should let it stand even if there were a fix. > On Jan 18, 2024, at 6:52 AM, Benchao Li <[email protected]> wrote: > > I've opened a PR[1] to use 'en_US' locale for the javadoc task. There > is no need to mention this in the docs now. > > [1] https://github.com/apache/calcite/pull/3637 > > Benchao Li <[email protected]> 于2024年1月18日周四 10:46写道： >> >> Thanks Guillaume for reporting this, >> >> Calcite hosts the javadoc here[1], it's in English. >> >> For the docs hosted in javadoc.io, it's in Chinese indeed. It seems to >> be a problem of the locale setting while preparing the artifacts for >> releasing, and this is an ignored process in our releasing steps in >> the past (making sure the locale is en). I'll open a PR to add this >> step in our documentation. >> >> [1] https://calcite.apache.org/javadocAggregate/ >> >> Guillaume Masse <[email protected]> 于2024年1月18日周四 04:36写道： >>> >>> It looks like the javadoc for 1.36.0 was publish in chinese: >>> https://javadoc.io/doc/org.apache.calcite/calcite-core/latest/index.html >>> >>> -- >>> Guillaume Massé >>> [Gee-OHM] >>> (马赛卫) >> >> >> >> -- >> >> Best, >> Benchao Li > > > > -- > > Best, > Benchao Li
