AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.01.19 12:26 "Unicode build of libtiff?", by Dirk Haun
2000.01.19 17:42 "RE: Unicode build of libtiff?", by Richard J. Otter
2000.01.19 21:27 "RE: Unicode build of libtiff?", by Leonard Rosenthol
2000.01.19 23:13 "RE: Unicode build of libtiff?", by Bryan H. Maret
2000.01.20 07:25 "RE: Unicode build of libtiff?", by Leonard Rosenthol
2000.01.20 17:05 "RE: Unicode build of libtiff?", by Eric J. Schwertfeger
2000.01.21 07:52 "Re: Unicode build of libtiff?", by Bjorn Brox
2000.01.21 12:37 "RE: Unicode build of libtiff?", by John Aldridge
2000.01.21 14:00 "RE: Unicode build of libtiff?", by Martinez, Max
2000.01.24 10:50 "RE: Unicode build of libtiff?", by John Aldridge
2000.01.20 14:21 "RE: Unicode build of libtiff?", by Dirk Haun

2000.01.20 14:21 "RE: Unicode build of libtiff?", by Dirk Haun

My understanding is that since the TIFF spec doesn't say anything about 2 byte wide characters, all text tags would have to be narrow for other software to read them.

It seems that any new image spec which includes text descriptions must support Unicode.

Well, for now my concern was only to change libtiff so that I can do a unicode build of it and link it statically to a unicode project I'm currently working on. I don't want to store any content in unicode (yet).

Of course, I would like to see the changes I need to make be incorporated into libtiff so that I don't have to do them again when the next version comes out.

How do non-Windows/MS platforms handle unicode builds? I mean, if the changes I described earlier are only necessary for MSVC then it probably doesn't make sense incorporating them into libtiff itself.

regards,

Dirk Haun
Dirk.Haun@yellow.de

Yellow Computing Computersysteme GmbH
Hanns-Martin-Schleyer-Strasse 1
D-74177 Bad Friedrichshall (Germany)
Phone +49-7136-9511-0
Fax +49-7136-9511-11
Web: http://www.yellow.de