Re: [NTG-context] Entity to receive donations?
On 12/27/19 4:49 PM, Jon Wong wrote: Is there a formal entity for ConTeXt to receive donations? What about receiving earnings? https://group.contextgarden.net/payment.shtml ___ 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 ___
[NTG-context] Entity to receive donations?
Is there a formal entity for ConTeXt to receive donations? What about receiving earnings? ___ 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] Watermark is behind \externalfigure
Any way to put the watermark in front? ___ 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] issues with attachments
On 12/18/2019 11:32, Pablo Rodriguez wrote:
Hi Hans,
I accidentally discovered that file attachment generates two entries in
Acrobat, such as this sample:
\setuppapersize[A5]
\showframe
\setupinteraction[state=start]
\setupinteractionscreen[option=attachment]
\starttext
a\attachment[file=xml-mkiv.pdf, name={attached.pdf}]
\stoptext
This happens with latest beta (from 2019.12.17) in both MkIV and MkXL.
https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf#search=usability
warns about the use of both /EmbeddedFiles and /FileAttachment
annotations. Acrobat seems to be the problematic software.
I think it is fine to have /FileAttachment annotations for
"method=normal" and /EmbeddedFiles for "method=hidden".
Would be also possible that the entries in /Embeddedfiles use the value
for "name" instead of "file" (when specified)?
And for the /EmbeddedFile annotation, would it be possible to add the
value for /Size entry (uncompressed size of the file in bytes,
https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#page=112)
in the /Params dictionary?
This is the way to avoid that Acrobat displays no uncompressed size but
real uncompressed size (I guess both values would be very similar, when
not the same).
Many thanks for your help,
Pablo
--
http://www.ousia.tk
I second this request. The bookmark is taking on the file= name, and not
that of name=. It would be better to take the name=, or to add a
bookmark= key.
--
Rik
___
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] Item group parentheses
Jairo A. del Rio schrieb am 26.12.2019 um 19:55: I'm defining item groups in ConTeXt and I find the following issue: combining the "text" parameter with others automatically disables "left" and "right" keys, so numbers always appear enclosed in parentheses. %What I expect: %I. This ain't right %What I get: %(I) This ain't right \defineitemgroup[erroneous] \setupitemgroup[erroneous][1][R,text,continue][left=,right=.,stopper=] \starttext \starterroneous \startitem This ain't right \stopitem \stoperroneous \stoptext Maybe a bug, I want to know how to get the expected result. Thank you in advance. You have to clear the values of the lefttext and righttext keys. 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Item group parentheses
I'm defining item groups in ConTeXt and I find the following issue: combining the "text" parameter with others automatically disables "left" and "right" keys, so numbers always appear enclosed in parentheses. %What I expect: %I. This ain't right %What I get: %(I) This ain't right \defineitemgroup[erroneous] \setupitemgroup[erroneous][1][R,text,continue][left=,right=.,stopper=] \starttext \starterroneous \startitem This ain't right \stopitem \stoperroneous \stoptext Maybe a bug, I want to know how to get the expected result. Thank you in advance. texstudio_HP2542.pdf Description: Adobe PDF document ___ 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] Adjust kern for one character
On 12/26/2019 08:40, Hans Hagen wrote:
On 12/26/2019 1:41 PM, Rik Kabel wrote:
Okay, I have progressed further but have run into something (else) I
cannot understand. Consider the following example:
\definefontfeature [myserif] [mode=node,kern=yes,xkern=yes]
\definefontfeature [mysans] [mode=node,kern=yes,xkern=no]
\definefontfeature [none] [mode=node]
\definefontfamily [mykerns] [serif] [Baskervaldx]
[features=myserif]
\definefontfamily [mykerns] [sans] [Dejavusans]
[features=mysans]
\definefontfamily [default] [serif] [Baskervaldx]
[features=default]
\definefontfamily [default] [sans] [Dejavusans]
[features=default]
\definefontfamily [nokerns] [serif] [Baskervaldx] [features=none]
\definefontfamily [nokerns] [sans] [Dejavusans] [features=none]
\definefontfamily [legends] [mono] [Dejavusansmono]
[features=default]
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
["x"] = { ["x"] = -300 },
[" "] = { ["A"] = 1000 }
}
}
fonts.handlers.otf.addfeature {
name = "xkern",
type = "kern",
data = {
["x"] = { ["x"] = 500 },
[" "] = { ["J"] = 500 }
}
}
\stopluacode
\startbuffer[Sample]
g, Jaxxb AJon
\stopbuffer
\define[2]\Test{
{\switchtobodyfont[#1]#2\getbuffer[Sample]}}
\setupbodyfont[legends]
\starttext
\starttabulate[|l|l|l|]
\NC test \NC Serif \NC Sans
\NC \NR
\NC nokerns \NC \Test{nokerns}{\tf} \NC \Test{nokerns}{\ss}
\NC \NR
\NC default \NC \Test{default}{\tf} \NC \Test{default}{\ss}
\NC \NR
\NC mykerns \NC \Test{mykerns}{\tf} \NC \Test{mykerns}{\ss}
\NC \NR
\stoptabulate
\stoptext
It shows, as far as I see, that the kern feature type supports " ",
but only when it is named kern. When it is named xkern, as here, it
does not support spaces, but does support other characters.
Indeed it's currently bound to 'kern' (mostly for convenience and a
little for performance) but it's not that hard to make it a bit more
flexible (but not today).
Hans
Thank you for the confirmation. I look forward to the update.
--
Rik
___
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] Adjust kern for one character
On 12/26/2019 1:41 PM, Rik Kabel wrote:
Okay, I have progressed further but have run into something (else) I
cannot understand. Consider the following example:
\definefontfeature [myserif] [mode=node,kern=yes,xkern=yes]
\definefontfeature [mysans] [mode=node,kern=yes,xkern=no]
\definefontfeature [none][mode=node]
\definefontfamily[mykerns] [serif] [Baskervaldx][features=myserif]
\definefontfamily[mykerns] [sans] [Dejavusans] [features=mysans]
\definefontfamily[default] [serif] [Baskervaldx][features=default]
\definefontfamily[default] [sans] [Dejavusans] [features=default]
\definefontfamily[nokerns] [serif] [Baskervaldx][features=none]
\definefontfamily[nokerns] [sans] [Dejavusans] [features=none]
\definefontfamily[legends] [mono] [Dejavusansmono] [features=default]
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
["x"] = { ["x"] = -300 },
[" "] = { ["A"] = 1000 }
}
}
fonts.handlers.otf.addfeature {
name = "xkern",
type = "kern",
data = {
["x"] = { ["x"] = 500 },
[" "] = { ["J"] = 500 }
}
}
\stopluacode
\startbuffer[Sample]
g, Jaxxb AJon
\stopbuffer
\define[2]\Test{
{\switchtobodyfont[#1]#2\getbuffer[Sample]}}
\setupbodyfont[legends]
\starttext
\starttabulate[|l|l|l|]
\NC test \NC Serif\NC Sans \NC \NR
\NC nokerns \NC \Test{nokerns}{\tf} \NC \Test{nokerns}{\ss} \NC \NR
\NC default \NC \Test{default}{\tf} \NC \Test{default}{\ss} \NC \NR
\NC mykerns \NC \Test{mykerns}{\tf} \NC \Test{mykerns}{\ss} \NC \NR
\stoptabulate
\stoptext
It shows, as far as I see, that the kern feature type supports " ", but
only when it is named kern. When it is named xkern, as here, it does not
support spaces, but does support other characters.
Indeed it's currently bound to 'kern' (mostly for convenience and a
little for performance) but it's not that hard to make it a bit more
flexible (but not today).
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 / 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] ntg-context Digest, Vol 186, Issue 61
Dear Hans,
I read the “luametafun.pdf” and run the codes one by one.
It is a really nice to have those figures easily.
During the reading, I found that there is a difference between the figure in
the manual and the output of my run.
I run the following code at page 24-25 in “luametafun.pdf”.
\startMPcode{doublefun} draw lmt_contour [
xmin = 0, xmax = 4*pi, xstep = .05,
ymin = -6, ymax = 6, ystep = .05,
levels =7,
height = 5cm,
preamble = "local sin, cos = math.sin, math.cos",
function = "cos(x) + cos(y)"
background = "bitmap",
foreground = "edge",
linewidth = 1/2,
cache = true,
];
\stopMPcode
In the output, the background of text is gray while the background of text in
the manual is white.
Here are versions of LuaMetaTeX and ConTeXt which I use.
%%%
This is LuaMetaTeX, Version 2.03.4
open source > level 1, order 1, name 'cont-yes.mkiv'
system >
system > ConTeXt ver: 2019.12.16 18:54 MKIV beta fmt: 2019.12.17
int: english/english
system >
%
Is there anything that I miss?
Would you please to check it?
Thank you.
Best regards,
Dalyoung___
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] Adjust kern for one character
On 12/23/2019 18:45, Rik Kabel wrote:
On 12/22/2019 21:34, Henri Menke wrote:
On 12/23/19 3:33 PM, Henri Menke wrote:
On 12/23/19 2:30 PM, Rik Kabel wrote:
On 12/22/2019 17:40, mf wrote:
Il 22/12/19 22:19, Rik Kabel ha scritto:
List,
Is there a way in ConTeXt to adjust the left-side kern for one
character? The cap J in the font I am using is being set too
close to
the preceding characters and I would rather not insert a thinspace
before each. (Inserting a thinspace is sufficient, but finer control
is welcome.)
\definecharacterspacing[distantJ]
\setupcharacterspacing[distantJ]["004A][left=.15,alternative=1] %
004A
is the unicode hex index of letter J
\starttext
normal: AJB\par
\setcharacterspacing[distantJ] more space on the left: AJB\par
\resetcharacterspacing normal again: AJB\par
\stoptext
Thank you for that, Massi.
Unfortunately, that is too blunt an instrument in this case -- in
addition to the body font where the problem exists, it works on the
heading and titling font, which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a
kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
[" "] = {
["J"] = 1000 % exaggerated value
Should of course be a Lua comment
["J"] = 1000 -- exaggerated value
}
}
}
\stopluacode
\setupbodyfont[modern] % have to reload the font
\starttext
No Jokes!
\stoptext
Henri,
This looks very promising. It works, mostly. That is, all fonts that
use default fontfeatures pick up the change. So, for example, the
companion sansserif for my body font also gets it even though that is
not what I want.
I can remove kerning from the default fontfeatures and add it back
just for the problematic font, but that means no kerning for the sans
font.
Is there a way to apply this to one font only (serif upright, bold,
italic, ...) or even a single face (upright), perhaps by giving it a
unique name? I have tried a few variations but had no success. The
fonts-mkiv manual has very little on this, and the cld manual nothing.
Okay, I have progressed further but have run into something (else) I
cannot understand. Consider the following example:
\definefontfeature [myserif] [mode=node,kern=yes,xkern=yes]
\definefontfeature [mysans] [mode=node,kern=yes,xkern=no]
\definefontfeature [none][mode=node]
\definefontfamily[mykerns] [serif] [Baskervaldx][features=myserif]
\definefontfamily[mykerns] [sans] [Dejavusans] [features=mysans]
\definefontfamily[default] [serif] [Baskervaldx][features=default]
\definefontfamily[default] [sans] [Dejavusans] [features=default]
\definefontfamily[nokerns] [serif] [Baskervaldx][features=none]
\definefontfamily[nokerns] [sans] [Dejavusans] [features=none]
\definefontfamily[legends] [mono] [Dejavusansmono] [features=default]
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
type = "kern",
data = {
["x"] = { ["x"] = -300 },
[" "] = { ["A"] = 1000 }
}
}
fonts.handlers.otf.addfeature {
name = "xkern",
type = "kern",
data = {
["x"] = { ["x"] = 500 },
[" "] = { ["J"] = 500 }
}
}
\stopluacode
\startbuffer[Sample]
g, Jaxxb AJon
\stopbuffer
\define[2]\Test{
{\switchtobodyfont[#1]#2\getbuffer[Sample]}}
\setupbodyfont[legends]
\starttext
\starttabulate[|l|l|l|]
\NC test \NC Serif\NC Sans \NC \NR
\NC nokerns \NC \Test{nokerns}{\tf} \NC \Test{nokerns}{\ss} \NC \NR
\NC default \NC \Test{default}{\tf} \NC \Test{default}{\ss} \NC \NR
\NC mykerns \NC \Test{mykerns}{\tf} \NC \Test{mykerns}{\ss} \NC \NR
\stoptabulate
\stoptext
It shows, as far as I see, that the kern feature type supports " ", but
only when it is named kern. When it is named xkern, as here, it does not
support spaces, but does support other characters.
If I can get support for a separate feature name, I can easily apply
this corrective kern to the single problematic font.
I also tried a goodie file, but it, too, did not support the " ".
--
Rik
___
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] xml differences between old context and lmtx
Hi all, are there any documented differences between the xml features of normal context and lmtx? In a fun project I compile xml sources from www.deutschestextarchiv.de to pdf via context using xmlsetups which kinda works with normal context current version: 2019.08.09 18:29 With lmtx current version: 2019.12.12 01:08 I don't get a usable result. And there is a change in file naming I discovered. Files from the deutschestextarchiv have names like marx_kapital01_1867.TEI-P5.xml lmtx skips the TEI-P5 part Any hints how I can adjust my xmlsetups? juh ___ 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] [LMTX] core dumped
On 26-12-2019 09:02, Wolfgang Schuster wrote: > > Delete the cache and regenerate the format file: > > mtxrun --script cache --erase --make . . . system | lua | compiling '/home/vm/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tma' into '/home/vm/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tmd' system | lua | dumping '/home/vm/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tma' into '/home/vm/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tmd' stripped Not much of an improvement yet... \starttext \input knuth \stoptext $ context ctx.tex resolvers | formats | executing runner 'run luametatex format': /home/vm/data/context/tex/texmf-linux-64/bin/luametatex --jobname="ctx" --fmt=/home/vm/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/home/vm/data/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui cont-yes.mkiv --c:currentrun=1 --c:fulljobname="./ctx.tex" --c:input="./ctx.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/home/vm/data/context/tex/texmf-linux-64/bin" This is LuaMetaTeX, Version 2.03.5 open source > level 1, order 1, name 'cont-yes.mkiv' system > system > ConTeXt ver: 2019.12.24 20:09 MKIV beta fmt: 2019.12.26 int: english/english system > system > 'cont-new.mkiv' loaded open source > level 2, order 2, name '/home/vm/data/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > beware: some patches loaded from cont-new.mkiv close source> level 2, order 2, name '/home/vm/data/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > files > jobname 'ctx', input './ctx', result 'ctx' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 2, order 3, name './ctx.tex' fonts > preloading latin modern fonts (second stage) fonts > 'fallback modern-designsize rm 12pt' is loaded open source > level 3, order 4, name 'knuth.tex' close source> level 3, order 4, name 'knuth.tex' backend > xmp > using file '/home/vm/data/context/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 Segmentation fault (core dumped) mtx-context | fatal error: return code: 35584 pEpkey.asc Description: application/pgp-keys ___ 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] [LMTX] core dumped
Floris van Manen schrieb am 25.12.2019 um 15:32: the latest version of lmtx does not run, e.g. core dumped... any hints as how to fix this locally? Delete the cache and regenerate the format file: mtxrun --script cache --erase --make 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
