info transmitted?
Structural elements are exported; raw typographical commands are not. So,
you would need:
\definehighlight[important][style=bold]
\starttext
\important{This is important}
\stoptext
Aditya___
.
Aditya gave some of the answer. But his answer implies that I will have to
define a whole bunch of
\definehighlight[typography][style=mystyle]
commands and change my entire style of writing... Yet another showstopper
3. My assumption is this: If I can get the xml/xhtml file looking right
Hi Aditya,
On Wed, 14 Jan 2015 14:38:25 -0700, Aditya Mahajan adit...@umich.edu
wrote:
Structural elements are exported; raw typographical commands are not.
So, you would need:
\definehighlight[important][style=bold]
\starttext
\important{This is important}
\stoptext
Ok, thanks
Am 2014-08-29 um 18:46 schrieb Hans Hagen pra...@wxs.nl:
Is there already a solution for \em (or \emph) and other switches? They
don’t show up in export.xml.
use 'highlights'
Ah, of course, thanks. Forgot to copy my \definehighlight from the previous
ebook project.
Greetlings, Hraban
Am 11.03.2014 um 09:09 schrieb Henning Hraban Ramm te...@fiee.net:
more issues:
[5] emphasis
How to markup emphasize (\em, \bf, \it, \sl) so that it gets exported? {\em
Something} doesn’t.
You have to create a command for them which add tags, e.g.
\definehighlight[important][style
by defining a new
typeface/family and refer to a certain alternative of this typeface with the
\classfont command.
\definefontfamily[keywords][ss][DejaVu Sans Mono]
\definefont[kword][\classfont{keywords}{Sans} at 13pt]
\definehighlight[keyword][style=kword]
\starttext
Text font \keyword
On 10/13/2013 12:42 AM, Marco Patzer wrote:
Hi,
certain font switches fail when XML export is used. Example:
\setupbackend [export=foo.xml]
\definehighlight
[emph]
[style=\ita] %% \bfa works
\starttext
\ita Foobar%% works
Foo \emph{Bar} %% fails
\stoptext
LuaTeX error
On 2013–10–13 Hans Hagen wrote:
On 10/13/2013 12:42 AM, Marco Patzer wrote:
Hi,
certain font switches fail when XML export is used. Example:
\setupbackend [export=foo.xml]
\definehighlight
[emph]
[style=\ita] %% \bfa works
\starttext
\ita Foobar%% works
Foo \emph
}. % sans serif
This is a {\tt test}. % typewriter
Rather teach logical markup from the very beginning.
\definehighlight
[important]
[style=bold]
\important{This} is logical markup.
6.3 Floats
This is arguable, but I personally would drop the (not deprecated
and still supported
Rather teach logical markup from the very beginning.
True. Not that I follow this advice myself, but probably should (some
of my earlier ConTeXt files are - umm - not beautiful because I have
some Word baggage).
\definehighlight
[important]
[style=bold]
\important{This} is logical
:
I an trying to use \definehighlight to define a macro that will color and
overstrike selected text.
Thus far,
\definehighlight[Delete][color=red,style={\overstrike}]
\starttext
test \Delete{test} test
\stoptext
reports
! Too many }'s.
system tex error on line 4 in file
I an trying to use \definehighlight to define a macro that will color and
overstrike selected text.
Thus far,
\definehighlight[Delete][color=red,style={\overstrike}]
\starttext
test \Delete{test} test
\stoptext
reports
! Too many }'s.
system tex error on line 4 in file ...TEST.tex
Wonderful, Hans! Many thanks.
Alan
On Mon, May 27, 2013 at 1:14 PM, Hans Hagen pra...@wxs.nl wrote:
On 5/27/2013 3:36 PM, Alan Bowen wrote:
I an trying to use \definehighlight to define a macro that will color
and overstrike selected text.
Thus far,
\definehighlight[Delete][**color=red
Am 27.05.2013 um 15:36 schrieb Alan Bowen bowenala...@gmail.com:
I an trying to use \definehighlight to define a macro that will color and
overstrike selected text.
Thus far,
\definehighlight[Delete][color=red,style={\overstrike}]
\starttext
test \Delete{test} test
\stoptext
versions the \definestyle
was a synonym for \definealternativestyle but now it it’s a command similar to
\definehighlight.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki
defines a command \important{...} that typesets the result in bold
and there.
The result of \definestyle is lost when the document is exported to XML.
For that case, you should use \definehighlight[...] which has the same
syntax
for \definealternativestyle but now it it’s a command
similar to \definehighlight.
On Tue, 5 Mar 2013, Idris Samawi Hamid ادريس سماوي حامد wrote:
You are, perhaps, thinking of \definealternativestyle which has the
syntax
that you are using above.
Thanks, Wolfgang and Aditya. I got it all working
On 2013–02–28 Alasdair McAndrew wrote:
So I've come back to using ConTeXt after a year away from it
Welcome back :)
\setupbodyfontenvironment[default][em={\slanted\color[red]}]
\setupbodyfontenvironment
[default]
[em=slantedred]
\definehighlight
[slantedred]
[style=slanted,
color
Thanks for that, but it doesn't seem to work:
I enter context myfile.tex, and a bit later:
l.26 \definehighlight
[slantedred][style=slanted,color=red]
? h
The control sequence at the end of the top line
of your error message was never \def'ed.
Do I have to include a special
On 2013–03–01 Alasdair McAndrew wrote:
Do I have to include a special module here?
No. I tested some versions between 2011.11.29 23:11 and 2013.02.26
00:17 and it worked for me. Which version are you using?
\definehighlight is nothing which was recent added.
\setupbodyfontenvironment
, 2013 at 12:40 AM, Marco Patzer home...@lavabit.com wrote:
On 2013–03–01 Alasdair McAndrew wrote:
Do I have to include a special module here?
No. I tested some versions between 2011.11.29 23:11 and 2013.02.26
00:17 and it worked for me. Which version are you using?
\definehighlight is nothing
file fdf
(c:/Users/Hussein/context/tex/texmf-context/tex/context/base/spec-fdf.mkii))
systems : begin file arab_inderschule at line 2
(./arab_inderschule.tex
! Undefined control sequence.
l.5 \definehighlight
+
Undefined control sequence definehighlight? Why
(./arab_inderschule.tex
! Undefined control sequence.
l.5 \definehighlight
+
Undefined control sequence definehighlight? Why?
With the Texlive2012 version of context the same code compiles without
problems. So are there some changes in the way
Am 15.11.2012 20:32, schrieb ntg-context-requ...@ntg.nl:
Am 13.11.2012 um 07:50 schrieb H. ?zoguzh.oezo...@mmnetz.de:
Am 13.11.2012 07:46, schriebntg-context-requ...@ntg.nl:
\definehighlight
[emph]
[style=bolditalic]
Quote: \quotation{He said: \quote{Hello \emph{World!}}}
Marco
I
Am 16.11.2012 um 10:13 schrieb H. Özoguz h.oezo...@mmnetz.de:
Am 15.11.2012 20:32, schrieb ntg-context-requ...@ntg.nl:
Am 13.11.2012 um 07:50 schrieb H. ?zoguzh.oezo...@mmnetz.de:
Am 13.11.2012 07:46, schriebntg-context-requ...@ntg.nl:
\definehighlight
[emph]
[style=bolditalic
Am 13.11.2012 um 07:50 schrieb H. Özoguz h.oezo...@mmnetz.de:
Am 13.11.2012 07:46, schrieb ntg-context-requ...@ntg.nl:
\definehighlight
[emph]
[style=bolditalic]
Quote: \quotation{He said: \quote{Hello \emph{World!}}}
Marco
I want the complete quotation emphasized- without
2012-11-12 H. Özoguz:
And if I want to have in
\quotation and \quote
additionaly \emphasis, how to make that?
To be clear (sorry for my english):
\quotation{\emph{Quote}}
\definehighlight
[emph]
[style=bolditalic]
Quote: \quotation{He said: \quote{Hello \emph{World!}}}
Marco
Am 13.11.2012 07:46, schrieb ntg-context-requ...@ntg.nl:
\definehighlight
[emph]
[style=bolditalic]
Quote: \quotation{He said: \quote{Hello \emph{World!}}}
Marco
I want the complete quotation emphasized- without extra writing \emph.
Huseyin
for the fix! Now another thing I noticed is that the text
style “capital” fails with highlights:
·
\definehead [testhead] [section] [style=capital] %% - works
\definehighlight [testhighlight] [style=capital] %% - not always
small caps in my current
font like in LibO and other popular GUI word-processing systems?
\definehighlight[smallcaps][style=\setff{smallcaps}]
\setupbodyfont[pagella]
\starttext
upright {\it italic} {\sc smallcaps}
upright {\it italic} {\it\setff{smallcaps}smallcaps}
upright {\it italic
On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
\definehighlight[smallcaps][style=\setff{smallcaps}]
Hello and thanks for your help but even if I copy-paste your example
into TeXWorks and typeset it (remember, I'm using ConTeXT with XeTeX)
I get the error
On 24-7-2012 21:29, Shriramana Sharma wrote:
On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
\definehighlight[smallcaps][style=\setff{smallcaps}]
Hello and thanks for your help but even if I copy-paste your example
into TeXWorks and typeset it (remember
On Tue, Jul 24, 2012 at 11:21:22PM +0200, Hans Hagen wrote:
On 24-7-2012 21:29, Shriramana Sharma wrote:
On Wed, Jul 25, 2012 at 12:55 AM, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
\definehighlight[smallcaps][style=\setff{smallcaps}]
Hello and thanks for your help but even if I
{}-{}-{}-{}-{}-{}- which works in latex, but in
context I'm still getting the long dashes. How can I prevent this conversion,
please?
\definehighlight[filepermission][style=\setff{none}]
\starttext
Verbatim: \type{rwx--}
Highlight: \filepermission{rwx--}
\stoptext
Wolfgang
\definehighlight[filepermission][style=\setff{none}]
Great, thank you. Anyway what is the purpose of the \setff macro? I have
not found its documentation anywhere. Also why the latex way -{}- does not
work? It is a feature of luatex?
best regards
Jan
--
Tato zpráva byla vytvořena
On 31-5-2012 11:46, Jan Pohanka wrote:
\definehighlight[filepermission][style=\setff{none}]
Great, thank you. Anyway what is the purpose of the \setff macro? I have
not found its documentation anywhere. Also why the latex way -{}- does
not work? It is a feature of luatex?
-{}- is a side
Am 31.05.2012 um 11:46 schrieb Jan Pohanka:
\definehighlight[filepermission][style=\setff{none}]
Great, thank you. Anyway what is the purpose of the \setff macro?
In MkIV you have tell which features of a font (e.g. ligatures or kerning) have
to enabled, this is done in two steps.
1. You
\addfontfeature and \setfontfeature which can be also
called in the two shorter commands \addff and \setff. In the
\definehighlight command I enabled the predefined “none” list where
ligatures and kerning is disabled to prevent that -- results in –.
Wolfgang
:
\definehighlight [tolower] [style=\words,] %%% This is problematic.
\def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
%%% works, though.
\starttext
FOO \tolower{FOO} FOO\par %%% Works.
\framed
and enumerations. Example:
\definehighlight [tolower] [style=\words,] %%% This is problematic.
\def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
%%% works, though
” parameter of
highlights: it breaks frames and enumerations. Example:
\definehighlight [tolower] [style=\words,] %%% This is problematic.
\def\mylower#1{\bgroup\words#1\egroup} %%% The command itself
combine them with the “style” parameter of
highlights: it breaks frames and enumerations. Example:
\definehighlight [tolower] [style=\words,] %%% This is problematic.
\def\mylower#1{\bgroup\words#1\egroup
and \WORD macros. But I can’t find a
way to properly combine them with the “style” parameter of
highlights: it breaks frames and enumerations. Example:
\definehighlight [tolower] [style=\words,] %%% This is problematic
On 2012-05-08 13:28, Wolfgang Schuster wrote:
It would be also useful to change the following line in font-pre.mkiv to use
\setcharacterchasing instead of \WORD (won’t work anymore when you remove
\groupedcommand from the \WORD as written in the comments in typo-cap.mkiv)
On 8-5-2012 13:28, Wolfgang Schuster wrote:
The next version will support named casing:
WORD
word
Word
Words
capitals cap
Capitals Cap
none
random
It would be also useful to change the following line in font-pre.mkiv to use
\setcharacterchasing instead of \WORD (won’t work anymore when you
creating, I'd like emphasized text {\em like this}
to
appear as red. I hoped that something like this would work:
\setupbodyfontenvironment[**default][em={slanted, textcolor=red}]
but it doesn't. What is the canonical way of obtaining red, emphasized,
text?
\definehighlight[emph][style
of obtaining red, emphasized,
text?
\definehighlight[emph][style=slanted, color=red]
\emph{...}
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context
Hi guys,
I'm getting this output:
errorinvalid xml file - parsed text/error
My test.tex file is following:
\setupbackend[export=yes,xhtml=yes]
\definehighlight[strong][style=bold]
\definehighlight[emph] [style=italic]
\starttext
Hello world!
text \strong{text} text \emph{text} text
\stoptext
On 17-1-2012 09:01, Martin Bruchanov wrote:
\setupbackend[export=yes,xhtml=yes]
\definehighlight[strong][style=bold]
\definehighlight[emph] [style=italic]
\starttext
Hello world!
text \strong{text} text \emph{text} text
\stoptext
a conflict in some macro names ... will be sorted out
that spaces matter:
\definehighlight[one][color=red ]
\definehighlight[two][color=blue]
\starttext
\one{Red} \two{Blue}
\stoptext
In the first definition i pass “red ” with a space at the end which is
different from “red” (without a space).
Wolfgang
,
header=high
]
works fine…
It’s a typo in the core, see Adityas mail but in the last case you need a
comma after the high otherwise you pass the value “high ” (with a space at
the end) to context.
Here is a simple example where you can that spaces matter:
\definehighlight[one
Hi Hans,
todays beta breaks the following example. It worked the day before yesterday.
\setupbackend[export=yes]
\definehighlight[Title][color=red]
\startsetups document:start
\Title{\documentvariable{title}}
\stopsetups
\startdocument [title=Test]
some text
\stopdocument
Thank you
On 7-11-2011 08:53, Marco wrote:
Hans Hagenpra...@wxs.nl writes:
On 6-11-2011 21:38, Marco Pessotto wrote:
Hi!
The highlight seems to act strangely. In addition to the previous
report, I get an unwantedbreak/:
%%% start example
\setupbackend[export=yes]
\definehighlight[emph][style=italic
I think I'm hitting another bug with highlights:
See this following example:
%%% start example
\setupbackend[export=yes]
\definehighlight[emph][style=italic]
\starttext
\startparagraph
Published on \dontleavehmode\emph{Dissonanze} vol. I
\stopparagraph
\startparagraph
Published on vol. I
Well, after some trial and errors, I think I get what is going on with
the highlight. When on the generated pdf the /highlight is at the edge
of the paper, the space is eaten. Hacky workaround follows:
%% start example
\setupbackend[export=yes]
\definehighlight[emph][style=italic]
\startmode
Hi!
See the following minimal example:
%%% start example
\setupbackend[export=yes]
\definehighlight[emph][style=italic]
\starttext
Hey, hello!
\emph{Hello world!}
\stoptext
%%% stop example
And the output is:
?xml version='1.0' encoding='UTF-8' standalone='yes' ?
!-- input filename
On 6-11-2011 21:38, Marco Pessotto wrote:
Hi!
The highlight seems to act strangely. In addition to the previous
report, I get an unwantedbreak/:
%%% start example
\setupbackend[export=yes]
\definehighlight[emph][style=italic]
\starttext
\section{test}
\emph{Hello} world!
\stoptext
Hans Hagen pra...@wxs.nl writes:
On 6-11-2011 21:38, Marco Pessotto wrote:
Hi!
The highlight seems to act strangely. In addition to the previous
report, I get an unwantedbreak/:
%%% start example
\setupbackend[export=yes]
\definehighlight[emph][style=italic]
\starttext
\section{test
!
\setupbackend[export=yes,xhtml=yes,css={test.css}]
\definefontfeature[default][default][itlc=yes]
\setupitaliccorrection[always] % not OK
% \setupitaliccorrection[always,global] % OK
\definehighlight[emph][style=\it]
\starttext
\emph{example} % highlight detail=emphex am ple/highlight
\spottiest
% for whatever
\startlines [space=on]
for {\it whatever}
for \italic{whatever}
You can use the commands \italic, \bold etc. which accept the text as argument
or you can define your own commands with \definehighlight or \definestyle which
will then also accept a argument like \italic above
On 12-10-2011 05:26, Aditya Mahajan wrote:
The bug is with xml.css.fontspecification function that does not
handle style=mono (or sans and serif for that matter). The proper
solution is to convert from context font specification into html font
specification for all styles.
I've added
On Mon, 10 Oct 2011, Aditya Mahajan wrote:
Compiling the following document
~~~
\definehighlight [object] [style=mono]
\setupbackend [export=yes]
\starttext
\object{test}
\stoptext
~~~
gives
backend export saving xml data in 'test.export
backend export saving css
On Tue, 11 Oct 2011, Aditya Mahajan wrote:
On Mon, 10 Oct 2011, Aditya Mahajan wrote:
Compiling the following document
~~~
\definehighlight [object] [style=mono]
\setupbackend [export=yes]
\starttext
\object{test}
\stoptext
~~~
gives
backend export saving xml data
Compiling the following document
~~~
\definehighlight [object] [style=mono]
\setupbackend [export=yes]
\starttext
\object{test}
\stoptext
~~~
gives
backend export saving xml data in 'test.export
backend export saving css image definitions in
'test-images.css
backend
://wiki.contextgarden.net/epub
As far as I understood and seen the font and style switching (like \it) are
ignored. First question: is it possible to avoid that behavior?
\setupbackend[export=yes]
\definehighlight[strong][style=bold]
\definehighlight[emph] [style=italic]
\starttext
text \strong
Am 02.09.2011 um 09:47 schrieb Peter Münster:
On Fri, Sep 02 2011, Alasdair McAndrew wrote:
\color[blue]{\type{%t^y_8*}}
doesn't seem to work; nor does
{\blue \type{%t^y_8*}}
No problem with mkiv.
You don’t even need \type in mkiv:
\asciimode
\starttext
\definehighlight[one
^y_8*}}
doesn't seem to work; nor does
{\blue \type{%t^y_8*}}
No problem with mkiv.
You don’t even need \type in mkiv:
\asciimode
\starttext
\definehighlight[one][color=red, style=mono]
\definehighlight[two][color=green,style=mono]
\mono{%t^y_8*}
\one{%t^y_8*}
\two{%t^y_8
Am 31.08.2011 um 07:04 schrieb Alasdair McAndrew:
This brings up a question I have - how do I obtain, say, all {\tt } text in
blue and all {\em } text in red? I seem to be using MkII, and I don't have
access to the \definehighlight command.
\definestartstop[emph][style=italic,color=red
to use \startcolor and \stopcolor every time I wish
this default to be applied.
\definehighlight[emph][style=em,color=red]
\emph{...}
Aditya
___
If your question is of interest to others as well, please add an entry
This brings up a question I have - how do I obtain, say, all {\tt } text in
blue and all {\em } text in red? I seem to be using MkII, and I don't have
access to the \definehighlight command.
Thanks,
Alasdair
On Wed, Aug 31, 2011 at 2:19 PM, Aditya Mahajan adit...@umich.edu wrote:
On Tue, 30
Hi,
I sometimes misuse the command key of itemize like this:
\definehighlight[important][style=italic, color=red]
\starttext
\startitemize[command=\important]
\item {Term}: definition
\stopitemize
\stoptext
However when I try this with
\setupbackend[export=yes]
I get the following error
On Thu, 25 Aug 2011, Aditya Mahajan wrote:
Hi,
I sometimes misuse the command key of itemize like this:
\definehighlight[important][style=italic, color=red]
\starttext
\startitemize[command=\important]
\item {Term}: definition
\stopitemize
\stoptext
However when I try
On Thu, 25 Aug 2011, Aditya Mahajan wrote:
I sometimes misuse the command key of itemize like this:
\definehighlight[important][style=italic, color=red]
Sorry...this works. My test file had
\definehighlight[important][style=em, color=red]
which fails even for
\important{A}
For pdf outout
apropriate tags?
\definestartstop[important][style=bold]
\important{...}
Or, if you don't need ths start-stop macros:
\definehighlight[important][style=bold]
Aditya
___
If your question is of interest
special command in order to put 'AGAIN'
between apropriate tags?
\definestartstop[important][style=bold]
\important{...}
Or, if you don't need ths start-stop macros:
\definehighlight[important][style=bold]
Aditya
Thank you Hans and Aditya. Both examples work as expected.
---
WBR
101 - 175 of 175 matches
Mail list logo
