Quoting Gunnar Hjalmarsson (2014-09-21 11:39:45) > On 2014-09-21 09:52, Christian PERRIER wrote: >> As of now, we have: >> >> bubulle@sesostris:~/src/debian/pkg-fonts/git/fonts-android(master) $ more >> debian/fonts-droid.install >> Droid*.ttf usr/share/fonts/truetype/droid >> ... >> >> So basically : "let's install all fonts whose name starts with "Droid" >> ". How can we technically do "All fonts whose name starts with 'Droid' >> but two of them" >> >> Unless we, of course, list them all one by one.... > > They were listed previously. > > http://anonscm.debian.org/cgit/pkg-fonts/fonts-android.git/diff/?id=7d59819 > >> Maybe something like this >> >> override_dh_install: >> dh_install >> rm <path>/DroidSansFallback.ttf || true >> rm <path>/DroidSansFallbackLegacy.ttf || true > > Would work too. > > On 2014-09-21 10:28, Jonas Smedegaard wrote: >> How about this instead: >> >> Droid*.ttf usr/share/fonts-droid/truetype > > That would put away all of them. Did you really mean that?
Whoops - I did mean "all three of them" but now realize that there's more than three. I favor Christians approach - except that I suggest not dropping those problematic fonts completely, but ship them outside of fontconfig paths so as to allow using them when explicitly needed. So in addition to rm'ing, I suggest to extend the *.install file with something like this: DroidSansFallback.ttf /usr/share/fonts-droid/truetype DroidSansFallbackLegacy.ttf /usr/share/fonts-droid/truetype ..and add a note to README.Debian on where those fonts are installed and why they are not registered with fontconfig. > However, I can't help suspecting that there is no real need to include > DroidSansFallback.ttf and DroidSansFallbackLegacy.ttf. Those in need of rendering documents correctly which references but does not embed those particular fonts. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature