Registration of new charset ISO 11548-1

[Samuel Thibault]

Hi,

Here is a submission request for the ISO 11548-1 charset, which is an
8bit charset used for transmitting braille dots, for braille embossers
and the Braille Protocol (aka BrlAPI). This is not a text charset since
it lacks CR and such.

Charset name:

ISO-11548-1

Charset aliases:

ISO_11548-1

Suitability for use in MIME text:

No.

Published specification(s):

ISO/TR 11548-1:2001

ISO 10646 equivalency table:

byte xy in ISO 11548-1 maps to U+28xy and vice-versa.

Additional information:

Samuel Thibault <***@ens-lyon.org>

Intended usage:

LIMITED USE

[Martin Duerst]

Post by Samuel Thibault
Hi,
Here is a submission request for the ISO 11548-1 charset, which is an
8bit charset used for transmitting braille dots, for braille embossers
and the Braille Protocol (aka BrlAPI). This is not a text charset since
it lacks CR and such.
ISO-11548-1
ISO_11548-1

Is this alias already used? If not, better not define one.

Post by Samuel Thibault
No.
ISO/TR 11548-1:2001
byte xy in ISO 11548-1 maps to U+28xy and vice-versa.

It may be good to say explicitly that this applies to
all 256 codepoints that can be expressed in this way.
The same thing as for your other registration applies.

Post by Samuel Thibault
LIMITED USE

What is the limitation? E.g. if this encoding is best limited
to certain devices, it would be good to say so.

Regards, Martin.


#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp

[Erik van der Poel]

Is this charset intended to be used with one of the "application"
subtypes? Which one(s)? It might be good to indicate this in the
registration.

Erik

Post by Samuel Thibault
Here is a submission request for the ISO 11548-1 charset, which is an
8bit charset used for transmitting braille dots, for braille embossers
and the Braille Protocol (aka BrlAPI). This is not a text charset since
it lacks CR and such.
No.

[Erik van der Poel]

I'm just concerned that we might start seeing headers like this if we
don't provide any recommendations:

Content-Type: application/x-braille; charset=ISO-11548-1

Would application/octet-stream be a suitable content type for
ISO-11548-1? Maybe this should be explicitly mentioned in the
registration, like this:

Suitability for use in MIME text:

No. May be used with application/octet-stream.

Erik

Hi,

Post by Erik van der Poel
Is this charset intended to be used with one of the "application"
subtypes? Which one(s)? It might be good to indicate this in the
registration.

I don't see an existing one that would really fit. And this charset is
not really related to any specific application: it is intended to just
express braille dot patterns, i.e. text. But it can't really be used as
a "text" type, since it lacks most (if not all) text properties (having
line / word breaks, etc).
Samuel

[Claus Färber]

Post by Erik van der Poel
No. May be used with application/octet-stream.

Shouldn't it be something like application/iso-11548-1 then?

Claus

[Martin Duerst]

It would definitely be a bad idea to make a charset label
part of a MIME media type. The way I understand Samuel's
explanations, this character encoding is mostly used as
part of some specific protocols/format, not directly in
as a parameter to a mime type. Nevertheless, registering
it makes sense in my view.

Regards, Martin.

Post by Claus Färber

Post by Erik van der Poel
No. May be used with application/octet-stream.

Shouldn't it be something like application/iso-11548-1 then?
Claus

#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp

[Claus Färber]

Post by Martin Duerst
It would definitely be a bad idea to make a charset label
part of a MIME media type. The way I understand Samuel's
explanations, this character encoding is mostly used as
part of some specific protocols/format, not directly in
as a parameter to a mime type. Nevertheless, registering
it makes sense in my view.

Well, I misinterpreted the description. I thought it was more a media
format to convey Braille information (including control data) instead of
a charset.

Now that mapping to Unicode has been posted, I agreee that it is a
charset and should be registered as such.

Claus

[Samuel Thibault]

I'm just concerned that we might start seeing headers like this if =

we

=20
Content-Type: application/x-braille; charset=3DISO-11548-1
=20
Would application/octet-stream be a suitable content type for
ISO-11548-1?

That would be fine, yes.

Maybe this should be explicitly mentioned in the
=20
=20
No. May be used with application/octet-stream.

Ok.

Samuel

[Samuel Thibault]

Hi,

Post by Erik van der Poel
Is this charset intended to be used with one of the "application"
subtypes? Which one(s)? It might be good to indicate this in the
registration.

I don't see an existing one that would really fit. And this charset i=
s
not really related to any specific application: it is intended to jus=
t
express braille dot patterns, i.e. text. But it can't really be used =
as
a "text" type, since it lacks most (if not all) text properties (havi=
ng
line / word breaks, etc).

Samuel

[Samuel Thibault]

Hi,

Post by Martin Duerst

Post by Samuel Thibault
ISO_11548-1

=20
Is this alias already used? If not, better not define one.

By the GNU libc, yes.

Post by Martin Duerst

Post by Samuel Thibault
LIMITED USE

=20
What is the limitation? E.g. if this encoding is best limited
to certain devices, it would be good to say so.

Well, there is no real limitation, except that it doesn't have any li=
ne
break marker, word separator, etc., which prevents from using it as
a generic way to express braille. But it is very commonly used for
internal braille representations.

Here is a corrected version:


Charset name:

ISO-11548-1

Charset aliases:

ISO_11548-1
ISO_TR_11548-1

Suitability for use in MIME text:

No.

Published specification(s):

ISO/TR 11548-1:2001

ISO 10646 equivalency table:

All 256 8-bit 0xuv codepoints in ISO/TR 11548 map to U+28uv and vice-=
versa.

Additional information:

This charset is mainly used by some braille embossers, the braille
protocol (aka BrlAPI), and as internal dot pattern representation.

Person & email address to contact for further information:

Samuel Thibault <***@ens-lyon.org>

Intended usage:

COMMON







Samuel