एक्सैक्ट-मैच पूल साझा किया जाता है, प्रति-प्रोजेक्ट स्विच के साथ।
पूल्ड एंट्री में क्या होता है
- +The source string and its translation (the linguistic pair only), keyed by a hash of the source.
- +Plural forms, where the string is pluralized.
- +Aggregate reuse counters (how often an entry was reused) for savings analytics.
सबसे पहले क्या हटाया जाता है
- -Any link to the person or the team behind an entry. There is no user column and no team column, so nothing in the pool can be traced back to who wrote it.
- -The workspace and project behind an exact-match entry: the pooled pair is written with no owner at all. A reviewed entry is the one exception, and there the workspace id is a fence rather than a label. Near-match (semantic) lookup filters on it, which is exactly what stops a reviewed entry from ever being returned to another workspace.
- -The translation key name, file path, screenshots, comments, and every other piece of surrounding context.
- -Request bodies: metering records token counts for billing, never the content of a request.
किल स्विच
Turning off "Translation memory" on a project stops it from both contributing to and drawing on the shared memory. The kill-switch is per project and available on every plan.
स्रोत स्ट्रिंग और इसके अनुवाद का पुनः उपयोग वर्कस्पेस across किया जा सकता है (साझा मेमोरी का उद्देश्य यही पुनः उपयोग है), लेकिन कोई भी एंट्री किसी व्यक्ति या टीम का नाम नहीं लेती, और पूल को कभी भी ब्राउज़ करने योग्य कॉर्पस के रूप मेंExposed नहीं किया जाता।
A reviewed entry is the one that carries a workspace id, and it carries one so that it can be fenced in: near-match lookup filters on that id, so what your reviewers approve is only ever offered back to you. Exact-match reuse, the genuinely shared part, carries no owner at all.