What the name describes

In a 2008 research paper, Gurpreet Singh Lehal and colleagues describe Shahmukhi as a local form of Urdu-script writing used for Punjabi, based on a right-to-left Perso-Arabic tradition. The important distinction is between the language being recorded and the writing system used to record it: this page concerns Punjabi text.[1]

Their comparison presents Gurmukhi and Shahmukhi as different written routes into Punjabi. Knowing one script does not automatically make the other readable.[1]

Why context matters

The paper explains that Shahmukhi is commonly written without short-vowel marks, creating ambiguity that readers resolve through context. It also discusses cases where one written form has multiple possible mappings into Gurmukhi. These are reasons to preserve a full phrase or sentence when asking about a word, rather than cropping away its surroundings.[1]

A later COLING demonstration paper separates two technical operations: identifying legacy Gurmukhi font encodings and transliterating the resulting Unicode text into Shahmukhi. This distinction is useful beyond software. Correcting a corrupted digital encoding, changing the script and translating a passage’s meaning are different tasks and should be recorded separately in research notes.[2]

Use conversion as an aid

The COLING authors report measured performance for a particular system and test material, rather than promising error-free conversion of every Punjabi document. A percentage in a research paper is not a certificate for a new family letter, damaged scan or unusual name. Keep machine output provisional until it has been checked against the source.[2]

For your own reading, keep the original image, a transcription, any transliteration and an English explanation in separate fields. Label uncertain readings. This is an editorial workflow inferred from the conversion problems discussed in the two papers. The first script lessons now offer source-checked character exercises. Independent human language review has not been performed.[2]

Sources & notes

Source records include access dates and, where known, limits on what was examined. Checks used AI assistance; independent human or specialist review has not been completed.

  1. Tejinder Singh Saini, Gurpreet Singh Lehal and Virinder S. Kalra. Shahmukhi to Gurmukhi Transliteration System ↗research paper · Source date: 2008-08 · Locator: Conference proceedings title page: COLING 2008 companion, pp. 177–180, Manchester, August 2008; script descriptions, sections 1.1–1.2 and 3.1–3.2. Accessed 2026-11-04.Inspected script descriptions, direction and ambiguity discussion; did not reuse dated speaker counts.Return to What the name describes, paragraph 1 ↑Return to What the name describes, paragraph 2 ↑Return to Why context matters, paragraph 1 ↑
  2. Gurpreet Singh Lehal, Tejinder Singh Saini and Savleen Kaur Chowdhary. An Omni-font Gurmukhi to Shahmukhi Transliteration System ↗research paper · Source date: 2012-12 · Locator: Proceedings of COLING 2012: Demonstration Papers, pp. 313–320; pp. 313–315, abstract, introduction and font conversion. Accessed 2026-11-04.Inspected the demonstration paper; performance claims remain tied to the authors’ tests. ACL Anthology confirms the three authors, December 2012 proceedings and page range: https://aclanthology.org/C12-3039/.Return to Why context matters, paragraph 2 ↑Return to Use conversion as an aid, paragraph 1 ↑Return to Use conversion as an aid, paragraph 2 ↑
Help improve this entry. Suggest a correction with a source. · Read recorded changes
Record PH-LAN-0004 · English edition · human review not performed