Terminology: add precedence note and normalize lists#17
Conversation
Add a precedence note to KEEP_ORIGINALITY.md and TRANSLATED_TERMINOLOGY.md clarifying that KEEP_ORIGINALITY entries take priority. Normalize and tidy the glossary entries (reformatting mappings into a canonical list, reordering and harmonizing terms between the two files) to make it clear which terms must remain untranslated and when translations should be applied.
daoauth
requested review from
Harrycho415,
dolf3131,
gkfyr,
jade653,
keem-hyun,
lloes098,
neonmintweb3,
nubro999,
parksol2004,
roode1017 and
stellaa61
|
밀려있던 pr 2개는 머지하였습니다. #15 @guboc11 그러나 의 경우는 - terminology/terminology_combined.csv 이 어떻게 사용되는지는 몰라서, 단어만 이번 버젼에서 추가하였습니다. |
Expand terminology glossaries by adding numerous original terms and their translations. Files changed: terminology/KEEP_ORIGINALITY.md (adds technical terms such as API, CLI, DAG, dApp, DeFi, DeepBookV3, Ethereum, Node.js, Rust, TypeScript, Web3, USDC/USDT, object ID/owned/shared, wrapped object, etc.) and terminology/TRANSLATED_TERMINOLOGY.md (adds translated mappings like argument, bytes, client, command, consensus, digest, endpoint, gas, input, payload, pure value, provider, result, salt, sender, smart contract, voting power, wallet, and others). These additions broaden the glossary coverage for technical and localized documentation consistency.
|
collection -> 컬렉션 getter -> 게터 transfer -> 전송/전환 release -> 릴리스 taker -> 테이커 validate -> validate Sui Move calls -> Sui Move calls |
업데이트
보류
|
|
on chain -> 온 체인 |
이미
|
|
LGTM |
6 participants
Add a precedence note to KEEP_ORIGINALITY.md and TRANSLATED_TERMINOLOGY.md clarifying that KEEP_ORIGINALITY entries take priority. Normalize and tidy the glossary entries (reformatting mappings into a canonical list, reordering and harmonizing terms between the two files) to make it clear which terms must remain untranslated and when translations should be applied.