Skip to content

Fix four IN subdivision names: TS, UK, PY, DH#957

Open
sachinkr7368 wants to merge 1 commit into
countries:masterfrom
sachinkr7368:fix/in-states-english-name
Open

Fix four IN subdivision names: TS, UK, PY, DH#957
sachinkr7368 wants to merge 1 commit into
countries:masterfrom
sachinkr7368:fix/in-states-english-name

Conversation

@sachinkr7368

@sachinkr7368 sachinkr7368 commented May 26, 2026

Copy link
Copy Markdown

Fixes #956.

What

Aligns the top-level name: field for four Indian subdivisions in lib/countries/data/subdivisions/IN.yaml:

 TS:
-  name: तेलंगाना
+  name: Telangana

 UK:
-  name: उत्तराखण्ड
+  name: Uttarakhand

 PY:
-  name: Pondicherry
+  name: Puducherry
   unofficial_names:
   - Pondicherry     # ← historical name preserved here

 DH:
   translations:
-    en: Dādra and Nagar Haveli and Damān and Diu
+    en: Dadra and Nagar Haveli and Daman and Diu
   ...
-  name: Dādra and Nagar Haveli and Damān and Diu
+  name: Dadra and Nagar Haveli and Daman and Diu

Why

  • TS / UK — every other IN state has English in name:; these two had Hindi. Hindi forms already live under translations.hi and are unchanged.
  • PY — official rename from "Pondicherry" to "Puducherry" took effect in 2006 and the gem already carried translations.en: Puducherry. The pre-rename label is kept under unofficial_names so consumers depending on it still get a hit.
  • DH — ISO 3166-2:IN's English short name uses simple ASCII ("Dadra and Nagar Haveli and Daman and Diu"). The macron form is a Hindi-to-Latin transliteration; localised scripts (ar, as, hi, etc.) for this subdivision are untouched and remain available via translations.

Verification

require 'countries'

ISO3166::Country['IN'].subdivisions['TS'].name   # => "Telangana"
ISO3166::Country['IN'].subdivisions['UK'].name   # => "Uttarakhand"
ISO3166::Country['IN'].subdivisions['PY'].name   # => "Puducherry"
ISO3166::Country['IN'].subdivisions['DH'].name   # => "Dadra and Nagar Haveli and Daman and Diu"

# Untouched:
ISO3166::Country['IN'].subdivisions['TS'].translations['hi']   # => "तेलंगाना"
ISO3166::Country['IN'].subdivisions['UK'].translations['hi']   # => "उत्तराखण्ड"
ISO3166::Country['IN'].subdivisions['PY'].unofficial_names     # => ["Pondicherry"]

YAML still parses; all 36 IN subdivisions load.

@pmor

pmor commented May 26, 2026

Copy link
Copy Markdown
Member

Thanks for the PR!

Four Indian subdivisions had a top-level `name:` value that diverged
from the canonical ISO 3166-2 English short name and / or from the
gem's own `translations.en` entry. Aligning all four:

* IN-TS Telangana — `name` was Hindi (तेलंगाना); translations.en already
  carried "Telangana".
* IN-UK Uttarakhand — `name` was Hindi (उत्तराखण्ड); translations.en
  already carried "Uttarakhand".
* IN-PY Puducherry — `name` was the pre-2006 form "Pondicherry" while
  translations.en already carried the post-rename "Puducherry". The
  historical name is preserved under `unofficial_names`.
* IN-DH Dadra and Nagar Haveli and Daman and Diu — `name` and
  translations.en used the macron transliteration ("Dādra…Damān…")
  inconsistent with the ISO 3166-2 OBP English short name, which is
  ASCII. Other locale translations (ar, as, hi, etc.) are unchanged.
@sachinkr7368 sachinkr7368 force-pushed the fix/in-states-english-name branch from 27f09c0 to 32301e5 Compare May 26, 2026 09:25
@sachinkr7368 sachinkr7368 changed the title Use English names for IN-TS (Telangana) and IN-UK (Uttarakhand) Fix four IN subdivision names: TS, UK, PY, DH May 26, 2026
@sachinkr7368

Copy link
Copy Markdown
Author

@pmor please review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Several IN subdivision names have inconsistent top-level name: (TS, UK, PY, DH)

2 participants