[
https://issues.apache.org/jira/browse/MJAVADOC-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958175#comment-17958175
]
Olivier Lamy commented on MJAVADOC-803:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1180|https://github.com/apache/maven-javadoc-plugin/issues/1180].
> Add default parameter to force root locale
> ------------------------------------------
>
> Key: MJAVADOC-803
> URL: https://issues.apache.org/jira/browse/MJAVADOC-803
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: jar, javadoc
> Affects Versions: 3.7.0
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.8.0
>
>
> 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)
