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

CLDR Ticket #7325(accepted data)

Opened 3 years ago

Last modified 2 years ago

Ordering rules for the languages spoken in Finland (FI)

Reported by: eik@… Owned by: emmons
Component: collation Data Locale:
Phase: rc Review:
Weeks: Data Xpath:
Xref:

Description

For the major languages (fi_FI and sv_FI) the ordering rules should be layered as follows: the ROOT ordering should be modified by the European Ordering Rules (EN 13710) and the Finnish ordering rules (SFS-EN 13710 Annex H). For each of the Sámi languages spoken in Finland (se_FI, smj_FI and sms_FI) the above should be modified by the relevant language dependent rules (to be supplied separately).

Attachments

SFS-EN 13710 Annex H p1.jpg (354.9 KB) - added by eik@… 3 years ago.
SFS-EN 13710 Annex H p2.jpg (528.1 KB) - added by eik@… 3 years ago.

Change History

comment:1 Changed 3 years ago by emmons

  • Status changed from new to assigned
  • Cc markus added
  • Component changed from unknown to data-collation
  • Milestone changed from UNSCH to 26rc
  • Owner changed from anybody to emmons
  • Type changed from unknown to enhancement

comment:2 Changed 3 years ago by markus

I would like to see details about the EOR portion of such tailoring requests before they go into the data files. The EOR has a number of issues, both technical (I don't think this is a complete list) and its for-pay publication status.

comment:3 follow-up: ↓ 4 Changed 3 years ago by eik@…

I'm asking Marc Küster, the editor of the standard to look into this. (Incidentally, I understand that Åke was rather heavily involved in the deverlopment of the standard.)

The relevant CEN body has a liaison status with Unicode, and a copy of the standard has already been forwarded to Unicode for its development efforts, i.e., the for-pay status should not pose any problem.

I'm sure that this can be worked out.

Erkki

comment:4 in reply to: ↑ 3 Changed 3 years ago by markus

Replying to eik@…:

The relevant CEN body has a liaison status with Unicode,

CEN TC 304 does not seem to exist any more.
See http://standards.cen.eu/dyn/www/f?p=CENWEB:6:::NO

and a copy of the standard has already been forwarded to Unicode for its development efforts

I asked, there is no record of this. The Unicode Consortium does not have a technical library, nor the means to set one up.

Changed 3 years ago by eik@…

Changed 3 years ago by eik@…

comment:5 Changed 3 years ago by eik@…

Marc Küster has sent the text of EN 13710 to Markus. I've now attached the Finnish Annex H of SFS-EN 13710 to this ticket.
Erkki

comment:6 Changed 3 years ago by emmons

  • Priority changed from assess to minor

comment:7 Changed 3 years ago by emmons

  • Milestone changed from 26rc to 27rc

Deferring to 27rc

comment:8 Changed 3 years ago by markus

  • Phase set to rc
  • Milestone changed from 27rc to 27

comment:9 Changed 3 years ago by emmons

  • Milestone changed from 27 to 28

Pushing to 28 due to lack of time.

comment:10 Changed 2 years ago by markus

  • Type changed from enhancement to data

comment:11 Changed 2 years ago by srl

  • Status changed from assigned to accepted

comment:12 Changed 2 years ago by emmons

  • Milestone changed from 28 to UNSCH

Moving this to UNSCH, for a couple of reasons:

1). Similar to the situation with German EOR rules, the tailoring that would be suggested by 13710 annex h would require many more characters to be tailored than are actually used by the language. This goes against some of the basic principles of Unicode/CLDR collation tailorings.

2). We're not convinced that doing an EOR based tailoring should be the default in CLDR. Perhaps offered as an alternative ( i.e. fi-FI-u-co-eor ). However, if this is really important than someone else is going to need to develop the tailoring rules. I have many other items to work on that are higher priority for the CLDR project as a whole.

View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.