Menu

#2500 pdfx package incomplete

None
in-the-works
None
2016-11-09
2016-05-25
U_Fischer
No

In pdfx quite a number of files are missing. This means that every document with \usepackage{pdfx} fails.

If I got everything right the files from CTAN should be place like this in the texmf:

In tex/latex/pdfx

8bit.def
AdobeColorProfiles.tex
AdobeExternalProfiles.tex
ICC_LICENSE.txt
armglyphs.dfu
coated_FOGRA39L_argl.icc
glyphtounicode-cmr.tex
l8uarb.def
l8uarm.def
l8ucyr.def
l8udev.def
l8uenc.def
l8ugrk.def
l8ulat.def
l8umath.def
pdfa.xmp
pdfe.xmp
pdfvt.xmp
pdfx.pdf
pdfx.sty
pdfx.xmp
sRGB_IEC61966-2-1_black_scaled.icc

In doc/latex/pdfx

sample.tex
sample.xmpdata
small2e-pdfx.tex
README
manifest.txt % this contains the file list

The files in scr folder are source for the sty and the documentation and should go in source

Discussion

  • Christian Schenk

    • status: open --> in-the-works
    • assigned_to: Christian Schenk
     
  • Christian Schenk

    I wonder if it is really necessary to install the license text file in the input directory searched by TeX. It is a file read by human users, isn't it?

     
  • U_Fischer

    U_Fischer - 2016-05-26

    On the texlive list Ross wrote explicitly

    Note that ICC_LICENSE.txt is a licence message for the ICC Color Profiles
    coated_FOGRA39L_argl.icc and sRGB_IEC61966-2-1_black_scaled.icc
    This licence text should accompany the profiles, within ../tex/latex/pdfx/ .

     
  • Mike

    Mike - 2016-11-09

    After the last update I get the following two warnings:
    Failed to load AGL file "pdfglyphlist.txt"
    Failed to load AGL file "glyphlist.txt"

    They are issued after a prompt for installing the dvipdfmx package. The respective measage of the MiKTeX package installer reads:
    "The requested file fonts\map\glyphlist\texglyphlist.txt is missing. It is a part of the following package: dvipdfmx".
    On the next latex run the installation prompt is issued again.

    Is this problem related to the one described by Ulrike or is it a separate bug?
    It seems to be similar to an old TeXLive bug described here.

     
  • Mike

    Mike - 2016-11-09

    Update: After a manual deinstallation and re-installation of dvimdfmx the problem is gone.