Package: t1utils Version: 1.41-4 Severity: normal Dear Maintainer,
during my tests with #1029168 I run into a lintian issue: Warning in processable [...]/fonts-urw-base35/debian/output/fonts-urw-base35_20200910-7+salsaci+20230120+4_all.deb: In file usr/share/fonts/type1/urw-base35/C059-Italic.t1: cp1252 "\x90" does not map to Unicode at /usr/share/lintian/lib/Lintian/Check/Fonts/Postscript/Type1.pm line 57. digging some deeper I had to notice that t1disasm C059-Italic.t1 (/usr/share/fonts/type1/urw-base35/C059-Italic.t1 from package fonts-urw-base35) does not disassemble the complete file but returns some binary data after the definition of /uni04E8. Similar behavior, if I try to convert the font to ascii using t1ascii C059-Italic.t1 which has some binary data (instead of the expected hex data) near the end of the output. If I compare the output of t1disasm C059-Italic.t1 and t1disasm C059-BdIta.t1 that there are 206 character definitions missing at the end of the output of the former. First I thought, that C059-Italic.t1 is broken, but than I did some testing with lcdf-typetools. t1lint C059-Italic.t1 does not shows only the same warning as I see on C059-BdIta.t1, but no errors. Creating a t1testpage for C059-Italic.t1 works and the result contains the same charset than C059-BdIta.t1 including some characters, that are missing in t1disasm output of C059-Italic.t1. So maybe not the font is broken but t1utils. If I try to convert C059-Italic.t1 to .pfa (using t1ascii) or to .pfb (using t1binary), the resulting files are always broken. t1lint shows errors on both generated files and a generated t1testpage cannot be opened (PS errors) and seems to have less pages than the testpage of C059-Italic.t1. So maybe this is a hint, that the problem does not exist in the font but in t1utils, which is only triggered by this special font. Greetings Roland