> On 3/27/2014 9:46 AM, Xan wrote:
> > \starttext
> >
> > A
> > \xmlprocessfile{demo}{./dades.xml}{}
> > B
> > \stoptext
>
> \startxmlsetups xml:demo:code
>\blank
>\start \ttx
> \xmlverbatim{#1}
>\stop
>\blank
> \stopxmlsetups
First of all, thank you very much, Hans.
But why
On 3/27/2014 9:46 AM, Xan wrote:
\starttext
A
\xmlprocessfile{demo}{./dades.xml}{}
B
\stoptext
\startxmlsetups xml:demo:code
\blank
\start \ttx
\xmlverbatim{#1}
\stop
\blank
\stopxmlsetups
--
-
ontext, all is ok, but when I substitute the
\startlines \stoplines with \starttyping \stoptyping context never ends.
Is that a bug?
I just found [this](http://www.ntg.nl/pipermail/ntg-context/2012/064750.html),
but really no solution. Since 2012 I suppose many things are changed so I ask.
Why d
Hi,
If I compile the following example, the pdf output is empty.
\starttyping
\usemodule[pstricks]
\startPSTRICKS
\pspicture(0cm,0cm)(20cm,20cm)
\psline(0,0)(20,20)
\psline(1,1)(10,10)
\endpspicture
\stopPSTRICKS
\stoptyping
Thanks
Am 06.02.2014 um 19:29 schrieb Pablo Rodriguez :
> On 02/06/2014 12:57 AM, Wolfgang Schuster wrote:
>> Am 05.02.2014 um 19:50 schrieb Pablo Rodriguez :
>>
>>> Hi Hans,
>>>
>>> I have the following sample:
>>>
>>> \setuptyping[option=
On 02/06/2014 12:57 AM, Wolfgang Schuster wrote:
> Am 05.02.2014 um 19:50 schrieb Pablo Rodriguez :
>
>> Hi Hans,
>>
>> I have the following sample:
>>
>> \setuptyping[option=TEX]
>> \starttext
>> \starttyping
>> \input zapf % knuth
>>
Am 05.02.2014 um 19:50 schrieb Pablo Rodriguez :
> Hi Hans,
>
> I have the following sample:
>
> \setuptyping[option=TEX]
> \starttext
> \starttyping
> \input zapf % knuth
> \stoptyping
> \stoptext
>
> The percent character is in bold font and gray color,
Hi Hans,
I have the following sample:
\setuptyping[option=TEX]
\starttext
\starttyping
\input zapf % knuth
\stoptyping
\stoptext
The percent character is in bold font and gray color, but the rest of
the commented text isn’t.
My suggestion would be to apply the same color and font of the
On 02/02/2014 07:16 PM, Wolfgang Schuster wrote:
> Am 02.02.2014 um 19:12 schrieb Pablo Rodriguez :
>> I would like to use \tex{visiblespace} which is actually character
>> u2420.
>> [...]
>
> \setuptype [space=on]
> \setuptyping[space=on]
>
> \starttext
>
ould I do it?
\setuptype [space=on]
\setuptyping[space=on]
\starttext
\type{x y}
\starttyping
x y
\stoptyping
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
mai
hown in the following sample (beta from 2014.02.01 14:22):
>
> \definefontfamily[mainface][mono][ryt1xtt][bf=ryt1xbtt]
> \setupbodyfont[mainface]
> \definetyping[TeXcode][option=TEX]
> \starttext
> \starttyping
> \ConTeXt\ is
> \stoptyping
> \startTeXcode
> \ConTeXt\
][mono][ryt1xtt][bf=ryt1xbtt]
\setupbodyfont[mainface]
\definetyping[TeXcode][option=TEX]
\starttext
\starttyping
\ConTeXt\ is
\stoptyping
\startTeXcode
\ConTeXt\ is
\stopTeXcode
\stoptext
If option=TEX is enabled, there is no space after the backslash.
I have checked the font and it seems to work
Dear list,
the following sample:
\showframe
\setuppapersize[S6]
\setuptyping[option=TEX,lines=yes]
\starttext
\starttyping
\startvariante[MRU]{{\em om} X}En un lugar de la Mancha, de cuyo nombre
no quiero acordarme, no ha mucho tiempo que vivía un hidalgo de los de
lanza en astillero, adarga
are user ones. With \type{\setupbodyfont}
%D one can set the document bodyfont size, font family, style
%D and/or options defined in files, for example:
%D
%D \starttyping
%D \setupbodyfont[modern,12pt,roman]
%D \stoptyping
%D
%D This command affects the document as a whole: text, headers
%D and foo
] [file:consolasbolditalic]
[features=none]
\stoptypescript
\definetypeface [mainface] [rm] [serif] [modern] [default]
\definetypeface [mainface] [tt] [mono] [consolas] [default]
%\definetypeface [mainface] [tt] [mono] [modern] [default]
\setupbodyfont[mainface]
\starttext
\starttyping
a b cd
x y z
s=none]
>> \definefontsynonym [MonoBoldItalic] [file:consolasbolditalic]
>> [features=none]
>> \stoptypescript
>>
>> \definetypeface [mainface] [rm] [serif] [modern] [default]
>> \definetypeface [mainface] [tt] [mono] [consolas] [default]
>> %\definety
] [default]
\definetypeface [mainface] [tt] [mono] [consolas] [default]
%\definetypeface [mainface] [tt] [mono] [modern] [default]
\setupbodyfont[mainface]
\starttext
\starttyping
a b cd
x y z
\stoptyping
\stoptext
are we talking about the same font?
\starttypescript [mono] [consolas
] [consolas] [default]
%\definetypeface [mainface] [tt] [mono] [modern] [default]
\setupbodyfont[mainface]
\starttext
\starttyping
a b cd
x y z
\stoptyping
\stoptext
Wolfgang
___
If your question is of interest to
On Sat, Aug 31, 2013 at 7:44 PM, Wolfgang Schuster
wrote:
> When you want a smaller size for the monospaced font you can use the rscale
> key from \definetypeface.
*That* was the command that I was grappling to find and that I've used before.
> \setuptyping[style=small]
If I do this, the fon
Am 31.08.2013 um 18:35 schrieb Mari Voipio :
> Hello,
>
> I know I should be able to do it (and think I've done it once upon a
> time), but how do I change the font size just for \tt and for
> \starttyping \stoptyping environment?
>
> I have no problems with the font
Hello,
I know I should be able to do it (and think I've done it once upon a
time), but how do I change the font size just for \tt and for
\starttyping \stoptyping environment?
I have no problems with the font used, I just want my typed text to be
a tad smaller (like \tfx for that font).
typing environment?
[...]
you shouldn't rely on \\ as it also starts a new line with content
\dorecurse{38}{line\par}
Hans,
I have adapted the sample to:
\starttext
\dorecurse{41}{line\par}
\starttyping
\setuplayout[setups=*lessstrict]
\startsetups[*lesss
n the typing environment?
> [...]
> you shouldn't rely on \\ as it also starts a new line with content
>
>\dorecurse{38}{line\par}
Hans,
I have adapted the sample to:
\starttext
\dorecurse{41}{line\par}
\starttyping
\setuplayout[setups=*lessst
\clubpenalty=1
\stopsetups
\starttext
\dorecurse{38}{line\\}
\starttyping
\setuplayout[setups=*lessstrict]
\startsetups[*lessstrict]
\setup[reset]
\widowpenalty=1
\clubpenalty=1
\brokenpenalty=1
\stopsetups
ty=1
\stopsetups
\starttext
\dorecurse{38}{line\\}
\starttyping
\setuplayout[setups=*lessstrict]
\startsetups[*lessstrict]
\setup[reset]
\widowpenalty=1
\clubpenalty=1
\brokenpenalty=1
\stopsetups
\stoptyping
\page
Dear list,
using the latest beta (it also happens with ConTeXt from TL 2013), I
don’t get the space in \type{\em #1}.
Here you have a minimal sample that shows the difference with other
verbatim commands:
\starttext
\type{\em #1}
\arg{\em #1}
\starttyping\em #1\stoptyping
Am 26.06.2013 um 20:30 schrieb Pablo Rodríguez :
> Dear list,
>
> I have the two following samples:
>
> \startstandardmakeup[align=middle]
> \starttyping[option=TeX]
> \mainlanguage[es]
> \setuplanguage[es][patterns={es,agr}]
> \stoptyping
> \stopstandardmakeup
&
Dear list,
I have the two following samples:
\startstandardmakeup[align=middle]
\starttyping[option=TeX]
\mainlanguage[es]
\setuplanguage[es][patterns={es,agr}]
\stoptyping
\stopstandardmakeup
\startstandardmakeup[align=middle]
Would that in body and spirit Shakespeare came\\
Visible emperor of
. I have problem with starttyping command.
> Somehow, it is not giving me same as I key in. Two examples are give here
> to explain my problem. Please see ">>>". Any help will be appreciated
> much.
>
> Jung, Jinki
>
>
> \starttyping
Am 29.04.2013 um 11:20 schrieb jinki jung :
> Hi there,
>
> I am using context 0.6 under W7. I have problem with starttyping command.
> Somehow, it is not giving me same as I key in. Two examples are give here
> to explain my problem. Please see ">>>&q
Hi there,
I am using context 0.6 under W7. I have problem with starttyping command.
Somehow, it is not giving me same as I key in. Two examples are give here
to explain my problem. Please see ">>>". Any help will be appreciated
much.
Jung, Jinki
\starttyping
Hi,
After some experimenting, I settled on the next interface for dynamic
features:
The is also a generic command \type {\feature} that takes two arguments.
Below we show all calls, with long and short variants:
\starttyping
\addfeature[f:mine] \feature [more][f:mine] \feature
e combinations. This is
where the \type {compositions} goodie kicks in:
\starttyping
local compose = {
[0x1E02] = {
anchored = "top",
},
[0x1E04] = {
anchored = "bottom",
},
[0x0042] = { -- B
anchors = {
top = {
x = 300,
y = 700,
On 2013–02–15 thomas wrote:
> how can i put a normal # sign (as part of a \type{} environment) in
> a footnote ? Until now i got "" or "\#" or nothing.
>
> Please look at the attached example and log-output.
It works for \type if you use \asciimode
Dear list,
how can i put a normal # sign (as part of a \type{} environment) in a
footnote ? Until now i got "" or "\#" or nothing.
Please look at the attached example and log-output.
Thanks
Thomas
\starttext
Repo initialisieren
\starttyping
$ git init
\stopty
Thank you for your answers,
in my case, start-/stoplines is actually much better.
Kind regards,
Ingo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context
, and
some problems are showing up now.
So here it goes ...
What I want to accomplish:
The user writes the address, and he should not have to use \crlf or have
to use several distinct commands.
Why does the following not work?
\defineblock[Address]
\setupblock[Address][
before=\starttyping
.
So here it goes ...
What I want to accomplish:
The user writes the address, and he should not have to use \crlf or have
to use several distinct commands.
Why does the following not work?
\defineblock[Address]
\setupblock[Address][
before=\starttyping,
after=\stoptyping
]
you pick the
accomplish:
The user writes the address, and he should not have to use \crlf or have
to use several distinct commands.
Why does the following not work?
\defineblock[Address]
\setupblock[Address][
before=\starttyping,
after=\stoptyping
]
\starttext
\beginAddress
Peter Pan
Somewhere over the
starts snapping
+with the default behavior. If this does not lead to the
+desired results, the value \type{strict} will adjust the
+grid more rigidly and \type{tolerant} more loosely.
+
+\startexample
+\starttyping
+\setuplayout[grid=yes]
+\stoptyping
+\stopexample
+
During typesetting on a grid the
re, I suppose that typesetting Greek characters verbatim
> > depends also upon which \tt font is being used.
>
> \setupbodyfont[dejavu]
>
> \starttext
>
> \starttyping
> $L_{α+β}$
> \stoptyping
>
ttext
\starttyping
$L_{α+β}$
\stoptyping
\stoptext
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875
exactly the
first one found in that text:
\usemodule[lettrine]
\starttext
\lettrine {T}{he two} typeset arguments are the dropped capital
and the run-in text following it; the \TeX\ source of this paragraph
started
with \starttyping "\usemodule[lettrine]
\starttext
\lettrine{
defines a memory pool from
* which we allocate neighbour entries. */
MEMB(neighbours_memb, struct neighbour, MAX_NEIGHBOURS);
\stopC
\blank
\starttyping
/* This MEMB() definition defines a memory pool from
* which we allocate neighbour entries. */
MEMB(neighbours_memb, struct neighbour
rd|/|backward
%D reference mechanism is provided by the macro \type{\atpage}:
%D
%D \starttyping
%D ... \somewhere{backward text}{forward text}[someref] ...
%D ... \atpage[someref] ...
%D \stoptyping
%D
%D In future versions there will be more sophisticated
% 0 = no page reference
% 1 = same page
% 2
ary|/|experimental forward|/|backward
> %D reference mechanism is provided by the macro \type{\atpage}:
> %D
> %D \starttyping
> %D ... \somewhere{backward text}{forward text}[someref] ...
> %D ... \atpage[someref] ...
> %D \stoptyping
> %D
> %D In future versions there wil
ded by the macro \type{\atpage}:
%D
%D \starttyping
%D ... \somewhere{backward text}{forward text}[someref] ...
%D ... \atpage[someref] ...
%D \stoptyping
%D
%D In future versions there will be more sophisticated
% 0 = no page reference
% 1 = same page
% 2 = preceding page
% 3 = following page
% 4
kes care of non||existing files. This macro has two faces.
%D
%D \starttyping
%D \ReadFile {filename}
%D \readfile {filename} {before loading} {not found}
%D \stoptyping
%D
%D Many \TEX\ implementations have laid out some strategy for
%D locating files. This can lead to unexpected results,
%D especially
le,ReadFile}
%D
%D One cannot be sure if a file exists. When no file can be
%D found, the \type{\input} primitive gives an error message
%D and switches to interactive mode. The macro \type{\readfile}
%D takes care of non||existing files. This macro has two faces.
%D
%D \starttyping
%D \ReadFil
date=\currentdate,
%D copyright={PRAGMA ADE \& \CONTEXT\ Development Team}]
%C
%C This module is part of the \CONTEXT\ macro||package and is
%C therefore copyrighted by \PRAGMA. See mreadme.pdf for
%C details.
%D The fonts can be downloaded from the (nice looking) page:
%D
%D \starttypin
own in the example you can use the \type {style} and
%D more low level \type {font} keys to set up the font where
%D the first one wins. If you don't like the behaviour you can always
%D roll out your own command.
%D
%D \starttyping
%D \placeinitial \input ward \par \input ward \par \placeinitia
··
> >\definetextbackground[tb]
> >\setuptyping[
> > after={\stoptextbackground},
> > before={\starttextbackground[tb]},
> >]
>
> add [location=paragraph]
Thanks, looks good now!
Philipp
>
> >\starttext
> >
> >foo
>
kground[tb]},
]
add [location=paragraph]
\starttext
foo
\starttyping
bar
\stoptyping
baz
\starttabulate[|r|l|]
\NC foo \NC bar \AR
\stoptabulate%
^^ missing \NC
\stoptext
·
Regards
Philipp
\setuptextbackgro
ook at it anyways because
the text background looks weird even after.
·
\definetextbackground[tb]
\setuptyping[
after={\stoptextbackground},
before={\starttextbackground[tb]},
]
\starttext
foo
\starttyping
bar
\stoptyping
baz
ced
start/stop pair.
The same message arise also with \starttyping:
\starttext
\starttyping
…
%\starttyping
…
\stoptyping
\stoptext
Wolfgang
___
If your question is of interest to others as well, please add an ent
> \cdot \sin(0.5x)\right+1) e^{-0.4x}$'
>
> to get nice result. On the other hand I'm not exactly sure how to
> reliably print whatever gets passed to ConTeXt. The only option that
> comes to my mind is some modification of
> \sometxt{\starttyping floor($1/0.01) \stoptypin
nTeXt. The only option that
comes to my mind is some modification of
\sometxt{\starttyping floor($1/0.01) \stoptyping}
where \starttyping would generate a single line. But one would need a
special option for that. (The command \type{...} would not be reliable
enough: in MKII it stops working at the seco
On 22-1-2012 22:41, Sietse Brouwer wrote:
After context.starttyping(), a hash mark in the first position gets
printed twice. A hash mark in any other position gets printed
normally.
This bug does not occur after tex.print("\\starttyping"),
It's not so much a bug as a side ef
In attempting to use Thomas's xml presentation style he presented at C5M, I
would like to add the ability to typeset verbatim code snippets. In the
xml:code setup example below, using commands like
\startlinenumbering-\stoplinenumbering work fine, but using
\starttyping-\stoptyping breaks
On Sat, Jan 14, 2012 at 04:37, Hans Hagen wrote:
> this related to the buffer bug (still no new beta as i'm redoing some font
> code and have not much time today)
OK. Is there some convenient way to revert to the last known good
version of standalone ConTeXt?
I ended up installing the Ubuntu pac
Am 13.01.2012 um 12:00 schrieb Richard Weickelt:
> Hi,
>
> I've tried to include some C-code into my document, but failed to enable
> syntax highlighting.
>
> Tested on: linux-64, context-2011.05.18 (same with the beta) stand-alone mkIV
>
> 1) \starttyping[option
On 14-1-2012 00:40, mathew wrote:
Just this minute updated via wget
http://minimals.contextgarden.net/setup/first-setup.sh and running
first-setup.sh, getting errors trying to use \starttyping/\stoptyping.
--- example file ---
\starttext
\startframedtext[width=5.5cm]
\starttyping
Line 1
Line 2
Hi,
I've tried to include some C-code into my document, but failed to enable
syntax highlighting.
Tested on: linux-64, context-2011.05.18 (same with the beta) stand-alone mkIV
1) \starttyping[option=C] just prints verbatim text. There seems to be no
formatter for C out of the box.
Just this minute updated via wget
http://minimals.contextgarden.net/setup/first-setup.sh and running
first-setup.sh, getting errors trying to use \starttyping/\stoptyping.
--- example file ---
\starttext
\startframedtext[width=5.5cm]
\starttyping
Line 1
Line 2
Line 3
\stoptyping
\stopframedtext
fine\PictureFrameHeight {.830\textheight}
\define\PictureFrameWidth {.476\textwidth}
%D As we said before, the presentation consists of three kinds of pages: title,
%D horizontal, and vertical. Each page can have a different background; we can
%D switch to a specific background using
%D \starttypin
and
namespacing).
"typing" (\starttyping) seems undefined now.
ah, I forgot something when moving to the new inheritance code .. fixed
Hans
-
Hans Hagen |
Am 2011-12-22 um 14:55 schrieb Hans Hagen:
This version might also solve some of the reported problems with
page imposition (as the page-* modules are being cleaned up buglets
cna be introduced .. nothing really changes there apart from speedup
and namespacing).
"typing" (\s
, I don’t know where you found the code but I’m going to explain
> what was wrong, this will help you write something better next time.
>
> What you defined was the following piece of code:
>
> \crlf
> \setupbackground[..,.=.,..]
> \startbackground
> \startlines[style=type]
help you write something better next time.
What you defined was the following piece of code:
\crlf
\setupbackground[..,.=.,..]
\startbackground
\startlines[style=type]
\setupalign[right]
\starttyping
…
\stoptyping
\stoplines
\stopbackground
\crlf
1. You used \crlf to add a empty line at the begin a
fset=0.5cm,
bottomoffset=0.5cm]
\startbackground
\startlines
},
after={
\stoplines
\stopbackground
\crlf
},
commands={\setupalign[right]},
style=type]
\starttext
Hello World
\startCodeExample
\starttyping
H
ep in mind that people might want to pass the generated code
around as arguments in which case catcodes can create a mess
Agreed. But this is for syntax highlighting, so I have to mess with
catcodes anyways. My code wail fail if it is passed as an argument to some
other macro, but so do
alpage \EQ \currentreferencerealpage \NC\NR
\stoptabulate
\stopsetups
\definereferenceformat[referencetable][setups=reference:table]
\starttext
\section[sec:table]{Values for the reference command}
\starttyping
\startsection[reference=sec:table,title={Values for the reference command}]
\s
nge in storing positional info in the tuc file.
No big deal, just another format.
== There has been a fix in otf contextual stuff ... for Idris (so that
he can finish the context book sooner).
== There are some new commands: \startdocument and \stopdocument. Copied
from mag-1101:
\s
Hello ConTEXist.
I know that this probably is no reason, but can be in an environment
\starttyping ... \stoptyping turn on, which will each blank line in the
statement reflect? I want put in the presentation in this environment, a
direct numbers of blank lines. The larger number of empty
gt;>
>>> \starttext
>>> \startframedtext[middle][width=.8\textwidth]
>>> \startframedtext[left][frame=off, width=.6\textwidth]
>>> \starttyping
>>> import x
>>> from x import y
>>> for z in b:
>>>print dfdg
>>> Som
verbatim lines are overflowing the framed text box I'm
>> putting them in. I see that I could define a pretty printer to handle
>> this but I came up with the following:
>>
>>
>> \starttext
>> \startframedtext[middle][width=.8\textwidth]
>> \startframedte
middle][width=.8\textwidth]
> \startframedtext[left][frame=off, width=.6\textwidth]
> \starttyping
> import x
> from x import y
> for z in b:
>print dfdg
> Some text
> Some text
> Some text
> Some text
> Some really long text Some really long text Some really long text
width]
\starttyping
import x
from x import y
for z in b:
print dfdg
Some text
Some text
Some text
Some text
Some really long text Some really long text Some really long text Some
really long text Some really longtextSomereallylong text Some really
long text Some really long text Some really long text Some r
l=yes,css=yes]
>> \stopasciimode
>>
>> And while searching a little further I also found:
>> \type{%\setupbackend[export=yes,xhtml=yes,css=yes]}
>>
>> This has the added benefit that it displays somewhat better because of the
>> increased indentati
rther I also found:
> \type{%\setupbackend[export=yes,xhtml=yes,css=yes]}
>
> This has the added benefit that it displays somewhat better because of the
> increased indentation (for which I misuse spaces).
>
>
> \setuptyping[margin=yes]
>
> \starttext
>
> \type{%\setupbackend[export=yes,xhtml=yes,css=yes]}
>
> This has the added benefit that it displays somewhat better because of the
> increased indentation (for which I misuse spaces).
\setuptyping[margin=yes]
\star
evision, (LuaTeX
date stamp \luatexdatestamp)}{mkii},
ConTeXt version \contextversion,
using the command:
\starttyping
context TEst
\stoptyping
\stopcomponent
..
..
\startcomponent test2
\chapter{ch 2}
\section{un}
\startuseMPgraphic{kdj}
pi
typeset
on \currentdate{}
at \currenttime,
with
\doifmodeelse{mkiv}{mkiv, LuaTeX revision \luatexrevision, (LuaTeX
date stamp \luatexdatestamp)}{mkii},
ConTeXt version \contextversion,
using the command:
\starttyping
context test.tex
\stoptyping
\stopcomponent
have:
\starttext
test (automatic based on spaces before \stop...):
\starttyping
test test
test test
test test
\stoptyping
test (key controlled):
\starttyping[strip=yes]
test test
test test
test test
\stoptyping
test
\startbuffer[x]
test test
like:
\startitemize
\startitem test
\starttyping
test
\stoptyping
\stopitem
\stopitemize
- Entities in xml mode have a slightly different roundtrip treatment now
and hopefully Thomas S as well as Hans vd M files still work ok.
- Unicode math variants (supported by xits) are supported:
\mathematics {
\ut
th the number of spaces in front of
> \stoptyping so that one can have nicely formatted input like:
>
> \startitemize
> \startitem test
>
> \starttyping
> test
> \stoptyping
>
> \stopitem
> \stopitemize
>
> - Entities in xml mode have a slightly diff
test
\starttyping
test
\stoptyping
\stopitem
\stopitemize
- Entities in xml mode have a slightly different roundtrip treatment now
and hopefully Thomas S as well as Hans vd M files still work ok.
- Unicode math variants (supported by xits) are supported:
\mathematics {
\utfchar{
t some point (but it
needs to be properly integrated in the page builder then and we probably
should forget about figure placement and display environments
(starttyping etc).
If one just wants vertical stacking (with quad*quad characters) then
columnsets are a nice way in between as then we c
> %D \macros
> %D {doiftextelse, doiftext}
> %D
> %D When \type {\doifelse} cum suis hopelessly fail, for
> %D instance because we pass data, we can fall back on the next
> %D macro:
> %D
> %D \starttyping
> %D \doiftextelse {data} {then branch} {else branch}
>
ome reason the space ends up in
the PDF nevertheless :-(
Any ideas?
From supp-box.mkiv:
%D \macros
%D {doiftextelse, doiftext}
%D
%D When \type {\doifelse} cum suis hopelessly fail, for
%D instance because we pass data, we can fall back on the next
%D macro:
%D
%D \starttyping
%D \doiftext
s used to show all the defined colors in a colo-xxx.(mkii|mkiv)
> file, e.g.
>
> \starttext
> \showcolor[rgb]
> \stoptext
>
> Wolfgang
Hi Hans,
Indeed as Wolfgang points out, in the file
colo-ini.mkii
it is said that:
%D But let's not forget that we also have
> >
> > ! ==> Fatal error occurred, no output PDF file produced!
> > mtx-context | fatal error: return code: 1
> >
> > Here is the troublemaker:
> > \starttyping
> > test;
> > äüöAR \test \Context
> > \stoptyping
> >
> > Interestingly
ofverbat...
l.71 \stoptyping
! ==> Fatal error occurred, no output PDF file produced!
mtx-context | fatal error: return code: 1
Here is the troublemaker:
\starttyping
test;
äüöAR \test \Context
\stoptyping
Interestingly I was not able to produce a real minimal example, because when
I remov
uot;display", }}
\dostoptagged
\endofverbat...
l.71 \stoptyping
! ==> Fatal error occurred, no output PDF file produced!
mtx-context | fatal error: return code: 1
Here is the troublemaker:
\starttyping
test;
äüöAR \test \Context
\stoptyping
Inte
2010/12/21 Wolfgang Schuster
> Make a example where this occurs, in the following example all dashes are
> correct in the typing environment with mkii and mkiv.
>
> \starttext
>
> \startlines
> -
> --
> ---
> \stoplines
>
> \starttyping
> -
> --
>
Am 21.12.2010 um 12:14 schrieb Philipp A.:
> so i want to use ' and -- in my code, which is embedded via \starttyping
> \stoptyping, but that’s impossible.
> context replaces -- with – and ' with ’. that’s wrong. i need to be able to
> tell context it shouldn’t do any “s
so i want to use ' and -- in my code, which is embedded via \starttyping
\stoptyping, but that’s impossible.
context replaces -- with – and ' with ’. that’s wrong. i need to be able to
tell context it shouldn’t do any “smart” stuff, since i’m smart enough to
press the ’-key if i want the
t all boils down hooking in a parser then:
\startluacode
local function parser(s)
local s = somexternalthing(s)
-- feedback s
end
visualizers.register("myparser", { parser = parser })
\stopluacode
\starttyping[option=myparser]
\stoptyping
Thanks for the explanation. But, I am not to
then:
\startluacode
local function parser(s)
local s = somexternalthing(s)
-- feedback s
end
visualizers.register("myparser", { parser = parser })
\stopluacode
\starttyping[option=myparser]
\stoptyping
Why are you using a C prefix for all environments? Isn't it better to
us
in MkIV, you can now write
>
> \setuptyping[escape=yes]
>
> \starttyping
> normal /BTEX\em emphasized/ETEX normal
> normal /BTEX\bf bold/ETEX normal
> \stoptyping
>
> or you set your own delimiters with
>
> \setuptyping[escape={[[,]]}]
>
> \starttypi
201 - 300 of 611 matches
Mail list logo
