Turn a term list into a clean glossary file.

What makes a good term base

A glossary is not a dictionary; it is a list of decisions. The terms worth pinning are the ones a translator could plausibly render three different ways: proper nouns, product and entity names, job titles, and agreed transliterations. "Al Dana Holdings" has exactly one approved Arabic form, and the glossary is where that decision lives so it survives staff changes and rush jobs.

• One approved target per source. A source term with two targets is a style debate, not a glossary entry. Settle it, then record the winner. The duplicate flag above exists for this reason.
• Prefer specific over general. "Board Pack Q3.pptx" needs "board of directors" pinned; it does not need the word "company".
• Record transliterations explicitly. Names of people, places, and brands are where inconsistency shows first, especially between Arabic and English.
• Use categories. Tagging rows as legal, product, or names lets reviewers audit one slice at a time and keeps unrelated departments from fighting over the same file.

TMX vs CSV

CSV is the right format for a term base: one source, one target, a category, easy to review in a spreadsheet and easy to import. TMX is a different animal, an XML exchange format for translation memory, which stores whole translated segments rather than terms. You maintain a glossary by hand; a translation memory accumulates automatically as work gets approved. TranslateX supports both: CSV-style term pairs with categories and notes in the glossary, and TMX import and export for memory.