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.21 12:37 "RE: Unicode build of libtiff?", by John Aldridge

At 23:25 19/01/00 -0800, Leonard Rosenthol <leonardr@lazerware.com> wrote:

I don't know enough about Unicode to comment on Leonard's suggestion about encoding into UTF-8. Would that break a non-Unicode-aware Baseline TIFF reader?

Nope! UTF-8 encoding is the same as ASCII for all values <=255, so all Roman/Latin based language information would look and act the same. For other languages (CJK, being the big example) a non-UTF-8 savvy reader would simply display strange looking values but would be able to handle it OK.

Not so! UTF-8 is different for characters >127. Characters between 128 and 255 are encoded as two bytes, not one. A non UTF-8 reader would display plain ASCII correctly, but give complete gibberish for, e.g, French accented characters.

--
Cheers,
John