anyone know where iso-8859-*.h files are?

[Sam Halliday]

i am currently in the process of writing a program to convert a type 1 psf font
file into a file compatible with the linux kernel's format for compiled-in fonts
(see drivers/video/console/font_8x16.c). since the cpi2fnt file used to generate
the 8x16 font has gone awol.

the problem i have encountered in the psf format
[http://www.win.tue.nl/~aeb/linux/kbd/font-formats-1.html]
is that the kernel file requires all the fonts to be created *in order* with
their decimal value. so, for example; the euro graph would be the 165th font in
the list. whereas the psf format allows graphs to be anywhere in the file and
uses a unicode entry at the end to say what goes where.

this would be no problem; if i had such a lookup table!

does anyone know of any (hopefully system/standard) .h file which has a listing
of all the iso-8859-* unicodes and their associated decimal values? i suppose i
could make one on my own... but it seems like such a mundane task, and there
MUST be a set of iso-8859-*.h files out there that have a list of Unicode (U+)
values and decimal equivalents for each character set...

 

[Sam Halliday]

does anyone know of any (hopefully system/standard) .h file which has a
listing of all the iso-8859-* unicodes and their associated decimal values? i
suppose i could make one on my own... but it seems like such a mundane task,
and there MUST be a set of iso-8859-*.h files out there that have a list of
Unicode (U+) values and decimal equivalents for each character set...

after a few hours of googling... i finally stumbled upon this, which i can
fashion for my needs:
http://www.cs.tut.fi/~jkorpela/iso8859

but i'd still be interested to hear if there is a system/standard header file
(or function call?) which will do this for me.

 

[Jack Klein]

i am currently in the process of writing a program to convert a type 1 psf font
file into a file compatible with the linux kernel's format for compiled-in fonts
(see drivers/video/console/font_8x16.c). since the cpi2fnt file used to generate
the 8x16 font has gone awol.

the problem i have encountered in the psf format
[http://www.win.tue.nl/~aeb/linux/kbd/font-formats-1.html]
is that the kernel file requires all the fonts to be created *in order* with
their decimal value. so, for example; the euro graph would be the 165th font in
the list. whereas the psf format allows graphs to be anywhere in the file and
uses a unicode entry at the end to say what goes where.

this would be no problem; if i had such a lookup table!

does anyone know of any (hopefully system/standard) .h file which has a listing
of all the iso-8859-* unicodes and their associated decimal values? i suppose i
could make one on my own... but it seems like such a mundane task, and there
MUST be a set of iso-8859-*.h files out there that have a list of Unicode (U+)
values and decimal equivalents for each character set...

And exactly what is your question about the standard C programming
language? C doesn't even specify any particular character set, either
for source or for the execution environment.

 

[Richard Bos]

does anyone know of any (hopefully system/standard) .h file which has a listing
of all the iso-8859-* unicodes and their associated decimal values?

There is no such Standard header. As for getting headers from other
systems, there's this: <http://www.eskimo.com/~scs/C-faq/q10.11.html>.

Richard

 

[Sam Halliday]

Sam Halliday

And exactly what is your question about the standard C programming
language? C doesn't even specify any particular character set, either
for source or for the execution environment.

excuse me, i thought this was a newsgroup to ask C related questions. i thought
asking if there was a standard header for iso-8859-* unicodes and their decimals
mappings would be very "on topic".

if i knew where exactly to ask such a question, chances are i'd also know where
to get the header file... so i wouldn't need to ask.

 

[Sam Halliday]

There is no such Standard header. As for getting headers from other
systems, there's this: <http://www.eskimo.com/~scs/C-faq/q10.11.html>.

its not the same question... i am asking if such a header of raw data exists
which i may use. i am only postulating its name and that it might be a
system/standard header. if it is a standard header, then thats great news
because i don't need to write it.

 

[Richard Bos]

its not the same question... i am asking if such a header of raw data exists
which i may use.

As I said, no, there is no such Standard header.

Richard

 

[Sam Halliday]

does anyone know of any (hopefully system/standard) .h file which has a

As I said, no, there is no such Standard header.

sorry... i should have changed my wording to "i was asking"; your seen your
original post had the answer. thanks anyway!

 

[P.J. Plauger]

sorry... i should have changed my wording to "i was asking"; your seen your
original post had the answer. thanks anyway!

Now that the Off Topic Police have left the building, you
might want to take a look at:

ftp://std.dkuug.dk/i18n/WG15-collection/charmaps/ISO_8859-*.

That's what we used to build our locale-dependent mbtowc
tables.

P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com

 

[Sam Halliday]

Now that the Off Topic Police have left the building, you
might want to take a look at:

ftp://std.dkuug.dk/i18n/WG15-collection/charmaps/

:-D

excellent! not *exactly* what i wanted... but certainly very handy

 

[Sam Halliday]

Now that the Off Topic Police have left the building, you
might want to take a look at:

ftp://std.dkuug.dk/i18n/WG15-collection/charmaps/ISO_8859-*.

hmm... on inspection, of say

ftp://std.dkuug.dk/i18n/WG15-collection/charmaps/ISO-8859-15

i see that these files are not correct... well at least they don't look it. take
the first character 'null'. this file says that the decimal value 0 should have
unicode value U+0000... which is wrong!!

(quoting the file)
<NU> /x00 <U0000> NULL (NUL)

the null character in iso-8859-* is usually mapped to unicode value U+00A0, not
U+0000. it seems all the non-printable characters in these files are incorrect.

thanks anyway though

 

[those who know me have no need of my name]

[fu-t set]

in comp.lang.c i read:

the null character in iso-8859-* is usually mapped to unicode value
U+00A0, not U+0000. it seems all the non-printable characters in these
files are incorrect.

i think you are working from a basic assumption that is different from the
norm -- U+00A0 is a non-breaking space, this seems an unlikely mapping for
what is classically a control character (null aka nul).

 

[P.J. Plauger]

hmm... on inspection, of say

ftp://std.dkuug.dk/i18n/WG15-collection/charmaps/ISO-8859-15

i see that these files are not correct... well at least they don't look it. take
the first character 'null'. this file says that the decimal value 0 should have
unicode value U+0000... which is wrong!!

(quoting the file)
<NU> /x00 <U0000> NULL (NUL)

the null character in iso-8859-* is usually mapped to unicode value U+00A0, not
U+0000.

News to me. I've always taken it as axiomatic that char zero maps
to wchar_t zero for *all* valid multibyte encodings.

it seems all the non-printable characters in these files are

incorrect.

They looked okay to me. YMMV.

thanks anyway though

Welcome.

P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com