Making a Biodata in Hindi, Telugu, Tamil, Marathi or Gujarati

VivahAI Editorial · 10 August 2026 · 6 min read

A biodata in the family's own language is read more carefully than one in English. It is also the version most likely to arrive as a page of little rectangles, because of a technical problem almost nobody is warned about.

Which language to use

Write for the person who will read it, not for the person who wrote it. In practice that usually means:

The regional language when the biodata goes to family elders, a local matrimonial bureau, or a community network.
English when it goes to a matrimonial site, an NRI match, or anyone under about thirty-five in a metro.
Both when you can. A bilingual page — regional labels with English values, or two versions of the same file — covers every reader without asking anyone to struggle.

Standard field labels

These are the conventional labels. Using the expected wording matters more than a technically precise translation — a reader scanning for their usual label should find it where they expect.

English	हिन्दी	मराठी	ગુજરાતી	తెలుగు	தமிழ்
Name	नाम	नाव	નામ	పేరు	பெயர்
Date of Birth	जन्म तिथि	जन्मतारीख	જન્મ તારીખ	పుట్టిన తేదీ	பிறந்த தேதி
Place of Birth	जन्म स्थान	जन्मस्थळ	જન્મ સ્થળ	పుట్టిన స్థలం	பிறந்த இடம்
Height	ऊँचाई	उंची	ઊંચાઈ	ఎత్తు	உயரம்
Education	शिक्षा	शिक्षण	શિક્ષણ	విద్య	கல்வி
Occupation	व्यवसाय	व्यवसाय	વ્યવસાય	వృత్తి	தொழில்
Father's Name	पिता का नाम	वडिलांचे नाव	પિતાનું નામ	తండ్రి పేరు	தந்தை பெயர்
Mother's Name	माता का नाम	आईचे नाव	માતાનું નામ	తల్లి పేరు	தாய் பெயர்
Contact	संपर्क	संपर्क	સંપર્ક	సంప్రదింపు	தொடர்பு

The empty-boxes problem

This is the failure worth understanding, because it is invisible to the person sending the file. Indian scripts are complex: characters combine into conjuncts and vowel marks reposition around consonants. Rendering them correctly requires both the right font and shaping support in whatever produced the file.

When either is missing, the result is one of three things — empty rectangles (□□□□), the correct letters in the wrong order, or vowel marks detached and floating beside their consonant. On the machine that made the file everything looks perfect, because that machine has the fonts installed. The recipient's phone does not.

Export the file, then open it on a different device — ideally a phone that is not yours.
Check the conjuncts specifically: क्ष, त्र, ज्ञ in Devanagari, க்ஷ in Tamil, క్ష in Telugu. These break first.
Check that vowel marks sit on the right consonant, particularly the ि in Devanagari, which is written before the consonant it follows.
If anything looks wrong, do not send it. A biodata full of boxes reads as carelessness about the reader's language.

This is why VivahAI renders exports through a browser engine with the Indic fonts embedded rather than a simple PDF writer — it is the only reliable way to get conjuncts right in a file that has to open on somebody else's phone.

Translating well

Translate the labels and the prose. Leave names, institutions and company names alone — an IIT is an IIT in every language.
Don't translate a job title into something nobody uses. "Software Engineer" is read as-is by nearly everyone; a laboured regional equivalent is not.
Keep numbers in the numerals your reader expects. Devanagari numerals look handsome and get misread.
Have one native speaker read it. Machine translation gets the words right and the register wrong, and a biodata in the wrong register reads as odd without the reader being able to say why.