-
Bug
-
Resolution: Fixed
-
Critical
-
-
pacific, atlantic, 1.0-b05/b-06, indian
In Scope
- All strings and formatting should be localisable
- Short explanation on how we localise components and the app put in a README.md
- Go through and extract all our current strings
Notes
- Looks like react-intl is the way things are done in React apps today. Here's a video from React.js conf 2015
- duplicates
-
JENKINS-35270 /i18n/resourceBundle does not load bundles from plugins
-
- Resolved
-
- is blocked by
-
JENKINS-39604 ResourceBundleUtil#getBundle() should not report missing resources on the WARNING level
-
- Resolved
-
- is blocking
-
JENKINS-39345 Use js-modules to coordinate async loading of i18n translation bundles as part of dependant JavaScript bundle
-
- Resolved
-
- is duplicated by
-
JENKINS-35904 Provide internationalization framework for components
-
- Closed
-
- relates to
-
JENKINS-36610 [Blue Ocean] Remove hard coded link to new job from blue ocean header
-
- Closed
-
kzantow - you were taking a look at this? tscherler might want to check with keith before opening a PR (if work hasn't started).
Also Keith - should route localisation be part of the scope of this? (do we want to do that? )
EDIT: I think route i18n should be another ticket (as it is likely a hairy beast)