bug #10520
closedSupport non-default language for new taxon pages (start with feature labels)
100%
Description
Currently only English is fully supported. If data exists and is required in other Languages/Locales it sometimes is not handled correctly.
An obvious data type are feature labels, but there might be more.
Related issues
Updated by Andreas Müller 4 months ago
- Related to task #10508: Remaining issues for DTO based taxon page added
Updated by Andreas Müller 4 months ago
- Related to feature request #10513: Use locale instead of Language at all places except for common name language added
Updated by Andreas Müller 3 months ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
I added locale to the API params.
@KL: Can you please implement locale passing by the dataportal?
Updated by Andreas Müller 3 months ago
- % Done changed from 10 to 60
Now, at least features should be shown correctly if locale is es, ru or de. Other terms or i18n-texts are not yet handled. We should open a follow up ticket for those.
Updated by Andreas Müller 3 months ago
- Subject changed from Support non-default language for new taxon pages to Support non-default language for new taxon pages (start with feature labels)
- Status changed from In Progress to Resolved
- Assignee changed from Andreas Müller to Katja Luther
- % Done changed from 60 to 70
others i18n issues are handled in #10508. So for now I do not open a follow up ticket.
Please do final review. (I checked already on flora cuba on test and it seems to work)
Updated by Katja Luther 3 months ago
- Status changed from Resolved to Closed
- Assignee changed from Katja Luther to Andreas Müller
- % Done changed from 70 to 100
Also checked on eFloraMex and all features are correctly displayed in Spanish, so I think we can close this ticket.