Bug #1922
closed
Missing user interface translations
Description
Update¶
Comments to the original descriptions were made in green.- -> type: means the label is taken from the type hierarchies. Because user can create new types this won't fix unless we implement multiple language functionality for data entry, see #1925
- -> reference system: the same as above just for reference systems
- -> fixed: means they are now fixed in the develop branch and on demo-dev. Some of them were related to other issues but some were added to the catalogue and can be translated now.
Original description¶
Messages not included in messages.po¶
- 'previous'
- 'next'
- 'Showing 1 to 25 of 1,416 entries'
- 'Show 25 entries'
- These are concerning table labels, I created a new issue (#1924) for this add added you as watcher
https://demo-dev.openatlas.eu/insert/source¶
Field labels:- 'Case Study' -> type
- 'Artifact' -> fixed
- 'Provenance' -> type
- 'Type' > 'Types for historical sources like ...' -> type
https://demo-dev.openatlas.eu/insert/activity¶
Field labels:- 'Case Study' -> type
- 'Type' > 'Categories for the type of events ...' -> type
- 'Wikidata' > 'A free and open knowledge' -> reference system
https://demo-dev.openatlas.eu/insert/acquisition¶
Field labels:- 'Case Study' -> type
- 'Type' > 'Categories for the type of events ...' -> type
- 'Wikidata' > 'A free and open knowledge' -> reference system
https://demo-dev.openatlas.eu/insert/move¶
Field labels:- 'Case Study' -> type
- 'Artifact' -> fixed
- 'Person' -> fixed
Info of Field labels: - 'Type' > 'Categories for the type of events ...' -> type
- 'Wikidata' > 'A free and open knowledge ...' -> reference system
https://demo-dev.openatlas.eu/insert/production¶
Field labels:- 'Artifact' -> fixed
- 'Sex' -> type
https://demo-dev.openatlas.eu/insert/person¶
Field labels:- 'Case Study' -> type
- 'Sex' -> type
Info of Field labels: - 'Sex' > 'Categories for sex like ...' -> type
- 'Wikidata' > 'A free and open knowledge ...' -> reference system
https://demo-dev.openatlas.eu/insert/place¶
Field labels:- 'Administrative unit' -> type
- 'Case Study' -> type
- 'Evidence' -> type
- 'Hilltop Classification HTC' -> type
- 'Historical place' -> type
- 'Sign of Power' -> type
- 'Stylistic Classification' -> type
- 'GeoNames' -> reference system
- 'Insert and add feature' -> fixed
- 'Type' > 'Types for non-moveables ...' -> type
- 'Administrative unit' > 'Hierarchy of administrative units ... ' -> type
- 'Historical place' > 'Hierarchy of historical places ...' -> type
- 'GeoNames' > 'Geographical database covering...' -> reference system
- 'Wikidata' > 'A free and open knowledge ...' -> reference system
https://demo-dev.openatlas.eu/insert/artifact¶
Field labels:- 'Case Study' -> type
- 'Kettchen und Halbmonde' -> type
- 'Position of Find in Grave' -> type
- 'Stylistic Classification' -> type
Info of Field labels: - 'Material' > 'Material of physical object' -> type
https://demo-dev.openatlas.eu/insert/human_remains¶
Info of Field labels:- 'Dimensions' > 'Physical ' -> type
- 'Type' > 'Human remains, that ...' -> type
https://demo-dev.openatlas.eu/insert/bibliography¶
Info of Field labels:- 'Type' > 'Categories for bibliographical ...' -> type
https://demo-dev.openatlas.eu/insert/edition¶
Field labels:- 'Case Study' -> type
Info of Field labels: - 'Type' > 'Categories for the classification ...' -> type
https://demo-dev.openatlas.eu/insert/external_reference¶
Info of Field labels:- 'Type' > 'Categories for the classification ...' -> type
Updated by Alexander Watzinger over 1 year ago
- Subject changed from Translations: I guess that messages are missing from the message files to Missing translations
- Category set to UI
- Status changed from New to In Progress
- Assignee set to Alexander Watzinger
- Target version set to 7.10.0
Thank you for reporting and the detailed list. These are concerning multiple areas, not all will be solvable, but I will go through them and give more feedback afterwards.
Updated by Alexander Watzinger over 1 year ago
- Related to Feature #1924: Unify translations, add missing table translations added
Updated by Alexander Watzinger over 1 year ago
- Tracker changed from Question to Bug
- Subject changed from Missing translations to Missing user interface translations
- Description updated (diff)
- Status changed from In Progress to Resolved
- Found in version set to 7.9.0
I've gone through the list and added comments, see updated description.
Thank you a lot for taking the time for the detailed report and sorry about the parts that can't be translated (types and reference systems) which is not that obvious at first.
Other issues should be fixed. There are some new items added to the catalogue in the develop branch and are now available to translate.
Updated by Enric Rodellas over 1 year ago
HI Alex,
I have revised Spanish and Catalan messages, specially these marked as 'fixed'
I have done a a fork 'feature_espanol-catalan' and a pull request (I hope to 'develop branch) ... sorry, but I'm not a master on github..
Updated by Alexander Watzinger over 1 year ago
Dear Enric,
Thank you for your latest changes (spanish catalan translation with fixed issues/1922). I merged this (manually) into develop and you can see on demo-dev that it is working. E.g. "Inserta y añade característica" at https://demo-dev.openatlas.eu/insert/place
There was a minor issue with the Spanish translation, if you see something like:
showing %(first)s to %(last)s of %(all)s entries
the %(something)s notation means these are placeholders and they should not be translated, the right entry for this would look like:
mostrando del %(first)s a %(last)s de %(all)s ítems
I fixed it already and you did it right in the Catalan translation, so this maybe was just an oversight.
About the GitHub pull requests for translations- Before doing the pull request you should always pull the latest develop branch version (which you did correctly).
- The pull request should be against the develop branch, you can choose this on top of the pull request site at the drop-down, instead "base:main" it should be "base:develop"
You can read more about it here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - You shouldn't close the pull request yourself because this would mean you changed your mind and don't want it anymore. Except of course this is what you wanted.
But no worries, these are just minor issues and we are getting there. Thanks again for your contributions and learning/using our workflows.
Updated by Alexander Watzinger over 1 year ago
- Status changed from Resolved to Closed
Closing this issue, please open a new one, in case more problems become apparent.
Thank you for reporting.