-
Bug
-
Resolution: Fixed
-
P3
-
15
-
b30
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8258642 | 17 | Jonathan Gibbons | P3 | Resolved | Fixed | b03 |
JDK-8260172 | 16.0.1 | Jonathan Gibbons | P3 | Resolved | Fixed | b03 |
One example of non-localized strings can be seen in search.js:
var noResult = {l: "No results found"};
var loading = {l: "Loading search index..."};
var catModules = "Modules";
var catPackages = "Packages";
var catTypes = "Types";
var catMembers = "Members";
var catSearchTags = "SearchTags";
var watermark = 'Search';
var UNNAMED = "<Unnamed>";
var noResult = {l: "No results found"};
var loading = {l: "Loading search index..."};
var catModules = "Modules";
var catPackages = "Packages";
var catTypes = "Types";
var catMembers = "Members";
var catSearchTags = "SearchTags";
var watermark = 'Search';
var UNNAMED = "<Unnamed>";
- backported by
-
JDK-8258642 Localize javadoc search
- Resolved
-
JDK-8260172 Localize javadoc search
- Resolved
- blocks
-
JDK-8258002 Update "type" terminology in generated docs
- Resolved