Unassigned code points

[Simon Josefsson]

All,

I'm comparing the RFC 5892 tables plus the draft-faltstrom-5892bis-04
changes with my own computations, and I see plenty of differences due to
previously unassigned code points that are now either PVALID or
DISALLOWED.  That is expected.

Has anyone created the complete updated tables for Unicode 6.0.0 that
IANA would publish (if draft-faltstrom-5892bis-04 is approved) that they
can share?

For example, RFC 5892 contains:

0526..0530  ; UNASSIGNED  # <reserved>..<reserved>

and in Unicode 6.0.0 the U+0526 and U+527 code points were introduced:

0526;CYRILLIC CAPITAL LETTER SHHA WITH DESCENDER;Lu;0;L;;;;;N;;;;0527;
0527;CYRILLIC SMALL LETTER SHHA WITH DESCENDER;Ll;0;L;;;;;N;;;0526;;0526

I believe that U+0526 will now be DISALLOWED and U+0527 will now be
PVALID, but would like to confirm that (and all other differences).

/Simon