Date:        Fri, 9 Dec 2022 12:11:14 +0000
    From:        "Geoff Clare via austin-group-l at The Open Group" 
<austin-group-l@opengroup.org>
    Message-ID:  <Y5Ml4jn/gDN/zpJf@localhost>

  | It made it to the list, but the lack of an answer probably means
  | nobody who read it can answer it.

Yes...

However, I was looking at XRAT (from the current standard)
today (for unrelated reasons) and...


  | > > In draft 2.1 (and the current spec) strftime's %Ou modified spec is 
described as:
  | > >
  | > > %Ou  Replaced by the weekday as a number in the locale’s alternative 
representation
  | > > (Monday=1).
  | > >
  | > > Should that say "as a number using the locale's alternative numeric 
symbols"?
  | > > Otherwise the definition is circular.

came across XRAT A.7.3.5 (LC_TIME) which happens to include this
statement:

    It can be noted that the above example is for illustrative purposes only;
    the %O modifier is primarily intended to provide for Kanji or Hindi digits
    in date formats.

That's on page 3532 (lines 119660-1 aside from the leading "It" which is
on line 119659).   I haven't checked Issue 8 Draft 2.1, but I cannot see
any reason that section would have changed.

I also cannot imagine that only Kanji or Hindi is intended there, just for
systems that don't use arabic digits (0 1 2 ...).

kre

ps: I agree that this is still largely a WG14 issue.


  • strftime %Ou Jonathan Wakely via austin-group-l at The Open Group
    • Re: strftime %Ou Jonathan Wakely via austin-group-l at The Open Group
      • Re: strftime... Geoff Clare via austin-group-l at The Open Group
        • Re: strf... Jonathan Wakely via austin-group-l at The Open Group
      • Re: strftime... Robert Elz via austin-group-l at The Open Group

Reply via email to