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

CLDR Ticket #10734(accepted data)

Opened 9 months ago

Last modified 4 weeks ago

yesstr and an nostr in br.xml not correct

Reported by: maiku.fabian@… Owned by: SurveyTool
Component: other Data Locale:
Phase: dsub Review: mellie
Weeks: Data Xpath:



8969 <posix>
8970 <messages>
8971 <yesstr>y</yesstr>
8972 <nostr>n</nostr>
8973 </messages>
8974 </posix>

This should probably be fixed to look like:

8969 <posix>
8970 <messages>
8971 <yesstr>Ya:y</yesstr>
8972 <nostr>Ket:k</nostr>
8973 </messages>
8974 </posix>

according to this information of Thierry Vignaud <thierry.vignaud@…>:

tvignaud> The Breton language basically has a 4 form system for
tvignaud> https://en.wikipedia.org/wiki/Yes_and_no
tvignaud> 1) Affirmative question:
tvignaud> "Dont a rit?" (Do you come?")
tvignaud> => Yes: Ya (ie I'm coming)
tvignaud> => No: "Ket" or "Ne zeuin ket" (ie I won't come)
tvignaud> (either just "ket" or repeat the verb in the negative form)
tvignaud> 2) Negative question:
tvignaud> "N’eo ket brao an amzer ?" ("the weather is NOT fine?")
tvignaud> => Yes: "Geo" ("yes, it is fine") like "*sí*" in Spanish or "si" in French
tvignaud> => No: "Nann" > aka indeed it's not fine
tvignaud> This removes the ambiguity that exists in 2 (eg: English) or 3 form systems
tvignaud> (eg: French)
tvignaud> Actually here, I'm not sure what would answer most English speakers to the
tvignaud> 2nd example :-)

See also:



Change History

comment:1 Changed 9 months ago by kent.karlsson14@…

8971 <yesstr>ya:y</yesstr>
8972 <nostr>ket:k</nostr>

(all lowercase)

comment:2 Changed 4 weeks ago by mellie

  • Status changed from new to accepted
  • Component changed from unknown to other
  • Priority changed from assess to minor
  • Milestone changed from UNSCH to 34
  • Owner changed from anybody to SurveyTool
  • Type changed from unknown to data
  • Review set to mellie

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.