- dev-context - NTG Mailing Lists

attachments in PDF/A-3
by Pablo Rodriguez 22 Apr '19

22 Apr '19

Dear list, my sample to add attachments to a PDF/A-3 valid document is the following: \setuptagging[state=start] \setupbodyfont[30pt] \setupbackend [format=PDF/A-3a, intent=sRGB IEC61966-2.1, profile={sRGB.icc,default_gray.icc}, level=0] \setupcolors[pagecolormodel=auto] \setupinteraction[state=start] \starttext \startTEXpage[offset=1em] an attachment\attachment[file=xml-mkiv.pdf] \stopTEXpage \stoptext There are five reported errors when tested with the latest development version of veraPDF (http://downloads.verapdf.org/dev/verapdf-installer.zip) - Annotation should have /F value (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an…) unless their Rect key value 1 equal to value 3 and value 2 equal to value 4, or the annotation subtype is /Popup or /Link. - Although not reported, the /F value should conform these considerations: If present, the F key's Print flag bit shall be set to 1 and its Hidden, Invisible, ToggleNoView, and NoView flag bits shall be set to 0. https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an… - Annotations need an appearance dictionary (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an…) unless the same exception for the /F value apply. - The /EmbeddedFile dictionary should specify the MIME type in its /Subtype entry (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an…) - The /AFRelationship key is missing from the /Filespec dictionary (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an…) Possible values are: Source, Data, Alternative, Supplement, EncryptedPayload, FormData, Schema or Unspecified (from https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf) - The /Filespec lacks association with the PDF document or any of its parts, such as pages (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an…) From https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf, it seems that either the /Catalog or a /Page dictionary (there are other ones, but I would limit attachments in ConTeXt to those two [if not to the /Catalog itself only]) should contain an /AF entry with the reference to the /Filespec object(s). I assume that the value type for the /AF entry is an array of one or multiple object references. These are all the issues veraPDF finds when validating the PDF document generated from the source above. I hope it helps. Many thanks for your help, Pablo -- http://www.ousia.tk

3 12

Quoting problems in grph-con.lua
by Kevin Boulain 21 Apr '19

21 Apr '19

Hi, >From my understanding, there are some superfluous quotes in context/base/mkiv/grph-con.lua, cancelling the proper quoting done by validcommand in context/base/mkiv/util-sbx.lua. For my document, it tries to run something like (the space in the 'Google Drive' directory breaks the generation): inkscape ""[...]/Google Drive/[...].svg"" --export-dpi=600 --export-pdf=""[...]/Google Drive/[...].svg.pdf"" Applying this patch fixes the double quotes issue: local runner = sandbox.registerrunner { name = "svg to something", program = "inkscape", template = longtostring [[ - "%oldname%" + %oldname% --export-dpi=%resolution% - --export-%format%="%newname%" + --export-%format%=%newname% ]], However, it seems there are more similar quotes in the other templates of the file. mtx-context | current version: 2019.04.16 08:54 (I hope this is the proper way of reporting.) Regards.

2 4

lmtx and page injections
by Wolfgang Schuster 04 Apr '19

04 Apr '19

Hi Hans, the new luametatex release doesn't work with the \pageinjection command. The resulting pdf shows the same content on all pages, e.g. in the following example I get the first page twice. \starttext Before \pageinjection [empty] After \stoptext Wolfgang

1 0

CGModules update: t-handlecsv version 2019.03.30 published.
by modules＠contextgarden.net 01 Apr '19

01 Apr '19

Pablo Rodriguez submitted an update to the t-handlecsv package. Version number: 2019.03.30 License type: GNU General Public License Wants to be in ConTeXt distribution: yes Wants to be synced with CTAN: no Summary description: handle .csv files in ConTeXt MkIV Announcement text: ---------------------------------------------------------------------- Remote revision: 4f53f04, log message: fixed spurious linebreak in \doloopif ----------------------------------------------------------------------

1 0

two proposals for attachments in PDF/A-3
by Pablo Rodriguez 25 Mar '19

25 Mar '19

Hans, I realized that the values for the /AFRelationship key that I provided in a previous message, are the ones defined for PDF-2.0 (Source, Data, Alternative, Supplement, EncryptedPayload, FormData, Schema or Unspecified). According to https://www.loc.gov/preservation/digital/formats/fdd/fdd000360.shtml, values for the /AFRelationShip key in PDF/A-3 are only: Source, Data, Alternative, Supplement, and Unspecified. If you allow me a suggestion, maybe it would be useful to have two new options in the \setupattachment command: relationship = source data alternative supplement unspecified association = document page The default values could be document and unspecified. The user should know what to do when changing these defaults. Of course, the /AF entry can be placed in other PDF objects, but document and page are enough options to start with. Many thanks for your help, Pablo -- http://www.ousia.tk

2 2

proposal for attachments (not restricted to PDF/A)
by Pablo Rodriguez 25 Mar '19

25 Mar '19

Hans, I think it would be great to add to all attachments (whether the file is PDF/A or not), the following information in /EmbeddedFile, /Params dictionary (as explained table 46 from page 104 from the PDF spec [https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#name…] the following entries: - /Size - /ModDate - /Subtype with MIME (as already reported). Many thanks for your help, Pablo -- http://www.ousia.tk

2 2

comment for attachments in PDF/A-3
by Pablo Rodriguez 24 Mar '19

24 Mar '19

Hans, I have other comments for embedded files, but I need more time to compose them. Right now I would like to comment an issue with the following source: \setupinteraction[state=start] \starttext \startTEXpage[offset=1em] \attachment[/home/ousia/xml-mkiv.pdf] [name=new-name.pdf, title=Title, subtitle=Subtitle, method=hidden, author=author] \stopTEXpage \stoptext If method=hidden, a /Names dictionary is added, with the following content: 9 0 obj << /Names [ (/home/ousia/xml-mkiv.pdf) 2 0 R ] >> endobj In some scenarios, this could be a security issue. Wouldn’t it be possible that the content of the /Names entries would be replaced by the option keys title or name from \attachment? Many thanks for your help, Pablo -- http://www.ousia.tk

3 5

typo-brk.lua
by Wolfgang Schuster 22 Mar '19

22 Mar '19

Hi, a local definition for numbers has to be added to get language dependant settings to \definebreakpoint. function breakpoints.handler(head) local done = false local attr = nil local map = nil local current = head while current do local char, id = isglyph(current) if char then -- local a = getattr(current,a_breakpoints) local a = takeattr(current,a_breakpoints) if a and a > 0 then if a ~= attr then local data = mapping[a] if data then map = data.characters else map = nil end attr = a end if map then local cmap = map[char] if cmap then -- setattr(current,a_breakpoints,unsetvalue) -- should not be needed -- for now we collect but when found ok we can move the handler here -- although it saves nothing in terms of performance local lang = getlang(current) + local numbers = languages.numbers local smap = lang and lang >= 0 and lang < 0x7FFF and (cmap[numbers[lang]] or cmap[""]) if smap then Wolfgang

1 0

publ-imp-commands.mkvi
by Wolfgang Schuster 15 Mar '19

15 Mar '19

Hi, the following change is needed in the publication file \let\<< -\let\<> +\let\>> because the wrong assignment creates a wrong bracket in math mode for left/right delimiters. \starttext \m { \left\< x \right\> } \m { \left\> x \right\< } \stoptext Wolfgang

2 1

Argument of \setupbtx[command=...] appears twice
by Wolfgang Schuster 15 Mar '19

15 Mar '19

Hi Hans and Alan, the argument of the command key for the \setupbtx command is shown twice in the running text. \usebtxdataset[mkiv-publications.bib] \setupbtx[command=\groupedcommand{<}{>}] \starttext \cite[article] \placelistofpublications \stoptext A possible fix for this is to change the name of one instance (publ-ini.mkiv) where the key is used from command to textcommand. \def\publ_cite_handle_variant_indeed[#1]% {\letbtxparameter\c!alternative\currentbtxcitealternative \edef\currentbtxreference{#1}% \saverunningstyleandcolor \usebtxstyleandcolor\c!style\c!color \uselanguageparameter\btxdatasetparameter % new \btxparameter\c!left - \btxparameter\c!command{\dobtxcitevariantblob}% {\publ_cite_handle_variant_blob}% + \btxparameter\c!textcommand{\dobtxcitevariantblob}% {\publ_cite_handle_variant_blob}% \btxparameter\c!right \endgroup} Wolfgang

1 0