n body text and ToC? (Body text is not a
problem.)
MNWE:
\setuphead[chapter][page=yes,style={\ss\bfc}]
\setuphead[section][page=no,style={\ss\bfa}]
\definehighlight[emph][style=\it]
\definestyle[emph][style=\italicface]
Wo
they should be tagged, too!
Wolfgang has mentioned that we have definestyle is that
tagged or not!
Furthermore, it is possible in ConTeXt to setup for example
the style italic, etc to what ever one cares to! for example one could
make and italic style be mono or bold! (naturally, it is
nonsense to do
to the structure, then only one font style
and color is needed.
So actually, in the end they should be tagged, too!
Wolfgang has mentioned that we have definestyle is that
tagged or not!
No.
Furthermore, it is possible in ConTeXt to setup for example
the style italic, etc to what ever one cares
reflect what it does. We can have synonyms to satisfy
the
semantic usage of it!
There is a \definestyle command (you can disable the creation of command [e.g.
\strong]
when you add “method=” to \definestyle) but it doesn’t add tags in the export
command.
\definestyle [strong] [style=bold
Dear gang,
Has the behavior of \definestyle changed? In my typescript I have e.g.
\definestyle [semibold] [\sb] []
It worked for years but now I get
=
! Undefined control sequence.
system tex error on line 1 in file
C:/ConTeXt/tex/texmf-project/tex/generic/private
Am 05.03.2013 um 20:55 schrieb Idris Samawi Hamid ادريس سماوي حامد
isha...@colostate.edu:
Dear gang,
Has the behavior of \definestyle changed? In my typescript I have e.g.
\definestyle [semibold] [\sb] []
Replace \definestyle with \definealternativestyle. In MkII and earlier MkIV
On Tue, 5 Mar 2013, Idris Samawi Hamid ادريس سماوي حامد wrote:
Dear gang,
Has the behavior of \definestyle changed? In my typescript I have e.g.
\definestyle [semibold] [\sb] []
You are, perhaps, thinking of \definealternativestyle which has the syntax
that you are using above
On Tue, 05 Mar 2013 13:07:08 -0700, Wolfgang Schuster
wolfgang.schus...@gmail.com wrote:
Am 05.03.2013 um 20:55 schrieb Idris Samawi Hamid ادريس سماوي حامد
Replace \definestyle with \definealternativestyle. In MkII and earlier
MkIV versions the \definestyle
was a synonym
% 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
[cn]
\definefontalternative [ci]
\definestyle [boldcondensed] [\bc] []
\definestyle [boldcondenseditalic] [\bci] []
\definestyle [semibold][\sb] []
\definestyle [semiboldcondensed] [\sbc] []
\definestyle [semiboldcondenseditalic] [\sbci] []
\definestyle
]
\definefontalternative [mf]
\definefontalternative [mc]
\definefontalternative [mci]
\definefontalternative [mi]
\definefontalternative [lf]
\definefontalternative [li]
\definefontalternative [lp]
\definefontalternative [lpi]
\definefontalternative [cn]
\definefontalternative [ci]
% \definestyle [black] [\bc
+MetaPost?
Currently, no.
Should I add
drawoptions(\MPvar{another-style-name}) before each draw/fill command, and
drawoptions() after it?
One option is to define two macros: definestyle (or perhaps newstyle,
which is more in line with metapost naming conventions) and withstyle so
that you can say
Hans van der Meer wrote:
This used to define command \fx in a typescript:
\definefontstyle [fax] [fx]
\definestyle [fax] [\fx] []
However MKIV produces an undefined control sequence \fx.
What happened?
actual definition of those commands is delayed so in order to test what
is wrong a more
solution or pointing out the way to go ;-)
On 19 aug 2009, at 09:08, Hans Hagen wrote:
Hans van der Meer wrote:
This used to define command \fx in a typescript:
\definefontstyle [fax] [fx]
\definestyle [fax] [\fx] []
However MKIV produces an undefined control sequence \fx.
What happened?
actual
:
\definefontstyle [fax] [fx]
\definestyle [fax] [\fx] []
However MKIV produces an undefined control sequence \fx.
What happened?
and does \hw work ok?
Hans
-
Hans Hagen | PRAGMA ADE
[fax] [fx]
\definestyle [fax] [\fx] []
However MKIV produces an undefined control sequence \fx.
What happened?
and does \hw work ok?
Hans
met vriendelijke groet
Hans van der Meer
___
If your question is of interest
This used to define command \fx in a typescript:
\definefontstyle [fax] [fx]
\definestyle [fax] [\fx] []
However MKIV produces an undefined control sequence \fx.
What happened?
Hans van der Meer
___
If your
as a mnemonic
device.
We also need some long-winded control sequences:
\definestyle [semiboldroman,semibold] [\sb][]
\definestyle [semibolditalic] [\st][]
\definestyle [smallcapssemibold,semiboldsmallcaps][\SB][]
\definestyle [smallcapsbold
in documents. The more
attractive and robust markup possibilities allowed by things like
\definestyle go unnoticed, and relatively unused.
So you can define your markup more semantically with \Emphasis{} and
\Acronym{} and \Arabic{} and \Bigger{} and \Slightlybolder{}, and Hans
can change the internals
use caps. This serves as a mnemonic
device.
We also need some long-winded control sequences:
\definestyle [semiboldroman,semibold] [\sb][]
\definestyle [semibolditalic] [\st][]
\definestyle [smallcapssemibold,semiboldsmallcaps
, with the
difference that the small caps versions use caps. This serves as a mnemonic
device.
We also need some long-winded control sequences:
\definestyle [semiboldroman,semibold] [\sb][]
\definestyle [semibolditalic] [\st][]
\definestyle
and uses the default fonts. My
user-defined switch works, but does not inherit from, e.g., \tfc. But \bf does
inherit.
What am I missing?
Thnx in advance
Idris
==type-lmtest===
\definestyle[smallcapssemibold,semiboldsmallcaps][\scsb][]
\starttypescript[serif
:
Dear crew,
I am having trouble defining my own font switches. I get an undefined
control
sequence for, e.g, \mv, with the following:
% output=pdf interface=en
\definestyle [myvariant] [\mv] []
\starttypescript [serif] [modern] [size]
\definebodyfont [9pt,10pt
Ok, I think I have come closer to understanding the \definestyle problem. The
problem (bug?) is in \definetypeface. Consider the following test typescript:
==type-testlm.tex===
\definestyle [mvmystyle] [\mv] []
\starttypescript [serif] [mystyle] [name
). \bf still switches to the optically-scaled bold, while
\ob uses cmmib10's numerals:
\definestyle [oldstylebold] [\ob] []
:
\definefontsynonym [OldStyleSerif-Bold] [cmrosb10]
%cmrosb10 is a virtual font that calls the numerals from
%cmmib10
:
\definefontsynonym [SerifBold
25 matches
Mail list logo
