Re: [NTG-context] Rotated table shifted on the layout
Am Fri, 17 Jan 2014 00:38:04 +0100
schrieb Wolfgang Schuster schuster.wolfg...@gmail.com:
\startplacetable [location={force,90,none}]
Thanks, it works. Interestingly, it works also if I write
location={90, page} instead of location={page, 90}.
Kind regards,
Joshua
___
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
___
Re: [NTG-context] latest beta
On 1/16/2014 11:23 PM, Thomas A. Schmitz wrote: Hi, the following test file gives an error with the latest beta: \setupbodyfont[gentium,12pt] \starttext \buildtextaccent\greekdasia\greekalphamacron \stoptext it works with a somewhat older one (2013.12.30). The error is ! Missing number, treated as zero. system tex error on line 5 in file /tmp/test.tex: Missing number, treated as zero ... to be read again \relax \buildtextaccent ...umber \b_enco_accent )}\relax \ifcase \scratchcounter \e... l.5 \buildtextaccent\greekdasia\greekalphamacron I thought this pointed to enco-ini.mkiv, but the file is unchanged between these two versions, so I'm a bit baffled. no, side effect of substantial optimizations (where i simply couldn't test everything ... you're probably the only user building accents) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] No bibliography in the output, depends on file name
On 2014–01–15 Nicola wrote:
maybe this is a known issue,
It's a known fact that context has a different notion of valid file
names than your operating system does. This is by design. To quote
the manual:
“It is highly recommended, that all input files, i.e. the ConTEXt
source and other included files such as image files, have only the
letters a–z, digits and dashes in their names, that is in the
names of their full paths, otherwise you can easily get into
problems.”
I'm writing a ConTeXt document called modern-c++.tex (in OS X 10.7.5). The
content of the file is:
\setupbibtex[database={modern-c++}, sort=author]
\setuppublications[numbering=yes]
\starttext
\completepublications[criterium=all]
\stoptext
Especially since c++ didn't work out, I expected dropping the “++”
would work (“modern-c”), but it didn't. So I ran some tracing:
\enabletrackers [resolvers.readfile]
\starttext
\readfile{file++.ext}{}{}
\stoptext
This reports:
files readfile not found by tree lookup: file .ext
Which means the “++” is replaced by two spaces, instead of searching
for “file++.ext” or “file.ext” which is what I had expected. I
didn't dig into the code to check where the spaces creep in.
Regardless if this particular issue gets fixed or not, I doubt that
Hans will put much effort into general support for “esoteric” file
names. So, it's best to avoid plus signs in file names.
Marco
signature.asc
Description: Digital signature
___
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
___
Re: [NTG-context] No bibliography in the output, depends on file name
On 1/17/2014 1:15 PM, Marco Patzer wrote:
On 2014–01–15 Nicola wrote:
maybe this is a known issue,
It's a known fact that context has a different notion of valid file
names than your operating system does. This is by design. To quote
the manual:
“It is highly recommended, that all input files, i.e. the ConTEXt
source and other included files such as image files, have only the
letters a–z, digits and dashes in their names, that is in the
names of their full paths, otherwise you can easily get into
problems.”
I'm writing a ConTeXt document called modern-c++.tex (in OS X 10.7.5). The
content of the file is:
\setupbibtex[database={modern-c++}, sort=author]
\setuppublications[numbering=yes]
\starttext
\completepublications[criterium=all]
\stoptext
Especially since c++ didn't work out, I expected dropping the “++”
would work (“modern-c”), but it didn't. So I ran some tracing:
\enabletrackers [resolvers.readfile]
\starttext
\readfile{file++.ext}{}{}
\stoptext
This reports:
files readfile not found by tree lookup: file .ext
Which means the “++” is replaced by two spaces, instead of searching
for “file++.ext” or “file.ext” which is what I had expected. I
didn't dig into the code to check where the spaces creep in.
Regardless if this particular issue gets fixed or not, I doubt that
Hans will put much effort into general support for “esoteric” file
names. So, it's best to avoid plus signs in file names.
indeed. names are parsed as url's (so + become space) so a possible fix is:
function getreadfilename(scheme,path,name)
local fullname
if hasscheme(name) or is_qualified_path(name) then
fullname = name
else
name = url.escape(name) -- yes or no ?
fullname = ((path == ) and format(%s:///%s,scheme,name)) or
format(%s:///%s/%s,scheme,path,name)
end
return resolvers.findtexfile(fullname) or -- can be more direct
end
but one cannot predict how this passes further on through the system
also, because one can say:
\readfile{file\letterpercent2B\letterpercent2B.ext}{}{}
the hack in fact should be:
if not string.find(name,%%) then
name = url.escape(name) -- if no % in names
end
which then handles both
\readfile{file\letterpercent2B\letterpercent2B.ext}{}{}
\readfile{file++.ext}{}{}
ok. Of course, when moving from c++ to c# one gets things like
\readfile{file\letterhash.ext}{}{}
where the # will sometimes confuses macros later on.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] A problem with itemize in columns - once again, now with an MWE
Hi all,
once again I have a problem with itemization in columns. This time, I
finally managed to isolate the problem and prepare an MWE. The
problem does not appear with Latin Modern fonts, but does with Pagella
(I didn't test other fonts). It seems that the height of the square
root sign is too high. \smash-ing helps, but I'd prefer not to have
to \smash things manually. Can anything be done about this? (Note:
I'm using the latest beta. In some earlier versions, \smash-ing
didn't help, so it's not something of high priority for me now. But
if it's something easy to fix, I'd be thankful.)
\setupbodyfont[pagella]
\starttext
\startitemize[columns,two,packed]% with packed, it's also wrong, but in
another way
\item abc
\item $a^2$
\item xyz
\item $\frac12$
\item foo
\item bar
\item baz
\item $\sqrt{2}$% \smash-ing helps, but I'd prefer not to have to smash...
\item asdf
\item qwerty
\stopitemize
\stoptext
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___
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
___
Re: [NTG-context] A problem with itemize in columns - once again, now with an MWE
Am 17.01.2014 um 16:05 schrieb Marcin Borkowski mb...@wmi.amu.edu.pl:
Hi all,
once again I have a problem with itemization in columns. This time, I
finally managed to isolate the problem and prepare an MWE. The
problem does not appear with Latin Modern fonts, but does with Pagella
(I didn't test other fonts). It seems that the height of the square
root sign is too high. \smash-ing helps, but I'd prefer not to have
to \smash things manually. Can anything be done about this? (Note:
I'm using the latest beta. In some earlier versions, \smash-ing
didn't help, so it's not something of high priority for me now. But
if it's something easy to fix, I'd be thankful.)
You can increase the linespacing in the itemize.
\setupbodyfont[pagella]
\startsetups[itemize:before]
\blank
\begingroup
\setupinterlinespace[medium]
\stopsetups
\startsetups[itemize:after]
\endgroup
\blank
\stopsetups
\starttext
\startitemize[columns,two,packed][before=\directsetup{itemize:before},after=\directsetup{itemize:after}]
\item abc
\item \math{a^2}
\item xyz
\item \math{\frac{1}{2}}
\item foo
\item bar
\item baz
\item \math{\sqrt{2}}
\item asdf
\item qwerty
\stopitemize
\stoptext
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] A problem with itemize in columns - once again, now with an MWE
Dnia 2014-01-17, o godz. 16:19:48
Wolfgang Schuster schuster.wolfg...@gmail.com napisał(a):
Am 17.01.2014 um 16:05 schrieb Marcin Borkowski
mb...@wmi.amu.edu.pl:
Hi all,
once again I have a problem with itemization in columns. This
time, I finally managed to isolate the problem and prepare an MWE.
The problem does not appear with Latin Modern fonts, but does with
Pagella (I didn't test other fonts). It seems that the height of
the square root sign is too high. \smash-ing helps, but I'd prefer
not to have to \smash things manually. Can anything be done about
this? (Note: I'm using the latest beta. In some earlier versions,
\smash-ing didn't help, so it's not something of high priority for
me now. But if it's something easy to fix, I'd be thankful.)
You can increase the linespacing in the itemize.
\setupbodyfont[pagella]
\startsetups[itemize:before]
\blank
\begingroup
\setupinterlinespace[medium]
\stopsetups
\startsetups[itemize:after]
\endgroup
\blank
\stopsetups
\starttext
\startitemize[columns,two,packed][before=\directsetup{itemize:before},after=\directsetup{itemize:after}]
\item abc
\item \math{a^2}
\item xyz
\item \math{\frac{1}{2}}
\item foo
\item bar
\item baz
\item \math{\sqrt{2}}
\item asdf
\item qwerty
\stopitemize
\stoptext
Thanks a lot! It did help (but only partially, see below). (I've also
put it into \setupitemize.)
One problem remains, however: it won't work with [joinedup]. (The same
problem as before seems to appear again.)
Wolfgang
TIA,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___
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] Colored text's background, which the more lcd-mkiv?
[Colored text's background, which the more lcd-mkiv?;
plus: Metapost variable text with \definetextbackground;
plus: {\input ward}]
Hi list,
What would be the best, also the more up to date, way to put colored
background behind text, that could cross page boundaries.
I have found three ways of doing this: I would like to know which is
best practice, and also the more lua context document fashion.
1- Using \startbar[underbar] \input zapf \stopbar as described p. 39
of hybrid.pdf.
2- Using \startMPpositionmethod{mpos:placeholder}, found in
http://tex.stackexchange.com/questions/125162/rounded-box-around-placeholder-text-that-supports-line-breaking/125323
(Thanks to Aditya).
A bit tricky, but perhaps the more versatile or universal?
3- Start with: \definetextbackground (same ref. as previous).
%
% About the third one I have had some difficulties, that might be
thought of as a bug.
% You might want and try the following example: it doesn't work if you
have a MetaPost variable
% whose name is text.
\starttext
\startMPcode
% numeric text; %% Try and uncomment this line
drawarrow (0,0)--(3cm,1cm);
\stopMPcode
%%%
\definecolor [lightblue] [r=0.5, g=0.5, b=1]
\definetextbackground
[placeholder]
[
location=text,
background=color,
backgroundcolor=lightblue,
frame=on,
corner=round,
radius=0.8\lineheight,
]
\placeholder{\input ward }
% \placeholder{\input ward} %% Try and uncomment this line
\stoptext
% Local Variables:
% mode: context
% coding: utf-8
% End:
Regards,
Chris
___
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
___
Re: [NTG-context] Colored text's background, which the more lcd-mkiv?
On Fri, 17 Jan 2014, Elspeth McGullicuddy wrote:
[Colored text's background, which the more lcd-mkiv?;
plus: Metapost variable text with \definetextbackground;
plus: {\input ward}]
Hi list,
What would be the best, also the more up to date, way to put colored
background behind text, that could cross page boundaries.
I have found three ways of doing this: I would like to know which is
best practice, and also the more lua context document fashion.
1- Using \startbar[underbar] \input zapf \stopbar as described p. 39
of hybrid.pdf.
Use this one, unless the underbars are indequate, as was the case for the
OP of the TeX.SX question.
2- Using \startMPpositionmethod{mpos:placeholder}, found in
http://tex.stackexchange.com/questions/125162/rounded-box-around-placeholder-text-that-supports-line-breaking/125323
(Thanks to Aditya).
A bit tricky, but perhaps the more versatile or universal?
3- Start with: \definetextbackground (same ref. as previous).
%
% About the third one I have had some difficulties, that might be
thought of as a bug.
% You might want and try the following example: it doesn't work if you
have a MetaPost variable
% whose name is text.
(Untested). Normally this means that there is already a variable with the
name text. You can use:
save text; numeric text;
or
newnumeric text;
which is shortcut for the former.
Aditya
___
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
___
Re: [NTG-context] Need for \buildtextaccent, was Re: latest beta
On 1/17/2014 5:04 PM, Rik Kabel wrote:
On 2014-01-17 06:22, Hans Hagen wrote:
no, side effect of substantial optimizations (where i simply couldn't
test everything ... you're probably the only user building accents)
Hans
It is needed to create what might otherwise be LATIN SMALL LETTER Q WITH
ACUTE ACCENT as well.
This is not a Unicode character, but is easily constructed as:
\buildtextaccent\textacute q
for use in setting, for example, this bit of Spinoza's /Tractatus
Politicus/, in which it appears four times.
The character was commonly used in Latin texts published from the 16th
through the 19th century.
The above was done with LaTeX (\csdef is from etoolbox) and the
following preamble code:
\DeclareTextAccent{\RKacute}{\UTFencname}{00B4}
\newcommand*{\RKqacute}{\RKacute q}% LATIN SMALL LETTER Q WITH ACUTE
ACCENT
% The following works, instead of the above, with Linux Libertine (and
%+ probably many other fonts) but does not work with the IM Fell
fonts,
%+ which are missing glyph 0x301, COMBINING ACUTE ACCENT:
% \csdef{RKacute}#1{#1\char301}
% \csdef{RKqacute}{\RKacute{q}}
do we need a module with predefined 'missing from unicode' characters?
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] hyphenating \ConTeXt
On 01/15/2014 11:56 PM, Marco Patzer wrote: On 2014–01–15 Pablo Rodriguez wrote: how should I invoke \hyphenation so it hyphens the \ConTeXt command? \ConTeXt is defined as “Con\TeX t” and \TeX uses kerns and boxes, both of which suppress hyphenation. AFAIK there's no easy way around it. Many thanks for your help, Marco. I would like to hyphenate ConTeXt as the standard English word (Con-TeXt). Sorry for having to explain that ;-), but I’m writing an introduction to ConTeXt in Spanish. I had already rewritten two sentences in less than five pages to avoid the not-hyphenated ConTeXt word. Is there no simpler way to do this? 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] hyphenating \ConTeXt
On Fri, 17 Jan 2014, Pablo Rodriguez wrote:
On 01/15/2014 11:56 PM, Marco Patzer wrote:
On 2014–01–15 Pablo Rodriguez wrote:
how should I invoke \hyphenation so it hyphens the \ConTeXt command?
\ConTeXt is defined as “Con\TeX t” and \TeX uses kerns and boxes,
both of which suppress hyphenation. AFAIK there's no easy way around
it.
Many thanks for your help, Marco.
I would like to hyphenate ConTeXt as the standard English word (Con-TeXt).
Sorry for having to explain that ;-), but I’m writing an introduction to
ConTeXt in Spanish. I had already rewritten two sentences in less than
five pages to avoid the not-hyphenated ConTeXt word.
Is there no simpler way to do this?
\starttext
\hsize 4mm
\CONTEXT
\def\CONTEXT{Con\discretionary{}{-}{}\TeX{}t}
\CONTEXT
% Or if you dislike the way TeX is typeset
\def\CONTEXT{ConTeXt}
\CONTEXT
\stoptext
Aditya___
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
___
Re: [NTG-context] Need for \buildtextaccent, was Re: latest beta
On Fri, Jan 17, 2014 at 7:11 PM, Hans Hagen wrote:
do we need a module with predefined 'missing from unicode' characters?
I don't think so. We can end up with a neverending and always
incomplete list (with theoretically unlimited number of entries),
usable only to those few people who will care to contribute. In my
opinion such a list is pretty much useless.
Unicode already specifies that one could use q followed by
combining acute. And TeX also has support for {\'q}. Everything else
is private use, something that users might not even use in more than a
single document. I don't see any advantage in creating an endless
incomplete list. In all honesty it's a lot more
useful/readable/straightforward to use {\'q} or proper Unicode in
these cases. And if it's not comfortable enough for the user, he can
always provide his own private definitions.
Thomas and Rik most probably need just the existing mechanism to work
properly. Well, it might be slightly different for Thomas where
Ancient Greek has a limited set of letters, but then such a list
should better be defined in an ancient greek predefined characters
module.
Just my 2 cents.
Mojca
___
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
___
Re: [NTG-context] Need for \buildtextaccent, was Re: latest beta
On 1/17/2014 7:39 PM, Mojca Miklavec wrote:
On Fri, Jan 17, 2014 at 7:11 PM, Hans Hagen wrote:
do we need a module with predefined 'missing from unicode' characters?
I don't think so. We can end up with a neverending and always
incomplete list (with theoretically unlimited number of entries),
usable only to those few people who will care to contribute. In my
opinion such a list is pretty much useless.
Unicode already specifies that one could use q followed by
combining acute. And TeX also has support for {\'q}. Everything else
is private use, something that users might not even use in more than a
single document. I don't see any advantage in creating an endless
incomplete list. In all honesty it's a lot more
useful/readable/straightforward to use {\'q} or proper Unicode in
these cases. And if it's not comfortable enough for the user, he can
always provide his own private definitions.
Thomas and Rik most probably need just the existing mechanism to work
properly. Well, it might be slightly different for Thomas where
Ancient Greek has a limited set of letters, but then such a list
should better be defined in an ancient greek predefined characters
module.
the mechanisms works ok (i just made it a bit more efficient, not that
it matters much)
Just my 2 cents.
it depends on to what extend such characters play a different role too
and need to travel around (but as there never was any demand for that i
assume 2 cents will do)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] hyphenating \ConTeXt
On 01/17/2014 07:18 PM, Aditya Mahajan wrote:
On Fri, 17 Jan 2014, Pablo Rodriguez wrote:
[...]
I would like to hyphenate ConTeXt as the standard English word (Con-TeXt).
Sorry for having to explain that ;-), but I’m writing an introduction to
ConTeXt in Spanish. I had already rewritten two sentences in less than
five pages to avoid the not-hyphenated ConTeXt word.
Is there no simpler way to do this?
[...]
\def\CONTEXT{Con\discretionary{}{-}{}\TeX{}t}
Many thanks, Aditya.
This was exactly what I wanted. I didn’t know of the existence of the
\discretionary command.
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] hyphenating \ConTeXt
On 2014–01–17 Pablo Rodriguez wrote: On 01/15/2014 11:56 PM, Marco Patzer wrote: On 2014–01–15 Pablo Rodriguez wrote: how should I invoke \hyphenation so it hyphens the \ConTeXt command? \ConTeXt is defined as “Con\TeX t” and \TeX uses kerns and boxes, both of which suppress hyphenation. AFAIK there's no easy way around it. Many thanks for your help, Marco. I would like to hyphenate ConTeXt as the standard English word (Con-TeXt). Sometimes I'm missing the obvious and make things more complicated than necessary. Sorry for having to explain that ;-), It's not you, it's me :) Is there no simpler way to do this? See Aditya's answer. Marco signature.asc Description: Digital signature ___ 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 ___
Re: [NTG-context] Colored text's background, which the more lcd-mkiv?
On Fri, Jan 17, 2014 at 6:16 PM, Aditya Mahajan adit...@umich.edu wrote:
On Fri, 17 Jan 2014, Elspeth McGullicuddy wrote:
[Colored text's background, which the more lcd-mkiv?;
plus: Metapost variable text with \definetextbackground;
plus: {\input ward}]
Hi list,
What would be the best, also the more up to date, way to put colored
background behind text, that could cross page boundaries.
I have found three ways of doing this: I would like to know which is
best practice, and also the more lua context document fashion.
1- Using \startbar[underbar] \input zapf \stopbar as described p. 39
of hybrid.pdf.
Use this one, unless the underbars are indequate, as was the case for the OP
of the TeX.SX question.
This one is very easy to use, but I liked the rounded corners of the example.
Also I want it to fill the whole background, as it is the case with
\definetextbackground: it starts where you tell it to start, then fill
the whole text area, not only where there actually are glyphs, so it
keeps going on even if you put a \pagebreak, and stop when you tell it
to stop.
Instead \startbar[underbar] put color only where there are glyphs,
which is not what I'm looking for, unless there is way to do other
wise, but it would contradict the name underbar, so it seems unlikely.
So I think I'll go to \definetextbackground. And try some experiments
with the MPposition stuffs.
2- Using \startMPpositionmethod{mpos:placeholder}, found in
http://tex.stackexchange.com/questions/125162/rounded-box-around-placeholder-text-that-supports-line-breaking/125323
(Thanks to Aditya).
A bit tricky, but perhaps the more versatile or universal?
3- Start with: \definetextbackground (same ref. as previous).
%
% About the third one I have had some difficulties, that might be
thought of as a bug.
% You might want and try the following example: it doesn't work if you
have a MetaPost variable
% whose name is text.
(Untested). Normally this means that there is already a variable with the
name text. You can use:
Yes it's what I gathered. It took me some time to do so, though.
I didn't know of the nuewnumeric which is a good shortcut.
Thanks for this quick answer,
Chris
save text; numeric text;
or
newnumeric text;
which is shortcut for the former.
Aditya
___
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] issues with \setuplist
Dear list,
generating a table of contents with the following sample:
\setupinterlinespace[line=3.5ex]
\setuplist[section][alternative=d, style={\itx\setupinterlinespace},
separator={·}]
\starttext
\placecontent
\dorecurse{5}{\chapter{Chapter}\dorecurse{10}{\section{Long Section
Title}}}
\stoptext
I experience two issues.
The first one is that I have no hay to get the sections that build a
paragraph to have an adapted \setupinterlinespace. Right now the
interline space is too high. And \setupinterlinespace from style doesn’t
seem to work.
The second issue is that I would like to get a separator between each
section item in the table of contents. Am I missing something about
separator?
Could anyone explain what is wrong with the sample?
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] hyphenating \ConTeXt
On 01/17/2014 08:04 PM, Marco Patzer wrote: On 2014–01–17 Pablo Rodriguez wrote: [...] I would like to hyphenate ConTeXt as the standard English word (Con-TeXt). Sometimes I'm missing the obvious and make things more complicated than necessary. Many thanks for the reply and for your help, Marco. I wonder whether it would make sense to enable \ConTeXt hyphenation by default. 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://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Need for \buildtextaccent, was Re: latest beta
On 01/17/2014 07:39 PM, Mojca Miklavec wrote: Thomas and Rik most probably need just the existing mechanism to work properly. Well, it might be slightly different for Thomas where Ancient Greek has a limited set of letters, but then such a list should better be defined in an ancient greek predefined characters module. Mojca is right. These are special cases (for example metrical descriptions), and for me at least, it wouldn't make sense to predefine them since I may need slighly different definitions depending on font, purpose, etc. Thomas ___ 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 ___
Re: [NTG-context] Need for \buildtextaccent, was Re: latest beta
I don't think so. We can end up with a neverending and always incomplete list (with theoretically unlimited number of entries), usable only to those few people who will care to contribute. I couldn't agree more. Unicode already has mechanisms to encode just about any accented character, and OpenType has its own mechanisms to display them very accurately. It's best to use these standard features and an appropriate font. Arthur ___ 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 ___
