Malaysian and bilingual authors often need English chapters with Malay abstracts — or full EN↔MS thesis pairs. Lattuce links Writer (authoring) to a collaborative translation editor (translators) so segments, translation memory, and review stay on lattuce.app.

EN↔MS is the documented example pair in this guide; the same workflow applies to other locale pairs your project configures.

Audience split

Translators do not need to learn the full Writer UI — they work in the translation editor. Authors stay in Writer.

Workflow overview

1. Author drafts the chapter in Writer (Compose → Write → approve sections).
2. Author opens Translate mode and syncs segments to the translation project.
3. Translator fills segments in the editor; TM and AI suggestions assist — human approves final text.
4. Author reviews imported segments; exports MS Word (or EN Word) when ready.

Cold path (first-time setup): link personal translation account in settings — see Collaborative translation on Lattuce.

Prepare the chapter for translation

1. Finish the English chapter through section approval in Writer.
2. Export or sync to translation by section — headings and paragraphs become segments.
3. Lock glossary terms (lab names, method labels) before translators start — reduces inconsistent TM matches.

For faculty-specific formatting after translation, run Format mode on the exported .docx — Thesis format check.

Translation project setup

1. Author: Account settings → Translation — connect your translation account.
2. Open the paper → Translate mode → create or link a project for this chapter.
3. Choose target locale (e.g. ms for Malay).
4. Sync segments from approved Writer sections.

Translators receive access to the project — not your full household vault.

Review and approve segments

AI machinery may propose suggestions — translators control the final string. Do not auto-accept without reading.

Import back to Writer

1. When translation review is complete, import segments into Translate mode.
2. Author reads the bilingual chapter beside the EN source.
3. Approve translated sections the same way as English — citation checks apply to whichever locale cites library sources.
4. Export to Word for faculty submission.

EN↔MS as example pair

Malaysia’s BM/BI thesis culture is why we document EN↔MS first:

Other pairs (EN↔AR, EN↔ZH) use the same segment workflow — locale labels change; roles do not.

Related reading

• Collaborative translation on Lattuce
• Bilingual journal abstracts
• Multilingual research lab

Bahasa Melayu: Terjemah bab tesis EN↔MS dengan terjemahan kolaboratif di Lattuce

Malaysian and bilingual authors often need English chapters with Malay abstracts — or full EN↔MS thesis pairs. Lattuce links Writer (authoring) to a collaborative translation editor (translators) so segments, translation memory, and review stay on lattuce.app.

EN↔MS is the documented example pair in this guide; the same workflow applies to other locale pairs your project configures.

Audience split

Translators do not need to learn the full Writer UI — they work in the translation editor. Authors stay in Writer.

Workflow overview

1. Author drafts the chapter in Writer (Compose → Write → approve sections).
2. Author opens Translate mode and syncs segments to the translation project.
3. Translator fills segments in the editor; TM and AI suggestions assist — human approves final text.
4. Author reviews imported segments; exports MS Word (or EN Word) when ready.

Cold path (first-time setup): link personal translation account in settings — see Collaborative translation on Lattuce.

Prepare the chapter for translation

1. Finish the English chapter through section approval in Writer.
2. Export or sync to translation by section — headings and paragraphs become segments.
3. Lock glossary terms (lab names, method labels) before translators start — reduces inconsistent TM matches.

For faculty-specific formatting after translation, run Format mode on the exported .docx — Thesis format check.

Translation project setup

1. Author: Account settings → Translation — connect your translation account.
2. Open the paper → Translate mode → create or link a project for this chapter.
3. Choose target locale (e.g. ms for Malay).
4. Sync segments from approved Writer sections.

Translators receive access to the project — not your full household vault.

Review and approve segments

AI machinery may propose suggestions — translators control the final string. Do not auto-accept without reading.

Import back to Writer

1. When translation review is complete, import segments into Translate mode.
2. Author reads the bilingual chapter beside the EN source.
3. Approve translated sections the same way as English — citation checks apply to whichever locale cites library sources.
4. Export to Word for faculty submission.

EN↔MS as example pair

Malaysia’s BM/BI thesis culture is why we document EN↔MS first:

Other pairs (EN↔AR, EN↔ZH) use the same segment workflow — locale labels change; roles do not.

Related reading

• Collaborative translation on Lattuce
• Bilingual journal abstracts
• Multilingual research lab

Bahasa Melayu: Terjemah bab tesis EN↔MS dengan terjemahan kolaboratif di Lattuce