Puljen med eksakte matches deles, med en projektvis kontakt.
Hvad en post i puljen indeholder
- +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.
Hvad der fjernes først
- -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.
Nødafbryderen
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.
Kildestrengen og dens oversættelse kan genbruges på tværs af arbejdsområder (det er formålet med en delt hukommelse), men ingen post nævner en person eller et team, og puljen eksponeres aldrig som en gennemsøgelig samling.
En gennemgået post er den, der bærer et arbejdsområdes-id, og den gør det for at kunne isoleres: søgning efter næsten ens matcher filtrerer på dette id, så det, dine anmeldere godkender, kun tilbydes tilbage til dig. Genbrug af eksakte matches, den reelt delte del, har slet ingen ejer.