#699 closed enhancement (fixed)
Use content language information in description fields
| Reported by: | Twan Goosen | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | VLO-3.1 |
| Component: | VLO web app | Version: | |
| Keywords: | Cc: | teckart@informatik.uni-leipzig.de |
Description
The importer stores content language (xml:lang) information in description fields when available, see #667 & r5849.
Represent this information in the webapp by (in case of multiple languages) showing the language alternatives (with language labels/flags/...) and possibly showing the description in language matching the client's locale if available (or maybe always English as long as the VLO is in English).
Change History (7)
comment:1 Changed 10 years ago by
| Cc: | teckart@informatik.uni-leipzig.de added |
|---|
comment:2 Changed 10 years ago by
| Milestone: | VLO-3.1 → VLO-3.2 |
|---|
comment:3 follow-up: 4 Changed 10 years ago by
| Milestone: | VLO-3.2 → VLO-3.1 |
|---|
All descriptions have a {lang='xxx'} prefix. In case of an unknown language, xxx is 'und'. Otherwise, it's a three letter ISO639 language code.
TODO:
- skip language string in display of description
- display the language information on the side or in a tooltip
- (in case of multiple languages, sort by the client's language preference)
comment:4 Changed 10 years ago by
Note: See
TracTickets for help on using
tickets.
Splitting 3.1 milestone. Most open tickets go to 3.2 so that we can have a release on the short term.