On 12-03-01 at 08:54am, Ian Zimmerman wrote: > > >> $ file > >> /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf > >> /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf: > >> broken symbolic link to > >> `../../../../fonts/truetype/droid/DroidSansFallback.ttf' > Jonathan> [...] > >> Versions of packages libgs9-common recommends: pn fonts-droid <none> > > Jonathan> That's why. I don't see an obvious bug here. What harm is > Jonathan> the broken symlink causing, and what change would you suggest > Jonathan> to avoid it? > > OK, that's a good point. Go ahead and close the bug if you like. > > In general, I think useless dangling symlinks are a bug even if they > don't cause tangible harm, just as for example documentation reference > to a feature that no longer exists would be a bug. They impede > administrators' (and developers') understanding of the package. I agree with you that it is a bug (even by Policy IIRC). Tricky to fix, though. > By the way, why does ghostscript need this font now? From upstream History9.htm: > Ghostscript's PDF interpreter is now able to make use of the > DroidSansFallback TrueType font to automatically substitute for > missing CIDFonts. Whilst it is always best to ensure the original > CIDFont is available for the best and most accurate output, the > ability to make an automatic substitution will be valuable for those > merely viewing or proofing such files. ...and that's another Policy-mandated bug: Long description should document the relevancy of optional parts IIRC. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: Digital signature