---
name: word-farsi-docx
description: Build a clean, editable Persian (Farsi) Word .docx in B Nazanin from a report, PDF or TeX source with python-docx. Use for Persian Word output, RTL or font problems in .docx, or converting a Persian report to Word.
title: word-farsi-docx
canonical_url: https://skilld.dev/gh/masihmoafi/skills/word-farsi-docx
last_updated: 2026-11-03T09:01:25.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [perfect-farsi-word.docx](https://skilld.dev/api/skills-raw/masihmoafi/skills/word-farsi-docx/perfect-farsi-word.docx).
>
> If the user asked to install this Skill, run `npx skilld install masihmoafi/skills/word-farsi-docx`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/word-farsi-docx`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/masihmoafi/skills/word-farsi-docx) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/word-farsi-docx`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/word-farsi-docx --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/word-farsi-docx --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Persian Word documents

Produce a Word-native, RTL-correct Persian `.docx` in B Nazanin that keeps a clean academic layout.

## Goal

- Real Word objects (paragraphs, tables, images), not PDF pages pasted into Word.
- The template's margins, spacing and headings preserved.
- RTL punctuation and alignment correct.
- B Nazanin everywhere, including English inside Persian text.
- Tables, bullets, headings, page breaks and images supported.

## Tools

- `python-docx` for generation and styling.
- Optionally, PDF text extraction or page images as a reference; rebuild the content as Word objects.
- For validation, render the final document with a Word-compatible renderer and compare its pages with the reference. If no renderer is available, report the visual check as incomplete.

## Steps

1. Start from the bundled template `perfect-farsi-word.docx` in this skill's folder, which already has the right margins, spacing and headings, because styling Word from scratch is fragile.
2. Clear the body but keep `w:sectPr`, which holds page size, margins and layout; deleting it changes the page geometry.
3. Set every paragraph to right alignment and add `w:bidi = 1`, since Persian can look right while punctuation, numbering and Latin tokens behave wrongly without the RTL flag.
4. Set B Nazanin on every run in all four `w:rFonts` channels (`w:ascii`, `w:hAnsi`, `w:cs`, `w:eastAsia`) and in `run.font.name`, because mixed-script runs fall back to other fonts unless all channels are set.
5. Rebuild the content as Word structures: headings, normal paragraphs, bullet and numbered lists, `Table Grid` tables and captioned images, so the document stays editable and its layout consistent.
6. Set `w:spacing` explicitly on key paragraphs and headings (for example `after = 120`), since Word's defaults inflate spacing around Persian text.
7. Build tables with `doc.add_table`, bold the header row and apply RTL and B Nazanin to every cell paragraph and run, because tables show direction and font bugs first.
8. Insert `doc.add_page_break()` after the cover, after the abstract and between major sections so Word does not reflow them unpredictably.
9. After all content is added, walk every paragraph and run and reapply RTL and B Nazanin, keeping centred cover paragraphs centred, because some operations add runs with default fonts or drop the bidi flag.
10. If the client cannot download Persian filenames, also save an ASCII-named copy and optionally a `.zip`.

## Quality checklist

- Persian punctuation (، ؛ ؟) is correct and stays RTL.
- English terms sit in parentheses and do not break the sentence flow.
- No empty placeholder squares.
- Headings are bold and consistently sized.
- Bullets align correctly in RTL.
- Tables are readable, aligned and do not overflow.
- Images are undistorted and captioned.
- Page breaks fall where intended.

## Failures and fixes

| Symptom | Fix |
| :--- | :--- |
| Wrong font | Set `w:rFonts` in all four channels |
| RTL looks right but punctuation is wrong | Add `w:bidi = 1` to the paragraph properties |
| Layout changed after editing | `sectPr` was removed; keep it |
| Download fails | Save an ASCII-named copy or zip it |
