Re: CVS commit: pkgsrc/print/xpdf

[Tim Zingelman <tez%netbsd.org@localhost>]

On Thu, Oct 27, 2011 at 12:44 AM, Bernd Ernesti 
<netbsd%lists.veego.de@localhost> wrote:
> On Thu, Oct 27, 2011 at 02:35:41AM +0000, Tim Zingelman wrote:
>> Module Name:  pkgsrc
>> Committed By: tez
>> Date:         Thu Oct 27 02:35:41 UTC 2011
>>
>> Modified Files:
>>       pkgsrc/print/xpdf: Makefile distinfo
>>       pkgsrc/print/xpdf/patches: patch-aa patch-ai patch-ak patch-al patch-am
>>           patch-aq patch-bc
>> Removed Files:
>>       pkgsrc/print/xpdf/patches: patch-ab patch-an patch-bb patch-bd
>>
>> Log Message:
>> Update to 3.03
>>
>> Fixes multiple vulnerabilites
>>
>> Change list too long to include here, see http://www.foolabs.com/xpdf/CHANGES
>> (file does not note what changes were included in 3.02pl1 - 3.02pl4 and which
>>  are new for 3.03)
>
> From the README:
>
> ==================================================================
> Upgrading from Xpdf 3.02 (and earlier)
> --------------------------------------
>
> The font configuration system has been changed.  Previous versions
> used mostly separate commands to configure fonts for display and for
> PostScript output.  As of 3.03, configuration options that make sense
> for both display and PS output have been unified.
>
> The following xpdfrc commands have been removed:
> * displayFontT1, displayFontTT: replaced with fontFile
> * displayNamedCIDFontT1, displayNamedCIDFontTT: replaced with fontFile
> * displayCIDFontT1, displayCIDFontTT: replaced with fontFileCC
> * psFont: replaced with psResidentFont
> * psNamedFont16: replaced with psResidentFont16
> * psFont16: replaced with psResidentFontCC
>
> See the xpdfrc(5) man page for more information on the new commands.
>
> Pdftops will now embed external 16-bit fonts (configured with the
> fontFileCC command) when the PDF file refers to a non-embedded font.
> It does not do any subsetting (yet), so the resulting PS files will be
> large.
> ==================================================================
>
> Will this break the other print/xpdf-* packages because of the xpdfrc
> changes?

I do not think so... looking at just one (xpdf-chinese-traditional) it
suggests (manually) adding the following to xpdfrc:
 #----- begin Chinese Traditional support package (2004-jul-27)
 cidToUnicode    Adobe-CNS1
/usr/pkg/share/xpdf/chinese-traditional/Adobe-CNS1.cidToUnicode
 unicodeMap      Big5
/usr/pkg/share/xpdf/chinese-traditional/Big5.unicodeMap
 unicodeMap      Big5ascii
/usr/pkg/share/xpdf/chinese-traditional/Big5ascii.unicodeMap
 cMapDir         Adobe-CNS1      /usr/pkg/share/xpdf/chinese-traditional/CMap
 toUnicodeDir                    /usr/pkg/share/xpdf/chinese-traditional/CMap
 #displayCIDFontTT       Adobe-CNS1      /usr/..../bkai00mp.ttf
 #----- end Chinese Traditional support package

Note that the one change/removed command is commented out.  I don't
know if the assumption is that the user will un-comment that line and
put in a correct font path?  If that is the case, then they would need
to use fontFileCC rather than displayCIDFontTT in that line.  Perhaps
the assumption is that a user of these fonts would already have them
configured via some other means?  In fact the pkgsrc package
containing that example font is fonts/arphic-ttf, and it puts the file
in ${PREFIX}/lib/X11/fonts/TTF/ which I note is not in the xpdf
default displayFontDirs, but probably should be?  (see
print/xpdf/patches/patch-al)

I don't have any way to test the pther print/xpdf-* packages, so I'd
welcome feedback from anyone who uses them.

 - Tim