AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2019.09.28 16:54 "[Tiff] Switch from bugzilla to gitlab issues ?", by Even Rouault
2019.09.28 19:42 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Roger Leigh
2019.09.28 22:05 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Damir Sudar
2019.09.28 22:15 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Bob Friesenhahn
2019.09.29 14:32 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Even Rouault
2019.09.29 17:08 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Bob Friesenhahn
2019.09.29 17:33 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Roger Leigh
2019.09.29 18:35 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Even Rouault
2019.09.29 19:53 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Bob Friesenhahn
2019.10.01 19:49 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Even Rouault

2019.09.29 17:08 "Re: [Tiff] Switch from bugzilla to gitlab issues ?", by Bob Friesenhahn

Comments?

This looks useful.

The main annoyance I see is that some font sizes are abnormally large. For example, for bug BZ#2849 (https://gitlab.com/rouault/test-libtiff-issues/issues/156) the text of the ASAN output (starting with "TIFFReadDirectoryCheckOrder:") looks like it uses the same large and bold font size as the issue title. Later in a comment by Thomas Bernard I see exessively large "$ tools/tiff2pdf -o" after "but indeed I reproduce" The text which uses the over-large font size seems to be selected in a haphazard manner or maybe it is just not a good translation from an existing formatting.

Be sure to verify that the attached image files have not been re-written as SourceForge tends to do. Re-written attachments might be a risk in the future if gitlab starts doing that.

Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/

Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt