lotobo/translator-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

feat(translator-tools): add locale review and glossary workflow

Browse Source
This commit is contained in:
zemion
2026-09-02 21:39:02 +02:00
parent 5e962ff0f3
commit 655797c4fe
32 changed files with 2084 additions and 2192 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/PRIVACY-SECURITY.md
+11 -4
View File
@@ -1,9 +1,16 @@
# Privacy and security
Source text, imported files, recipes and results stay in page memory. There is no telemetry, analytics, account, persistence or runtime network path. Imported text is rendered as text/preformatted content, not executable HTML; HTML escaping produces a string and does not preview it as markup.
Locale files and generated outputs stay in-browser and are not uploaded.
Files are rejected above 16 MiB before reading. Decoded/pasted pipeline input is limited to 2,000,000 UTF-16 units, recipe text to 1,000,000 units/100 steps, and output to both 8× the original (with a small-input floor) and 32 MiB. Quoted CSV selection additionally limits rows, columns and field size. Strict inverse stages reject malformed escapes/encodings and invalid UTF-8; they do not attempt permissive repair. These limits reduce accidental expansion but do not prove that output is safe for a downstream interpreter.
No accounts, telemetry or runtime network requests are used for the core workflow.
The app stores glossary terms in local browser storage so they are available on the same
device for repeated reviews.
Compatibility normalisation, case conversion, transliteration, whitespace/line transforms, column selection and narrow encodings can change or lose information. Locale sorting depends on the browser's `Intl.Collator`. The exact source, output, per-step counts and warnings remain visible so users can review those changes before copying or downloading.
Parser/serializer limits are bounded to prevent accidental expansion:
Byte evidence does not guess an encoding or prove the selected decoder is correct. A valid UTF-8 byte sequence may represent text intended for another encoding, zero-byte parity is only a UTF-16 review signal, and replacement characters may already have existed in the source. Artifact evidence hashes canonical UTF-8 source text and exact exported bytes, clearly labels both, and includes filenames and transformation details that may themselves be sensitive.
- Imports and exports are capped at 5 MiB each.
- Large objects are flattened and rendered with per-session bounds.
Suggested translations are purely local matching; they do not call external services.
Transfers to the Portal are signed local handoffs only and never stored by a remote
processor by default.