Running an Urdu-medium school on software that actually speaks Urdu
Almost every school ERP sold in India will tell you it supports Urdu. Very few can print a report card an Urdu-medium parent can read. The difference is not a feature list — it is typography, and it shows up on the day you hand out results.
7 min read
Interface Urdu and document Urdu are different problems
When a vendor says "we support Urdu", they usually mean the menus can be translated. That is the easy half. The screen is a web page, the browser has Urdu fonts, and right-to-left text is something browsers have handled well for years.
The hard half is the paper. Report cards, fee receipts, transfer certificates, ID cards and notices are generated as PDFs, and a PDF does not borrow fonts from the browser — the font has to be embedded in the file by whatever generated it. If nobody did that work, one of three things happens: the Urdu comes out as empty boxes, or it comes out as disconnected letters that technically spell the word but read as nonsense, or the system quietly falls back to English.
That third failure is the one that survives a demo. Everything looks fine on screen, you sign, and then in March the report cards print in English for a school where half the parents read Urdu more comfortably than English.
Why Urdu breaks when Hindi and Marathi do not
Urdu is written in the Nastaliq style, which is cursive and slopes downward. Letters change shape depending on what sits either side of them, and words stack diagonally rather than sitting on a flat baseline. A rendering engine that just places one glyph after another produces something that looks like Urdu letters scattered on a line.
Devanagari — Hindi and Marathi — is far more forgiving. Letters join, but the line is flat and the shaping rules are simpler. So a vendor can get Marathi looking correct with very little effort and reasonably assume Urdu will follow. It does not.
This is why asking "do you support Urdu?" gets you a yes that means nothing. The useful question is narrower.
The four things to ask for in a demo
Do not accept a screenshot for any of these. Ask for the actual file, and open it yourself.
- A generated report-card PDF with a real pupil name in Urdu script — not typed into a design mockup, but produced by the system from its own records. Check that the name reads as joined words, not separated letters.
- A fee receipt in Urdu, because receipts are the document parents keep and bring back when there is a dispute.
- A pupil whose name is in Urdu and whose class and marks are in English on the same page. Mixed direction on one line is where most implementations fall apart.
- The same PDF opened on a phone. Parents read almost everything on a phone, and some PDF viewers substitute fonts more aggressively than a desktop reader does.
What else an Urdu-medium school needs beyond the script
Script is the part vendors fail at, but it is not the whole job. A few things matter just as much and are easier to check.
Names need to exist twice. An Urdu-medium school in Maharashtra files U-DISE returns and board paperwork in English or Marathi, and sends report cards home in Urdu. If the system stores one spelling of a pupil's name, somebody maintains the second one in a spreadsheet forever. The record should hold both, and each document should pull the right one without anyone choosing.
The parent-facing side has to be the Urdu side. Fee reminders, attendance messages and notices are read by parents, so those are exactly where Urdu matters most — and exactly where systems default to English because the message templates were written once, in English, by the vendor.
Staff should not have to switch languages to do their job. An office clerk who is faster in Urdu should not be forced through an English-only admissions form, and a teacher entering marks should not have to.
Where Xavellus stands on this
We built Urdu document rendering because a school we run is Urdu-medium and needed it, not because it tested well as a feature. Report cards, fee receipts, marksheets, ID cards, submission cards and notices are generated with an embedded Nastaliq font, so the Urdu in a printed document is the same Urdu you see on screen.
The interface is translated too, not only the documents — staff and parent screens both, with right-to-left layout rather than Urdu text poured into a left-to-right page. Pupil records hold an English name and an Urdu name, and documents pull whichever suits the audience: board and government paperwork in English, parent-facing documents in Urdu. Notice and message templates are editable per school in either script.
The limitation worth stating, since this guide has spent several hundred words telling you to distrust vendors who skip it: our Devanagari document rendering is not at the same standard. Urdu has an embedded Nastaliq font; Marathi and Hindi do not yet have an embedded Devanagari one, so a Marathi-medium school gets English documents today. If you are Urdu-medium, we are unusually well suited to you. If you are Marathi-medium, ask us where that work has got to before you sign anything.
Keep reading
