Most Urdu encoding headaches come down to one thing: Unicode and InPage are two different systems, and people expect text to move freely between them. It does not, unless you convert. Here is the clear comparison.
How they store text
| Unicode | InPage (classic) | |
|---|---|---|
| Stores | The underlying letter | Fixed glyph shapes |
| Shaping | Done by the font engine | Baked into the encoding |
| Works in | Word, web, phones, PDFs | InPage software |
| Searchable | Yes | No, outside InPage |
| Best for | Digital, sharing, the web | Traditional print layout |
When to use Unicode
Use Unicode for anything digital: websites, social media, Word documents, databases and PDFs. It is universal, searchable and future proof. If you are writing new content, write it in Unicode.
When to use InPage
Use InPage when your final destination is traditional Urdu print and your shop's workflow is built around it, especially for newspapers and books with demanding Nastaleeq layout.
Moving between them
This is where the converter earns its place. Draft in Unicode, then run Unicode to InPage to typeset. Have an old InPage file, then run InPage to Unicode to publish it online. If your text is breaking, the cause is almost always this mismatch, explained fully in why Urdu breaks in InPage.