, and we need to
see to
that our procedures are adequate and timely, also in our ISO work.
Best regards
keld
On Tue, Sep 06, 2016 at 06:14:10PM +0100, Andrew Josey wrote:
> I checked in with our IEEE staff liaison and they confirmed they have
> initiated the process to have the TC2-2008
&
w, tere are a few major systems out ther that runs utf-18, such as at
least OS X and IOS.
The 30112 i18n locale is actually proven technology, and has been used in Linux
implementations for something like 20 years. Many hundreds of locales have been
built
on it.
Best regards
Keld
; And again, UTF-16 is not relevant to the POSIX API.
>
> BIG5 and GB18030 are compatible with the POSIX API, they are a
> superset of ASCII, but they are the source of many bugs when
> used as locale charsets and not really needed nowadays as they
> can be replaced with UTF-8. I'm not even mentioning the locking
> shift encodings which hopefully nobody uses in locales anymore.
Of cause you are right saying that ISO 10646/Unicode can handle
all of these encodings. But I cannot tell what needs there are
out there in the marketplace for other encodings.
POSIX has machinery to handle all of this, so I think it is good that
this capability is there.
best regards
keld
]] are tied to that, so it is impossible to use
> > any other decimal digits.
>
> This seems to be an important idea, as this japanese one two three
> is not in a contiguous order.
Well, the digits in other scripts are ordered consequetively, so the calculation
could easily be done, for the scripts I previously documented, as prescribed
in ISO 14652.
This is not rocket science.
Best regards
keld
find proposals for that providing efficient implementations.
>
> 1. https://en.wikipedia.org/wiki/UTF-8
Oh, well. You should be able to implement efficient code for the specs from
14652 and 30112,
one would be that you, after testing for isdigit, the you index into a 4-bit
table
with the binary value corresponding to the digit character. This is probably on
par speedwise
with subtracting the value for zero.
Best regards
keld
..;/
% COLLECTION 18 BENGALI/
..;/
% COLLECTION 18 GURMUKHI/
..;/
% COLLECTION 19 GUJARATI/
..;/
% COLLECTION 20 ORIYA/
..;/
% COLLECTION 21 TAMIL/
<0>;..;/
% COLLECTION 22 TELUGU/
..;/
% COLLECTION 23 KANNADA/
..;/
% COLLECTION 24 MALAYALAM/
..;/
% COLLECTION 25 THAI/
..;/
% COLLECTION 26 LAO/
..;/
% COLLECTION 72 BASIC TIBETAN/
..;/
% COLLECTION 68 HALFWIDTH AND FULLWIDTH FORMS/
..
%
Best regards
keld
I Listed digits that were consequitive. I did not list japanese nor chinese
digits.
But it would be easy to also include japanese and chinese digits.
you could just include character classes like zero, one, two etc.
Best regards
Keld
On Tue, May 22, 2018 at 02:15:16PM +0200, Joerg Schilling
On Sat, Jan 13, 2018 at 06:03:37AM +, Andrew Josey wrote:
> hi Keld , all
>
> > On 12 Jan 2018, at 21:23, k...@keldix.com wrote:
> >
> > How can it be the final text for IEEE when ths has not been balloted
> > in ISO (and to my knowledge not in the Open Group
How can it be the final text for IEEE when ths has not been balloted
in ISO (and to my knowledge not in the Open Group either)?
best regards
keld
On Fri, Jan 12, 2018 at 06:24:31PM +, Andrew Josey wrote:
> All
> Enclosed are the minutes from yesterdays call
> regards
I am also interested in doing work on this, for the 30112 standard.
Do we have any text that could be used for normative wording in a standard?
best regards
keld
On Thu, Aug 09, 2018 at 11:32:50AM -0500, Eric Blake wrote:
> Hello GNU gettext folks,
>
> Jörg Schilling is i
On Wed, Aug 14, 2019 at 09:55:46AM +0100, Andrew Josey wrote:
> Minutes of the 12th August 2019 Teleconference Austin-960 Page 1 of 1
> Submitted by Andrew Josey, The Open Group. 14th August 2019
>
> * General news
>
> We discussed the email from Keld about ISO plann
hi
I understand that ieee is revising its posix standard.
should we not also revise 9945 and what is the plan to keep them in sync?
best regards
Keld simponsen
sc22 alternate or
ieee iso tog ballots
2022-12 ieee revcom , formal ieee approval
when are ISO CD, DIS and FDIS ballots?
CD in ISO are normally feature comlete, so should be D3
DIS should probably be D5
FDIS should probably be d5.1
NP+WD should probably be on D1 or D2
what about TOG plan
Keld
On Sun, Aug 11, 2019
of Category A Liaison with The Open Group
JTC 1/SC 22 requests that Keld Simonsen forward the ISO form "Application to
establish a liaison with a
ISO Committee" to The Open Group. SC 22 requests its Committee Manager to
initiate the liaison
process once the completed form is receiv
what is happening with the action to update the syncronisation plan about the
revision
of posix? it seems to be not even mentioned in the meeting. Please refer to the
sc22
resolution, I have prevously sent you.
best regards
keld
On Tue, Sep 24, 2019 at 10:06:31AM +0100, Andrew Josey wrote
15 matches
Mail list logo
