From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/106271
Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail
From: Rik Kabel <ConTeXt@rik.users.panix.com>
Newsgroups: gmane.comp.tex.context
Subject: Re: attachments working again (issue with
 /EmbeddedFiles)
Date: Wed, 12 Feb 2020 17:22:13 -0500
Message-ID: <08cf8ae6-ca6f-db76-7fda-59320e479a93@rik.users.panix.com>
References: <1ae56857-1fcb-cce5-e964-86b6b67c6c1d@gmx.es>
 <a9f7e816-a4ca-06d7-e925-006f8f0ebb7d@rik.users.panix.com>
 <b0049403-ef29-4454-29a4-41792a8881ce@gmx.es>
 <10b7abb5-70d6-e1a3-a083-1288e762ac9b@xs4all.nl>
 <e3d60180-ad6e-2f36-689d-1a2ef83983fb@gmx.net>
 <7282fa22-4d0a-57db-93a7-7aab2f4ef514@gmx.es>
 <c00aa08c-61f7-489e-0843-0fe59173812f@rik.users.panix.com>
 <bb987d2c-522e-496d-0514-65f753f66fcb@gmx.es>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0902382461979736569=="
Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202";
	logging-data="23783"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Firefox/68.0 Thunderbird/68.4.2
To: ntg-context@ntg.nl
Original-X-From: ntg-context-bounces@ntg.nl Wed Feb 12 23:23:04 2020
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1j20PP-000641-T5
	for gctc-ntg-context-518@m.gmane-mx.org; Wed, 12 Feb 2020 23:23:03 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id CBA291807AD;
	Wed, 12 Feb 2020 23:22:38 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id B3x8mPOChLIM; Wed, 12 Feb 2020 23:22:37 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id C003418086E;
	Wed, 12 Feb 2020 23:22:37 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 8123718086E
 for <ntg-context@ntg.nl>; Wed, 12 Feb 2020 23:22:36 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 7thFoMqj-ILV for <ntg-context@ntg.nl>;
 Wed, 12 Feb 2020 23:22:35 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=166.84.1.89;
 helo=mailbackend.panix.com; envelope-from=context@rik.users.panix.com;
 receiver=<UNKNOWN> 
Original-Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 11B9C1807AD
 for <ntg-context@ntg.nl>; Wed, 12 Feb 2020 23:22:34 +0100 (CET)
Original-Received: from [192.168.201.21] (cpe-72-228-11-252.nycap.res.rr.com
 [72.228.11.252])
 by mailbackend.panix.com (Postfix) with ESMTPSA id 48HvK34dTgznmJ
 for <ntg-context@ntg.nl>; Wed, 12 Feb 2020 17:22:31 -0500 (EST)
In-Reply-To: <bb987d2c-522e-496d-0514-65f753f66fcb@gmx.es>
Content-Language: en-US
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:106271
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/106271>

This is a multi-part message in MIME format.
--===============0902382461979736569==
Content-Type: multipart/alternative;
 boundary="------------D7D70808B94C27C22AACE3E1"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------D7D70808B94C27C22AACE3E1
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 2/12/2020 14:20, Pablo Rodriguez wrote:
> On 2/8/20 10:13 PM, Rik Kabel wrote:
>>
>> Not quite ready yet. When the hidden method is used, it passes the
>> online validator[1], but fails VeraPDF[2] for clause 6.8-1. When
>> visible, it fails the online validator stating that the appearance
>> dictionary doesn't contain an entry, and fails VeraPDF for clauses 6.8-1
>> and 6.3.3-1.
> Hi Rik,
>
> as for 6.8-1, did you set MIME type of the attached file (such as in
> "type={application/pdf}")?
>
>> Oddly, the bookmarks do not appear either way under MkIV, and they do
>> not appear when the attachment is visible under LMTX. The bookmarks do
>> appear with a hidden attachment under LMTX.
> As far as I understand, only LMTX will receive regular updates now. (But
> Hans knows better 😅.)
>
> I get both visible attachments and bookmarks in LMTX (latest and
> previous latest [“latest” is the new beta]).
>
> Could you provide a minimal sample that shows the issue?
>
> Pablo
> --
> http://www.ousia.tk

Hello Pablo (and everyone else),

Here is my test file. You can use "context --mode=hidden file.tex" to 
hide the pushpin, or  leave out the mode to expose it.

    %%  Test file for pdf3a compliance.
    %%
    %%  So far, this fails when the attachment is included. Other than the
    %%    handling of attachments, ConTeXt does a good job with the various
    %%    PDF/A variants.
    %%
    %%  Testing done locally with the VeraPDF validator (most recently with
    %%    version 1.14.8) and online with the 3-Heights validator found at
    %%    https://www.pdf-online.com/osa/validate.aspx (current 2020-01-20).
    %%
    %%  This is not a minimal example.
    \definemode          [hidden][keep]
    \setuplanguage       [en]
    \setuppapersize      [A6,landscape]
    \setuppagenumbering  [location=]
    \setuptagging        [state=start]
    \setupinteraction    [state=start]
    %setupbackend        [format={pdf/a-3u},
    \setupbackend        [format={pdf/a-3a},
                           level=0,
                           profile={default_gray.icc},
                           intent={ISO coated v2 300\letterpercent\space (ECI)}]
    \setupstructure      [state=start,
                           method=auto]
    \setupcolors         [pagecolormodel=auto,
                           start=yes,
                           rgb=no,
                           cmyk=no]
    \setupbodyfont       [palatino,18pt]
    \starttext

      This document was produced using version \contextversion\ of
      \ConTeXt\ \doifelse{\texenginename}{luametatex}{LMTX}{\contextmark}
      with the version \texengineversion\ of \texenginename.

      

      \attachment        [file=./\jobname.tex,
                          method={\doifmodeelse{hidden}{hidden}{normal}},
                          type={text/plain;charset=UTF-8}]
      The source code for this document is attached as a plain text file. It
      should show up in the pdf bookmarks for the document\doifmodeelse
      {hidden}{}{ and through the icon at the start of this paragraph}.

    \stoptext

I have tested with LMTX 2020.02.11 16:41.

*Mime type*

  * You can see that the mime type is set in the ConTeXt file and it
    appears in the resulting pdf, although not knowing enough about the
    pdf file structure I do not know if it appears correctly.

*Validation*

  * With the pin hidden, VeraPDF 1.14.8 complains about two occurrences
    of clause 6.8 test 1 failure. With the pin exposed, it complains
    about one occurrence of clause 6.8 test 1 failure and one occurrence
    of clause 6.3.3 test 1 failure (appearance dictionary).
  * With the pin hidden, pdf-online.com declares the  valid. With the
    pin exposed, pdf-online.com fails it because "[t]he appearance
    dictionary doesn't contain an entry." They are aware of the
    difference between their report and that of VeraPDF.

*Viewing*

  * Acrobat Reader DC shows the pushpin, changes the pointer, and
    displays flyover text when appropriate and shows the bookmark for
    both variants.
  * SumatraPDF shows the pushpin, changes the pointer, and displays
    flyover text when appropriate. It does not show the bookmark when
    the pushpin is visible, but does show it when it is hidden.
  * MuPDF does not show the pushpin, instead leaving empty space, when
    it should be visible. It does not show bookmarks or any other
    indication that there is an attachment for either variant. (MuPDF
    can show bookmarks for some other documents.)
  * Firefox 73 does not show the pushpin when it should be visible, but
    does change the pointer and show the attachment name as a flyover.
    Firefox 73 does show the bookmark for both variants.
  * Chrome 80 does not show the pushpin when it should be visible, but
    does show the attachment name as a flyover. Chrome 80 does not show
    the bookmark for either variant. (Chrome 80 does show bookmarks for
    some other PDF document.)
  * The three viewers listed here that do not show the pushpin do
    reserve the appropriate space ­ ­– changing the symbol to the
    Paperclip demonstrates that even though the paperclip is not displayed.

Clearly there are issues with the various viewers. How much ConTeXt can 
or should do to manage the differences is not clear to me.

-- 
Rik Kabel



--------------D7D70808B94C27C22AACE3E1
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    On 2/12/2020 14:20, Pablo Rodriguez wrote:<br>
    <blockquote type="cite"
      cite="mid:bb987d2c-522e-496d-0514-65f753f66fcb@gmx.es">
      <pre class="moz-quote-pre" wrap="">On 2/8/20 10:13 PM, Rik Kabel wrote:
</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">

Not quite ready yet. When the hidden method is used, it passes the
online validator[1], but fails VeraPDF[2] for clause 6.8-1. When
visible, it fails the online validator stating that the appearance
dictionary doesn't contain an entry, and fails VeraPDF for clauses 6.8-1
and 6.3.3-1.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
Hi Rik,

as for 6.8-1, did you set MIME type of the attached file (such as in
"type={application/pdf}")?

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">Oddly, the bookmarks do not appear either way under MkIV, and they do
not appear when the attachment is visible under LMTX. The bookmarks do
appear with a hidden attachment under LMTX.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
As far as I understand, only LMTX will receive regular updates now. (But
Hans knows better 😅.)

I get both visible attachments and bookmarks in LMTX (latest and
previous latest [“latest” is the new beta]).

Could you provide a minimal sample that shows the issue?

Pablo
--
<a class="moz-txt-link-freetext" href="http://www.ousia.tk">http://www.ousia.tk</a>
</pre>
    </blockquote>
    <br>
    <p>Hello Pablo (and everyone else),</p>
    <p>
      Here is my test file. You can use "context --mode=hidden file.tex"
      to hide the pushpin, or  leave out the mode to expose it.</p>
    <blockquote>
      <pre>%%  Test file for pdf3a compliance.
%%
%%  So far, this fails when the attachment is included. Other than the
%%    handling of attachments, ConTeXt does a good job with the various
%%    PDF/A variants.
%%
%%  Testing done locally with the VeraPDF validator (most recently with
%%    version 1.14.8) and online with the 3-Heights validator found at
%%    <a class="moz-txt-link-freetext" href="https://www.pdf-online.com/osa/validate.aspx">https://www.pdf-online.com/osa/validate.aspx</a> (current 2020-01-20).
%%
%%  This is not a minimal example.
\definemode          [hidden][keep]
\setuplanguage       [en]
\setuppapersize      [A6,landscape]
\setuppagenumbering  [location=]
\setuptagging        [state=start]
\setupinteraction    [state=start]
%setupbackend        [format={pdf/a-3u},
\setupbackend        [format={pdf/a-3a},
                      level=0,
                      profile={default_gray.icc},
                      intent={ISO coated v2 300\letterpercent\space (ECI)}]
\setupstructure      [state=start,
                      method=auto]
\setupcolors         [pagecolormodel=auto,
                      start=yes,
                      rgb=no,
                      cmyk=no]
\setupbodyfont       [palatino,18pt]
\starttext

 This document was produced using version \contextversion\ of
 \ConTeXt\ \doifelse{\texenginename}{luametatex}{LMTX}{\contextmark}
 with the version \texengineversion\ of \texenginename.

 

 \attachment        [file=./\jobname.tex,
                     method={\doifmodeelse{hidden}{hidden}{normal}},
                     type={text/plain;charset=UTF-8}]
 The source code for this document is attached as a plain text file. It
 should show up in the pdf bookmarks for the document\doifmodeelse
 {hidden}{}{ and through the icon at the start of this paragraph}.

\stoptext

</pre>
    </blockquote>
    <p>I have tested with LMTX 2020.02.11 16:41. <br>
    </p>
    <p><b>Mime type</b><br>
    </p>
    <ul>
      <li>You can see that the mime type is set in the ConTeXt file and
        it appears in the resulting pdf, although not knowing enough
        about the pdf file structure I do not know if it appears
        correctly.</li>
    </ul>
    <p><b>Validation</b></p>
    <ul>
      <li>With the pin hidden, VeraPDF 1.14.8 complains about two
        occurrences of clause 6.8 test 1 failure. With the pin exposed,
        it complains about one occurrence of clause 6.8 test 1 failure
        and one occurrence of clause 6.3.3 test 1 failure (appearance
        dictionary).</li>
      <li>With the pin hidden, pdf-online.com declares the  valid. With
        the pin exposed, pdf-online.com fails it because "[t]he
        appearance dictionary doesn't contain an entry." They are aware
        of the difference between their report and that of VeraPDF.</li>
    </ul>
    <p><b>Viewing</b></p>
    <ul>
      <li>Acrobat Reader DC shows the pushpin, changes the pointer, and
        displays flyover text when appropriate and shows the bookmark
        for both variants.</li>
      <li>SumatraPDF shows the pushpin, changes the pointer, and
        displays flyover text when appropriate. It does not show the
        bookmark when the pushpin is visible, but does show it when it
        is hidden.<br>
      </li>
      <li>MuPDF does not show the pushpin, instead leaving empty space,
        when it should be visible. It does not show bookmarks or any
        other indication that there is an attachment for either variant.
        (MuPDF can show bookmarks for some other documents.)<br>
      </li>
      <li>Firefox 73 does not show the pushpin when it should be
        visible, but does change the pointer and show the attachment
        name as a flyover. Firefox 73 does show the bookmark for both
        variants.</li>
      <li>Chrome 80 does not show the pushpin when it should be visible,
        but does show the attachment name as a flyover. Chrome 80 does
        not show the bookmark for either variant. (Chrome 80 does show
        bookmarks for some other PDF document.)</li>
      <li>The three viewers listed here that do not show the pushpin do
        reserve the appropriate space ­ ­– changing the symbol to the
        Paperclip demonstrates that even though the paperclip is not
        displayed.<br>
      </li>
    </ul>
    <p>Clearly there are issues with the various viewers. How much
      ConTeXt can or should do to manage the differences is not clear to
      me.</p>
    <p>-- <br>
      Rik Kabel<br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------D7D70808B94C27C22AACE3E1--

--===============0902382461979736569==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============0902382461979736569==--