[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #8520(accepted data)

Opened 3 years ago

Last modified 3 years ago

Prs-AF vs Fa-AF code

Reported by: kristi Owned by: shervin
Component: main Data Locale:
Phase: rc Review:
Weeks: Data Xpath:




Research on Dari locale code:

prs-AF is the only truly necessary locale of the two.

The existence of fa-AF is quite moot, since by definition, Dari is the variety of Persian spoken in Afghanistan. As anywhere - especially with such a non-standardized language like Dari - there are numerous varieties and dialects of the language that stretch to the Iranian border where they are indistinguishable from the language spoken on the other side. So Dari, more than anything is a political designation for the language as it is formalized around major Dari-speaking centers, mostly Kabul.

Farsiwan/Parsiban is a generic designation for Persian/Dari speakers by non-Persian/Dari speakers in Afghanistan and Pakistan, and although some of these peoples are distinct from other Afghan native Dari speakers (mostly referred to as Tajiks) in their closer cultural connections to Persia (such as Shia beliefs) - linguistically they still fall within the Dari spectrum and would certainly identify themselves as speakers of Dari.


Change History

comment:1 Changed 3 years ago by shervin

  • Cc shervin, roozbeh added

comment:2 Changed 3 years ago by shervin

  • Xref set to 8402, 8193

comment:3 Changed 3 years ago by shervin

Four points need to be mentioned here:

  1. When the TC considered ticket:8402, it was decided to see if currently existing data under fa_AF is actually Dari. Is there any resolution from Microsoft regarding this existing data? I investigated the data and can confirm that it is in Dari.
  2. Dari is not as non-standardized as one might imagine; see documents developed by Everson and Pournader for UNDP for locale requirements for languages of Afghanistan.
  3. The comment above does not clarify if the inheritance relationship from mother-language, Persian, is something desired or not. Right now, Dari uses this inheritance to use the values existing for Persian.
  4. In CLDR, fa-AF is Dari and not "a variety of Persian spoken in Afghanistan". There seems to be a misunderstanding in definitions here.
Last edited 3 years ago by shervin (previous) (diff)

comment:4 Changed 3 years ago by shervin

Also, the TC recommended to have an alias added for prs to fa_AF.

comment:5 Changed 3 years ago by emmons

  • Status changed from new to accepted
  • Priority changed from assess to medium
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 28
  • Owner changed from anybody to shervin
  • Type changed from unknown to data

comment:6 Changed 3 years ago by kristi

I'm looking further into #1 and also investigating #3.

comment:7 Changed 3 years ago by kristi

Linguist feedback from CLDR fa-AF data:

  • The Approved Language or Country/Region names with contribution are Dari
  • Inherited data from fa-IR is Persian (Farsi), and they are not appropriate for FA-AF
  • Most of the Formats data (Date, Time, number formats) are currently missing, and the inherited values are for Persian. Contribution of Dari data would be more appropriate.

We (Microsoft) have prs-AF (Dari) Format data that we can contribute, but not for all data points in ST.

comment:8 Changed 3 years ago by shervin

Thanks. These make sense. I think the best course of action right now would be for Microsoft to contribute the data they have via ST for Dari and override the inherited values where Persian data values are not appropriate for Dari.

comment:9 follow-up: ↓ 10 Changed 3 years ago by kristi

Is the plan of record still to keep fa-AF and alias prs-AF for data consumers?

We can contribute Dari data in the next contribution period (we are too late for v28)

comment:10 in reply to: ↑ 9 Changed 3 years ago by shervin

Replying to kristi:

Is the plan of record still to keep fa-AF and alias prs-AF for data consumers?

Certainly. I have it in my list, but I'm just currently blocked by some unrelated issues.

comment:11 Changed 3 years ago by emmons

  • Component changed from unknown to main

comment:12 Changed 3 years ago by shervin

  • Milestone changed from 28 to 29

comment:13 Changed 3 years ago by emmons

  • Milestone changed from 29 to upcoming

Add a comment

Modify Ticket

as accepted

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.