Am Freitag, 28. Juni 2024, 11:59:19 MESZ schrieb Wolfgang Schuster:
> Gerion Entrup schrieb am 28.06.2024 um 11:40:
>
> > Do you know, why the groupedcommand solution does not work?
>
> The command and the environment which are created by \definestartstop
> can't be interchanged when you use the
Gerion Entrup schrieb am 28.06.2024 um 11:40:
Do you know, why the groupedcommand solution does not work?
The command and the environment which are created by \definestartstop
can't be interchanged when you use the before/after and left/right keys.
begin example
\usemodule[visual]
\de
t;>> wanted to simplify the code in the same move.
> >>>>> I discovered headcommand for that, but struggled to set the text in an
> >>>>> highlight _and_ make a colon at the end.
> >>>> Not sure what exactly you want, but how about:
>
process to convert an itemize part to a description and wanted to
simplify the code in the same move.
I discovered headcommand for that, but struggled to set the text in an
highlight _and_ make a colon at the end.
Not sure what exactly you want, but how about:
\definehighlight[hl][style={\m
t;>>
> >>> I was in the process to convert an itemize part to a description and
> >>> wanted to simplify the code in the same move.
> >>> I discovered headcommand for that, but struggled to set the text in an
> >>> highlight _and_ make a colon at th
headcommand for that, but struggled to set the text in an
highlight _and_ make a colon at the end.
Not sure what exactly you want, but how about:
\definehighlight[hl][style={\m{>}\,\switchtobodyfont[tt]}]
% This is the wrong way to define such a command as '>' is not part of the
style.
discovered headcommand for that, but struggled to set the text in an
> > highlight _and_ make a colon at the end.
>
> Not sure what exactly you want, but how about:
>
> \definehighlight[hl][style={\m{>}\,\switchtobodyfont[tt]}]
> % This is the wrong way to define such a
the end.
Not sure what exactly you want, but how about:
\definehighlight[hl][style={\m{>}\,\switchtobodyfont[tt]}]
% This is the wrong way to define such a command as '>' is not part of the
style. I have left this definition just for comparison with the soln b
:
```
\definehighlight[hl][style={\m{>}\,\switchtobodyfont[tt]}]
\definedescription[category][
alternative=top,
headstyle=bold,
width=broad,
]
\definedescription[desc][
width=broad,
distance={\widthofstring{~}},
headcommand={\groupedcommand{
},
]
\definefont[highfont][name:ibmplexsansbold*default at 10pt]
\definehighlight[newhigh][color=darkblue,style=highfont]
\starttext
\input{knuth} \Mynote{refrence}
\startitemize
\item \newhigh{\input{knuth}\Mynote{refrenceTwo}}
\stopitemize
\placenotes[Mynote]
\stoptext
as you can see the note number
10pt]
\definehighlight[newhigh][color=darkblue,style=highfont]
\starttext
\input{knuth} \Mynote{refrence}
\startitemize
\item \newhigh{\input{knuth}\Mynote{refrenceTwo}}
\stopitemize
\placenotes[Mynote]
\stoptext
as you can see the note number has same style all over the document.
but i want it
ai2472206...@yeah.net schrieb am 05.06.2024 um 16:03:
As described, here is example:
%
\def\cmd#1{{\tt\textslash #1}}
\def\cmdii#1{\tt #1}
\def\cmdiii#1{\rm #1}
You can use \definehighlight to create a custom command for a style.
The case where you want a slash before the text you have
\let\md\normalmd
\let\mi\normalmi
\let\ms\normalms
\definehighlight[medium ] [command=no,style=medium]
\definehighlight[mediumitalic ] [command=no,style=mediumitalic]
\definehighlight[mediumslanted] [command=no,style=mediumslanted]
Is that necessary? And is it enough?
\starttypescript
}
\let\md\normalmd
\let\mi\normalmi
\let\ms\normalms
\definehighlight[medium ] [command=no,style=medium]
\definehighlight[mediumitalic ] [command=no,style=mediumitalic]
\definehighlight[mediumslanted] [command=no,style=mediumslanted]
Is that necessary? And is it enough?
\starttypescript
\bodyfontsize,
lines=26,
footer=\bodyfontsize,
footerdistance=\bodyfontsize]
\definehighlight
[sesamedot]
%\showframe
%\showgrid
%\showboxes
%\showmakeup
% [glyph,fontkern]
\starttext
\starttitle [title={ごん狐}]
[author={新美南吉},source={https://www.aozora.gr.jp/cards/000121/files/628_14895.html
?
\setupbodyfontenvironment
[default]
[em=italicface] %same with italic for this example
\definehighlight
[emIt]
[style=italic]
\definehighlight
[emIf]
[style=italicface]
\definehighlight
[emEm]
[style=\em
with italic for this example
\definehighlight
[emIt]
[style=italic]
\definehighlight
[emIf]
[style=italicface]
\definehighlight
[emEm]
[style=\em]
\starttext
{\em abc {\em def} ghi}: \type{\em}
\emph
hairline the example below, but see that italicface
adapts to nesting, while italic does not:
Are there other places where this makes a difference?
\setupbodyfontenvironment
[default]
[em=italicface] %same with italic for this example
\definehighlight
to nesting,
while italic does not:
Are there other places where this makes a difference?
\setupbodyfontenvironment
[default]
[em=italicface] %same with italic for this example
\definehighlight
[emIt]
[style=italic]
\definehighlight
ss] [sans] [modern] [default]
\definetypeface [ka] [tt] [mono] [modern] [default]
\definetypeface [ka] [mm] [math] [modern] [default]
\definetypeface [ka] [hw] [handwriting] [comicsans] [default]
\stoptypescript
\setupbodyfont[ka,rm,18pt]
\setupbodyfontenvironment[default][em=italicface]
\de
On Thu, 20 May 2021, Rik Kabel wrote:
> Consider the following example:
>
>\define \HighlightColor {red}
Why not just use:
\definecolor[HighlightColor][red]
and then use color=HighlightColor, etc.
>\definehighlight[RED][color=\HighlightColor]
>\definelabel[
Consider the following example:
\define \HighlightColor {red}
\definehighlight[RED][color=\HighlightColor]
\definelabel[AA][alternative=inright,headcolor=\HighlightColor,text=]
\definelabel[BB][alternative=inright,headcolor=red,text=]
\noheaderandfooterlines
\starttext
Hi Andrés,
You could probably put the notes inside a \start...\stopxtablefoot
Sylvain
On Tue, 10 Nov 2020 at 21:49, Andres Conrado Montoya <
andresconr...@gmail.com> wrote:
> MWE (sorry for the long table, I hadn't anything else at hand):
>
> %%%%
> \defi
MWE (sorry for the long table, I hadn't anything else at hand):
%%%%
\definehighlight[emph][style={\em}]
\definehighlight[strong][style={\bf}]
\setupfloat[table][default={here}]
\definereferenceformat[figura][text={Figura~}]
\definereferenceformat[tabla][text={
ou also see **Before you start...** section on that page:
https://wiki.contextgarden.net/Font_Switching#Before_you_start_...
> If you go to *Export*, it says: "Also note that switches like \em don’t
> translate into output structure, you need to
> \definehighlight[emph][style={\em}] an
lanted; for OpenType fonts, recommends using
\definefontfeature[default][default][itlc=yes] to also activate the italic
correction. However, this seems not to work in x(ht)ml export.
If you go to *Export*, it says: "Also note that switches like \em don’t
translate into output structure, you need
ich can be used. Example:
\setupbuffer
[before=\blank\blackrule\startnarrower\BufferStyle,
after=\stopnarrower\blackrule\blank]
[...]
\definehighlight
[BufferStyle]
[style=smallitalic,
color=blue]
Use the highlight-environment or create a new startstop-environment to
apply style
er
> [before=\blank\blackrule\startnarrower\BufferStyle,
> after=\stopnarrower\blackrule\blank]
>
> %% alternatively define custom buffers
> \definebuffer
> [foobar]
>
> \setupblackrules
> [width=1cm,
>height=1pt,
>color=gray]
>
> \defi
er has before and after keys which can be used. Example:
\setupbuffer
[before=\blank\blackrule\startnarrower\BufferStyle,
after=\stopnarrower\blackrule\blank]
%% alternatively define custom buffers
\definebuffer
[foobar]
\setupblackrules
[width=1cm,
height=1pt,
color=gray]
\definehighli
] [factor=0.12]
\definecharacterkerning [LittleMoreB] [factor=0.08]
\setuphead
[chapter]
[distance=2em,
style=\tfd,
textstyle={\smallcaps\setcharacterkerning[LittleMoreA]}]
\definehighlight
[emphasis]
[style={\setcharacterkerning[LittleMoreA]}]
\starttext
\startchapter[title=Something
ter a regular
(even) page, everything works as expected (no color-filled page, no header
in the start-chapter page).
MWE:
%% START MWE
\definecolor[rojo][h=ED553B]
\definehighlight[rojo][color=rojo]
\startMPinclusions
numeric u ; u := 1.125pt ;
numeric i ;
The following mwe
\definefontfeature[fraction][frac=yes]
\definehighlight[textfraction][style={\feature[+][fraction]}]
\starttext
a fraction \m{\frac{1}{n}}, \textfraction{1/n}, \vulgarfraction{1}{n} in
the text
\stoptext
works for all but \textfraction in the latest beta (luatex, luametatex
-chapter page).
MWE:
%% START MWE
\definecolor[rojo][h=ED553B]
\definehighlight[rojo][color=rojo]
\startMPinclusions
numeric u ; u := 1.125pt ;
numeric i ; i := 0.125in ;
string prevChapterTitle, currentChapterTitle;
prevChapterTitle := "&
Henning Hraban Ramm schrieb am 23.01.19 um 17:32:
And how can I \definefont so that \em or \emph works the same as in bodyfont?
You can’t.
Or, the other way round, how must I \definehighlight[emph][style=italic] so
that it works in all sizes?
-
\setupbodyfont[rm,12pt]
\definefont
And how can I \definefont so that \em or \emph works the same as in bodyfont?
Or, the other way round, how must I \definehighlight[emph][style=italic] so
that it works in all sizes?
-
\setupbodyfont[rm,12pt]
\definefont[TitleFont][SansBold*default sa 3]
\setuphead[chapter][style
:
\definehighlight [Term][style={{\underbar}}]
\definehighlight [Term] [style={\setbar[underbar]}]
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg
List,
With recent betas, since a fix for tagged elements in tables, underbar
processing seems to have changed (or perhaps I just noticed it after
that fix).
Previously, the following highlight definition worked for both pdf and
export outputs:
\definehighlight [Term][style={{\underbar
using \definehighlight.
I replaced \em and \bf by \emph{} and \strong{} in my projects.
Didn’t try real bibliographies or xml input yet, but I guess you
can change the setup to use those.
\definehighlight does not (by default) nest. You can handle this to
some degree in css or xslt for XML exports
er could then
> >> apply the appropriate styling with css or other transformation
> >> mechanisms.
> > Generally, you get stylistic tagging by using \definehighlight.
> > I replaced \em and \bf by \emph{} and \strong{} in my projects.
> >
> > Didn’t try re
, they
could be implemented as highlights or tagged elements, both of which
are currently carried through, and the user could then apply the
appropriate styling with css or other transformation mechanisms.
Generally, you get stylistic tagging by using \definehighlight.
I replaced \em and \bf by
highlights or tagged elements, both of which are currently carried through,
and the user could then apply the appropriate styling with css or other
transformation mechanisms.
Generally, you get stylistic tagging by using \definehighlight.
I replaced \em and \bf by \emph{} and \strong{} in my projects
or tagged elements, both of which are currently carried
> through, and the user could then apply the appropriate styling with css or
> other transformation mechanisms.
Generally, you get stylistic tagging by using \definehighlight.
I replaced \em and \bf by \emph{} and \strong{} in my projects
eaks?
MWE:
\setupbackend [export=yes]
\definehighlight [emIt]
[style=italic]
\starttext
\startparagraph
{\emIt Taa} aaa aa a aa aaa aa aa
aa. Taa a, a aa a
anyone dealt with this before? Is there a way to control the
insertion of the breaks?
MWE:
\setupbackend [export=yes]
\definehighlight [emIt]
[style=italic]
\starttext
\startparagraph
{\emIt Taa} aaa aa a aa aaa aa
a way to control the
insertion of the breaks?
MWE:
\setupbackend [export=yes]
\definehighlight [emIt]
[style=italic]
\starttext
\startparagraph
{\emIt Taa} aaa aa a aa aaa aa aa
aa. Taa a
On 6/26/2018 8:26 PM, Rik wrote:
In September 2015 thread "Custom XML Export," Hans instructed us on how
to create custom tags. The example he presented is:
\setupbackend[export=yes]
\definehighlight[this]
\starttext
\startelement[what]
\this{tha
In September 2015 thread "Custom XML Export," Hans instructed us on how
to create custom tags. The example he presented is:
\setupbackend[export=yes]
\definehighlight[this]
\starttext
\startelement[what]
\this{that} \input ward
\stopelement
On Tue, 5 Jun 2018, Alan Braslau wrote:
The "style=" use is, in general, preferable for tagging (and
exporting). For less than paragraph switching, the use of
\definehighlight for example could be used.
Quick and dirty font switching is almost always poor usage...
You didn't
The "style=" use is, in general, preferable for tagging (and
exporting). For less than paragraph switching, the use of
\definehighlight for example could be used.
Quick and dirty font switching is almost always poor usage...
Alan
On Tue, 5 Jun 2018 12:57:59 -0400 (EDT)
Aditya Maha
g Hraban Ramm wrote:
> > Here are a few problems that I encountered in my current ePub
> > projects:
> >
> > * \color[]{} leaves no trace in export.
>
> Hi Hraban,
>
> this works with PDF, it should work with ePub:
>
> \definehighlight[read][color=red,
g into
lowercase like {\sc iso}.
(I also tried OpenType features, but those were too unreliable with my
fonts. That’s not the problem here.)
But my small caps end as unmarked lowercase in the exported xml.
I didn’t manage to combine my above approach with \definehighlight,
but after poking around
On 11/12/2017 09:33 AM, Henning Hraban Ramm wrote:
> Am 2017-11-11 um 19:46 schrieb Pablo Rodriguez:
>> \definehighlight[read][color=red, style=\sc]
>> [...]
>> I guess you have to use this instead of \color[]{}.
>
> Yes, I guess too. I remembered highlight suits colo
ith PDF, it should work with ePub:
>
> \definehighlight[read][color=red, style=\sc]
> \starttext
> \starthighlight[read] rot\stophighlight
> \stoptext
>
> I guess you have to use this instead of \color[]{}.
Yes, I guess too. I remembered highlight suits color after sending, but
On 11/11/2017 06:30 PM, Henning Hraban Ramm wrote:
> Here are a few problems that I encountered in my current ePub projects:
>
> * \color[]{} leaves no trace in export.
Hi Hraban,
this works with PDF, it should work with ePub:
\definehighlight[read][color=red, style=\sc]
\
too unreliable with my fonts.
That’s not the problem here.)
But my small caps end as unmarked lowercase in the exported xml.
I didn’t manage to combine my above approach with \definehighlight, but after
poking around in the source (core-sys.mkiv, strc-tag.mkiv)
I found this solution:
\def\SC#1
Henning Hraban Ramm <mailto:te...@fiee.net>
16. August 2017 um 17:47
In my current project, section titles are typeset in SansBold while
the body text (and that of the ToC) is roman.
How can I define \definehighlight[emph], so that I get SansBoldItalic
in titles and SerifItalic i
Am 2017-08-16 um 18:09 schrieb Pablo Rodriguez :
> On 08/16/2017 05:47 PM, Henning Hraban Ramm wrote:
>> In my current project, section titles are typeset in SansBold while
>> the body text (and that of the ToC) is roman.
>>
>> How can I define \definehig
On 08/16/2017 05:47 PM, Henning Hraban Ramm wrote:
> In my current project, section titles are typeset in SansBold while
> the body text (and that of the ToC) is roman.
>
> How can I define \definehighlight[emph], so that I get
> SansBoldItalic in titles and SerifItalic in bo
In my current project, section titles are typeset in SansBold while the body
text (and that of the ToC) is roman.
How can I define \definehighlight[emph], so that I get SansBoldItalic in titles
and SerifItalic in body text and ToC? (Body text is not a problem.)
MNWE:
\setuphead[chapter][page
wrote:
On Mon, 2017-07-10 at 19:34 -0400, Alan Bowen wrote:
Adding
\definefontfeature[fraction][frac=yes]
\definehighlight[textfraction][style={\feature[+][fraction]}]
fixes the problem in the sample just sent.
This, and the font has to have the corresponding feature present.
Sorry for t
, 2017 at 8:09 PM, Henri Menke wrote:
> > On Mon, 2017-07-10 at 19:34 -0400, Alan Bowen wrote:
> > > Adding
> > >
> > > \definefontfeature[fraction][frac=yes]
> > > \definehighlight[textfraction][style={\feature[+][fraction]}]
> > >
> > >
, 2017 at 8:09 PM, Henri Menke wrote:
> On Mon, 2017-07-10 at 19:34 -0400, Alan Bowen wrote:
> > Adding
> >
> > \definefontfeature[fraction][frac=yes]
> > \definehighlight[textfraction][style={\feature[+][fraction]}]
> >
> > fixes the problem in the sample j
On Mon, 2017-07-10 at 19:34 -0400, Alan Bowen wrote:
> Adding
>
> \definefontfeature[fraction][frac=yes]
> \definehighlight[textfraction][style={\feature[+][fraction]}]
>
> fixes the problem in the sample just sent.
This, and the font has to have the cor
Adding
\definefontfeature[fraction][frac=yes]
\definehighlight[textfraction][style={\feature[+][fraction]}]
fixes the problem in the sample just sent.
Sorry for the misfire.
Alan
On Mon, Jul 10, 2017 at 1:53 PM, Alan Bowen wrote:
> Has there been a change to \textfraction?
>
>
]
\definehighlight[textfraction][style={\feature[+][fraction]}]
\starttext
A. \textfraction{1/2}
B. \textfraction{1.5/2}
C. \textfraction{{2\textfraction{1/2}}/7}
\stoptext
Alan
___
If your question is of interest to others as
slash; something like 1{}^1/_2 to mean one and a half?
\definefontfeature[fraction][frac=yes]
\definehighlight[textfraction][style={\feature[+][fraction]}]
\starttext
\m{1\vfrac{1}{2}}
1\textfraction{1/2}
\stoptext
Wo
Thomas Fehige <mailto:tho...@fehige.de>
22. Juni 2016 um 14:34
Is there a clean and easy way in mkiv to create text inline fractions
with a slash; something like 1{}^1/_2 to mean one and a half?
\definefontfeature[fraction][frac=yes]
\definehighlight[textfraction][style={\feature[+][fr
>
> Many thanks for any hint.
Perhaps (untested):
\definealternativestyle [BigFont] [{\setbodyfont [12pt]}]
\definealternativestyle [SmallFont] [{\setbodyfont [8pt]}]
\definehighlight [BigSize] [style=BigFont]
\defin
t don’t know who to get \BigSize
> and \SmallSize defined (and have Bar1 and Bar2 of same size) :
>
>
> {\BigSize Foo {\SmallSize Bar1}} {\SmallSize Bar2} Baz.
>
>
> Many thanks for any hint.
Perhaps (untested):
\definealternativestyle [BigFont] [{\setbodyfont [12pt]}]
Alan Bowen <mailto:bowenala...@gmail.com>
29. November 2015 um 14:49
Hi, Wolfgang—
at line 34, I have \Query
which is defined:
\definehighlight[Query][color=magenta,style=bold]
There also instances of \emph (\definehighlight[emph][style=italic])
at lines 41 and 58.
You have create a m
Hi, Wolfgang—
at line 34, I have \Query
which is defined:
\definehighlight[Query][color=magenta,style=bold]
There also instances of \emph (\definehighlight[emph][style=italic]) at
lines 41 and 58.
Alan
On Sat, Nov 28, 2015 at 11:31 AM, Wolfgang Schuster <
schuster.wolfg...@gmail.com>
\emph lapsus}, even if it is not clear whether the
mistake is a haplography or a dittography.}
%
μορίουϲ.
\stoplines
\stopparagraph
\stopextract <— LINE 80
Many thanks for any thoughts on this or advice.
Did you create a command with \definehighlight which is used in this
part of the docum
\pandocstrong could be defined as
\definehighlight[pandocstrong][style=bold]
Simplicarly, h2, h3, can be translated to \startpandocsection etc.,
allowing the user to change the level of the sections. Have a look at
m-markdown in the source for such an implementation.
This makes it much easier for a user
/2015 4:21 PM, Toby Miller wrote:
>>>> I'm using ConTeXt's export to XML feature, but I'd like more control
>>>> over the XML output. Is there a way to define a TeX command that will
>>>> output a specific tag (content) around some text in t
Xt's export to XML feature, but I'd like more control
over the XML output. Is there a way to define a TeX command that will
output a specific tag (content) around some text in the
output?
\setupbackend[export=yes]
\definehighlight[this]
\starttext
\startelement[what]
\this{tha
that will
>> output a specific tag (content) around some text in the
>> output?
>
> \setupbackend[export=yes]
>
> \definehighlight[this]
>
> \starttext
> \startelement[what]
> \this{that} \input ward
> \stopelement
> \stoptext
>
>
On 9/11/2015 4:21 PM, Toby Miller wrote:
I'm using ConTeXt's export to XML feature, but I'd like more control
over the XML output. Is there a way to define a TeX command that will
output a specific tag (content) around some text in the output?
\setupbackend[export=yes]
\defin
\setupmarginrules color remains even in bodymatter mode (the \setupbar
color does not).
\setupmarginrules[rulethickness=1pt]
\setupmarginrules[1][rulecolor=red]
\setupbar[overstrike][color=red]
\define[1]\RR {\startmarginrule[1]\RRR#1\stopmarginrule}
\definehighlight [RRR
On 15 May 2015 at 21:57, Hans Hagen wrote:
> On 5/15/2015 9:57 PM, Kate F wrote:
>>
>> Hi,
>>
>> I'm looking for something like \definehighlight which I can use to
>> markup various things in inline body text. I want different
>> environments to be ab
On 5/15/2015 11:00 PM, Aditya Mahajan wrote:
On Fri, 15 May 2015, Hans Hagen wrote:
On 5/15/2015 9:57 PM, Kate F wrote:
Hi,
I'm looking for something like \definehighlight which I can use to
markup various things in inline body text. I want different
environments to be able to have thei
On Fri, 15 May 2015, Hans Hagen wrote:
On 5/15/2015 9:57 PM, Kate F wrote:
Hi,
I'm looking for something like \definehighlight which I can use to
markup various things in inline body text. I want different
environments to be able to have their own setups to configure how
these appear, ju
On 5/15/2015 9:57 PM, Kate F wrote:
Hi,
I'm looking for something like \definehighlight which I can use to
markup various things in inline body text. I want different
environments to be able to have their own setups to configure how
these appear, just as \setuphighlight would provide.
Ho
Hi,
I'm looking for something like \definehighlight which I can use to
markup various things in inline body text. I want different
environments to be able to have their own setups to configure how
these appear, just as \setuphighlight would provide.
However there's one situation whi
On Fri, 24 Apr 2015, Idris Samawi Hamid ادريس سماوي حامد wrote:
\definehighlight[emphasis][style=\em]
...
Some \emph{emphasis} and \important{important}.
The exported formatting of \emph vanishes in each instance.
You define \emphasis but use \emph
Dear gang,
Here are two export bugs, full test suite attached:
==sh_ahmad-qajar-xml-test-highlight.tex===
\setupexport[cssfile=sh_ahmad-qajar.css]
\setupbackend[export=yes]
\definehighlight[emphasis][style=\em]
\definehighlight[important][style=bold]
\starttext
> Am 28.03.2015 um 19:18 schrieb Idris Samawi Hamid ادريس سماوي حامد
> :
>
> Dear syndicate,
>
> We have \definehighlight[tagged][style=] so that
>
> \tagged{arg}
>
> tags the argument. Analogously: Is there a general facility to tag
> startstops? I played a
Dear syndicate,
We have \definehighlight[tagged][style=] so that
\tagged{arg}
tags the argument. Analogously: Is there a general facility to tag
startstops? I played around with \dostarttagged etc but could not get it
to work (too low-level for me I guess). What would be nice is to be able
Ok, I've made some progress:
On Sun, 15 Mar 2015 17:01:16 -0600, Idris Samawi Hamid ادريس سماوي حامد
wrote:
export-highlight.tex==
\setupbackend
[export=yes,css=highlight.css]
\setupexport[cssfile=highlight.css]
\setupbackend[export=yes]
\definehigh
ached.
Immediate problem is highlights.
export-highlight.tex==
\setupbackend
[export=yes,css=highlight.css]
\definehighlight[emphasis] [style=italic]
\definehighlight[important][style=bold]
\definehighlight[regular][style=\tf]
\starttext
\startchapter[title=Highl
> Am 09.02.2015 um 14:34 schrieb Keith Schultz :
>
> 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 on
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
On Sun, 8 Feb 2015 13:56:54 +0100
"Keith J. Schultz" 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 to avoided!
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 n
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 sch
nto output 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
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 structur
Hi Wolfgang,
On Sun, 08 Feb 2015 12:17:11 -0700, Wolfgang Schuster
wrote:
Am 08.02.2015 um 15:40 schrieb Idris Samawi Hamid ادريس سماوي حامد
:
[…]
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 o
> Am 08.02.2015 um 15:40 schrieb Idris Samawi Hamid ادريس سماوي حامد
> :
>
> […]
>
> 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
did this setups
b
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]
\definehighlight[\v
> to it contents.
>
> 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 u
1 - 100 of 190 matches
Mail list logo
