Re: [NTG-context] PDF forms not creating proper children
Hi, > On 9 Jun 2021, at 16:41, Pablo Rodriguez wrote: > > > Only mupdf-gl sees the signature annotation after signing it. Acrobat, > Evince, Okular and xpdf cannot deal with the signature. Just FYI: On the Mac, I can sign the processed example using Adobe Acrobat Reader DC, and it can save a signed pdf as well as re-open it, including showing that verification bar that says it is a signed pdf. mupdf-gl ‘sees’ the original field also, but mine is compiled without openssl so it cannot actually sign. It happily correctly opens the signed version from AR DC, of course. Apple Preview does not recognize the signature field (well, it has zero support for signing to begin with, so that is not a surprise). — Taco Hoekwater E: t...@bittext.nl genderfluid (all pronouns) ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On Wed, 2021-06-09 at 16:41 +0200, Pablo Rodriguez wrote: > On 6/8/21 11:07 PM, Leonard Janis Robert König wrote: > > On Tue, 2021-06-08 at 17:41 +0200, Pablo Rodriguez wrote: > > > [...] > > > Try to open a PDF document signed with mupdf-gl in Acrobat > > > (Reader or > > > not). You will see that the signature is wrong. > > > > Hm, I tested with Okular, Firefox and MasterPDF as I don't have > > Acrobat > > on Linux [...] > Hi Pablo, > > Acrobat for Linux is available (although the version is too old) at > ftp://ftp.adobe.com/pub/adobe/reader/unix/9.x/9.5.5/enu/. > > Acrobat isn’t able to deal with the signature annotation and with the yeah, I try to stay away from this pile of security holes :) > > > Sorry, objects is a very special term in PDF parlance. It has > > > nothing > > > to do with signatures. > > Here is a description: > https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#search=4.35 > (link should work with Firefox). Thanks a bunch! I wonder why PDF 2.0 still isn't uploaded there, but probably it's now ISO only(?) > > But you might check yourself with the following sample: > > \setuppapersize[A10, landscape] > \setuplayout[page] > \setupinteraction[state=start] > \starttext > \setupfield[sl][horizontal] > [frame=on, width=\textwidth, height=\textheight] > \definefield[x][signature][sl] > \field[x] > \stoptext > > The attached certificate has the password 123456. > > Only mupdf-gl sees the signature annotation after signing it. > Acrobat, > Evince, Okular and xpdf cannot deal with the signature. On my system (but rather recent, Arch-Testing) Okular did see the signature actually! However the validator doesn't recognize a thing. > > https://validator.docusign.com/ gives a warning: > > This document doesn't have any digital signatures. > > I hope it might help, Luckily(?) I don't have to deal with signatures that much right now, but my problem is more related to other kinds of forms which seems to be able to be worked around by not using TABLE. ~ Leo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On 6/9/21 12:28 PM, Leonard Janis Robert König wrote: > On Tue, 2021-06-08 at 23:29 +0100, Adam Reviczky wrote: >> Not sure how good it is, but in the poppler discussion this site was >> mentioned to verify the signature details: >> https://validator.docusign.com/ > > Oh, that's a great tool, thanks! Many thanks for the link to the tool, Adam. Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On 6/8/21 11:07 PM, Leonard Janis Robert König wrote: > On Tue, 2021-06-08 at 17:41 +0200, Pablo Rodriguez wrote: >> [...] >> Try to open a PDF document signed with mupdf-gl in Acrobat (Reader or >> not). You will see that the signature is wrong. > > Hm, I tested with Okular, Firefox and MasterPDF as I don't have Acrobat > on Linux [...] Hi Leo, Acrobat for Linux is available (although the version is too old) at ftp://ftp.adobe.com/pub/adobe/reader/unix/9.x/9.5.5/enu/. Acrobat isn’t able to deal with the signature annotation and with the >> Sorry, objects is a very special term in PDF parlance. It has nothing >> to do with signatures. Here is a description: https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#search=4.35 (link should work with Firefox). But you might check yourself with the following sample: \setuppapersize[A10, landscape] \setuplayout[page] \setupinteraction[state=start] \starttext \setupfield[sl][horizontal] [frame=on, width=\textwidth, height=\textheight] \definefield[x][signature][sl] \field[x] \stoptext The attached certificate has the password 123456. Only mupdf-gl sees the signature annotation after signing it. Acrobat, Evince, Okular and xpdf cannot deal with the signature. https://validator.docusign.com/ gives a warning: This document doesn't have any digital signatures. I hope it might help, Pablo -- http://www.ousia.tk JohnDoe.pfx Description: application/pkcs12 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On Tue, 2021-06-08 at 23:29 +0100, Adam Reviczky wrote: > Not sure how good it is, but in the poppler discussion this site was > mentioned to verify the signature details: > https://validator.docusign.com/ > > I have tried using with poppler's pdfsig and Okular. > Oh, that's a great tool, thanks! Leo > Adam > > On Tue, Jun 8, 2021 at 10:14 PM Leonard Janis Robert König < > l...@ljrk.org> wrote: > > On Tue, 2021-06-08 at 17:41 +0200, Pablo Rodriguez wrote: > > > On 6/7/21 10:43 PM, Leonard Janis Robert König wrote: > > > > Hi Adam, Hi Pablo, > > > > > > > > I just noticed your replies, sorry for the late answer! > > > > > > > > I could sign forms with both okular as well as mupdf just fine, > > > > although the behavior is different. The former assumes that > > > > the > > > > field > > > > is already an existing signature and segfaults when you look at > > the > > > > properties, but cann successfully add another signature using > > > > the > > > > "Tools" menu. > > > > > > > Hi Pablo, > > > > > I’m afraid that I don’t use Okular. > > > > > > > With the latter you can click on the form field to > > > > trigger a menu to select the signature you want to sign with, > > > > and > > > > it > > > > "replaces" the "empty" signature generated by ConTeXt. Both > > > > work > > > > fine, > > > > even with my newer ConTeXt. > > > > > > mupdf-gl signs the document, but in a way that only mupdf-gl > > > understands it. > > > > > > Try to open a PDF document signed with mupdf-gl in Acrobat > > > (Reader > > or > > > not). You will see that the signature is wrong. > > > > Hm, I tested with Okular, Firefox and MasterPDF as I don't have > > Acrobat > > on Linux, and both understand the signature, which is why I thought > > it'd be correct. > > > > > > > > > > On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez > > > > > wrote: > > > > > > [...] > > > > > > From my experience, only Acrobat deals with child objects > > > > > > in > > > > > > signatures > > > > > > generating a valid signature (and rewriting the two objects > > > > > > into a > > > > > > single one). > > > > > > > > As mentioned above, it seems that mupdf (now?) actually > > > > rewrites > > > > "both" > > > > signatures into one, however Okular doesn't. > > > > > > Sorry, objects is a very special term in PDF parlance. It has > > nothing > > > to > > > do with signatures. > > > > > > Just in case it might help, > > > > Ah, I see. I'm still a bit unsure what to make of the "fields > > nested > > in TABLEs" issue, but maybe further debugging will show at some > > point. > > > > ~ Leo > > > > ___ > > __ > > __ > > If your question is of interest to others as well, please add an > > entry to the Wiki! > > > > maillist : ntg-context@ntg.nl / > > http://www.ntg.nl/mailman/listinfo/ntg-context > > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > > archive : https://bitbucket.org/phg/context-mirror/commits/ > > wiki : http://contextgarden.net > > ___ > > __ > > __ > _ > __ > If your question is of interest to others as well, please add an > entry to the Wiki! > > maillist : ntg-context@ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > _ > __ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
Not sure how good it is, but in the poppler discussion this site was mentioned to verify the signature details: https://validator.docusign.com/ I have tried using with poppler's pdfsig and Okular. Adam On Tue, Jun 8, 2021 at 10:14 PM Leonard Janis Robert König wrote: > On Tue, 2021-06-08 at 17:41 +0200, Pablo Rodriguez wrote: > > On 6/7/21 10:43 PM, Leonard Janis Robert König wrote: > > > Hi Adam, Hi Pablo, > > > > > > I just noticed your replies, sorry for the late answer! > > > > > > I could sign forms with both okular as well as mupdf just fine, > > > although the behavior is different. The former assumes that the > > > field > > > is already an existing signature and segfaults when you look at the > > > properties, but cann successfully add another signature using the > > > "Tools" menu. > > > > Hi Pablo, > > > I’m afraid that I don’t use Okular. > > > > > With the latter you can click on the form field to > > > trigger a menu to select the signature you want to sign with, and > > > it > > > "replaces" the "empty" signature generated by ConTeXt. Both work > > > fine, > > > even with my newer ConTeXt. > > > > mupdf-gl signs the document, but in a way that only mupdf-gl > > understands it. > > > > Try to open a PDF document signed with mupdf-gl in Acrobat (Reader or > > not). You will see that the signature is wrong. > > Hm, I tested with Okular, Firefox and MasterPDF as I don't have Acrobat > on Linux, and both understand the signature, which is why I thought > it'd be correct. > > > > > > > On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez > > > > wrote: > > > > > [...] > > > > > From my experience, only Acrobat deals with child objects in > > > > > signatures > > > > > generating a valid signature (and rewriting the two objects > > > > > into a > > > > > single one). > > > > > > As mentioned above, it seems that mupdf (now?) actually rewrites > > > "both" > > > signatures into one, however Okular doesn't. > > > > Sorry, objects is a very special term in PDF parlance. It has nothing > > to > > do with signatures. > > > > Just in case it might help, > > Ah, I see. I'm still a bit unsure what to make of the "fields nested > in TABLEs" issue, but maybe further debugging will show at some point. > > ~ Leo > > > ___ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___ > ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On Tue, 2021-06-08 at 17:41 +0200, Pablo Rodriguez wrote: > On 6/7/21 10:43 PM, Leonard Janis Robert König wrote: > > Hi Adam, Hi Pablo, > > > > I just noticed your replies, sorry for the late answer! > > > > I could sign forms with both okular as well as mupdf just fine, > > although the behavior is different. The former assumes that the > > field > > is already an existing signature and segfaults when you look at the > > properties, but cann successfully add another signature using the > > "Tools" menu. > Hi Pablo, > I’m afraid that I don’t use Okular. > > > With the latter you can click on the form field to > > trigger a menu to select the signature you want to sign with, and > > it > > "replaces" the "empty" signature generated by ConTeXt. Both work > > fine, > > even with my newer ConTeXt. > > mupdf-gl signs the document, but in a way that only mupdf-gl > understands it. > > Try to open a PDF document signed with mupdf-gl in Acrobat (Reader or > not). You will see that the signature is wrong. Hm, I tested with Okular, Firefox and MasterPDF as I don't have Acrobat on Linux, and both understand the signature, which is why I thought it'd be correct. > > > > On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez > > > wrote: > > > > [...] > > > > From my experience, only Acrobat deals with child objects in > > > > signatures > > > > generating a valid signature (and rewriting the two objects > > > > into a > > > > single one). > > > > As mentioned above, it seems that mupdf (now?) actually rewrites > > "both" > > signatures into one, however Okular doesn't. > > Sorry, objects is a very special term in PDF parlance. It has nothing > to > do with signatures. > > Just in case it might help, Ah, I see. I'm still a bit unsure what to make of the "fields nested in TABLEs" issue, but maybe further debugging will show at some point. ~ Leo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On 6/7/21 10:43 PM, Leonard Janis Robert König wrote: > Hi Adam, Hi Pablo, > > I just noticed your replies, sorry for the late answer! > > I could sign forms with both okular as well as mupdf just fine, > although the behavior is different. The former assumes that the field > is already an existing signature and segfaults when you look at the > properties, but cann successfully add another signature using the > "Tools" menu. Hi Leo, I’m afraid that I don’t use Okular. > With the latter you can click on the form field to > trigger a menu to select the signature you want to sign with, and it > "replaces" the "empty" signature generated by ConTeXt. Both work fine, > even with my newer ConTeXt. mupdf-gl signs the document, but in a way that only mupdf-gl understands it. Try to open a PDF document signed with mupdf-gl in Acrobat (Reader or not). You will see that the signature is wrong. >> On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez wrote: >>> [...] >>> From my experience, only Acrobat deals with child objects in >>> signatures >>> generating a valid signature (and rewriting the two objects into a >>> single one). > > As mentioned above, it seems that mupdf (now?) actually rewrites "both" > signatures into one, however Okular doesn't. Sorry, objects is a very special term in PDF parlance. It has nothing to do with signatures. Just in case it might help, Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
Hi Adam, Hi Pablo, I just noticed your replies, sorry for the late answer! > On the viewers, I cannot recall exactly what I've done earlier in the > year, > but indeed, most likely I have tried evince after signing it from the > command line. From > https://gitlab.gnome.org/GNOME/evince/-/issues/143 there > is still no support for the signing itself, though okular should have > some > support. I could sign forms with both okular as well as mupdf just fine, although the behavior is different. The former assumes that the field is already an existing signature and segfaults when you look at the properties, but cann successfully add another signature using the "Tools" menu. With the latter you can click on the form field to trigger a menu to select the signature you want to sign with, and it "replaces" the "empty" signature generated by ConTeXt. Both work fine, even with my newer ConTeXt. > On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez wrote: > > > > > > > Using the https://live.contextgarden.net/ with (LuaTeX 2.06 > > > 20200630 + > > > ConTeXt MkIV 2020.06.30 17:30) looks good, but evince does not > > > display > > > the field. > > > > Evince never displays the signature field, only when signed. > > > > BTW, using mupdf-gl to sign the PDF document will mess it, since it > > has > > problems to recognize the child object. > > > > From my experience, only Acrobat deals with child objects in > > signatures > > generating a valid signature (and rewriting the two objects into a > > single one). As mentioned above, it seems that mupdf (now?) actually rewrites "both" signatures into one, however Okular doesn't. I could, however, isolate the original issue I posted on the ML: Actually forms still work, but they don't, if embedded into TABLEs. Here's a MWE: \setupinteraction[state=start] \definefield[lineField][line][][][] \starttext \bTABLE[] \bTR \bTD \field[lineField] \eTD \eTR \eTABLE \stoptext This produces Syntax Error: Form field child is not a dictionary when you run pdfinfo on it, and Firefox can't properly render the forms either. However, if you comment the lines defining the begin and end of the TABLE, the form is properly displayed in FF and pdfinfo doesn't produce any errors anymore. This was apparently not an issue when the original beschwerdeform.pdf in the form/ subdir of [1] was built, but both my local installation and live.contextgarden.net produce the "faulty" PDF. ~ Leo [1]: https://github.com/fiee/ConTeXt ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
Hi Pablo, First of all, my bad, the test suite example works just fine in Adobe, including with ConTeXt latest. I have messed up my form by overriding the PDF version to 2.0, shouldn't have done that. On the viewers, I cannot recall exactly what I've done earlier in the year, but indeed, most likely I have tried evince after signing it from the command line. From https://gitlab.gnome.org/GNOME/evince/-/issues/143 there is still no support for the signing itself, though okular should have some support. In any case, thanks for the hints (I probably should've done more testing)! Adam On Sun, May 2, 2021 at 5:50 PM Pablo Rodriguez wrote: > On 5/2/21 12:20 AM, Adam Reviczky wrote: > > Hi, > > > > I cannot get the signature working either, but almost certain it did > > work in February this year, as I have done some with MKIV. > > [...] > > Hi Adam, > > I’m on a Linux computer, so I’m not able to check this now. > > If the signature isn’t working, you mean that the output PDF document > from fields-007.tex cannot be signed with Acrobat DC, don’t you? > > Sorry for asking the obvious question, but this worked perfectly fine > each time I tested. > > > Using the https://live.contextgarden.net/ with (LuaTeX 2.06 20200630 + > > ConTeXt MkIV 2020.06.30 17:30) looks good, but evince does not display > > the field. > > Evince never displays the signature field, only when signed. > > BTW, using mupdf-gl to sign the PDF document will mess it, since it has > problems to recognize the child object. > > From my experience, only Acrobat deals with child objects in signatures > generating a valid signature (and rewriting the two objects into a > single one). > > Just in case it might help, > > Pablo > -- > http://www.ousia.tk > > ___ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___ > ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
On 5/2/21 12:20 AM, Adam Reviczky wrote: > Hi, > > I cannot get the signature working either, but almost certain it did > work in February this year, as I have done some with MKIV. > [...] Hi Adam, I’m on a Linux computer, so I’m not able to check this now. If the signature isn’t working, you mean that the output PDF document from fields-007.tex cannot be signed with Acrobat DC, don’t you? Sorry for asking the obvious question, but this worked perfectly fine each time I tested. > Using the https://live.contextgarden.net/ with (LuaTeX 2.06 20200630 + > ConTeXt MkIV 2020.06.30 17:30) looks good, but evince does not display > the field. Evince never displays the signature field, only when signed. BTW, using mupdf-gl to sign the PDF document will mess it, since it has problems to recognize the child object. From my experience, only Acrobat deals with child objects in signatures generating a valid signature (and rewriting the two objects into a single one). Just in case it might help, Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] PDF forms not creating proper children
Hi, I cannot get the signature working either, but almost certain it did work in February this year, as I have done some with MKIV. >From the test suite: fields-007.tex \nopdfcompression \setupinteraction[state=start] \starttext \definefield[x][signature] \field[x] \stoptext Using the https://live.contextgarden.net/ with (LuaTeX 2.06 20200630 + ConTeXt MkIV 2020.06.30 17:30) looks good, but evince does not display the field. Adam On Fri, Apr 23, 2021 at 8:52 PM Leonard Janis Robert König wrote: > Hello, > > I currently try to build a document with AcroForms, e.g., the examples > from [1] also linked in the Wiki. The most recent example is in the > form/ subdirectory and dated mid 2020. However, when building the > file(s) with my ConTeXt distribution the file created is broken, in > comparison to the PDF checked in into the Git. > > The more obvious difference is that the PDF in the repository can be > filled in the Firefox 89 beta, while the other PDF doesn't even display > the fields as forms. Running pdfinfo also yields: > > > Syntax Error: Form field child is not a dictionary > > I suspect that due to some breakage the forms children aren't set in > the AcroForms dictionary anymore? My ConTeXt versions are: > > # ArchLinux Repos > > context --version > mtx-context | ConTeXt Process Management 1.04 > mtx-context | > mtx-context | main context file: /usr/share/texmf- > dist/tex/context/base/mkiv/context.mkiv > mtx-context | current version: 2021.03.05 19:11 > mtx-context | main context file: /usr/share/texmf- > dist/tex/context/base/mkxl/context.mkxl > mtx-context | current version: 2021.03.05 19:11 > > # Debian Buster Repos > mtx-context | ConTeXt Process Management 1.02 > mtx-context | > mtx-context | main context file: > /usr/share/texmf/tex/context/base/mkiv/context.mkiv > mtx-context | current version: 2018.04.04 00:51 > > # Docker Image: Current > > mtx-context | ConTeXt Process Management 1.03 > mtx-context | > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkiv/context.mkiv > mtx-context | current version: 2020.01.30 14:13 > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkiv/context.mkxl > mtx-context | current version: 2020.01.30 14:13 > > # Docker Image: Beta > mtx-context | ConTeXt Process Management 1.03 > mtx-context | > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkiv/context.mkiv > mtx-context | current version: 2020.01.30 14:13 > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkiv/context.mkxl > mtx-context | current version: 2020.01.30 14:13 > > # Docker Image: LMTX > mtx-context | ConTeXt Process Management 1.04 > mtx-context | > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkiv/context.mkiv > mtx-context | current version: 2021.04.14 22:58 > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkxl/context.mkxl > mtx-context | current version: 2021.04.14 22:58 > > # Docker Image: Beta from 2019-09 > mtx-context | ConTeXt Process Management 1.03 > mtx-context | > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkiv/context.mkiv > mtx-context | current version: 2019.09.10 20:03 > mtx-context | main context file: /context/tex/texmf- > context/tex/context/base/mkiv/context.mkxl > mtx-context | current version: 2019.09.10 20:03 > > The ConTeXt version of the checked in file on GitHub is (according to > pdfinfo): > > > Creator:LuaTeX 1.10 7138 + ConTeXt MkIV 2019.08.20 17:20 > > Producer: macOS Version 10.14.6 (Build 18G5033) Quartz > PDFContext > > I also remebered another time were I toyed around with it and indeed > that PDF also had broken form field children: > > > > Creator:LuaTeX 1.12 7306 + ConTeXt MkIV 2020.03.10 14:44 > > Producer: LuaTeX-1.12 > > A broken version that I built locally using the :current IslandOfTeX > [2] can be found at [3]. > > The version difference between the broken and not-broken PDFs hints > that the breakage occured between 2019.08.20 and 2019.09.10-beta, while > the Debian breackage might be due to a backport(?) > > Alternatively, this could just be a mistake on my side? > > Cheers > Leo König > > > [1]: https://github.com/fiee/ConTeXt > [2]: https://gitlab.com/islandoftex/images/context/ > [3]: > https://mega.nz/file/ThcghTqb#JqRCSsd59bBbMgTMr3ahaPdU4LPlZd0cpA3ZFBJLJ3A > > > > > ___ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/
[NTG-context] PDF forms not creating proper children
Hello, I currently try to build a document with AcroForms, e.g., the examples from [1] also linked in the Wiki. The most recent example is in the form/ subdirectory and dated mid 2020. However, when building the file(s) with my ConTeXt distribution the file created is broken, in comparison to the PDF checked in into the Git. The more obvious difference is that the PDF in the repository can be filled in the Firefox 89 beta, while the other PDF doesn't even display the fields as forms. Running pdfinfo also yields: > Syntax Error: Form field child is not a dictionary I suspect that due to some breakage the forms children aren't set in the AcroForms dictionary anymore? My ConTeXt versions are: # ArchLinux Repos context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/share/texmf- dist/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.03.05 19:11 mtx-context | main context file: /usr/share/texmf- dist/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.03.05 19:11 # Debian Buster Repos mtx-context | ConTeXt Process Management 1.02 mtx-context | mtx-context | main context file: /usr/share/texmf/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2018.04.04 00:51 # Docker Image: Current mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.01.30 14:13 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.01.30 14:13 # Docker Image: Beta mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.01.30 14:13 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.01.30 14:13 # Docker Image: LMTX mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.04.14 22:58 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.04.14 22:58 # Docker Image: Beta from 2019-09 mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2019.09.10 20:03 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2019.09.10 20:03 The ConTeXt version of the checked in file on GitHub is (according to pdfinfo): > Creator:LuaTeX 1.10 7138 + ConTeXt MkIV 2019.08.20 17:20 > Producer: macOS Version 10.14.6 (Build 18G5033) Quartz PDFContext I also remebered another time were I toyed around with it and indeed that PDF also had broken form field children: > Creator:LuaTeX 1.12 7306 + ConTeXt MkIV 2020.03.10 14:44 > Producer: LuaTeX-1.12 A broken version that I built locally using the :current IslandOfTeX [2] can be found at [3]. The version difference between the broken and not-broken PDFs hints that the breakage occured between 2019.08.20 and 2019.09.10-beta, while the Debian breackage might be due to a backport(?) Alternatively, this could just be a mistake on my side? Cheers Leo König [1]: https://github.com/fiee/ConTeXt [2]: https://gitlab.com/islandoftex/images/context/ [3]: https://mega.nz/file/ThcghTqb#JqRCSsd59bBbMgTMr3ahaPdU4LPlZd0cpA3ZFBJLJ3A ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] PDF Forms - expanding multi-line text fields
I am composing a document that contains pdf forms. Example code in Widgets Uncovered, shows how to specify the height and width of a multi-line text field. Here is a small example: \usemodule[fields] \setupinteraction[state=start] \setupfield [TextSetup] [width=\textwidth,height=5em,background=screen,backgroundscreen=.97,frame=off] \definefield [Block] [text] [TextSetup] \starttext \field [Block] \stoptext In this example the height is 5em. The field will scroll lines up when the height of the lines typed exceeds the height of the field. Click outside the field and the field displays the first n-lines that fit within its height. My question is, is it possible to tell the field to expand beyond its initial field height to display all its lines? A second less pressing question is, is it possible to tell lines to wrap when they exceed the field width? -- With kind regards, Michael Guravage ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] pdf-Forms
Hi!
I wanted to test pdf-forms with the latest minimals from contextgarden
and ran into some interesting errors.
The following code compiles, but I cannot change the fieldvalue:
\starttext
Field \fillinfield[test]{Fieldtext}
\stoptext
When I add \setupinteraction[state=start], the compilation breaks with
an error:
! Undefined control sequence.
var :j:fields_1 -
visible_field = new Array() ; var
visible_fields = 0...
\docommand ...code {\getvalue {\r!java \r!java #1}
}\ifoneJSpreamble
\...@ea \se...
\next2 #1,-\docommand {#1}
\doprocesscommaitem
argument \relax fields_1,
Do_Check_Answer
\doprocesscommalist ...aitem \gobbleoneargument #1
,]\relax \global
\advance ...
\presetJSpreamble ...[\allJSpreambles ]\docommand
\ifoneJSpreamble
\gdef \al... ...
l.6 \stoptext
Neither pdfcontext nor luatex wanted to compile. Can anyone help?
Best regards,
Eyke
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] pdf-Forms
Am 04.01.2009 um 18:44 schrieb Holzminister: When I add \setupinteraction[state=start], the compilation breaks with an error: [...] This is fixed in the last alpha. Neither pdfcontext nor luatex wanted to compile. Can anyone help? Why the pdf prefix for context? Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] pdf-Forms
When I add \setupinteraction[state=start], the compilation breaks with an error: [...] This is fixed in the last alpha. Thanks, it works. Neither pdfcontext nor luatex wanted to compile. Can anyone help? Why the pdf prefix for context? I thought it was nicer to distinguish the normal pdf-output and luatex. Do you know some good tutorials or example documents about forms and JavaScript created with context? mwidget-s.pdf or the wikipage are not that efficient. I want to create forms with a lot of textfields and automatic calculations via JavaScript. Best regards, Eyke ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] pdf-Forms
Am 04.01.2009 um 19:41 schrieb Holzminister: When I add \setupinteraction[state=start], the compilation breaks with an error: [...] This is fixed in the last alpha. Thanks, it works. Neither pdfcontext nor luatex wanted to compile. Can anyone help? Why the pdf prefix for context? I thought it was nicer to distinguish the normal pdf-output and luatex. You could explain it with MkII and MkIV. Do you know some good tutorials or example documents about forms and JavaScript created with context? mwidget-s.pdf or the wikipage are not that efficient. I want to create forms with a lot of textfields and automatic calculations via JavaScript. No but you search in the list archive. Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] pdf forms
I wrote a simple context file for pdf form filling. Translates fine, but the
resulting pdf simply shows text but no fillable forms. What's needed to
actually get forms?
Here's the tex code:
% interface=en tex=pdfetex output=pdftex
\starttext
Field 1: \fillinfield[name]{text that defines field length}
\definefield [Email] [line] [ShortLine] [] [EMAIL PROTECTED]
Field 2: \field [Email] [your email]
\stoptext
Thanks!
Bernhard
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] pdf forms
try \setupinteraction[state=start]
Greetings Lutz
2008/5/29 Bernhard Boser [EMAIL PROTECTED]:
I wrote a simple context file for pdf form filling. Translates fine, but the
resulting pdf simply shows text but no fillable forms. What's needed to
actually get forms?
Here's the tex code:
% interface=en tex=pdfetex output=pdftex
\starttext
Field 1: \fillinfield[name]{text that defines field length}
\definefield [Email] [line] [ShortLine] [] [EMAIL PROTECTED]
Field 2: \field [Email] [your email]
\stoptext
Thanks!
Bernhard
___
If your question is of interest to others as well, please add an entry to
the Wiki!
maillist : ntg-context@ntg.nl /
http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] PDF Forms
Bob Kerstetter wrote: Hi, Is there some way to create PDF docs (as forms maybe?) so end users can add their own contact information and logos just by using Adobe Reader, not Acrobat? These are one to four page documents. Right now I can do this by supplying them with Word docs. see widgets manual; you can edit forms with acrobat reader but not save them; you can however send the data to a server; Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] PDF Forms
Am 24.03.2005 um 23:30 schrieb Bob Kerstetter: Is there some way to create PDF docs (as forms maybe?) so end users can add their own contact information and logos just by using Adobe Reader, not Acrobat? These are one to four page documents. Right now I can do this by supplying them with Word docs. See http://www.contextgarden.net/Widgets and please add your experiences to this page. I had no time to work further on my form project (a self-calculating RPG character sheet)... Grüßlis vom Hraban! --- http://www.fiee.net/texnique/ http://contextgarden.net ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] PDF Forms
Hi, Is there some way to create PDF docs (as forms maybe?) so end users can add their own contact information and logos just by using Adobe Reader, not Acrobat? These are one to four page documents. Right now I can do this by supplying them with Word docs. Thanks. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
