[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Control how terms are translated\n\n| Starting on June 30, 2025, Translation Hub is officially deprecated and will no longer be supported. You can continue using Translation Hub until on June 30, 2026, when it will be shut down.\n\n\u003cbr /\u003e\n\nIn cases where domain-specific terms and named entities must be consistently\ntranslated, create a glossary. A glossary is a custom dictionary that contains\ncorresponding terms in two or more languages. During machine translation,\nTranslation Hub automatically replaces matching source-language terms\nwith their associated target-language terms.\n\nUse glossaries to fine tune how certain terms or entities are translated. For\nexample, you can include a glossary entry to prevent a product name (like\n\"Google Home\") from being translated.\n\nAfter you create a glossary, add it to portals to make it available for portal\nusers to use.\n\nGlossary compared to other translation resources\n------------------------------------------------\n\nIn addition to glossaries, you can provide other resources to assist portal\nusers with their translations. The following section describes the differences\nbetween each resource.\n\n- [Translation memories](/translation-hub/docs/admin-translation-memory) match on segments, whereas glossaries match on terms. Use translation memories to reuse human-reviewed translations that were imported, captured during post-editing, or both. Translation memories can include as many segments pairs in as many languages as you require.\n- [Custom models](/translation-hub/docs/admin-custom-model) are trained with your sentence pairs and can help you improve machine translations when you don't have a comprehensive glossary or translation memory available. In cases where you want to tune machine translations for a specific domain and writing style, use AutoML Translation to build custom models that produce better-fitting predictions.\n\nPortal users can use a combination of these resources to help improve the\nquality of their translations. For more information about how\nTranslation Hub applies resources during translations, see [Translate\ndocuments](/translation-hub/docs/user-translate#translation-process).\n\nStopwords\n---------\n\nTranslation Hub ignores some terms that are included in a glossary; these\nterms are known as *stopwords* . Translation Hub still translates\nstopwords but ignores any matching glossary entries. For a list of all\nstopwords, see [Glossary\nstopwords](/translation-hub/docs/admin-glossary-stopwords).\n\nBefore you begin\n----------------\n\nTo populate your glossary, you need a file with terms in their corresponding\nlanguages. The format of your source file depends on the type of glossary that\nyou create: *unidirectional* or *equivalent term set*.\n\nGlossary entries are case sensitive. For case-insensitive entries, include both\nforms in your glossary.\n\n### Unidirectional\n\nA unidirectional glossary specifies the desired translation for terms as source\nand target language pairs. These glossaries work one way. For example, an\nEnglish to Spanish unidirectional glossary doesn't apply to Spanish to English\ntranslations.\n\nYou can provide a TSV (tab-separated values), CSV (comma-separated values), or\nTMX (Translation Memory eXchange) file. For TSV and CSV files, don't include a\nheader row to identify the source and target languages. You specify them when\nyou create the glossary. For TMX files, use the [TMX version\n1.4](https://www.gala-global.org/knowledge-center/industry-development/standards/lisa-oscar-standards) standard.\n\nFor details and examples of glossaries, see [Creating\nand using glossaries](/translate/docs/advanced/glossary) in the Cloud Translation documentation.\n\n### Equivalent term set\n\nAn equivalent term set contains equivalent terms in multiple languages and must\nbe defined in a CSV file. Each row contains corresponding terms in different\nlanguages. These glossaries are bi-directional. The header row must identify the\nlanguage for each column by its corresponding [language code](/translation-hub/docs/supported-languages).\n\nFor details and examples of glossaries, see [Creating\nand using glossaries](/translate/docs/advanced/glossary) in the Cloud Translation documentation.\n\n### Glossary limits\n\nTranslation Hub sets limits on the size of the source file and\non the size of each glossary entry. For more information, see [Quotas and\nlimits](/translation-hub/docs/quotas).\n\nCreate glossary\n---------------\n\nYou create glossaries by using the Google Cloud console. If you have previously\ncreated resources through the Cloud Translation API, Translation Hub makes\nthem available to you. You can assign those resources to portals.\n\n1. In the **Translation Hub** section of the Google Cloud console, go to the\n **Resources** page.\n\n [Go to the Resources page](https://console.cloud.google.com/translation-hub/resources)\n2. Click **Add resource**.\n\n3. In the **Add resource** pane, select the **Glossaries** tab.\n\n4. Specify a name for the glossary.\n\n5. Select the glossary type.\n\n6. Upload a local glossary file to Cloud Storage or select an existing\n glossary file from Cloud Storage.\n\n7. Specify the glossary languages.\n\n8. Click **Add** to create the glossary.\n\nAdd glossaries to portals\n-------------------------\n\nAfter you create glossaries, add them to portals to let portal users use them\nwhen they request translations.\n\n1. In the **Translation Hub** section of the Google Cloud console, go to the\n **Resources** page.\n\n [Go to the Resources page](https://console.cloud.google.com/translation-hub/resources)\n2. From the list of resources, select one or more glossaries to add to one\n or more portals.\n\n3. Click **Assign to portals** , which opens the **Assign resource to portal**\n pane.\n\n4. From the portals field, select one or more portals to add the glossaries to.\n\n5. Click **Assign**.\n\n On the **Resources** page, you can confirm the addition by viewing the\n **Portal names** column for each resource.\n\nWhat's next\n-----------\n\n- Learn how portal users [request translations](/translation-hub/docs/user-translate)."]]
