This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 1/1] Pashto yesstr/nostr locale are missing


Rafal Luzynski <digitalfreak@lingonborough.com> wrote:

> 6.07.2017 10:24 Mike FABIAN <mfabian@redhat.com> wrote:
>>
>>
>> Akhilesh Kumar <akhilesh.k@samsung.com> wrote:
>>
>> > [...]
>> > diff --git a/localedata/locales/ps_AF b/localedata/locales/ps_AF
>> > index 702a830..2413b1c 100644
>> > --- a/localedata/locales/ps_AF
>> > +++ b/localedata/locales/ps_AF
>> > @@ -232,6 +232,8 @@ END LC_MONETARY
>> > LC_MESSAGES
>> > yesexpr "<U005E><U005B><U002B><U0031><U0079><U0059><U0628><U0066><U005D>"
>> > noexpr
>> > "<U005E><U005B><U002D><U0030><U006E><U004E><U062E><U0646><U006F><U005D>"
>> > +yesstr "<U0647><U0648>"
>> > +nostr "<U0646><U0647>"
>> > END LC_MESSAGES
>> >
>> > LC_MEASUREMENT
>>
>> I checked that http://thepashto.com/ gives the same strings for yes and
>> no.
>>
>> Committed.
>
> Don't yesexpr and noexpr need an update now?  At least, I can't see
> "<U0647>" character in yesexpr.

Yes, but I am unsure how. There are some Arabic characters in yesexpr
and noexpr, but they seem to have nothing to do with what we have no in
yesstr and nostr. I wonder whether these Arabic characters which we have
now in yesexpr and noexpr are just wrong ...

-- 
Mike FABIAN <mfabian@redhat.com>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]