#1053 closed defect (fixed)
scripts/ext/locale/* not loading
| Reported by: | estorm | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | v2.8.0 |
| Component: | General | Version: | v2.8.0RC0 |
| Keywords: | Cc: |
Description
Geonetwork now uses 3 character language identifiers. However, the multilanguage versions of ext-lang.js found in scripts/ext/locale all still use a 2 character language identifier, which means that they are not loaded.
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
My comments were related to new UI interface.
Indeed in classic UI tries to load ext-lang-eng.js instead of ext-lang-en.js
comment:3 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Master commit: 145780f0623263fc98ea8f696aa34ff0f0c54166 2.8.0 branch commit: 05c9e8dc11776c7db0d63ce3fefd021e7a2240e4
comment:4 by , 12 years ago
| Milestone: | v2.9.0 → v2.8.0 |
|---|
Note:
See TracTickets
for help on using tickets.
The method setLang in js/GeoNetwork/lib/GeoNetwork/Util.js manages about translating 3 letter code to 2 letter code. This method is call in application loading.
Tested with english and french, the javascript console reports that ext-lang-en.js and ext-lang-fr.js are loaded.
To check further.