Assamese
অসমীয়া
Eighth Schedule named-language baseline. State, territory, community and document-specific applicability remains separate.
Open translation handoff →INDIA-AFRICA C0-001 · SCOPE · 2026-11-20
A visible route from translation to accepted use.
Each profile identifies what exists, what remains untranslated, which variety or script requires agreement, and which professional decision remains open.
The English entry is intentionally linked in both India and Africa. This count includes completed AI drafts, existing editions, blank handoffs and retained scope tasks. It is not a count of new translations.
অসমীয়া
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 →Kiswahili
Shared standard written draft. Country and sector terminology still require local acceptance.
Open review edition →Hausa
This release uses Latin/Boko. Ajami is a separate script work item. Section 55 is a parliamentary-use provision.
Open review edition →Yorùbá
Preserve tone marks and underdots. Country or community variants require separate review.
Open review edition →አማርኛ
Federal constitutional working-language baseline, not Ethiopia’s only recognized language. Later administrative policies remain to be checked.
Open review edition →Igbo
Section 55 uses the spelling Ibo. Agree contemporary technical terminology and orthography.
Open translation handoff →Soomaali
Candidate local-language production scope. Country, community and regulatory language status not yet researched.
Open translation handoff →Afaan Oromoo
Agree Oromo variety, technical terminology and intended place of use. No nationwide legal claim.
Open translation handoff →ትግርኛ
Agree community and country terminology. Eritrean and Ethiopian uses are not one legal market record.
Open translation handoff →Wolof
Agree orthography and scope before translation. Ajami is not silently included.
Open translation handoff →Lingála
Agree country, standard and diacritics; no automatic legal applicability across borders.
Open translation handoff →Malagasy
Macrolanguage/standard choice requires agreement before target production.
Open translation handoff →Ikinyarwanda
Candidate local-language edition; national and document applicability research remains open.
Open translation handoff →Afrikaans
Reuse the existing registered task identity; target text remains untranslated.
Open translation handoff →isiZulu
Reuse the existing registered task identity; target text remains untranslated.
Open translation handoff →isiXhosa
Reuse the existing registered task identity; target text remains untranslated.
Open translation handoff →isiNdebele
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →siSwati
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →Sepedi
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →Setswana
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →Sesotho
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →Xitsonga
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →Tshivenda
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →South African Sign Language
Retained from the existing South Africa extension register. No new text or signed-media translation is claimed.
View retained scope tasks →العربية
Existing shared edition linked as an institutional entry. National legal use and local business documents require their own scope decision.
Open existing edition →English
Existing shared edition linked as an institutional entry. National legal use and local business documents require their own scope decision.
Open existing edition →Français
Existing shared edition linked as an institutional entry. National legal use and local business documents require their own scope decision.
Open existing edition →Português
Existing shared edition linked as an institutional entry. National legal use and local business documents require their own scope decision.
Open existing edition →Español
Existing shared edition linked as an institutional entry. National legal use and local business documents require their own scope decision.
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.
Full official PDF retrieved. The Eighth Schedule lists 22 named languages. Article 343 specifies Hindi in Devanagari for the Union. Scheduled status is not a blanket nationwide official-use rule.
Official search index returned section 3 text on continued English use in addition to Hindi. Direct PDF fetch returned 404; the IndiaCode official record is an additional lookup route.
AU institutional language page lists Arabic, English, French, Portuguese, Spanish, Kiswahili and other African languages. This is an institutional entry baseline, not a list of every member state language or a ratification opinion.
Kiswahili is national; Kiswahili and English are official. Indigenous languages, Kenyan Sign Language and accessible formats are separately protected.
EAC identifies Kiswahili and English as official languages. This descriptive source does not settle document-specific legal requirements in Mainland Tanzania or Zanzibar.
Official indexed policy describes Kiswahili and English and addresses sign, tactile and Braille communication. Used as supporting evidence only.
National Assembly business uses English; Hausa, Ibo and Yoruba are provided for when adequate arrangements exist. This is not a blanket claim that the three are nationwide co-official for every document.
Official index returned Article 5: equal recognition for Ethiopian languages; Amharic as federal working language; member states determine their own working languages. Direct PDF fetch timed out. Current administrative language policies and regional use require local verification.
Official catalogue confirms the Constitution entry and supplies a download route. No claim that this catalogue verifies all later federal working-language policy.
Retain the eleven prior local extension/media records, including South African Sign Language. Signing and media production remain separate from written translations. Commencement and operational duties must be confirmed for the transaction.
Exact primary-source snapshot reused from preceding MERCOSUR release. All 50 campaign locale/media identifiers are registered language subtags. Base-language registration does not establish agreement on script, variety or local applicability.
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.