[NTG-context] Re: Upgrading from 2021.03.05.20230120 -> 2023.05.05.20230730 breaks BibTeX footnotes
On Tue, 2024-06-18 at 18:48 +0200, Hans Hagen wrote:
> then use \alwayscite
Hey Hans. I note that command is not documented (yet) so thank you for
providing that. That works in getting the reference typeset without
having to list all of them.
That at least gets the reference to typeset, but back to the original
issue, it still doesn't typeset correctly. I've managed to come up with
a minimal that displays the garbled reference:
\startbuffer[testdata]
@Book{cicero-tuscu2011,
author = {Cicéron, Marcus Tullius},
editor = {Fohlen, G.},
publisher = {Les Belles Lettres},
title = {Tusculanes},
year = {2011},
address= {Paris},
edition= {7e tirage},
isbn = {9782251010830},
series = {œuvres philosophiques},
volume = {1},
ppn_gvk= {1823774121},
translator = {Jules Humbert},
}
\stopbuffer
% Setup bibliography...
% Select References.bib and name it the main database...
\usebtxdataset[main][testdata.buffer]
% Citation style...
\usebtxdefinitions[apa]
% Use our main dataset for citations...
\setupbtx[dataset=main]
\definebtxrendering[main][apa][dataset=main]
\setupbtxrendering[main][
pagestate=start,
continue=yes,
numbering=yes]
% Macro to put the citations as footnotes...
\unexpanded\def\footnotecite{\dodoubleempty\domycite}
\def\domycite[#1][#2]%
{\ifsecondargument
\footnote{\alwayscite[alternative=entry,#1][main::#2]}%
\else
\footnote{\alwayscite[alternative=entry][main::#1]}%
\fi}
\starttext
Some footnote.\footnotecite[cicero-tuscu2011]
\stoptext
If I use ConTeXt via https://context-on-web.eu/, which appears to be
ConTeXt ver: 2022.12.22 22:17 LMTX fmt: 2022.12.23, it works fine and I
see the following in the footnote, as expected:
1 Cicéron, M. T. (2011). Tusculanes (G. Fohlen, Ed.) (J. Humbert,
Trans.). (Vol. 1, 7e tirage ed.). Paris: Les Belles Lettres.
But on my machine which has ConTeXt 2023.05.05, I see the following:
1 internal()Cicéron, M. T. (2011). Tusculanes (G. Fohlen, Ed.) (J.
Humbert, Trans.). (Vol. 1, 7e tirage ed.). Paris: Les Belles Lettres.
isbn∶9782251010830
--
Kip Warner
OpenPGP signed/encrypted mail preferred
https://www.thevertigo.com
signature.asc
Description: This is a digitally signed message part
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Cron /var/www/aanhet.net/context/bin/cron/context-mirror
receiving incremental file list ./ ctan.lsr document-2.htm download-1.htm download-2.htm logo-ade.png logo-cts.png logo-pod.png rss.xml show-fil.pdf context/latest/ context/latest/cont-lmt.zip context/latest/cont-mpd.zip context/latest/cont-ppc.zip context/latest/cont-sci.zip context/latest/cont-tmf.zip context/latest/cont-tst.7z context/latest/cont-tst.tar.xz context/latest/cont-tst.zip general/manuals/ general/manuals/mathincontext-paper.pdf general/manuals/mathincontext-screen.pdf sent 216,768 bytes received 55,456,970 bytes 2,715,792.10 bytes/sec total size is 617,026,476 speedup is 11.08 Running archiver: New dir: /var/www/aanhet.net/context//htdocs/archives/context-2024-06-18.23 271327488 /var/www/aanhet.net/context//htdocs/archives/context-2024-06-18.23/latest 126745317 /var/www/aanhet.net/context//htdocs/archives/context-2024-06-18.23/current 398076901 /var/www/aanhet.net/context//htdocs/archives/context-2024-06-18.23 398076901 total ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] new upload
Hi, three fixes / improvements: - math composities get more generous bounding boxes - tikz inclusion (also new compact=tikz option that strips some nops) - more fonts got the get-rid-of-bad-apply-characters tweak enabled - for pablo to test signing Hans ps. i'm looking a bit into csl but nothing yet - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: digital signing in ConTeXt
On 6/18/24 19:28, Pablo Rodriguez via ntg-context wrote: > [...] > I have just discovered that verify didn’t work with the binary. > > Figuring out now how to do the testing with the library. For some strange reason, I cannot get --library verification. I only get: sign pdf| verifying with the binary is not yet implemented sign pdf| signature in file 'a.pdf' doesn't match the content I‘m afraid I don’t know what I’m missing. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: digital signing in ConTeXt
On 6/18/24 18:42, Hans Hagen via ntg-context wrote: > On 6/18/2024 6:26 PM, Pablo Rodriguez via ntg-context wrote: >> [...] >> As far as I know, this has to be a reason for digest mismatch (or a huge >> hash collision). > > could be (depends on checker) but it we change that we also need to > change the verify offset (so two patches) I have just discovered that verify didn’t work with the binary. Figuring out now how to testing with the library. >> Signatures in PDF-2.0 loose their possibility of other ranges than the >> entire file. Their use is simply not allowed. > > so more limited then to basically two ranges It makes sense and it is recommended for PDF-1.x. Sorry for insisting, but please don’t require plaintext password in the command line (again, OpenSSL prompts for it). >>> not if we use the library >> >> Weird, on both Linux64 and Win64, the openssl runner requires the >> openssl binary to be installed. > > i meant the --library option In that case, when --library is not invoked, we might avoid mandating the password in plain text. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Upgrading from 2021.03.05.20230120 -> 2023.05.05.20230730 breaks BibTeX footnotes
On 6/18/2024 6:38 PM, Kip Warner wrote: On Tue, 2024-06-18 at 18:16 +0200, Hans Hagen wrote: you need to place a list in order to get some ref Is there no way to use references without having to list the entire bibliography? then use \alwayscite % hidden : mark for list, don't show in text % list : mark for list, show in text only when in list % text : not to list, show in text % always : mark for list, show in text - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: digital signing in ConTeXt
On 6/18/2024 6:26 PM, Pablo Rodriguez via ntg-context wrote: On 6/18/24 10:27, Hans Hagen via ntg-context wrote: On 6/18/2024 8:44 AM, Pablo Rodriguez via ntg-context wrote: [...] Generating certificates with OpenSSL is basically free. you cannot use a 'web certificate' Self-signed certificates may be used to stamp PDF documents to set both signing time and to detect modifications after signing. In fact, I’m planning to digitally stamp documents at work to ensure they aren’t modified after submission (by people or by any automated program). well, if you can figure it out ... i'll can only spend time on it in a real project (it's notp that interesting as hobby) I think this may be avoided by adding a timestamp token (as unsigned attribute) in the PKCS#7 (as mentioned in the PDF spec). dunno, can test it https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008.pdf#nameddest=G11.2054251 refers to https://www.rfc-editor.org/rfc/pdfrfc/rfc3161.txt.pdf#page=20. Not sure how to get that with OpenSSL (never tried). But I may ask how to get that at their GitHub repository. ok Acrobat may be wrong in not detecting the signature (I’m investigating it). i think it only looks for 'official' ones I have created self-signed certificates with Acrobat Reader and signed PDF documents with both ones (cert and Acrobat) and Acrobat displayed these signatures. ok I have used the provided certificate to sign with pdfsig and Acrobat displayed the signature. I think Acrobat may be misbehaving here (requiring some optional content as mandatory). dunno, if you can create examples i suppose we can reverse engineer them because the standard is fuzzy I’m afraid that the patch is needed since /ByteRange excludes a blank space before the value of /Contents that is in the temporary file (tmpfile). i need to test more Perfectly fine for me. Of course, it should be tested more. The blank space (marked above with the underscore) is included in the hashed file (tmpfile), but it is not included in the /ByteRange. This is the reason why we can only have digest mismatch. yes but that what i noticed when testing: mupdf, qpdf, acrobat, etc .. trial and error is not to add that one Sorry, but I have to be missing your point completely. /ByteRange considers this part of the document to be written as: << /ByteRange [ … 006421 010520 000384 ] /Contents<3… But document is written, hashed and signed: << /ByteRange [ … 006421 010520 000384 ] /Contents <3… Of course, the value of the contents hasn’t been hashed, but the blank space between /Contents and is value has been hashed. i know but when i tested with q and m that spaces was kind of fuzzy so i stuck with what seemed to work As far as I know, this has to be a reason for digest mismatch (or a huge hash collision). could be (depends on checker) but it we change that we also need to change the verfy offset (so two patches) As far as I can remember, this is mandatory for PDF-2.0 (and highly recommended for previous versions [although not required]). not sure what you mean, 2.0 demanding signing? Not at all. Sorry for my poor wording. From the PDF-1.7 spec itself (https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008.pdf#search=ByteRange): This range should be the entire file, including the signature dictionary but excluding the signature value itself (the Contents entry). Other ranges may be used but since they do not check for all changes to the document, their use is not recommended. When a byte range digest is present, all values in the signature dictionary shall be direct objects. Signatures in PDF-2.0 loose their possibility of other ranges than the entire file. Their use is simply not allowed. so more limited then to basically two ranges Sorry for insisting, but please don’t require plaintext password in the command line (again, OpenSSL prompts for it). not if we use the library Weird, on both Linux64 and Win64, the openssl runner requires the openssl binary to be installed. i meant the --library option Many thanks for your help, Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] “call for articles” (context meeting 2023)
Dear participants of last year’s context meeting, after a lot of procrastination and more or less resolving several technical and personal issues, I’m finally ready to work on the context journal (proceedings of the 17th context meeting in Sibřina). If I didn’t overlook anything, I got only a preliminary version of Massi’s article so far (directly after the meeting). So, please submit your talks/articles now! Additional articles (that are not related to a meeting talk in 2023 or 2024) are also welcome! Best, Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: digital signing in ConTeXt
On 6/18/24 10:27, Hans Hagen via ntg-context wrote: > On 6/18/2024 8:44 AM, Pablo Rodriguez via ntg-context wrote: >> [...] >> Generating certificates with OpenSSL is basically free. > > you cannot use a 'web certificate' Self-signed certificates may be used to stamp PDF documents to set both signing time and to detect modifications after signing. In fact, I’m planning to digitally stamp documents at work to ensure they aren’t modified after submission (by people or by any automated program). >> I think this may be avoided by adding a timestamp token (as unsigned >> attribute) in the PKCS#7 (as mentioned in the PDF spec). > > dunno, can test it https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008.pdf#nameddest=G11.2054251 refers to https://www.rfc-editor.org/rfc/pdfrfc/rfc3161.txt.pdf#page=20. Not sure how to get that with OpenSSL (never tried). But I may ask how to get that at their GitHub repository. >> Acrobat may be wrong in not detecting the signature (I’m investigating it). > > i think it only looks for 'official' ones I have created self-signed certificates with Acrobat Reader and signed PDF documents with both ones (cert and Acrobat) and Acrobat displayed these signatures. I have used the provided certificate to sign with pdfsig and Acrobat displayed the signature. I think Acrobat may be misbehaving here (requiring some optional content as mandatory). >> I’m afraid that the patch is needed since /ByteRange excludes a blank >> space before the value of /Contents that is in the temporary file (tmpfile). > > i need to test more Perfectly fine for me. Of course, it should be tested more. >> The blank space (marked above with the underscore) is included in the >> hashed file (tmpfile), but it is not included in the /ByteRange. >> >> This is the reason why we can only have digest mismatch. > > yes but that what i noticed when testing: mupdf, qpdf, acrobat, etc .. > trial and error is not to add that one Sorry, but I have to be missing your point completely. /ByteRange considers this part of the document to be written as: << /ByteRange [ … 006421 010520 000384 ] /Contents<3… But document is written, hashed and signed: << /ByteRange [ … 006421 010520 000384 ] /Contents <3… Of course, the value of the contents hasn’t been hashed, but the blank space between /Contents and is value has been hashed. As far as I know, this has to be a reason for digest mismatch (or a huge hash collision). >> As far as I can remember, this is mandatory for PDF-2.0 (and highly >> recommended for previous versions [although not required]). > > not sure what you mean, 2.0 demanding signing? Not at all. Sorry for my poor wording. From the PDF-1.7 spec itself (https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008.pdf#search=ByteRange): This range should be the entire file, including the signature dictionary but excluding the signature value itself (the Contents entry). Other ranges may be used but since they do not check for all changes to the document, their use is not recommended. When a byte range digest is present, all values in the signature dictionary shall be direct objects. Signatures in PDF-2.0 loose their possibility of other ranges than the entire file. Their use is simply not allowed. >> Sorry for insisting, but please don’t require plaintext password in the >> command line (again, OpenSSL prompts for it). > not if we use the library Weird, on both Linux64 and Win64, the openssl runner requires the openssl binary to be installed. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: extensibles not rendered
Thanks Mikael….I’m glad to know that it wasn’t a problem with my installation. Best. __martin > On 18 Jun 2024, at 12:49, Mikael Sundqvist wrote: > > Martin: We did not add the "wipeweirdones" to the cambria tweak file > yet. It should be there, but even then, one sees this, so some more > work is needed to get it also to work for Cambria. I will discuss it > with Hans. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: context / auctex problem? half-solved
Here just an inelegant half-solution:
I added the whole program path to the 'TeX-command-list and it works,
but this is hardly satisfying.
At least it suggests that nothing else is wrong except that emacs 29.3
and auctex 14.0.5 together decide
not to find a path, which is in .bashrc and works fine when called
from a shell (not from eshell though).
Thanks again for the tips,
Jürgen
- Nachricht von Lizardo Reyna via ntg-context
-
Datum: Tue, 18 Jun 2024 00:34:32 -0500
Von: Lizardo Reyna via ntg-context
Antwort an: mailing list for ConTeXt users
Betreff: [NTG-context] context / auctex problem?
An: ntg-context@ntg.nl
Cc: Lizardo Reyna
Hi,
You can update the command for ConTeXt as follows:
Graphically:
M-x customize-variable *↵*
TeX-command-list *↵*
find the appropriate section for ConTeXt commands and change it with
(e.g.) "context --purgeall %t" (see attached image).
Apply and save.
-
Using the init.el you can also create your own commands:
(custom-set-variables
'(ConTeXt-Mark-version "lmtx")
'(ConTeXt-engine "lmtx"))
(eval-after-load "context"
'(setq TeX-command-list
(append
'(
("context"
"context --purgeall %t"
TeX-run-command t :help "Run context (lmtx)")
("luametatex"
"context --purgeall %t"
TeX-run-command t :help "Run context (lmtx)")
) TeX-command-list
)
)
)
I hope this helps.
Lizardo R.
- Ende der Nachricht von Lizardo Reyna via ntg-context
-
---
Prof. Dr. Juergen Hanneder
Philipps-Universitaet Marburg
FG Indologie u. Tibetologie
Deutschhausstr.12
35032 Marburg
Germany
Tel. 0049-6421-28-24930
hanne...@staff.uni-marburg.de
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: extensibles not rendered
Hi,
Thanks!
Jacob: Hans is aware. It is a bit weird, since it works differently
depending on the viewer...
Martin: We did not add the "wipeweirdones" to the cambria tweak file
yet. It should be there, but even then, one sees this, so some more
work is needed to get it also to work for Cambria. I will discuss it
with Hans.
/Mikael
On Tue, Jun 18, 2024 at 1:25 PM Martin C. Moncrieffe wrote:
>
>
> Using the latest release (ConTeXt ver: 2024.06.16 18:22 LMTX fmt:
> 2024.6.17, the following renders correctly with pagella but not cambria.
>
>
> \setupbodyfont[cambria, 12pt]
>
> \starttext
>
> \startformula
> s\of(1) = s\of (\set{0}) = \set{0} \cup \set{\set{0}}
> \stopformula
>
> \stoptext
>
>
> __martin
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: extensibles not rendered
Using the latest release (ConTeXt ver: 2024.06.16 18:22 LMTX fmt: 2024.6.17,
the following renders correctly with pagella but not cambria.
\setupbodyfont[cambria, 12pt]
\starttext
\startformula
s\of(1) = s\of (\set{0}) = \set{0} \cup \set{\set{0}}
\stopformula
\stoptext
__martin
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] extensibles not rendered
Dear list,
thank you for the excellent Math in ConTeXt documentation!
Some extensibles are not properly rendered in some viewers after the most
recent update.
The code below produces a pdf with only a few visible artifacts in Acrobat
Reader.
E.g. Safari or Preview render them correctly.
If I remember correctly extensibles were properly rendered in Acrobat Reader
before the update.
Best wishes,
Jacob
\setupbodyfont[8pt]
\startTEXpage[offset=none]
$\overbracket{\hbox to 1cm{}}$
\blank
$\fenced[brace]{\vbox to 1cm{}}$
\stopTEXpage
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: expanded doif's
Finally found the culprit. Macro call to restart reporting errors in the
printed output residing at the wrong point in the code.
Again thanks for pointing out where it was not.
yours sincerely
dr. Hans van der Meer
> On 17 Jun 2024, at 16:52, Wolfgang Schuster
> wrote:
>
> Hans van der Meer schrieb am 17.06.2024 um 09:01:
>> I want to show an errormessage when the macro is undefined. It requires
>> expansion of \xmlatt{#1}{name}.
>> \ifdefined\xmlatt{#1}{name} didn't worked nor \expandafter\ifdefined
>> I thought of the expanding \doif's.
>> See the attached output of this xmlsetup attached.
>> \startxmlsetups hvdm:system:macrocall
>> %
>> \doifelsedefined{\xmlatt{#1}{name}}
>> {
>> %
>> %macro without argument
>> %
>> \ifxmlattempty{#1}{arg}
>> \begincsname\xmlatt{#1}{name}\endcsname
>> %
>> %macro with argument
>> %
>> \else
>> \begincsname\xmlatt{#1}{name}\endcsname{\xmlatt{#1}{arg}}
>> \fi
>> }
>> {
>> \ERROR{macro \xmlatt{#1}{name} is not defined}
>> }
>> \stopxmlsetups
>
> I have no idea what's wrong in your code without a proper minimal example. As
> the example below shows you can use \doifelsedefined in combination with
> \xmlatt.
>
> \startbuffer[ifdefined]
>
>
>
>
> \stopbuffer
>
> \startxmlsetups xml:document
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:macro
>
> \doifelsedefined{\xmlatt{#1}{name}}
>{\texdefinition{\xmlatt{#1}{name}}{\xmlatt{#1}{arg}}}
>{{\tttf macro \tex{\xmlatt{#1}{name}} not defined}}
>
> % \ifcsname\xmlatt{#1}{name}\endcsname
> % \lastnamedcs{\xmlatt{#1}{arg}}
> % \else
> % %
> % \fi
>
> \stopxmlsetups
>
> \startxmlsetups xml:hvdm
> \xmlsetsetup{\xmldocument}{document|macro}{xml:*}
> \stopxmlsetups
>
> \xmlregistersetup{xml:hvdm}
>
> \starttext
> \xmlprocessbuffer{hvdm}{ifdefined}{}
> \stoptext
>
> Wolfgang
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: context / auctex problem?
1. This sounded like a good solution:
Despite the contextgarden wiki page, which says:
;; AUCTeX defaults to mkii; change to iv for iv and lmtx
(ConTeXt-Mark-version "IV")
this seemed like a good idea,
(custom-set-variables
'(ConTeXt-Mark-version "lmtx")
'(ConTeXt-engine "lmtx"))
but on my system the error just changes:
Running `ConTeXt Full' on `context-test' with ``texexec --engine=lmtx
--nonstop context-test.tex''
/usr/bin/texexec: Zeile 2: mtxrun: Kommando nicht gefunden.
auctex apparently stops using the command "context" directly, but via texexec.
2.
Apparently, your Emacs doesn’t use the same PATH as your terminal.
The error message is from /bin/sh, I guess you usually run bash, zsh
or the like, and that gets its PATH from .bashrc or something like
that.
Check how Emacs calls that script, and if you can define a PATH.
I tried the method from https://www.emacswiki.org/emacs/ExecPath
and set explicitly a path as
(setq exec-path (append exec-path '("-Path as in Bashrc-")))
Does not work.
3.
And the information in AucTeX on how to change that is frankly deficient.
Exactly. It is a little absurd that it should be so difficult to tell
auctex anything.
To the point that I, who
am an Emacs user for almost everything, when I write in ConTeXt I
prefer to use Vim.
I started using emacs in the nineties on a college mainframe, so I am
not (yet) ready for vim:)
Thanks a lot for your tips, I shall write if and when I find a solution.
Jürgen
---
Prof. Dr. Juergen Hanneder
Philipps-Universitaet Marburg
FG Indologie u. Tibetologie
Deutschhausstr.12
35032 Marburg
Germany
Tel. 0049-6421-28-24930
hanne...@staff.uni-marburg.de
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: digital signing in ConTeXt
On 6/18/2024 8:44 AM, Pablo Rodriguez via ntg-context wrote: On 6/18/24 00:52, Hans Hagen via ntg-context wrote: On 6/17/2024 7:51 PM, Pablo Rodriguez via ntg-context wrote: [...]>> 2. I cannot get any signature display in Acrobat. Does any PDF viewer (I have tested this with pdfsig from poppler and MuPDF-GL) display the digital signature at all? this whole digitial signing is a bit of a scam imo ... Digital signing may be a marketing gig also, but we may only consider the pure feature as such. I mean, I’m not interested here in the legally binding value of certain digital certificates, but just in having digital signatures right. - one has to buy a specific kind of certificate Generating certificates with OpenSSL is basically free. you cannot use a 'web certificate' - often one is supposed to use some token - when the root cert expires one has to resign I think this may be avoided by adding a timestamp token (as unsigned attribute) in the PKCS#7 (as mentioned in the PDF spec). dunno, can test it - reader has root certs built in and checking is supposed to be online - it doesn't come cheap and supporting / testing is not something one can expect for free (so i can't really test it) ... so just some business model and not really something one can do out of the box This is all related to certificate (legal) validity. This is out of the scope. whatever ... ... apart from ... - just sign with some certificate and don't expect viewers to do something Acrobat may be wrong in not detecting the signature (I’m investigating it). i think it only looks for 'official' onex concerning the suggested patches: thisboundary is a bit fuzzy and i found that different viewers / checkers expect either or not +/- 1 but i didn't check recently if things have improved There are two different issues here: digest mismatch and total document signing. I’m afraid that the patch is needed since /ByteRange excludes a blank space before the value of /Contents that is in the temporary file (tmpfile). i need to test more I mean, here are the contens of the temporary file from the sample (tweaked to fit a single line]): << /ByteRange [ … 006421 010520 000384 ] /Contents / Byte 6421 is the s (before the underscore): << /ByteRange [ … 006421 010520 000384 ] /Contents_ / The blank space (marked above with the underscore) is included in the hashed file (tmpfile), but it is not included in the /ByteRange. This is the reason why we can only have digest mismatch. yes but that what i noticed when testing: mupdf, qpdf, acrobat, etc .. trial and error is not to add that one As for total document signing, it is better only to exclude from /ByteRange the value for /Contents (from < to >). As far as I can remember, this is mandatory for PDF-2.0 (and highly recommended for previous versions [although not required]). not sure what you mean, 2.0 demanding signing? if we know the specs and have way to test ... no big deal to fix a few offsets I’m happy to contribute as far as I can. Sorry for insisting, but please don’t require plaintext password in the command line (again, OpenSSL prompts for it). not if we use the library Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Combine \setupdelimitedtext with an author (define custom variable?)
Am Montag, 17. Juni 2024, 21:20:19 MESZ schrieb Wolfgang Schuster:
> Gerion Entrup schrieb am 17.06.2024 um 13:04:
> > Am Donnerstag, 6. Juni 2024, 16:34:03 MESZ schrieb Wolfgang Schuster:
> >> [...]
> >>
> >> Wolfgang
> >>
> >
> > I tried to combine this with the code of the mail thread: "setuphead in
> > connection with the command argument" but had not luck.
> > ConTeXt always stops with:
> > ```
> > close source> level 1, order 2, name './mwe.tex'
> > tex error > runaway error: end of file encountered
> > mtx-context | fatal error: return code: 1
> > ```
> >
> > Here is the MWE:
> > ```
> > [...]
> >
> > \startsetups[my_chapter]
> > \startlocalheadsetup
> > \startframed[chapter_frame]
> > \blank[2cm]
> > \startfont[Serif sa 8]
> > \color[darkgray]{\headnumbercontent}
> > \stopfont
> > \blank[5mm]
> > \startfont[SerifBold sa 2]
> > \color[m-indigo-800]{\headtextcontent}
> > \stopfont
> > \blank[1cm]
> > \startfont[SerifBold sa 1.5]
> >
> > \color[m-indigo-800]{\structureuservariable{subtitle}}
> > \stopfont
> > \blank[3cm]
> >
> > \startextract[author={\structureuservariable{quoteauthor}}]
> > \structureuservariable{quote}
> > \stopextract
> > \stopframed
> > \stoplocalheadsetup
> > \stopsetups
>
> The userdata environment uses the buffer mechanism of Context which has
> a few limitations where you can use it, e.g. putting the environment in
> the arguments of other commands (like the setup-environment above)
> fails. One way to avoid this is to replace the \startextract ...
> \stopextract in this case with the code for the quoted text, another way
> is to put all content in a buffer and just load the buffer in the
> setups-environment.
>
> \startbuffer[my_chapter]
> \startlocalheadsetup
> \startframed[chapter_frame]
> ...
> \stopframed
> \stoplocalheadsetup
> \stopbuffer
>
> \startsetups[my_chapter]
>\getbuffer[my_chapter]
> \stopsetups
>
> Wolfgang
>
Thanks, I solved it by embedding the extract code directly (more less).
Gerion
signature.asc
Description: This is a digitally signed message part.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Transparency in external PDFs does not work
Am Montag, 17. Juni 2024, 23:50:16 MESZ schrieb Hans Hagen:
> On 6/17/2024 5:07 PM, Gerion Entrup wrote:
> > Hi,
> >
> > I'm using LaTeX-Beamer and TikZ for figure typesetting.
> > With this combination, it is easy to combine Beamer's animation system with
> > TikZ transparency feature.
> > This way, the resulting PDFs contain the full graphic on every page, but
> > parts of it are invisible for a specific page.
> > One of these files is attached as an example.
> >
> > The problem is to embed these PDFs into a ConTeXt document.
> > For example, this MWE seems to not respect transparency (see mwe.pdf):
> > ```
> > \starttext
> > \externalfigure[fig.pdf][page=1]
> > \stoptext
> > ```
> >
> > I use Okular/Poppler as PDF viewer.
> > Can I fix this somehow or is it a bug somewhere deeper?
> next time check the file that you include ... it has no transparency (it
> has zero values)
I don't really have a clue about the PDF standard. It is made with the TikZ
opacity flag therefore I thought it controls the transparency.
See the attached tex file to reproduce fig.pdf (compilation with `latexmk
-pdflua fig.tex`).
I also found a workaround. It is possible to import fig.pdf with Inkscape and
export just the correct page as PDF again and embed that in ConTeXt:
```
inkscape --export-page=1 fig.pdf --export-type=pdf --export-filename=1.pdf
```
Gerion
\documentclass{beamer}
\usepackage{tikz}
\usetikzlibrary{fit}
\usepackage[active, tightpage]{preview}
\PreviewEnvironment{tikzpicture}
% taken from https://github.com/luhsra/texmf/blob/main/tex/latex/beamertools/beamertools.sty
\tikzset{
onslide/.code args={<#1>#2}{%
\only<#1>{\pgfkeysalso{#2}}
},
alt/.code args={<#1>#2#3}{%
\alt<#1>{\pgfkeysalso{#2}}{\pgfkeysalso{#3}}
},
global opacity/.style={
opacity=#1,
text opacity=#1,
every shadow/.append style={opacity=#1},
every on layer/.append style={opacity=#1},
every node/.append style={opacity=#1},
prefix after command={\pgfextra{\tikzset{every pin/.style={opacity=#1},
every pin edge/.style={opacity=#1},
every label/.style={opacity=#1,
},
invisible/.style={global opacity=0},
visible/.style={global opacity=1},
visible on/.style={alt=#1{}{invisible}},
invisible on/.style={alt=#1{invisible}{}},
}
\begin{document}
\begin{frame}
\begin{tikzpicture}
\node[draw, visible on=<1>] (fp) {First Page};
\node[draw, visible on=<2>] (sp) {Second Page};
\node[draw, fit=(fp)(sp)] {};
\end{tikzpicture}
\end{frame}
\end{document}
signature.asc
Description: This is a digitally signed message part.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
