what_you_need
Prepare the inputs before opening the apps
- A frozen source-language folder
- Target languages and locales
- A glossary of names and fixed terms
- A native or qualified reviewer for each public language
step_by_step
The working process
-
1
Freeze the source edition
Correct and approve the source documents first. Assign a version or date so every translation can be traced back to the same text.
-
2
Create the terminology rules
List product names, people, places, phrases that should not be translated, and preferred terminology. Locale matters: the same language can differ by market.
-
3
Run a small translation sample
Use Batch Translate Text with any AI on representative files before processing the full set. Evaluate tone, formatting, names, headings, and repeated terminology.
-
4
Translate into separated folders
Run the approved configuration for each target language and keep output directories clearly labelled by language and source version.
-
5
Use human language review
Have a capable reviewer correct meaning, tone, cultural fit, and layout. Back-translation can surface problems but does not replace a native review.
-
6
Publish as distinct editions
Keep canonical source links and language labels clear. When the source changes, update translations deliberately rather than silently drifting out of sync.
human_checkpoint
Review before you call it finished
- Is every translation tied to one approved source version?
- Are names and product terms consistent?
- Did a qualified person review public-facing output?
- Are language and locale labels correct?
honest_boundaries
Limits and privacy
Practical limitation
AI translation can miss context, idiom, legal meaning, and culturally sensitive nuance. High-stakes material requires qualified professional review.
Privacy boundary
Documents are sent to the AI provider selected in Batch Translate Text with any AI. The translated files are saved locally and are not stored by a separate 3thousand30 service.
faq
Questions worth answering
Can I publish without a human reviewer?
For public work, that is risky. At minimum, have a fluent reviewer check meaning, terminology, tone, and formatting.