\framed{Régalage des paramèters de contrôle} etex) ;
newEllipse.N4(btex \framed{Envoi du contenu de l'\cap{EEPROM}} etex) ;
newEllipse.N5(btex \framed{{\bf Mode stop|/| réglage}
Attente de commande} etex) ;
newEllipse.N6(btex \framed{\bf Mode freins libres} etex
Hi,
I want to ensure that the titles displayed in the header always begin
with a capital letter regarless of any truncation with \nomarking..
I tried the following in my environment but it doesn't work:
\setupheadertexts[\Cap{\getmarking[Title][current]}][Author]
What should I use?
Thanks
Elliot Clifton wrote:
Hi,
I want to ensure that the titles displayed in the header always begin
with a capital letter regarless of any truncation with \nomarking..
Why don't you add explicit marking then? That may be easiest in
this case.
\marking[Title]{Whatever you desire with Cap
most of what I want to do. I have a follow-up question if anybody would like to provide more help! Because lines in \startlines\stoplines with \setuplines[space=yes] can be indented by space characters, I want to set Nindent for the dropped cap to (N * width of space character), so lines can
with expand* ended up with either the same
result or with a TeX error message.
Using \setupheader[style=kap] (or =cap) does not work - as TeX bails out:
! Undefined control sequence.
\p!doifinstringelse ...ifinstringelse #2#1}@@\war
Any idea how to solve this?
Tobias
PS: I just saw that I asked
[style=kap] (or =cap) does not work - as TeX bails out:
! Undefined control sequence.
\p!doifinstringelse ...ifinstringelse #2#1}@@\war
Any idea how to solve this?
Tobias
PS: I just saw that I asked the same question two years ago (15 January
2004):
http://www.mail-archive.com/ntg-context@ntg.nl
);
label.bot(btex $A\cup B$ etex,T2);
\stopMPpage
\startMPpage
draw_venn_two(false,false,true,false);
label.lft(btex $A$ etex,A);
label.rt(btex $B$ etex,B);
label.bot(btex $A\cap B$ etex,T2);
\stopMPpage
\startMPpage
draw_venn_two(true,false,false,false);
label.lft(btex $A$ etex,A);
label.rt
Dear gang,
I am having difficuly getting dropped caps and the new indenting mechanism
coordinated; the dropped cap goes into the margin. Try this:
===
\setupoutput[pdftex]
\setupindenting[medium,next,yes]
\def\TextDroppedCaps{%
\DroppedCaps
]
\usetypescriptfile[type-buy]
\loadmapfile[ec-bh-lucida.map]
\usetypescript[lucida][ec]
\setupbodyfont[lucida]
\starttext
Test \high{exposants} ainsi que des S\cap{mall} C\cap{apitals} !!!
{\em emph !}
{\sl slanted}
{\tt verbatim}
$$t+e+x+t = m+a+t+h + \theta$$
\stoptext
with:
# texfont demofont.dat
# test test
--ve=test --co=test --ma --indemofont
--ve=test --co=test --ma --in --sla=.167 demofont
--ve=test --co=test --ma --in --ext=1.50 demofont
--ve=test --co=test --ma --in --cap=.750 demofont
--ve=test --co=test --ma --in --nol demofont
...and by running
assume that demofont.afm and demofont.pfb are present
# run with:
# texfont demofont.dat
# test test
--ve=test --co=test --ma --indemofont
--ve=test --co=test --ma --in --sla=.167 demofont
--ve=test --co=test --ma --in --ext=1.50 demofont
--ve=test --co=test --ma --in --cap=.750
# [, --sla=.167, --ext=1.50, --cap=.750].each do |option|
# job.execute_command(texmfstart texfont --ve=test --co=test --
ma --in #{option} demofont)
# end
job.execute_command(texmfstart texfont --ve=test --co=test --ma --in
demofont.dat)
I imagine this is where I should start? I try
. Setting textstyle=cap
doesn't do anything. Setting style=cap gives an error (see end of
message). style=slanted works, commands (\cap, \kap) don't work.
\cap{some text} used in the text works.
style=\sc works.
Cheers, Jörg
bothering you with another question:The subsection heads should be capitals. Setting textstyle=cap doesn't do anything. Setting style=cap gives an error (see end of message). style=slanted works, commands (\cap, \kap) don't work. \cap{some text} used in the text works.This is how I'm setting up the
Answering one of my own questions:The subsection heads should be capitals. Setting textstyle=cap doesn't do anything. Setting style=cap gives an error (see end of message). style=slanted works, commands (\cap, \kap) don't work. \cap{some text} used in the text works.style=\sc works.Cheers, Jörg
Taco Hoekwater wrote:
Marcus Vinicius Mesquita de So wrote:
Problems occur with Lettrine when used with the linenumbering
environment, the dropped cap stays outside the margin.
Minimal example below.
Sorry, this is unfixable.
Greetings,
Taco
Thank you for your effort!!
Marcus
--- Taco Hoekwater [EMAIL PROTECTED] wrote:
Taco Hoekwater wrote:
Marcus Vinicius Mesquita de So wrote:
Problems occur with Lettrine when used with the
linenumbering
environment, the dropped cap stays outside the
margin.
Minimal example
Problems occur with Lettrine when used with the
linenumbering
environment, the dropped cap stays outside the margin.
Minimal
example below.
A zipped file (129 Kb) with the pdf generated and a
corrected one
with Pitstop can be downloaded from the following
link:
http://rapidshare.de/files
have it all, anyway.
I'll have a look, but don't get your hopes up.
Cheers, Taco
Marcus Vinicius Mesquita de So wrote:
Problems occur with Lettrine when used with the linenumbering
environment, the dropped cap stays outside the margin.
Minimal example below
)
an alternative is to copy for instance ec.enc to ec-cap.enc and change the lowercase entries to uppercase ones (we can add such files to the distribution); then you use texfont with that encoding so you get ec-cap-whatever kind of font files
Hans
fine, and one can change the font that
comes after
the dropped cap with commands like \sc (default), \it,
\sl or \bf, but
the option FontHook, which changes the font of the
capital, doesn't
seem to work when one uses, for example,
. Did I miss something?
Marcus Vinicius
does work only with the commands which change the
style from that point onwards (e.g., \it, \tfx). What about the
commands which take the text as a parameter (such as \cap{text})?
And what are textcommand and numbercommand? I tried playing a bit
with them. For example, \it or \bf can be put either
\cap{abcABCåäöÅÄÖ}
\uppercased{abcABCåäöÅÄÖ}
\WORD{abcABCåäöÅÄÖ}
\uppercase{abcABCåäöÅÄÖ}
\stoptext
---
So, the test string is: abcABC\aumlaut\aring\oumlaut\Aumlaut\Aring\Oumlaut
(just in case it does not display correctly). It gives:
\cap - ABCABCÅÄÖÅÄÖ (in \tfx size), just as expected
Ville Voipio said this at Wed, 4 May 2005 00:32:59 +0300:
As \uppercase is a plain TeX macro, fixing it is not a good
choice, especially because it is known to be bad. However,
if \WORD could be built on \cap but without the font size
changing, it would work fine. The odd behaviour of \uppercased
I've been trying to make capitalized (uppercase)
headings with little success. I'd like to have
the titles simply capitalized as with \cap or
\WORD.
A minimal example:
---
\setuphead[title][style=WORD]
\starttext
\title{This is a title}
The title should be \cap{capitalized} or \WORD
Ville Voipio said this at Mon, 2 May 2005 20:49:45 +0300:
I've been trying to make capitalized (uppercase)
headings with little success. I'd like to have
the titles simply capitalized as with \cap or
\WORD.
A minimal example:
---
\setuphead[title][style=WORD]
\starttext
\title
of floats.
\starttext
\chapter[sample]{Sample}
\placefigure[here][a]{cap}{test}
Reference: \in{figure}[a]
\section[test]{Test}
\stoptext
In this setup, chapter numbers do not use OSF, and the numbers of
figures (as well as references to them) use a mixed form, which
looks rather odd.
I can
felicidade era causa da desventura da amiga, e agora
que a tinha
quase realizado, sentia morderlhe um piedoso remorso.
\stoplinenumbering
\stoptext
then the dropped cap doesn't stay where it should.
Any suggestions?
Thanks in advance
Marcus Vinicius
Steffen Wolfrum wrote:
Hi,
Each kind of emphasizing - like \it \bf \cap \sc etc. -
lets the respective phrase fall back to the documents
bodyfont (see example below).
How can I avoid this bug?
not a bug, this is the expected behaviour of \definefont.
Do I use wrong code?
Yes
,
but windows does not care, i.e. all access deep down in the system is (afaik)
cap. So i saw no difference here.
so, what do you recomend, renaming the file to lowercase?
Hans
-
Hans Hagen
Hello Hans,
[...]
ah, i explicitly tried both lower and uppercase variants of the sample
files, but windows does not care, i.e. all access deep down in the
system is (afaik) cap. So i saw no difference here.
so, what do you recomend, renaming the file to lowercase?
Well, my mail was sent
-cap fonts
with old-style numerals that I could then use in my typescript. So I'm
wondering: is this a good idea, or is there a simpler way of doing
this?
Best
Thomas
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo
high quality intitials, a ConTeXt
equivalent should not have any less parameters than lettrine.sty.
To re-cap the parameters in lettrine.sty:
==
- lines=integer sets how many lines the dropped capital will occupy
(default=2);
- lhang
Hi,
there seems to be a fundamental problem with headings - or at least I have :(
Each kind of emphasizing - like \it \bf \cap \sc etc. - lets the respective
phrase fall back to the documents bodyfont (see example below).
How can I avoid this bug? Do I use wrong code?
Thank you,
Steffen
Steffen Wolfrum wrote:
Hi,
Each kind of emphasizing - like \it \bf \cap \sc etc. -
lets the respective phrase fall back to the documents
bodyfont (see example below).
How can I avoid this bug?
not a bug, this is the expected behaviour of \definefont.
Do I use wrong code?
Yes. \definefont
full-blown bodyfont switch - that sounds good.
thank you Taco!
st.
Taco Hoekwater [EMAIL PROTECTED] wrote:
Steffen Wolfrum wrote:
Hi,
Each kind of emphasizing - like \it \bf \cap \sc etc. -
lets the respective phrase fall back to the documents
bodyfont (see example below
to be a fundamental problem with headings - or at least I have :(
Each kind of emphasizing - like \it \bf \cap \sc etc. - lets the respective
phrase fall back to the documents bodyfont (see example below).
How can I avoid this bug? Do I use wrong code?
Thank you,
Steffen
\starttext
\def\Textit
Been working my way through the examples in the Columns Manual, the Details
Manual etc. and had some thoughts on additional features.
Versals come in many different flavors, of which the conventional dropped cap
is just one. Even that facility could use a tweak. Conventionally, to provide
and would not want to replace stretched text simply by emphasized. Is
it absolutely discouraged in ConTeXt or is there any way to have
it... (in spite of its ugliness).
It's still recommended in certain cases, for example in all capital or
small cap titles. Sometimes I do it and sometimes
. Is
it absolutely discouraged in ConTeXt or is there any way to have
it... (in spite of its ugliness).
It's still recommended in certain cases, for example in all capital or
small cap titles. Sometimes I do it and sometimes not.
You can do it in Context. See:
http://home.salamander.com/~wmcclain/context
On Thu, 02 Sep 2004 14:54:52 +0200, Hans wrote:
do you suggest that i just don't set that catcode?
I was asking because the initial request was probably related to
\uppercase/\lowercase, and if so, then it is probably better
to write explicitly iterating \CAP macros for that, than to mess
Taco Hoekwater wrote:
On Thu, 02 Sep 2004 14:54:52 +0200, Hans wrote:
do you suggest that i just don't set that catcode?
I was asking because the initial request was probably related to
\uppercase/\lowercase, and if so, then it is probably better
to write explicitly iterating \CAP macros
Salman Khilji wrote:
Why don't I see capitals in the following example?
\setupbodyfont [cmr,12pt]
\starttext
\startbuffer[test]
The quick brown fox jumps over the lazy dog.
\stopbuffer
\getbuffer[test]
\CAP{\getbuffer[test]}
\stoptext
in this case you should follow Hraban's suggestion
Why don't I see capitals in the following example?
\setupbodyfont [cmr,12pt]
\starttext
\startbuffer[test]
The quick brown fox jumps over the lazy dog.
\stopbuffer
\getbuffer[test]
\CAP{\getbuffer[test]}
\stoptext
___
ntg-context mailing list
[chapter]
[criterium=chapter,
alternative=c,
aligntitle=yes,
textstyle={\tfa\cap}]
\setuplist
[section]
[criterium=section,
alternative=c,
margin=0.7cm,
textstyle=bold]
\setuplist
[subsection]
[criterium=subsection,
alternative=c,
margin=0.9cm
command do you
use to get Frutiger Ultra Black in a chapter title? I still don't know
how to use a medium small cap font in a document!
\definefont[ChapterTitleFont][Frutiger-Ultra-Black]
\setuphead[chapter][style=ChapterTitleFont]
so, that's not for typescripts but for styles
Hi Andreas,
Though not a wizzard ... Did you try to use the \setupcaption :
\setupcaptions
[location=top|bottom|none|high|low|middle,
width=fit|broad|max|dimension,
minwidth=fit|dimension,
headstyle=normal|bold|slanted|boldslanted|type|cap|small...|command,
style=normal|bold|slanted
\startenvironment layout
\setuppagenumbering[location={footer,middle}]
\setuphead
[chapter]
[numberstyle=bold,
textstyle=cap,
before=\hairline\blank,
after={\nowhitespace\hairline\blank[line]}]
\stopenvironment
% screenbook/screenbook.tex
% contains definitions for the relevant product
% Maybe
301 - 348 of 348 matches
Mail list logo
