[
https://issues.apache.org/jira/browse/MJAVADOC-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAVADOC-803:
------------------------------------
Description:
Javadoc suffers from the following two problems:
* During HTML generatation {{Locale#getDefault()}} is invoked and all generated
content maybe localized, e.g. German, Japanese. That is a surprise for most
since they expect to see English content. One has to force with
{{<locale>en</locale>}}.
* In the past JDKs Oracle now started to even localize stdout and stderr output
to those languages (see
https://github.com/openjdk/jdk21u-dev/tree/master/src/jdk.javadoc/share/classes/jdk/javadoc/internal/tool/resources),
even more could come. This causes a regression with MJAVADOC-751 which relies
on English language output to work.
Therefore, we will introduce a new parameter {{forceRootLocale}} which will add
{{-J-Duser.language= -J-Duser.country=}} and will result in {{Locale#ROOT}}.
Both will force generated HTML output and std output to be in English. Those
who still need generated content in a specific language can pass {{<locale/>}}
and it will work independently of the std output.
was:
Javadoc suffers from the following two problems:
* During HTML generatation {{Locale#getDefault()}} is invoked and all generated
content maybe localized, e.g. German, Japanese. That is a surprise for most
since they expect to see English content. One has to force with
{{<locale>en</locale>}}
* In the past JDKs Oracle now stated to even localize stdout and stderr output
to those languages (see
https://github.com/openjdk/jdk21u-dev/tree/master/src/jdk.javadoc/share/classes/jdk/javadoc/internal/tool/resources),
even more could come. This cases a regression with MJAVADOC-751 which relies
on English language output to do work.
Therefore, we will introduce a new parameter {{forceRootLocale}} which will add
{{-J-Duser.language= -J-Duser.country=}} which will result in {{Locale#ROOT}}
and force both generated HTML output and std output to be in English. Those who
still need generated content in specific language can pass {{<locale/>}} and it
will work independently of the std output.
> Add default parameter to force root locale
> ------------------------------------------
>
> Key: MJAVADOC-803
> URL: https://issues.apache.org/jira/browse/MJAVADOC-803
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: jar, javadoc
> Affects Versions: 3.7.0
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.7.1
>
>
> Javadoc suffers from the following two problems:
> * During HTML generatation {{Locale#getDefault()}} is invoked and all
> generated content maybe localized, e.g. German, Japanese. That is a surprise
> for most since they expect to see English content. One has to force with
> {{<locale>en</locale>}}.
> * In the past JDKs Oracle now started to even localize stdout and stderr
> output to those languages (see
> https://github.com/openjdk/jdk21u-dev/tree/master/src/jdk.javadoc/share/classes/jdk/javadoc/internal/tool/resources),
> even more could come. This causes a regression with MJAVADOC-751 which
> relies on English language output to work.
> Therefore, we will introduce a new parameter {{forceRootLocale}} which will
> add {{-J-Duser.language= -J-Duser.country=}} and will result in
> {{Locale#ROOT}}. Both will force generated HTML output and std output to be
> in English. Those who still need generated content in a specific language can
> pass {{<locale/>}} and it will work independently of the std output.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
