OmniDocTable of Contents in Arabic and Malay Word Files
Build a table of contents in Arabic or Malay Word files, including right-to-left layout, heading styles, and the checks to run after translating.
If you need a table of content in Arabic or Malay, the English-language guides usually leave out the parts that matter most. Arabic runs right to left, so the dot leaders, page numbers, and indentation can end up in the wrong place. Malay uses the Latin alphabet, but it still needs its own language setting and a title that readers will recognize. This guide covers both cases for Word (.docx) files.
The short version is that you build the contents list from heading styles, set the language and text direction for each section, and then regenerate the list in the final file. If you translate the document with OmniDoc, you do the regeneration step on the translated output, not the original. The steps below walk through that workflow from start to finish.
How do you build a table of content in Arabic or Malay? The short answer
Use your word processor's automatic contents feature, set the right language and direction on each section, and rebuild the list after any translation or edit. Here is how the main situations break down.
| Your situation | What to do | Why |
|---|---|---|
| Arabic text only | Set the Arabic paragraphs to right-to-left and the language to Arabic before you insert or update the list | Direction controls where page numbers and leader dots sit |
| Malay text only | Set the language to Malay (Bahasa Melayu) and write the title as "Kandungan" or "Senarai Kandungan" | Spelling checks and hyphenation follow the language setting |
| Mixed Arabic and English | Set direction per paragraph, not for the whole file, and keep the English headings left to right | Each heading keeps the direction of its own language |
| Translating an English report into Arabic or Malay | Insert the contents list in the source, translate, then regenerate it in the output | Translated headings and page counts differ from the original |
| Editing a translated file in a browser | Open the file in the UniDoc web editor at app.unidoc.top, then check the list there | The web editor supports Word-compatible editing for the same file |
Before you start
Check these items before you build the list. Each one prevents a problem that is hard to spot later.
- Heading styles on every section title. An automatic contents list reads heading styles. Bold text that looks like a heading will not appear in the list, and you will have to fix it section by section later.
- The language each section is written in. Mixed-language files need the right language set on each part. Otherwise spell checking and line breaking can flag or split correct words.
- A font with Arabic characters. Some fonts display Latin letters but leave Arabic glyphs blank or substitute them. Confirm the font shows Arabic correctly on your screen before you print or export.
- The target page layout. Right-to-left pages often need their margins and tab stops reviewed. Decide whether the document will be read on screen or printed, because that changes how much room the page numbers need.
- A plan for machine translation review. If you translate the file, plan time to read the headings and key terms yourself. Automated translation can get technical or legal terms wrong, so check anything important before you share the file.
Building a table of content in Arabic or Malay, step by step
- Apply heading styles to the source document. Mark every chapter and section title with the built-in heading styles, using the level that matches its place in the outline. The contents list is built from these styles, so this step controls what appears in it.
- Insert the automatic contents list in the source file. Place the cursor where the list should go, usually after the title page, and use your word processor's built-in contents feature. Doing this in the source file gives you a working list to compare against after translation.
- Translate the file in OmniDoc. Upload the .docx file on omnidoc.top, choose bilingual or translation-only output, and download the result. OmniDoc keeps the layout, tables, and pictures, so the structure of the file carries over to the output.
- Open the translated file and set the language. Select the Arabic sections and set their language to Arabic. For Malay sections, set the language to Malay (Bahasa Melayu). This makes spelling checks and line breaking work correctly for each part of the document.
- Set Arabic paragraphs to right-to-left. Select each Arabic paragraph and change its text direction to right-to-left. This moves the paragraph alignment and the order of the words and punctuation to match Arabic reading order.
- Write the contents heading in the target language. For Arabic, use فهرس المحتويات. For Malay, use "Kandungan" or "Senarai Kandungan". Apply a heading style that does not appear in the list itself, so the title is not listed as an entry.
- Update the contents list. Automatic lists do not refresh on their own after a change. Use the update option for the whole list so that the headings, page numbers, and direction all match the translated text.
- Review the headings and page numbers. Read through the list once, then jump to two or three headings to confirm the page numbers point to the right place. If you edit a heading later, update the list again.
If you prefer to make these changes in a browser, the UniDoc web editor at app.unidoc.top supports Word-compatible editing and can be used for the same file.
Check the result
Run these checks on the final file, not the original, because translation changes both the text and the layout.
| Check | How to see it | If it's wrong |
|---|---|---|
| All headings are listed | Scroll the body and compare each section title with the list | Apply the heading style to the missing title, then update the list |
| Page numbers match | Click a listed heading and confirm it sits on the page the list shows | Update the list again, and check for manual page breaks |
| Arabic direction is correct | Confirm the dot leaders run toward the page number and the numbers sit on the left side of each line | Set the paragraph to right-to-left, then check the tab stops |
| Digits look consistent | Compare the numerals in the list with numerals in the body text | Check the number setting in the document's language options so both areas match |
| Translated headings read naturally | Read each heading against the source and check key terms | Edit the heading text by hand, then update the list |
❓ FAQ
1. Why do the dots and page numbers look wrong in an Arabic contents list?
Arabic paragraphs are usually set left to right by default. Switch each Arabic paragraph to right-to-left, then update the list. The dot leaders and page numbers should follow the new direction.
2. Does a Malay contents list need any special direction setting?
No. Malay uses the Latin alphabet and reads left to right, so the default direction works. The main setting to change is the document language, which controls spelling and hyphenation.
3. Will a translated Word file keep its existing contents list?
Layout is kept in translation, but the headings and page numbers change, so the old list may not match. Regenerate the list in the translated file to be sure it points to the right places.
4. Which font should I use for Arabic headings?
Pick a font that includes Arabic characters and check how it displays on your screen before you print or export. If a character looks blank or shows a substitute glyph, switch to another font that supports Arabic.
5. Do I need OmniDoc to build a contents list?
No. The contents list is created in your word processor from heading styles. OmniDoc is useful for translating the document, after which you rebuild the list in the output.
📝 Summary
A table of content in Arabic or Malay works well when you build it from heading styles, set the language and direction for each section, and regenerate it after translation. Arabic needs right-to-left settings to keep page numbers and leader dots in the right place. Malay mainly needs the correct language setting and a clear title.
