Assamese
অসমীয়া
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open translation handoff →INDIA-AFRICA C0-001 · INDIA · 2026-11-20
One shared blueprint, more local entry points.
Four new written editions, a reused Tamil edition and an English operational reference. The full scheduled-language baseline remains visible so translation and acceptance can continue in the same register.
This is the Constitution’s Eighth Schedule baseline. It does not make all 22 languages interchangeable official languages for every Union, state, local or business document.
First wave: Hindi, Bengali, Marathi and Telugu. Tamil is reused. The remaining 17 scheduled languages have blank translation handoffs.
অসমীয়া
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open translation handoff →বাংলা
India-oriented written draft. Bangladesh or other jurisdictional adaptation is separate.
Open review edition →बड़ो
Confirm community terminology and preferred written scope.
Open translation handoff →डोगरी
Confirm script and regional scope before production.
Open translation handoff →ગુજરાતી
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open translation handoff →हिन्दी
Union official-language constitutional reference does not replace state or document requirements.
Open review edition →ಕನ್ನಡ
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open translation handoff →Choose script and readership explicitly; do not merge scripts into one completed edition.
Open translation handoff →Macrolanguage and script scope need competent local agreement.
Open translation handoff →मैथिली
Confirm script for this delivery; heritage scripts are not automatically covered.
Open translation handoff →മലയാളം
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open translation handoff →Agree Meitei Mayek and/or Bengali-script deliverables explicitly.
Open translation handoff →मराठी
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open review edition →नेपाली
India scheduled-language scope; no assertion of a completed Nepal market annex.
Open translation handoff →ଓଡ଼ିଆ
The modern constitutional name is Odia; preserve the established language code or.
Open translation handoff →ਪੰਜਾਬੀ
India-oriented Gurmukhi scope requires agreement; no Shahmukhi coverage implied.
Open translation handoff →संस्कृतम्
Agree technical register and script; no claim of every regional script.
Open translation handoff →Confirm script and community; constitutional named-language coverage is not every written tradition.
Open translation handoff →Two script traditions require separate target decisions.
Open translation handoff →தமிழ்
Reuse the existing shared Tamil edition. India-specific terms and business documents still need review.
Open existing edition →తెలుగు
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open review edition →اردو
Confirm typeface, ligatures, bidirectional layout and local terminology.
Open translation handoff →English
Existing operational reference. Continued Union English use is addressed by statute; English is not an Eighth Schedule language.
Open existing edition →Confirm the variety, script and intended readers. Work against the frozen 149-key source and record terminology decisions.
A qualified independent reviewer checks the exact translation. Layout checks preserve the text, fonts, A3/A4 relationship, QR address and NFC payload.
Publish the stated review status. Record who accepted which version and for which use. Local business applicability is determined for the actual transaction.
Language availability supports participation. Country rules, professional review, physical printing and NFC write/read acceptance have their own evidence.
Bring a capability. Help deliver a real outcome.
QR encodes the address shown here.
URL → QR → COPY → PRINT → NFC
QR and URL are ready. NFC writing starts only when you choose it.
Write this URL as an NDEF URI record, then tap the tag independently to verify it. Sharing an address does not grant execution authority.