용어집¶
Each project can include one or more glossaries for storing terms and their preferred translations. Glossaries help keep translations consistent by showing matching terms in the translation editor.
Glossaries are regular translation components with special behavior. The source language stores the terms Weblate searches for in source strings. Each glossary translation stores the preferred term, forbidden term, or untranslatable entry for one target language.
Terms from the glossary containing words from the currently translated source string are displayed in the sidebar of the translation editor.
힌트
용어집 용어는 활성화하지 않는 한 품질 검사에 사용되지 않습니다. 자세한 내용은 용어집 미준수 를 참조하세요.
How glossary matching works¶
When you translate a regular component, Weblate searches the source string for terms from the source language of the project glossaries. When a term matches, Weblate looks up the corresponding glossary entry for the language currently being translated and shows it in the editor.
This means glossary entries need to exist in the target glossary language to be shown while translating that target language. A source-language-only glossary can still store definitions and context, but it will not provide target-language matches for languages that do not have glossary entries.
If you want a term to be present in every glossary language, mark the source entry as 전문 용어. If the term should stay unchanged in every language, use 번역 불가 용어; combine it with terminology only when you want Weblate to create and maintain entries for all glossary languages.
용어집 관리¶
버전 4.5에서 변경: 용어집은 이제 일반 번역 구성 요소이며, 의견 작성, 원격 저장소 저장, 설명 추가 등 Weblate의 모든 기능을 사용할 수 있습니다.
용어집으로 사용 를 켜서 모든 구성 요소를 용어집으로 사용하세요. 하나의 프로젝트에 대해 여러 개의 용어집을 만들 수 있습니다.
지정된 프로젝트에 대한 빈 용어집이 프로젝트와 함께 자동으로 생성됩니다. 용어집은 동일한 프로젝트의 모든 구성 요소 간에 공유되며, 선택적으로 각 용어집 구성 요소의 프로젝트에서 공유 를 사용하여 다른 프로젝트와도 공유됩니다.
용어집 구성 요소는 색상 레이블이 추가된 Weblate의 다른 구성 요소와 동일하게 표시됩니다:
모든 용어집 용어를 탐색할 수 있습니다:
또는 일반 번역과 동일하게 편집할 수 있습니다.
용어집 용어¶
용어집 용어는 일반 문자열과 같은 방식으로 번역됩니다. 각 용어에 대해 도구 메뉴를 사용하여 추가 기능을 전환할 수 있습니다.
더 보기
유형 |
Purpose |
|---|---|
Regular glossary term |
Preferred translation or explanation for a term in one or more languages. |
Source term Weblate keeps present in every glossary language so missing translations can be tracked and filled. |
|
Term that should stay unchanged or should not be translated. |
|
Translation that should not be used for the source term. |
|
Alternative wording, abbreviation, or shorter form grouped with another glossary term. |
Choosing glossary terms¶
Choose glossary terms for meaning and audience, not only for literal word shape. If a source term is ambiguous, add an explanation so translators know which meaning applies in the project.
Glossary entries are especially useful for brand names, acronyms, product features, technical terms, and newly coined or transliterated words. Use variants for abbreviations or shorter wording, mark important cross-language terms as 전문 용어, mark terms that should stay unchanged as 번역 불가 용어, and mark misleading translations as 금지된 번역.
번역 불가 용어¶
Added in version 4.5.
Flagging certain glossary term translations read-only by bulk-editing,
typing in the flag, or by using Tools ↓
Mark as untranslatable means they can not be translated. Use this
for brand names, product names, domains, technology names, or other terms that
should not be changed in other languages. Such terms are visually highlighted
in the glossary sidebar.
The read-only flag is enough when the glossary entry already exists in the
languages where it should be shown. Add the 전문 용어 flag as
well only when Weblate should create and maintain the untranslatable entry in
every glossary language.
더 보기
금지된 번역¶
Added in version 4.5.
일괄 편집, 플래그 직접 입력 또는 도구 ↓ 금지된 번역으로 표시 를 사용하여 특정 용어집 용어 번역을 forbidden 으로 표시하면 해당 번역은 사용할 수 없습니다. 일부 단어가 모호하거나 예상치 못한 의미를 가질 수 있는 경우 번역을 명확히 하기 위해 사용하세요.
Use forbidden entries for translations that should be avoided. Use regular glossary entries for preferred translations.
더 보기
전문 용어¶
Added in version 4.5.
Flagging certain source-language glossary terms as terminology by
bulk-editing, typing in the flag, or by using Tools ↓
Mark as terminology adds entries for them to all languages in the
glossary. Use this for important terms that should be well thought out, and
retain a consistent meaning across all languages.
Enable 문자열 관리 on the glossary component to synchronize terminology. When it is disabled, Weblate does not create missing language entries, even for terms marked as terminology.
Weblate shows a dismissible diagnostic when string management is disabled for a glossary with no remote repository, or for another glossary that contains terminology. Enable string management to add terms directly in Weblate and synchronize terminology, or dismiss the warning if you maintain the glossary files separately.
The terminology flag is ongoing state, not just a one-time action. While the flag remains on the source term, Weblate treats it as terminology and keeps an entry for it in every glossary language. If a language entry is removed, the next glossary synchronization creates it again.
terminology 플래그를 제거하면 이 자동 유지 관리가 중단되지만, 이미 생성된 항목은 삭제되거나 되돌려지지 않습니다. 해당 항목은 일반 용어집 항목으로 유지됩니다.
A regular glossary term can also have translations in every language. The difference is that Weblate does not recreate missing language entries for a regular term after they are removed.
더 보기
변형¶
변형은 문자열을 함께 그룹화하는 일반적인 방법입니다. 번역할 때 모든 용어 변형이 용어집 사이드바에 나열됩니다.
힌트
이 기능을 사용하여 용어에 대한 약어나 더 짧은 표현을 추가할 수 있습니다.
더 보기
용어집 가져오기¶
일반 번역 구성 요소와 마찬가지로 기존 용어집을 Weblate에 업로드할 수 있습니다. CSV 파일 또는 TermBase eXchange 형식 와 같은 형식이 지원되며 업로드할 수 있습니다. 번역 업로드 를 참조하세요.
TBX files can include explanations, read-only metadata, and glossary flags; see TermBase eXchange 형식 for the exact metadata mapping.
Even though TBX can contain multiple languages, Weblate still maps component files to languages using the component file mask and language settings. For a TBX glossary component, keep the component source language as the source term language and name translation files for the target language they represent. Avoid naming a translation file with the same language as the component source language, because the source language already exists in Weblate and this can lead to duplicate language detection.
Language files and synchronization¶
Glossary components follow the languages used by the regular components in the same project. When a language is added to a regular component, Weblate adds the missing glossary language as well so glossary matches can be shown for that language.
This automatic language synchronization is intentional. Filtering glossary language files with 언어 필터 can reduce the number of managed files, but it also means Weblate has no glossary entries to show for filtered-out target languages.
Terminology entries are also synchronized. When a source glossary term is marked as terminology, Weblate creates missing entries in all glossary languages and recreates them if they are removed while the flag is still set.
Weblate can clean up stale glossary translations only for Weblate-managed glossaries, only when no regular component in the project still uses that language, and only when the stale glossary translation has no translated terms. If the stale glossary language still contains terms, Weblate keeps it and reports it as an unused glossary language.
Common setup patterns¶
- English-only explanatory glossary
Add source-language glossary terms with explanations. This works as a maintained term list, but it will not show target-language glossary matches unless you also create entries in the target glossary languages.
- Required terminology
Add terms in the source glossary language, mark them as 전문 용어, and let translators fill the created entries in each target language. Use explanations to document the intended meaning.
- Non-translatable terms
Mark terms as 번역 불가 용어 when they should stay unchanged. Add 전문 용어 only when the term should be present in every glossary language for matching and review.
- 금지된 번역
Add the misleading translation as a 금지된 번역 entry. Add the preferred wording as a separate regular glossary entry when translators should use a specific translation instead.
자동 제안에서의 용어집¶
Added in version 5.3.
일부 자동 제안 서비스는 번역 중 용어집을 활용합니다. 지원 여부는 자동 제안 의 해당 문서를 참조하세요.
용어집은 서비스에 전달되기 전에 처리됩니다:
Duplicate source entries are skipped for services that require unique source terms. LLM-based services can receive duplicates with explanations to disambiguate them.
모든 제어 문자와 선행 및 후행 공백이 제거됩니다.
금지된 번역 는 건너뜁니다.
참고
많은 서비스가 서버 측에 용어집을 저장하고 저장된 용어집 수에 제한을 둡니다. Weblate는 공간이 부족할 경우 항상 가장 오래된 용어집을 삭제합니다.