Re: [NTG-context] Minimum METAPOST code produces problematic PDF
Evince and Okular (Linux) open the PDF output without warnings nor issues. Jairo :) El mar., 7 de jul. de 2020 a la(s) 17:50, Gerben Wierda ( gerben.wie...@rna.nl) escribió: > The following code: > > \startMPpage[instance=doublefun] > draw (0,0)--(100,0) dashed withdots; > \stopMPpage > > When run through LuaMetaTeX produces a PDF about which Acrobat complains: > > The dimensions of this page are out-of-range. Page content might be > truncated. > > and Adobe InDesign cannot handle it at all (displays empty). > > The error message stays with > > \startMPpage[instance=doublefun] > draw (0,0)--(100,0)—(100,2) dashed withdots; > \stopMPpage > > but disappears with > > \startMPpage[instance=doublefun] > draw (0,0)--(100,0)—(100,3) dashed withdots; > \stopMPpage > > > Additionally, on the Adobe forums I have been told: > > Also, the color space is device gray (not RGB or CMYK) > > which might be a more generic problem with LMTX output, I don’t know. It > might also be an Adobe problem. Previw.app on macOS handles the result > without problems. > > ConTeXt standalone: > > This is LuaMetaTeX, Version 2.06.02 > open source > level 1, order 1, name 'cont-yes.mkiv' > system > > system > ConTeXt ver: 2020.05.12 16:21 MKIV beta fmt: > 2020.5.16 int: english/english > > > G > > > > ___ > 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] Minimum METAPOST code produces problematic PDF
The following code: \startMPpage[instance=doublefun] draw (0,0)--(100,0) dashed withdots; \stopMPpage When run through LuaMetaTeX produces a PDF about which Acrobat complains: The dimensions of this page are out-of-range. Page content might be truncated. and Adobe InDesign cannot handle it at all (displays empty). The error message stays with \startMPpage[instance=doublefun] draw (0,0)--(100,0)—(100,2) dashed withdots; \stopMPpage but disappears with \startMPpage[instance=doublefun] draw (0,0)--(100,0)—(100,3) dashed withdots; \stopMPpage Additionally, on the Adobe forums I have been told: Also, the color space is device gray (not RGB or CMYK) which might be a more generic problem with LMTX output, I don’t know. It might also be an Adobe problem. Previw.app on macOS handles the result without problems. ConTeXt standalone: This is LuaMetaTeX, Version 2.06.02 open source > level 1, order 1, name 'cont-yes.mkiv' system > system > ConTeXt ver: 2020.05.12 16:21 MKIV beta fmt: 2020.5.16 int: english/english G ___ 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] About xstring and ConTeXt
Yep, now it finally works. Certainly it requires a few more lines. I was
going to rewrite some TikZ code which was too dependent on LaTeX and
xstring was the last stone on the shoe. Thank you a lot, Phelype and
Wolfgang (I didn't know about push/popmacro either and now it's in my to-do
readings).
Jairo :D
El mar., 7 de jul. de 2020 a la(s) 16:31, Phelype Oleinik (
phe.h...@gmail.com) escribió:
> On Tue, Jul 7, 2020 at 6:21 PM Jairo A. del Rio
> wrote:
> >
> > Thank, Wolfgang! Both methods work, but both fail with the following
> example:
> >
> > \pushmacro\unexpanded
> > \let\unexpanded\normalunexpanded
> > \input xstring
> > \popmacro\unexpanded
> > \starttext
> > \StrGobbleLeft{bcdef}{4}
> > \stoptext
> >
> > The log says:
> >
> > tex error > tex error on line 6 in file ./tests.tex: ! This can't happen
> (prefixed command)
> >
> >
> > \unexpanded {
> >
> > f}
> >
> > \xs_execfirst #1#2->#1
> >
> > However, some others work.
>
> As I said, the internals of `xstring` still use \unexpanded which, after
> you do \popmacro\unexpanded, will mean e-TeX's \protected, rather than
> \unexpanded, which are quite different. To be on the safe side, you'd
> need to wrap every `xstring` command in
> \pushmacro\unexpanded
> \let\unexpanded\normalunexpanded
>
> \popmacro\unexpanded
> to make sure that \unexpanded means what `xstring` expects.
>
> The *proper* way to make `xstring` work in ConTeXt would be something
> like Circuitikz does:
> \ifcsname normalunexpanded\endcsname
> \let\pgfcircutil@unexpanded\normalunexpanded
> \else
> \let\pgfcircutil@unexpanded\unexpanded
> \fi
> then use \pgfcircutil@unexpanded in the code, which will always have the
> same meaning. That, of course, requires an update to `xstring`.
>
> Phelype
>
> ___
> 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] About xstring and ConTeXt
On Tue, Jul 7, 2020 at 6:21 PM Jairo A. del Rio wrote:
>
> Thank, Wolfgang! Both methods work, but both fail with the following example:
>
> \pushmacro\unexpanded
> \let\unexpanded\normalunexpanded
> \input xstring
> \popmacro\unexpanded
> \starttext
> \StrGobbleLeft{bcdef}{4}
> \stoptext
>
> The log says:
>
> tex error > tex error on line 6 in file ./tests.tex: ! This can't happen
> (prefixed command)
>
>
> \unexpanded {
>
> f}
>
> \xs_execfirst #1#2->#1
>
> However, some others work.
As I said, the internals of `xstring` still use \unexpanded which, after
you do \popmacro\unexpanded, will mean e-TeX's \protected, rather than
\unexpanded, which are quite different. To be on the safe side, you'd
need to wrap every `xstring` command in
\pushmacro\unexpanded
\let\unexpanded\normalunexpanded
\popmacro\unexpanded
to make sure that \unexpanded means what `xstring` expects.
The *proper* way to make `xstring` work in ConTeXt would be something
like Circuitikz does:
\ifcsname normalunexpanded\endcsname
\let\pgfcircutil@unexpanded\normalunexpanded
\else
\let\pgfcircutil@unexpanded\unexpanded
\fi
then use \pgfcircutil@unexpanded in the code, which will always have the
same meaning. That, of course, requires an update to `xstring`.
Phelype
___
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] About xstring and ConTeXt
Thank, Wolfgang! Both methods work, but both fail with the following
example:
\pushmacro\unexpanded
\let\unexpanded\normalunexpanded
\input xstring
\popmacro\unexpanded
\starttext
\StrGobbleLeft{bcdef}{4}
\stoptext
The log says:
tex error > tex error on line 6 in file ./tests.tex: ! This can't happen
(prefixed command)
\unexpanded {
f}
\xs_execfirst #1#2->#1
However, some others work.
El mar., 7 de jul. de 2020 a la(s) 15:20, Wolfgang Schuster (
wolfgang.schuster.li...@gmail.com) escribió:
> Phelype Oleinik schrieb am 07.07.2020 um 20:53:
> > Hi Jairo,
> >
> > ConTeXt's \unexpanded is e-TeX's \protected, so the error boils down to
> > something like: \edef\x{\unexpanded{#}}, which works in Plain but not in
> > ConTeXt.
> >
> > Usually packages that claim to be generic have to cope with that.
> > xstring would need to do (in a ConTeXt-specific loader):
> > \let\xstring@unexpanded\normalunexpanded
> > and
> > \let\xstring@unexpanded\unexpanded
> > in Plain and LaTeX loaders, then then use \xstring@unexpanded in the
> > code. But `xstring` doesn't claim (that I found, at least) to be
> > compatible with ConTeXt, so it's understandable: though if it is
> > compatible with Plain, it wouldn't be hard to adapt to ConTeXt.
> >
> > That said, you can load `xstring` if you do:
> > \let\unexpanded\normalunexpanded
> > \input xstring.tex
> > \let\unexpanded\protected
> > but the internals of the package will probably be comprimised by the
> > misuse of (ConTeXt) \unexpanded.
>
> Bad idea because ConTeXt also changes the meaning of \protected (you can
> use \normalprotected to get the primitve).
>
> A better version is
>
> \pushmacro\unexpanded
> \let\unexpanded\normalunexpanded
> \input xstring
> \popmacro\unexpanded
>
> 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
>
> ___
>
___
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] Bad interaction between \setupinteraction and \defineenumeration
Thanks Wolfgang!
Your patch seems to fix also another issue with the cross references in ConTeXt
at least on MacOS and TeXShop. In principle a document typeset with TeXShop, in
the resulting PDF when the pointer hovers above a link to a reference, TeXShop
shows a small pop-up window where the reference is shown (for instance with the
example sent by Jairo the text of Proposición is shown). This works fine with
LaTeX documents typeset with TeXShop, but it didn't work at all with ConTeXt
documents. After applying your patch and making the format, the feature works
with some ConTeXt documents, such as the example sent by Jairo (but
unfortunately the feature does not work in a large document where I tested it).
Best regards: Otared K.
> On 6 Jul 2020, at 20:48, Wolfgang Schuster
> wrote:
> […]
>
> I'm not Hans but this fixed the problem for me (strc-con.mkiv):
>
> \def\strc_constructions_register_yes[#1][#2]% #1=optional user data
> #2=interfaced-settings
> {\begingroup % similar to structure so we might
> generalize this
> ...
> \clf_setinternalreference
> - prefix{\referenceprefix}%
> + prefix{\currentconstructionreferenceprefix}%
> reference {\currentconstructionreference}%
> internal \locationcount
> view {\interactionparameter\c!focus}%
> \relax
> ...
> \fi}
>
> 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] lpath to select last item
Dear list,
I have the following sample:
\startbuffer[demo]
Heading
list
Heading
list
list
Heading
list
list
list
\stopbuffer
\startxmlsetups xml:demo:base
\xmlsetsetup{#1}{document|h2|ul|li}{xml:*}
%~ \xmlsetsetup{#1}{ul/li/!ul}{xml:last:item} % nothing changes
%~ \xmlsetsetup{#1}{ul/li/!li}{xml:last:item} % blank item inserted
%~ \xmlsetsetup{#1}{h2/**/ul/li}{xml:last:item} % nothing changes
\xmlsetsetup{#1}{h2/***/ul/li/!ul}{xml:last:item} % shouldn’t be
this one?
\stopxmlsetups
\xmlregistersetup{xml:demo:base}
\startxmlsetups xml:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:h2
\section{\xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:ul
\startitemize\xmlflush{#1}\stopitemize
\stopxmlsetups
\startxmlsetups xml:li
\startitem\xmlflush{#1}\stopitem
\stopxmlsetups
\startxmlsetups xml:last:item
\startitem\red\xmlflush{#1}\stopitem
\stopxmlsetups
\starttext
\xmlprocessbuffer{main}{demo}{}
\stoptext
I need to be able to select the last (the one with no child)
in the element.
I thought that the lpath for that would be "h2/***/ul/li/!ul", but I
don’t know what I’m missing, since it doesn’t work at all.
Which would be the right lpath to select the last item in each list?
Many thanks for your 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] About xstring and ConTeXt
On Tue, Jul 7, 2020 at 5:19 PM Wolfgang Schuster wrote: > > Bad idea because ConTeXt also changes the meaning of \protected (you can > use \normalprotected to get the primitve). Oops, forgot about that one. > A better version is > > \pushmacro\unexpanded > \let\unexpanded\normalunexpanded > \input xstring > \popmacro\unexpanded Nice, didn't know about \push/\popmacro. Thanks! Phelype ___ 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] About xstring and ConTeXt
Phelype Oleinik schrieb am 07.07.2020 um 20:53:
Hi Jairo,
ConTeXt's \unexpanded is e-TeX's \protected, so the error boils down to
something like: \edef\x{\unexpanded{#}}, which works in Plain but not in
ConTeXt.
Usually packages that claim to be generic have to cope with that.
xstring would need to do (in a ConTeXt-specific loader):
\let\xstring@unexpanded\normalunexpanded
and
\let\xstring@unexpanded\unexpanded
in Plain and LaTeX loaders, then then use \xstring@unexpanded in the
code. But `xstring` doesn't claim (that I found, at least) to be
compatible with ConTeXt, so it's understandable: though if it is
compatible with Plain, it wouldn't be hard to adapt to ConTeXt.
That said, you can load `xstring` if you do:
\let\unexpanded\normalunexpanded
\input xstring.tex
\let\unexpanded\protected
but the internals of the package will probably be comprimised by the
misuse of (ConTeXt) \unexpanded.
Bad idea because ConTeXt also changes the meaning of \protected (you can
use \normalprotected to get the primitve).
A better version is
\pushmacro\unexpanded
\let\unexpanded\normalunexpanded
\input xstring
\popmacro\unexpanded
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
___
Re: [NTG-context] About xstring and ConTeXt
I've tried with a wrapper and it seems to work fine. However, changing
definitions "on the fly" to make xstring usable seems to break things in
ConTeXt... Whatever. I guess I will have to find out other command
redefinitions in ConTeXt.
Thank you very much, Phelype.
Jairo :)
El mar., 7 de jul. de 2020 a la(s) 13:54, Phelype Oleinik (
phe.h...@gmail.com) escribió:
> Hi Jairo,
>
> ConTeXt's \unexpanded is e-TeX's \protected, so the error boils down to
> something like: \edef\x{\unexpanded{#}}, which works in Plain but not in
> ConTeXt.
>
> Usually packages that claim to be generic have to cope with that.
> xstring would need to do (in a ConTeXt-specific loader):
> \let\xstring@unexpanded\normalunexpanded
> and
> \let\xstring@unexpanded\unexpanded
> in Plain and LaTeX loaders, then then use \xstring@unexpanded in the
> code. But `xstring` doesn't claim (that I found, at least) to be
> compatible with ConTeXt, so it's understandable: though if it is
> compatible with Plain, it wouldn't be hard to adapt to ConTeXt.
>
> That said, you can load `xstring` if you do:
> \let\unexpanded\normalunexpanded
> \input xstring.tex
> \let\unexpanded\protected
> but the internals of the package will probably be comprimised by the
> misuse of (ConTeXt) \unexpanded.
>
> Phelype
>
> On Tue, Jul 7, 2020 at 3:40 PM Jairo A. del Rio
> wrote:
> >
> > Reading about macro bundles meant to be generic (format agnostic), some
> of them work in plain/LaTeX, but crash when loaded on ConTeXt. The
> following happens with xstring.tex
> >
> > tex error > tex error on line 372 in file xstring.tex: ! Illegal
> parameter number in definition of \xs_reserved_C
> >
> >
> >
> >
> > 1
> >
> > \xs_newlines ->\unexpanded {}\xs_def \xs_arg_i {##1
> >
> > }
> >
> > \xs_newmacro_ ...name \xs_myarg }\edef \xs_reserved_C {\unexpanded
> \expandafter {\xs_newlines
> >
> > }\edef \noexpand \xs_call }\edef \xs_reserved_D {...
> >
> > l.372 \xs_newmacro\StrRemoveBraces{}{1}{1}
> >
> > {%
> >
> >
> >
> >
> >
> > You meant to type ## instead of #, right? Or maybe a } was forgotten
> somewhere
> >
> > earlier, and things are all screwed up? I'm going to assume that you
> meant ##.
> >
> > I've tried changing the catcode regime, but with no effect.
> >
> > Don't misunderstand me. I'm aware of ConTeXt capabilities and string
> manipulation via Lua. My question is more like: "Why doesn't xstring.tex?"
> >
> > Sorry if my question is outside the scope of ConTeXt
> developers/maintainers. Thank you very much.
> >
> > Jairo :)
> >
> >
> ___
> > 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] About xstring and ConTeXt
Hi Jairo,
ConTeXt's \unexpanded is e-TeX's \protected, so the error boils down to
something like: \edef\x{\unexpanded{#}}, which works in Plain but not in
ConTeXt.
Usually packages that claim to be generic have to cope with that.
xstring would need to do (in a ConTeXt-specific loader):
\let\xstring@unexpanded\normalunexpanded
and
\let\xstring@unexpanded\unexpanded
in Plain and LaTeX loaders, then then use \xstring@unexpanded in the
code. But `xstring` doesn't claim (that I found, at least) to be
compatible with ConTeXt, so it's understandable: though if it is
compatible with Plain, it wouldn't be hard to adapt to ConTeXt.
That said, you can load `xstring` if you do:
\let\unexpanded\normalunexpanded
\input xstring.tex
\let\unexpanded\protected
but the internals of the package will probably be comprimised by the
misuse of (ConTeXt) \unexpanded.
Phelype
On Tue, Jul 7, 2020 at 3:40 PM Jairo A. del Rio wrote:
>
> Reading about macro bundles meant to be generic (format agnostic), some of
> them work in plain/LaTeX, but crash when loaded on ConTeXt. The following
> happens with xstring.tex
>
> tex error > tex error on line 372 in file xstring.tex: ! Illegal parameter
> number in definition of \xs_reserved_C
>
>
>
>
> 1
>
> \xs_newlines ->\unexpanded {}\xs_def \xs_arg_i {##1
>
> }
>
> \xs_newmacro_ ...name \xs_myarg }\edef \xs_reserved_C {\unexpanded
> \expandafter {\xs_newlines
>
> }\edef \noexpand \xs_call }\edef \xs_reserved_D {...
>
> l.372 \xs_newmacro\StrRemoveBraces{}{1}{1}
>
> {%
>
>
>
>
>
> You meant to type ## instead of #, right? Or maybe a } was forgotten somewhere
>
> earlier, and things are all screwed up? I'm going to assume that you meant ##.
>
> I've tried changing the catcode regime, but with no effect.
>
> Don't misunderstand me. I'm aware of ConTeXt capabilities and string
> manipulation via Lua. My question is more like: "Why doesn't xstring.tex?"
>
> Sorry if my question is outside the scope of ConTeXt developers/maintainers.
> Thank you very much.
>
> Jairo :)
>
> ___
> 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] About xstring and ConTeXt
Reading about macro bundles meant to be generic (format agnostic), some of
them work in plain/LaTeX, but crash when loaded on ConTeXt. The following
happens with xstring.tex
tex error > tex error on line 372 in file xstring.tex: ! Illegal parameter
number in definition of \xs_reserved_C
1
\xs_newlines ->\unexpanded {}\xs_def \xs_arg_i {##1
}
\xs_newmacro_ ...name \xs_myarg }\edef \xs_reserved_C {\unexpanded
\expandafter {\xs_newlines
}\edef \noexpand \xs_call }\edef \xs_reserved_D {...
l.372 \xs_newmacro\StrRemoveBraces{}{1}{1}
{%
You meant to type ## instead of #, right? Or maybe a } was forgotten
somewhere
earlier, and things are all screwed up? I'm going to assume that you meant
##.
I've tried changing the catcode regime, but with no effect.
Don't misunderstand me. I'm aware of ConTeXt capabilities and string
manipulation via Lua. My question is more like: "Why doesn't xstring.tex?"
Sorry if my question is outside the scope of ConTeXt
developers/maintainers. Thank you very much.
Jairo :)
___
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] Vertical space between label and title
> Am 07.07.2020 um 19:27 schrieb Fabrice Couvreur : > > Hello, > I want a vertical space between the label and the chapter title: is this the > right way to proceed ? Why not? It seems to work. What’s your problem? BTW I’d set \mainlanguage[fr] Hraban ___ 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] Vertical space between label and title
Hello,
I want a vertical space between the label and the chapter title: is this
the right way to proceed ?
Thank you.
Fabrice
\setuplabeltext[chapter=Chapitre~]
\unexpanded\def\Title#1#2{\framed[frame=off,width=fit,align=flushleft]{#1\blank#2}}
\setuphead
[chapter]
[style=\bfc,
command=\Title]
\setupenumerations
[before={\blank},
after={\blank},
alternative=serried,
title=yes,
prefix=yes,
prefixsegments=chapter,
way=bychapter,
titlestyle=bold,
width=broad]
\defineenumeration
[definition]
[text=Définition,
number=yes,
headcommand=\groupedcommand{}{.},
style=italic]
\starttext
\startchapter
[title=Nombres complexes : point de vue algébrique]
\startdefinition
\input zapf
\stopdefinition
\startdefinition
\input zapf
\stopdefinition
\stopchapter
\stoptext
___
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
___
