Shahmukhi U+08C7 Compatibility Lab

A reproducible Punjabi Shahmukhi rendering lab turning a character-support gap into testable evidence and manufacturer outreach.

Visit project

Public reference lab · follow-up ongoingAN INDUSIAN TECHNOLOGIES PROJECT

Indusian Labs Punjabi Shahmukhi U+08C7 compatibility research, with the reference glyph — Shahmukhi U+08C7 Compatibility Lab · Research & learning

From a rendering gap to an engineering conversation

A research and advocacy milestone.

The contribution is a practical bridge: a language community can demonstrate the issue, and a platform team can investigate the same evidence. The original Unicode encoding work predates this lab; Indusian's work focuses on compatibility testing, explanation and escalation.

01 / IDENTIFY

Separate the character from the display.

Correct text can remain intact even when a font cannot display it. The lab explains that distinction without blaming the keyboard by default.

02 / REPRODUCE

Make the evidence portable.

Compare system and reference rendering, inspect the code point and generate a device/app evidence report.

03 / ESCALATE

Bring the gap to engineering teams.

Indusian reports outreach through Google Issue Tracker and Samsung support, alongside email responses from Realme and OPPO.

Outreach and resolution record

Google

Issue 563089596 ↗
Issue reference supplied by Indusian; current tracker status not independently verified.

Samsung

Support case reported by Indusian. The account-specific ticket is not published here; no fix or release date is asserted.

Realme & OPPO

Indusian reports email responses indicating that the issue will be addressed. These are reported intentions, not verified software releases.

Next verification

Confirm device model, OS build, application and font behavior after a released update. A committed response and a verified fix are recorded separately.

Why the distinction matters

U+08C7 is ARABIC LETTER LAM WITH SMALL ARABIC LETTER TAH ABOVE, documented for Punjabi in the Unicode encoding proposal. A bundled reference font can demonstrate a compatible rendering path; it does not change another app's fonts or install a system-wide fix.

Unicode proposal · L2/19-111R ↗

01 / The problem

A clear need.

A correctly entered Punjabi Shahmukhi character can still appear as a missing-glyph box when a device or application lacks suitable font coverage. For the person writing, the distinction between an input error and a rendering limitation is rarely visible.

02 / The approach

A useful response.

Indusian Labs built a public comparison between system rendering and a compatible reference font, a Unicode code-point inspector and an evidence-report generator. The work gives language users and engineering teams a shared, reproducible way to identify the gap and discuss remediation.

03 / Inside the project

What it brings together.

A controlled comparison

Render the same character through the system font and a bundled compatible reference font.

Code-point inspection

Check whether the underlying text contains U+08C7 independently of its visible glyph.

Reproducible reporting

Capture device, application and rendering observations in a structured evidence report.

Standards-led outreach

Connect the observed rendering issue to Unicode references and platform or manufacturer follow-up.

U+08C7Character under investigation

2Rendering paths compared

OpenDevice-level resolution remains under follow-up

Project record · reviewed 9 October 2026

Technical scope is documented in the supplied public lab. Google Issue Tracker reference and Samsung outreach were supplied by Indusian Technologies. The company reports email responses from Realme and OPPO indicating intent to address the issue; those private emails and a shipped device fix have not been independently verified for this case study. Status recorded 9 October 2026.

Open the reference lab Google Issue Tracker reference Read the Unicode encoding proposal

Keep exploring