Terminology: export do-not-translate and forbidden terms correctly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 611
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 49
Description
Do not translate
We currently don't export do-no-translate terms when creating the TBX file.
TBX-Basic doesn't support marking a term as do-not-translate, so we would need to create a dialect. The alternative is to export the source as translation for the locale.
Forbidden
forbidden terms should be flagged with
<termNote type="administrativeStatus">
deprecatedTerm-admn-sts
</termNote>
We currently export them as standard terms
<conceptEntry id="c622">
<langSec xml:lang="en-US">
<termSec>
<term>abort</term>
<termNote type="partOfSpeech">verb</termNote>
<descripGrp>
<descrip type="definition">Cancel a process</descrip>
<descrip type="context">Do you want to abort this download</descrip>
</descripGrp>
</termSec>
</langSec>
<langSec xml:lang="it">
<termSec>
<term>annullare</term>
</termSec>
</langSec>
</conceptEntry>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the TBX export implementation and its existing tests, then trace how do-not-translate and forbidden terms are serialized. Use the TBX-Basic limitation and the provided XML examples as acceptance criteria: do-not-translate terms need the chosen export representation, and forbidden terms must receive the specified administrativeStatus note.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- localization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100