IPP Mail Archive: Re: IPP> Re: MOD - Comment on RFC 2044: need to specify the ISO 10646

Re: IPP> Re: MOD - Comment on RFC 2044: need to specify the ISO 10646

Harald.T.Alvestrand@uninett.no
Wed, 15 Oct 1997 09:41:31 +0200

Ira,
I think an appropriate solution for IPP is to put the following note into
the spec:

NOTE: For the case where IPP requests are gatewayed into DPA, the text
strings in the protocol must be limited to conform to ISO 10646 level 2.
This means that the following characters are dropped when copying strings
from an IPP PDU into a DPA PDU:

0483 COMBINING CYRILLIC TITLO
0484 COMBINING CYRILLIC PALATALIZATION
0485 COMBINING CYRILLIC DASIA PNEUMATA
0486 COMBINING CYRILLIC PSILI PNEUMATA
093C DEVANAGARI SIGN NUKTA
0953 DEVANAGARI GRAVE ACCENT
0954 DEVANAGARI ACUTE ACCENT
09BC BENGALI SIGN NUKTA
09D7 BENGALI AU LENGTH MARK
0A3C GURMUKHI SIGN NUKTA
0A70 GURMUKHI TIPPI
0A71 GURMUKHI ADDAK
0ABC GUJARTI SIGN NUKTA
0B3C ORIYA SIGN NUKTA
0B56 ORIYA AI LENGTH MARK
0B57 ORIYA AU LENGTH MARK
0BD7 TAMIL AU LENGTH MARK
0C55 TELUGU LENGTH MARK
0C56 TELUGU AI LENGTH MARK
0CD5 KANNADA LENGTH MARK
0CD6 KANNADA AI LENGTH MARK
0D57 MALAYALAM AU LENGTH MARK
302A IDEOGRAPHIC LEVEL TONE MARK
302B IDEOGRAPHIC RISING TONE MARK
302C IDEOGRAPHIC DEPARTING TONE MARK
302D IDEOGRAPHIC ENTERING TONE MARK
302E HANGUL SINGLE DOT TONE MARK
302F HANGUL DOUBLE DOT TONE MARK
3099 COMBINING KATAKANA-HIRAGANA VOICED SOUND MARK
309A COMBINING KATAKANA-HIRAGANA SEMI-VOICED SOUND MARK

It always helps to be explicit about those things....

Harald A