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

CLDR Ticket #11303(new survey)

Opened 3 weeks ago

Fixing remaining errors in French

Reported by: Marcel Schneider <charupdate@…> Owned by: anybody
Component: unknown Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description

Under coverage:Modern [1], we have to fix:

http://st.unicode.org/cldr-apps/v#/fr/MassWeight/3989187f52fc7104
Replace "{0}²microgramme" with "{0} microgramme" where the space is NBSP, then make win.

[External links are limited to 4 per post.]

st.unicode.org/cldr-apps/v#/fr/MassWeight/96457fe7037bd12
Replace "{0}²microgramme" with "{0} microgramme" where the space is NBSP, then make win.

st.unicode.org/cldr-apps/v#/fr/MassWeight/1a09415ff9ecc8b7
Replace "{0} par kg" with "{0} par kilogramme" (all spaces are SP), then make win.

st.unicode.org/cldr-apps/v#/fr/Area/c7c43fa94e22e7a
Replace "{0}/mi²" with "{0} par mille carré", then make win.

st.unicode.org/cldr-apps/v#/fr/Area/58ad6c84d4358d32
This item has a mistake in the list I’d sent you. I wrote: Make the value "{0} par kilomètre carré" win.
But that value is just a remainder of a set of wrong values I’ve unvoted to align on winning value. Here I
did not update, because the winning value is wrong as part of a set of 3 values where short form mistakenly
stands for long form. Hence:
Replace "{0} par kilomètre carré" (first space is NBSP) with "{0} par kilomètre carré" (all spaces SP) and make win.

st.unicode.org/cldr-apps/v#/fr/Duration/5ee3359215d1a55e
Upvote as winning the value "{0} ans" with NBSP, that has not been upvoted like the singular form, because
ST displays it as fallback (span.fallback) with the dark-blue inheritance background like some inherited English values.
This bug has been reported in ticket:11298.

st.unicode.org/cldr-apps/v#/fr/Duration/2b2ddb8c19e122e5
Make the value "{0} siècle" (with NBSP) win, wrongly brandmarked as inherited.
Jean-Michel’s votes are missing because he was diverted by ST and is now on holidays.

st.unicode.org/cldr-apps/v#/fr/Duration/4da443978637ff59
Make the value "{0} siècles" (with NBSP) win, wrongly brandmarked as inherited.

st.unicode.org/cldr-apps/v#/fr/Duration/5cdb2c63947c403b
Make the value with NNBSP win, that Jean-Michel upvoted and posted on the forum:
st.unicode.org/cldr-apps/v#forum/fr30385
[v34] 2018-07-26 11:57
I wrongly voted for the value with NBSP and misled Ann, additionally to the wrong
inheritance markup that ST added to the item with NNBSP, that I’d probably entered,
before being misled myself by the wrong markup. Jean-Michel was not, he noticed
the narrow width of the space albeit the value is flagged as fallback. He noted:
“[…] it looks like this is the one containing the NNBSP” (quoted from forum post).
Now I’ve updated my vote, but that is not enough.

http://st.unicode.org/cldr-apps/v#/fr/Symbols2/703401538a593242
Replace "bélier zodiaque" with "Bélier zodiaque" and make it win, as titlecase is mandatory in fr (not only in fr-CA).
Ʈhe same transform should be performed on the 12 other names of signs:

st.unicode.org/cldr-apps/v#/fr/Symbols2/374e2ab6cf5165ab

st.unicode.org/cldr-apps/v#/fr/Symbols2/4064f0ce8babd70c

st.unicode.org/cldr-apps/v#/fr/Symbols2/4d0d31291051f1ee

st.unicode.org/cldr-apps/v#/fr/Symbols2/1235938adab4f44e

st.unicode.org/cldr-apps/v#/fr/Symbols2/63d6878b55e1dcab

st.unicode.org/cldr-apps/v#/fr/Symbols2/25f99b0b201fae5e

st.unicode.org/cldr-apps/v#/fr/Symbols2/25cba8159dac6398

st.unicode.org/cldr-apps/v#/fr/Symbols2/10321527a38c648d

st.unicode.org/cldr-apps/v#/fr/Symbols2/6e4f2405c291c421

st.unicode.org/cldr-apps/v#/fr/Symbols2/33863a1154ba8919

st.unicode.org/cldr-apps/v#/fr/Symbols2/108be50f4b2918cc

st.unicode.org/cldr-apps/v#/fr/Symbols2/6e455a5bee4b8b8f

(Synching the keywords is pointless, as per new guideline the name must not be repeated therein.)

See also ticket:11302 about Ordinal minimal pairs for French.
That data pertains to what is actually:

http://st.unicode.org/cldr-apps/v#/fr/MinimalPairs/5ebe132520280dd2

http://st.unicode.org/cldr-apps/v#/fr/MinimalPairs/4aadabab33db3504

Then, under coverage:Comprehensive, we have to fix some errors in narrow display forms.
But that is off-topic here.

Note: I file this ticket after being directed to do so. I understand that with hundreds of locales and a million votes, TC is overworked so that list is posted here for the record.

Thanks in advance if the above can be fixed for the release of version 34 on October 10.

Attachments

View

Add a comment

Modify Ticket

Action
as new
Author


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

 
Note: See TracTickets for help on using tickets.