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

CLDR Ticket #8244(closed: fixed)

Opened 4 years ago

Last modified 4 years ago

Wrong month names in vo (Volapük)

Reported by: malafaya@… Owned by: emmons
Component: datetime Data Locale: vo
Phase: dsub Review: pedberg
Weeks: Data Xpath:


The month names for January and March are wrong.
janul should be yanul.
mäzil should be mäzul.

Abbreviaton for yanul should also be change (J to Y)

You can check Wiktionary for example:


Changes through the next Survey Tool will never get 4 votes to be approved as there aren't enough contributors.


Change History

comment:1 Changed 4 years ago by emmons

  • Owner emmons deleted

comment:2 Changed 4 years ago by emmons

  • Owner set to emmons
  • Priority changed from assess to medium
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 28

comment:3 Changed 4 years ago by emmons

  • Priority changed from medium to trivial

comment:4 Changed 4 years ago by emmons

  • Status changed from assigned to reviewing
  • Review set to pedberg

You need a regular strength vetter (not a guest) who will have a 4 point vote to get things approved in the CLDR. See http://cldr.unicode.org/index/process

comment:5 Changed 4 years ago by malafaya@…

Problem is it seems there is no such user contributing to the Volapük language. If that's the only way to get things corrected, the mistakes are to be there indefinitely. I wonder how they got there in the first place.

comment:6 Changed 4 years ago by markus

  • type set to data

comment:7 Changed 4 years ago by markus

  • Component changed from data-other to other

comment:8 Changed 4 years ago by markus

  • version 26 deleted

comment:9 Changed 4 years ago by pedberg

  • Status changed from reviewing to closed
  • Resolution set to fixed
  • Component changed from other to datetime

Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

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

Note: See TracTickets for help on using tickets.