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 14:21 "RE: Unicode build of libtiff?", by Dirk Haun
2000.01.21 14:00 "RE: Unicode build of libtiff?", by Max Martinez
Indeed UTF-8 is only compatible with ASCII, but would that make it unwise to say that the type formerly known as ASCII has been redefined to be UTF-8? How would this break anything other than to have non-savvy apps display gibberish where they wouldn't have been able to display anything anyway? (i.e., the alternative would be to change the type field causing the old app to say it can't read it [and, in fact, might break some poorly written apps] or write two tags, one in ASCII saying "you can't read the real data because it is non-ASCII" and the new tag containing the Unicode data).