Topic: Context for Tricky Translations
Topic type:
Some of the more administrator or programmer facing pieces of text in Kete's user interface may be tricky to translate without some context. Add your tricky translations for Kete here.
This topic gives context to those translations that may need some explanation to translate. Add your tricky translations to the topic directly or as discussion:
| Key | English version | Explanation |
|---|---|---|
| content_types.form.humanized_plural | Humanized Plural | Humanized in this context means what is shown in the user interface for the content type. E.g. the content type StillImage is called "image" in the user interface and what we refer to as the "humanized" version of the content type name. The humanized plural in this case would be "images". So maybe "non-technical" is best way to read "humanized". "Humanized Plural" could then be read as "the plural version of the non-technical name". |
| search.setup_rebuild.end_rebuild_at_description | You must {{t.base.choose}} a specific type to rebuild rather than "all types" to use anything but 'last'. If you {{t.base.choose}} a specific type, you may specify the id number in the Kete database to finishing rebuilding at, i.e. the value you of the id column in the topics table that corresponds to the last {{t.base.zoom_types.topic}} to be {{t.base.added}} to the {{t.base.search}} engine. |
This is about choosing technical settings for rebuildng the search engine databases. Only technical administrators see this area. To get a feel for the context, I recommend, as a technical administrator, visiting Administrator's Toolbox > Rebuild Search Databases link.
|
| search.setup_rebuild.start_rebuild_at_description | You must {{t.base.choose}} a specific type to rebuild rather than "all types" to use anything but 'first'. If you {{t.base.choose}} a specific type, you may specify the id number in the Kete database to start rebuilding at, i.e. the value you of the id column in the topics table that corresponds to the first {{t.base.zoom_types.topic}} to be {{t.base.added}} to the {{t.base.search}} engine. | Same as above. |
| search_helper.pagination_links.depreciated | depreciated, we now use will_paginate plugin | This is probably safely left as English only as it will be completed deleted from the user interface in a future version of Kete. |
| search_sources_helper.or_syntax_form_column.case | Case | This refers to whether the setting is all upper case version of the word "or", lowercase, or capitalized. |
| topic_types.generic_topic_fields.description_field | Description: Describe the topic. This where we store the {{t.base.history}} of the {{t.base.zoom_types.topic}} we are writing about. TODO: flesh out description of this attribute. |
Seen only by site administrators. This is place holder text that actually should be replaced. We'll likely update it to say this: "Description: this is where users put the body of their {{t.base.zoom_types.topic}}." |
| topic_types.generic_topic_fields.note | All {{t.base.zoom_types.topic}} types are descended from the generic "Topic" which can not have it form fields {{t.base.changed}}. They are the following: |
This will be replaced with the following: All {{t.base.zoom_types.topic}} types inherit the following form fields: |
