On Sun, 8 Feb 2015 13:56:54 +0100
Keith J. Schultz keithjschu...@web.de wrote:
As to setting up defaults, the question is their a generic usage of
such ways of for so called highlights. These are, basically, by those
that: 1) like this much fluff
2) idiosyncratic terminology
1) is supposed
On 2/9/2015 12:42 AM, Keith Schultz wrote:
Hi Hans, Idris, All,
Then we should call it definetag of definestyletag ! It would describe
its function better!
Like I said I find the command highlight nice because it is alot easier than
define my own commands for setting styles with color!
it's
Hi Hans, Idris, All,
fonts and color are as such appearance.
But, when one uses different fonts and colors or mix
then then we add meaning or as you tend to call
it structure.
If their use does not add to the structure, then only one font style
and color is needed.
So actually, in the end they
Am 09.02.2015 um 14:34 schrieb Keith Schultz keithjschu...@icloud.com:
Hi Hans, Idris, All,
fonts and color are as such appearance.
But, when one uses different fonts and colors or mix
then then we add meaning or as you tend to call
it structure.
If their use does not add to the
, what we have is a use color and style!
would it not be better to call it
definecharstyle
or
definetextstyle
For compatibility we could use keep the definehighlight as a synonym.
As to setting up defaults, the question is their a generic usage of such ways of
for so called highlights
.
The problem is that is this REALLY a Highlight!
A style and color is applied so, what we have is a use color and style!
would it not be better to call it
definecharstyle
or
definetextstyle
For compatibility we could use keep the definehighlight as a synonym.
As to setting up
and \quotation already work in the exporter. The
following iteration then:
=
\unprotect
\definehighlight[\v!italic] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[\v!bold ] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[\v!bolditalic] [\c!command=\v!no,\c!style=\v!bolditalic
untagged in the exporter to xml
Ok, so I suppose \quote and \quotation already work in the exporter. The
following iteration then:
=
\unprotect
\definehighlight[\v!italic] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[\v!bold ] [\c!command=\v!no,\c!style=\v!bold
Am 08.02.2015 um 15:40 schrieb Idris Samawi Hamid ادريس سماوي حامد
isha...@colostate.edu:
[…]
There seems to be a bug with \smallcaps. Otherwise I think the above makes a
good default set to start with.
Hans changed the effect of “style=smallcaps”, in the ConTeXt used \sc when you
On 2/8/2015 1:56 PM, Keith J. Schultz wrote:
Basically, a highlight allows one so setup a font style and color to be
applied
to it contents.
the only reason why highlight exists is that it can be used to tag stuff
that is otherwise untagged in the exporter to xml which is why there is
Hi Keith,
On Sun, 08 Feb 2015 05:56:54 -0700, Keith J. Schultz
keithjschu...@web.de wrote:
Also, not everybody would want the predefined styles and colors
so they will have to be changed in the setuphighlight anyway!
Indeed, but the point is not to predefine the styles but to predefine
then:
=
\unprotect
\definehighlight[\v!italic] [\c!command=\v!no,\c!style=\v!italic]
\definehighlight[\v!bold ] [\c!command=\v!no,\c!style=\v!bold]
\definehighlight[\v!bolditalic] [\c!command=\v!no,\c!style=\v!bolditalic]
\definehighlight[\v!mono] [\c!command=\v!no,\c!style
On 2/8/2015 8:08 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Ok. It's clear that I'm doing a lot of guessing, so question: Can you
specify exactly what does *not* get tagged in xml-export? What exactly
do we need to worry about? Then we can go from there...
everything that has some
Hi Wolfgang,
On Sun, 08 Feb 2015 12:17:11 -0700, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
Am 08.02.2015 um 15:40 schrieb Idris Samawi Hamid ادريس سماوي حامد
isha...@colostate.edu:
[…]
There seems to be a bug with \smallcaps. Otherwise I think the above
makes a good
structure,
you need to \definehighlight[emph][style=italic] and use as
\emph{emphasized}.
==
Now \em does have structural meaning (emphasis) so either the wiki is
wrong or we have some inconsistency here -)
highlights are for the few things left ... but often one can also use
Hi Hans, Idris, All,
Then we should call it definetag of definestyletag ! It would describe
its function better!
Like I said I find the command highlight nice because it is alot easier than
define my own commands for setting styles with color!
regards
Keith.
Am 08.02.2015 um 15:01
On 2/7/2015 2:07 AM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Dear gang,
Thinking of present and future documents (maximum flexibility in
converting from format to format), I'm moving from the standard {\em
text} to something like \definehighlight[emph][style=italic]. Here's the
question
is that we won't overload
existing commands by default, so redefining is not an option in the core.
An option is to provide a set like:
\unprotect
\definehighlight[\v!italic][\c!command=\v!no,\c!style=\v!italic]
\definehighlight[\v!bold ][\c!command=\v!no,\c!style=\v!bold
On Sat, 07 Feb 2015 12:33:00 -0700, Idris Samawi Hamid ادريس سماوي حامد
isha...@colostate.edu wrote:
\definehighlight[extraimportant]
[\c!command=\v!no,\c!style=\v!bolditalic]
\definehighlight[extraimportant]
[\c!command=\v!no,\c!style=\v!smallcaps]
% \definehighlight
Dear gang,
Thinking of present and future documents (maximum flexibility in
converting from format to format), I'm moving from the standard {\em text}
to something like \definehighlight[emph][style=italic]. Here's the
question:
Does ConTeXt contain some default highlights that need
:
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
:
\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
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
35 matches
Mail list logo
