Text
> could be corrected directly from the proofreader in this file2.tex file,
> but won't do that in the xml file.
I don’t mean the proofreader personally, but TeX code may not be
inherenlty more readable that XML code.
Compile the following:
\starttext
\startXML
St.&nn
Dear list,
I have the following sample:
\showframe
\setuppapersize[A8]
\setuptyping
[align={right,broad},
strip=yes,
lines=yes,
blank=halfline]
\starttext
\startXML
content content content content
content content
content content
Hi Pablo,
The example you gave in your first message about the Scite module, that is:
\usemodule[scite]
\starttext
\startXML ñ\stopXML
\stoptext
gives an error on my machine (MacOS 11.6.5 and Context version 2022.05.11
11:36), with Context saying: « The file ended when scanning an
Dear list,
I have this minimal sample (with current latest from 2022.05.11 11:36 on
Linux64):
\usemodule[scite]
\starttext
\startXML ñ\stopXML
\stoptext
Commenting out the first line avoids compilation error.
Replacing ñ with n also allows compilation.
I think there may be an error in
lo Rodriguez
> Betreff: Re: [NTG-context] \startXML vs \startPARSEDXML
>
> On 5/11/22 11:47, Denis Maier via ntg-context wrote:
> > Hi everyone,
> >
> > the wikipage on \starttyping
> > (https://wiki.contextgarden.net/Command/_starttyping
> > <https://wiki
On 5/11/22 11:47, Denis Maier via ntg-context wrote:
> Hi everyone,
>
> the wikipage on \starttyping
> (https://wiki.contextgarden.net/Command/_starttyping
> <https://wiki.contextgarden.net/Command/_starttyping>) says there are
> some dedicated commands, e.g. \startXML and
Hi everyone,
the wikipage on \starttyping
(https://wiki.contextgarden.net/Command/_starttyping) says there are some
dedicated commands, e.g. \startXML and \startPARSEDXML. How do they differ?
Best,
Denis
___
If
On 5/19/2019 7:38 PM, Pablo Rodriguez wrote:
Hi Hans,
I’m afraid I found another issue with UTF8 chars in attribute values
when printing them.
\starttext
\startTEXpage[offset=1em]
\startXML
\stopXML
\stopTEXpage
\stoptext
Inspecting buff-imp-xml.lua, I
Hi Hans,
I’m afraid I found another issue with UTF8 chars in attribute values
when printing them.
\starttext
\startTEXpage[offset=1em]
\startXML
\stopXML
\stopTEXpage
\stoptext
Inspecting buff-imp-xml.lua, I understand that "alsoname" should be
added to &q
To limit the smaller font to \starttyping it should be
\setuptyping [typing] [style=\ttxx]
or
\setuptyping [typing] [style=smalltype]
because \starttyping is a generated command like \startXML.
Wolfgang
Taco Hoekwater schrieb am 10.09.18 um 11:32:
Hi Hans,
Replace y
To limit the smaller font to \starttyping it should be
\setuptyping [typing] [style=\ttxx]
or
\setuptyping [typing] [style=smalltype]
because \starttyping is a generated command like \startXML.
Wolfgang
Taco Hoekwater schrieb am 10.09.18 um 11:32:
Hi Hans,
Replace your two
I want to differentiate the typing of XML-code with \startXML and other text with \starttyping.That doesn’t work as I expect or I misinterpret something.The minimal example shows that in the following code there is no difference between using \startXML or \starttyping
typingsetup.pdf
Description
comment: \inlineTEX{ag%befe}
\Lua\ inline comment: \inlineLUA{agb --efe}
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
> On 22 Dec 2017, at 4
fe}
>
> \Lua\ inline comment: \lua{agb --efe}
>
> \startTEX
> This is text. % a comment, not \comment
> \stopTEX
>
> \startXML
> This is text.
> \stopXML
>
> \startLUA
> if code=="code" then --this is a comment
> \
}
\Lua\ inline comment: \lua{agb --efe}
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
Would it b
\comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
Would it be possible that all comments in type and typing (at least, for
Lua, XML and TeX) would have the same formatting for
}
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
\stopLUA
\stopTEXpage
\stoptext
Would it be possible that all comments in type and typing (at least, for
Lu
Hans,
[I have reported this before the meeting, but it was wiser to wait after
the meeting was over.]
I have the following sample:
%~ \usemodule[scite]
\starttext
\startTEXpage[offset=2em]
\startTEX
This is text. % a comment, not \comment
\stopTEX
\startXML
This
[offset=1em]
\startTEX
This is text. % and this is a comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
--[[
this is a
multiline comment
--]]
---[[
this isn’t a
multili
Hans,
I have the following sample:
\starttext
\startTEXpage[offset=1em]
\startTEX
This is text. % and this is a comment
\stopTEX
\startXML
This is text.
\stopXML
\startLUA
if code=="code" then --this is a comment
--[[
and this is a
}
\startluacode
function xml.functions.processXML(t)
buffers.assign("MyXml", "\\startXML\n" .. tostring(xml.text(t)) ..
"\n\\stopXML")
context.getbuffer { "MyXml" }
end
\stopluacode
\startxmlsetups xml:a
\xmlflush{#1}
\st
Hans,
many thanks for having added \xmlprettyprinttext to ConTeXt.
I have now another problem with inline code:
\definetype[TeX][option=TEX, lines=hyphenated]
\starttext
\startTEXpage[offset=1em]
This is inline code: \TeX{\command[option=value]{final text}}
\startXML
Inline code: \TeX[option
ailing interline space
\hrule
\startXML
\stopXML
\hrule
\medskip
\setuptyping[before=,after=] % <- works as expected
\hrule
\starttyping
\TeX
\stoptyping
\hrule
\stoptext
Thank you for any advice!
Christoph
__
\setupstartstop[XmlSnippetName][color=magenta,style=\bfa]
\starttext
\startXML
hello world
\stopXML
\stoptext
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
,
backgroundscreen=.9]},
after={\stopframedtext}]
\definepalet[MYcolors]
[prettyone=paleblue,
prettytwo=palecyan,
prettythree=palered,
prettyfour=darkgreen]
\definepalet[XMLcolorpretty][MYcolors]
\starttext
\startXML
hello world
\stopXML
het.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
\setupcolors[state=start]
\start
Christopher Creutzig wrote:
> \starttext
> \startXML
> a::b
> \stopXML
> \stoptext
The problem is the \setpretty`\:=10 in \XMLsetspecials in
verb-xml.tex. This should only be done inside <...>.
Suggested patch (I hope it survives being sent by mail):
--- verb-xml.tex
Salvete,
trying to typeset an unchanged old file with a more recent ConTeXt
version, I keep running into problems. I have reduced the first of these
(others may or may not be symptoms of the same, I'll see that later) to
this input:
\starttext
\startXML
a::b
\stopXML
\stoptext
It seem
ts colored
with tag-color, the "tag" with attr-color. I think the whole "ns:tag"
should be of tag-color.
How about this?
%% allows XML tag names to continue after colons (namespaces)
\input verb-xml % TRICK
\appended\gdef\XMLsetspecials{\setpretty`\:=10 }
\startte
[state=start]
\setuptyping[option=color]
\starttext
\startXML ... \stopXML
\stoptext
Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
30 matches
Mail list logo
