<div class="gmail_quote">On Fri, Sep 14, 2012 at 9:46 AM, Nicolas Mailhot <span dir="ltr"><<a href="mailto:nicolas.mailhot@laposte.net" target="_blank">nicolas.mailhot@laposte.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5"><br>
</div></div>Adobe CMAP is used by lots of font, ps and pdf related apps and IIRC<br>
packaging it is currently on the wishlist.<br>
<br>
You should unbundle it and create a separate package.<br>
<br>
I don't think CMAP has security implications, but projects that bundle old<br>
versions of the Adobe datafiles will behave in non-optimal ways when they<br>
hit a font/text combination that requires a mapping Adobe introduced in a<br>
later version.<br></blockquote><div><br></div><div>That sounds like a good idea.</div><div><br></div><div>How should it work though? I can grab all the .tar.z files from <a href="http://sourceforge.net/adobe/cmap/home/Home/">http://sourceforge.net/adobe/cmap/home/Home/</a>, extract them, and throw them somewhere into /usr/share (/usr/share/cmap/)... then packages can grab up-to-date copies of the cmap resources from there?</div>
<div><br></div><div>Ben</div></div><br>