On 2014-09-21 13:23, Jonas Smedegaard wrote:
> Quoting Gunnar Hjalmarsson (2014-09-21 11:39:45)
>>
> 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.
It could be done in debian/rules like this:
override_dh_install:
dh_install
for f in DroidSansFallback.ttf DroidSansFallbackLegacy.ttf ; \
do ; \
cd debian/fonts-droid/usr/share ; \
mv fonts/truetype/droid/$$f \
fonts-droid/truetype/$$f || true ; \
done
> ..and add a note to README.Debian on where those fonts are installed and
> why they are not registered with fontconfig.
I like that solution. That way we would safely get rid of risks for
confusing fontconfig and causing subtle bugs.
>> 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.
Fair enough.
--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
