Add Properties in TermBase
Hi again, WordBee team!
I had a question about the editing terms in the termbase. On this page in the knowledge base, under how to add synonyms in examples, we see an add properties button.
However, as shown in the screenshot, the button isn't showing up. Do you know how we fix this? Thank you!
-
Hello Stefan,
You may need to check with the administrator of your system what the configuration of the Terminology module is. I am sure there are no TBX Fields or Custom Fields defined in your working templates (that would explain why you don't see the 'Add Property' button).
The following documentation page provides guidance on the topic: Getting Started with the Terminology Management Tool
Let us know if this helped!
Cheers,
Sara Méndez
Product Manager1 -
Thank you, Sara! I will check with our administrator.
I did have a follow up question. I am considering keeping a term and its acronym as one concept in the term base and using the properties to mark which one is the acronym.
Is it possible, during QA, to have wordbee flag terms and their translations which do not have matching properties? So that if the source has the acronym but the target doesn't, then WordBee would flag it.
Currently, I've been adding the term and acronym as separate entries.
Kind regards,
Stefan
0 -
Hello Stefan, the current version of the QA module does not check for any term properties in the database (beyond the segment status, which is a native property in Wordbee Translator property). However, such details can be checked in the Translation Editor while performing any translation job. Depending on the language you are translating to, one form of the term or the other may be preferred (due to the many factors that play a role, this type of check does not get automated in Wordbee Translator). Note that sometimes acronyms need to be developed into their full forms while no equivalent is coined in the target and that is made explicit by other means (like the use of italics, quotes, etc.).
In my opinion, by creating a concept-oriented structure you are already covering your case in the most efficient way:
- by avoiding duplicate entries in the database (with the risk of polluting your resources)
- by documenting each concept accordingly. This helps translators make the best decision when terms are found in their texts. As soon as a term is spotted in the source text, the system will propose all the related target terms within the same concept.
It is up to the translator to use an acronym or the full form of a term, who will decide by inspecting the matching terms in the Translation Finder.
We keep your feedback documented for future extensions of the QA module and we will let you know in case something changes in this direction.
Cheers,
Sara Méndez
Project Manager0 -
Hi Sara,
Thank you for letting me know! We generally like to leave it to our translators to make the best decision; however, some clients have some very specific style guide considerations such as always using the acronym in both the target and the source. As I cannot read all of the languages we perform a QA check on, I was also hoping to also have WordBee be able to flag if an inconsistent grammatical number was used, for instance, singular in source but plural in target.
Should I put these in the feature suggestion forum?
Kind regards,
Stefan
0 -
sure, you can always do that. Although the concept of pluralization exists in many languages, the notion of singular and plural is not a simple conversion. As you may know, it often depends on the context, interpolation, the subject of the sentence, etc. As an example, Arabic has 5 plural forms, so unless your source text is structured as per CLDR principles, the conversion is not so straightforward.
The good thing about having a feature suggestion is that other users can contribute to your post too. It would be useful to capture all the particular scenarios in which such a feature could make sense.
Cheers,
Sara
0
Please sign in to leave a comment.
Comments
5 comments