was still in feet we decided to adapt it accordingly so now in addition
it reports
different values, including Theodores little feet measured by Arthur as
being roughly
five Ediths.
Here is the fitting error message when you pass a dimension too large
for TeX:
Dimension too large", I can
with
setupinterlinearspace[1.3ex] was the right way (I read somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspacing
t; setting ConTeXt with setupinterlinearspace[1.3ex] was the right way.
Hi Miguel,
sorry, but I don’t have any idea what \linespread might mean for LaTeX
in plain English.
Some ConTeXt users may also use LaTeX too, but don’t rely on that.
> (I read somewhere that vertical spaces should be measured i
with
setupinterlinearspace[1.3ex] was the right way (I read somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspacing
somewhere that vertical
spaces should be measured in ex and horizontal spaces in em; maybe it's not
widely accepted).
I tried setting my interlinearspace to 3ex and it looked much better, but I
must compare it with a onehalfspacing of wordprocessors to be sure it is not
such different.
Sorry
to a
more realistic variant. (Actually, because tex has no foot unit, we could as
well replace that with a more impressive little feet unit but we forgot to
measure the smallest foot present which i guess was about 3 es so the limit
is then some 75 bare theodores.)
I measured the theodore a
ex has no foot unit, we could as
> well replace that with a more impressive little feet unit but we forgot to
> measure the smallest foot present which i guess was about 3 es so the limit
> is then some 75 bare theodores.)
I measured the theodore at 13cm, so that puts the limit at
se to the total runtime (in the second example, 14.774 seconds of
23.057 are accounted), so there are other unidentified processes
involved.
these stats are an indication because below a threshold (time
accuracy) nothing is measured
In any case, the processing time has been improving greatly
conds of 23.057
are accounted), so there are other unidentified processes involved.
these stats are an indication because below a threshold (time accuracy)
nothing is measured
In any case, the processing time has been improving greatly over the
last couple of years, and LMTX is significantly f
;"
Missing ) inserted for expression
.
\commalistcommand
2mm + (0.09mm * 1.
5 * \noffigurepages /2)
\measured
#1->\dimexpr \ifcsname \??measure #1\endcsname \lastnamedcs
\else \zeropoint \fi \relax
...
"""
I also tried 1.5sp since sp should b
Am 04.11.22 um 11:52 schrieb Herbert Voss via ntg-context:
\definemeasure[FlapWidth][\measured{PageWidth} * 0.8]
\definemeasure[FlapWidth][0.8\measured{PageWidth}]
works
Yes, thank you!
That’s why I asked for the basics in my first post – which operators can
I use how, in which order
with dimension calculations. Is there
anything I can read about the possibilities and limitations?
e.g. with
\definemeasure[PageWidth][132mm]
none of the following works:
\definemeasure[FlapWidth][0.8 * \measure{PageWidth}]
use \measured (with a "d" to get a dimension)
Only in expres
the possibilities and limitations?
e.g. with
\definemeasure[PageWidth][132mm]
none of the following works:
\definemeasure[FlapWidth][0.8 * \measure{PageWidth}]
use \measured (with a "d" to get a dimension)
Only in expressions like that or always?
In https://source.contextgarden.net/syst-aux.mki
]
none of the following works:
\definemeasure[FlapWidth][0.8 * \measure{PageWidth}]
use \measured (with a "d" to get a dimension)
Only in expressions like that or always?
In https://source.contextgarden.net/syst-aux.mkiv
it looks like \measured returns a dimension, while \measure returns
* \measure{PageWidth}]
use \measured (with a "d" to get a dimension)
\definemeasure[FlapWidth][.8\measure{PageWidth}]
\definemeasure[FlapWidth][\measure{PageWidth} * 0.8]
\definemeasure[FlapWidth][\measure{PageWidth}*8/10]
\definemeasure[FlapWidth][8\measure{PageWidth}/1
>> >
>> > 1. I'd like to shift the text area down so that the red lines
>> > align with the blue lines (I think this amount is called depth). How
>> > would I do that?
>>
>> Quick and dirty:
>>
>> \setuplayout
>>[...,
>>
ft the text area down so that the red lines
> > align with the blue lines (I think this amount is called depth). How
> > would I do that?
>
> Quick and dirty:
>
> \setuplayout
>[...,
> topspace=\dimexpr5\measured{base}+2bp+\strutdp\relax,
> ...]
&
that the red lines
align with the blue lines (I think this amount is called depth). How
would I do that?
Quick and dirty:
\setuplayout
[...,
topspace=\dimexpr5\measured{base}+2bp+\strutdp\relax,
...]
2. The font is such that exactly 2 characters fit into the grid cell,
but I see
,
Stefan
On Mon, Jun 6, 2022 at 5:50 PM Aditya Mahajan wrote:
> On Mon, 6 Jun 2022, Stefan Nedeljkovic via ntg-context wrote:
>
> > Dear list,
> >
> > I have 2 small questions:
> >
> > 1. In \setuplayout if I try to set topspace=5\measured{base} +
> > \d
On Mon, 6 Jun 2022, Stefan Nedeljkovic via ntg-context wrote:
> Dear list,
>
> I have 2 small questions:
>
> 1. In \setuplayout if I try to set topspace=5\measured{base} +
> \dimexpr2bp I get an error. How should I add these 2bp?
(Untested)
\dimexpr\measure{base}+2bp\re
Stefan Nedeljkovic via ntg-context schrieb am 06.06.2022 um 07:55:
Dear list,
I have 2 small questions:
1. In \setuplayout if I try to set topspace=5\measured{base} +
\dimexpr2bp I get an error. How should I add these 2bp?
\setuplayout
[topspace=\dimexpr 5\measured{base} + 2bp\relax]
2
Dear list,
I have 2 small questions:
1. In \setuplayout if I try to set topspace=5\measured{base} +
\dimexpr2bp I get an error. How should I add these 2bp?
2. I have an mp graphic defined in the file "graphic.mp" which has the
exact same dimensions as my page. I'd like to set th
Perfect, thank you very much Max!
On Sat, May 28, 2022 at 10:40 AM Max Chernoff wrote:
> On 2022-05-28 2:27 a.m., Stefan Nedeljkovic wrote:
> > One slight problem is when I use 2\measured{xheight} as the font size I
> > get an error. \measure works fine though.
>
> The
On 2022-05-28 2:27 a.m., Stefan Nedeljkovic wrote:
One slight problem is when I use 2\measured{xheight} as the font size I
get an error. \measure works fine though.
The old version expected direct input, not a \dimen. Try this:
\starttexdefinition setxheight [#1][#2
One slight problem is when I use 2\measured{xheight} as the font size I get
an error. \measure works fine though.
On Sat, May 28, 2022 at 9:34 AM Stefan Nedeljkovic
wrote:
> Awesome, thank you very much Max!
>
> On Sat, May 28, 2022 at 8:49 AM Max Chernoff wrote:
>
>> >
;
> \definemeasure[xheight][0.1in]
>
> \definemeasure[base][3\measured{xheight}]
>
> % Since all distances are in terms of base units, specify the paper size
> in those
>
> % terms as well.
>
> \definepapersize[slide][width=26\measured{base},height=20\measured{base}]
>
&g
, the text shifts downwards by two lines.
My code:
\definemeasure[xheight][0.1in]
\definemeasure[base][3\measured{xheight}]
% Since all distances are in terms of base units, specify the paper
size in those
% terms as well.
\definepapersize[slide][width=26\measured{base},height=20\measured{base
Thank you very much Aditya for looking into this. But I still have the same
baseline grid offset problem. Interestingly, when I remove the columns, the
text shifts downwards by two lines.
My code:
\definemeasure[xheight][0.1in]
\definemeasure[base][3\measured{xheight}]
% Since all distances
st are 1 unit wide.
I believe that columns has to be an integer. Why do you want fractional
columns? Columns are useful because you can say:
\setlayer[name][line=2,column=3]{}
for absolute positioning of layers. So, you can always use:
\setlayer[name][line=2,column=3,x=0.5\measured{ba
space at the bottom.
2. The number of columns is 21.5, that is the first column is 0.5 units
wide and the rest are 1 unit wide.
How would I achieve this?
Here is what I got right now:
\definemeasure[xheight][0.1in]
\definemeasure[base][3\measured{xheight}]
\definepapersize[slide][width=80
rgins and similar things and only have a text area with
>> > an offset of 0.2in all around the page (see slide_grid_overlay.pdf).
>> > Here is my current attempt:
>>
>> You have to use the \measured (with a trailing s) command when you need
>> multiples of a measure
have a text area with
> > an offset of 0.2in all around the page (see slide_grid_overlay.pdf).
> > Here is my current attempt:
>
> You have to use the \measured (with a trailing s) command when you need
> multiples of a measure value. When you use something like 2\measure{...}
> Co
margins and similar things and only have a text area with
an offset of 0.2in all around the page (see slide_grid_overlay.pdf).
Here is my current attempt:
You have to use the \measured (with a trailing s) command when you need
multiples of a measure value. When you use something like 2\measure
think that napoleon sort of forced the netherlands to standardize
times (clocks) were definitely different per city
i remember reading that for instance when the car industry needed oarts
and there were more suppliers needed it were the supliers who
standardized measured (bolts and nuts
,
backgroundcolor=blue,
backgroundoffset=\measured{bleed}
]
wonder if this would be handy in the DIN lang folder template in the
wiki, as most such brochures will supposingly have a colored
background...?
Am Samstag, den 01.06.2019, 05:48 +0200 schrieb Benjamin Koppe
]
%% This is the pagesize of the final PDF.
%% The bleed size is added two times to width and height.
\definepapersize
[A4-flyer]
[width=\dimexpr297mm+2\measured{bleed}\relax,
height=\dimexpr210mm+2\measured{bleed}\relax]
%% The size of a normal page.
\definepapersize
[flyer-page]
[width=100mm
added the whole file as I really do not knwo (yet) how to reduce
things...
When you increase the size of the printed paper
\definepapersize
[A4-flyer]
[width=\dimexpr297mm+10\measured{bleed}\relax,
height=\dimexpr210mm+10\measured{bleed}\relax]
and center the arranged pages
-flyer]
[width=\dimexpr297mm+2\measured{bleed}\relax,
height=\dimexpr210mm+2\measured{bleed}\relax]
%% The size of a normal page.
\definepapersize
[flyer-page]
[width=100mm,
height=210mm]
%% The size of the folded page.
\definepapersize
[flyer-page-small]
[width
On 17/10/2018 11:10, Alan Braslau wrote:
On 17/10/2018 11:05, Hans Hagen wrote:
And compare it to sizing dogs or so ... what do you measure? Its tail
or its legs.
Of course, horses are measured in "hands"
lax,
>>\dimexpr\measure{bleed}/2\relax,
>>\dimexpr\measure{bleed}/2\relax,
>>\dimexpr\measure{bleed}/2+2\measured{shortfold}\relax,
>>\dimexpr\measure{bleed}/2\relax,
>>\dimexpr\measure{bleed}/2-\measure{shortfold}\relax]
>
> I don't get the sa
x,
>\dimexpr\measure{bleed}/2+2\measured{shortfold}\relax,
>\dimexpr\measure{bleed}/2\relax,
>\dimexpr\measure{bleed}/2-\measure{shortfold}\relax]
I don't get the same values like before, when I calculate with these
equations.
And while the aligns of the pages look good I
On Tue, 25 Sep 2018 12:57:54 +0200
"Jan U. Hasecke" wrote:
> \definemeasure
> [bleed]
> [3mm]
>
> I used this value to generalize the A4-flyer dimensions.
>
> \definepapersize
> [A4-flyer]
> [width=\dimexpr297mm+2\measured{bleed}\r
eshift works.
\definemeasure
[bleed]
[3mm]
I used this value to generalize the A4-flyer dimensions.
\definepapersize
[A4-flyer]
[width=\dimexpr297mm+2\measured{bleed}\relax,
height=\dimexpr210mm+2\measured{bleed}\relax]
But horizontal pageshift is beyond my grasp.
I c
age shift of page #6 needs to be adjusted if shortfold is adjusted, no
%% clue why.
\definepageshift
[flyer]
[horizontal]
[\zeropoint,
\measure{shortfold},
\measure{shortfold},
3\measured{shortfold},
\measure{shortfold},
\zeropoint]
\definepageshift
[flyer]
[vertical]
[\measure{shortfold}
e why.
\definepageshift
[flyer]
[horizontal]
[\zeropoint,
\measure{shortfold},
\measure{shortfold},
3\measured{shortfold},
\measure{shortfold},
\zeropoint]
\definepageshift
[flyer]
[vertical]
[\measure{shortfold}]
\setuppageshift
[paper]
[flyer]
\definemeasure
[small]
[3mm]
\definemea
On 8/21/2018 4:46 PM, Aditya Mahajan wrote:
Are the x and y values in pts (post script points or big points?)
measured from the top-left corner?
afaik bottom up base points
the script will look into the synctex file and figure out where to go
to. Basically all the viewer needs to do
points or big points?)
measured from the top-left corner?
the script will look into the synctex file and figure out where to go to.
Basically all the viewer needs to do is react to a click/cursor/key
combination and call mtxrun with the page and positions (basepoints in
pdf coordinate space)
>
> > \starttext
> > \framed[width=4cm]{Foobar}
> > \framed[width=\measure{mymeasure}]{Foobar}
> > \framed[width=2\mydim]{Foobar}
> > \framed[width=2\measure{mymeasure}]{Foobar}
> > \stoptext
> You can use \measured
That's what I was looking
wdimen\mydim \mydim4cm
\starttext
\framed[width=4cm]{Foobar}
\framed[width=\measure{mymeasure}]{Foobar}
\framed[width=2\mydim]{Foobar}
\framed[width=2\measure{mymeasure}]{Foobar}
\stoptext
You can use \measured or just create more named lengths.
\definemeasure [onemeasure] [4cm]
\definemeasure
to process xml ... well, then mkiv is definitely faster.)
If you think that there's a bottleneck somewhere that shouldn't be, I
can look into it when I'm bored.
A while ago I measured performance this way:
\usemodule[art-01]
\starttext
\input tufte % simulate stupid one page output
\stoptext
}
bla
\page[yes]}
\stoptext
I can't see that the header space is to small, no? or what am I missing?
using `\showglyphs' (which I didn't know of: thanks),
it still looks to me as if the problem is caused by the fact, that all
positions are measured from the top and
the header line's baseline
[fontsize:big] [17pt]
\definemeasure[fontsize:small][0.7\measured{fontsize:big}]
\definefont[big] [name:arial at \measure{fontsize:big}]
\definefont[small][name:arial at \measure{fontsize:small}]
\starttext
\big Dies ist ein großer Text. \blank
\small Dies ist ein kleiner Text
which is why the next is better:
\definemeasure[fontsize:big] [17pt]
\definemeasure[fontsize:small][0.7\measured{fontsize:big}]
\definefont[big] [name:arial at \measure{fontsize:big}]
\definefont[small][name:arial at \measure{fontsize:small}]
\starttext
\big Dies ist ein großer Text
\definemeasure[h1][1.2\measured{w1}+26mm]
\definemeasure[h2][1.2\measured{w2}+26mm]
\measured gives me this error (*Undefined control sequence*):
*\17h1 ^^@-1.2\measured*
* {w1}+26mm*
*\measure ...sname \csname \??measure #1\endcsname
On 11/19/2013 11:20 AM, Géry Ogam wrote:
\definemeasure[h1][1.2\measured{w1}+26mm]
\definemeasure[h2][1.2\measured{w2}+26mm]
then use
\dimexpr\measure{w2}\relax
\measured gives me this error (/Undefined control sequence/):
old context
Hans
:
\definemeasure[w1][0.7500\paperwidth]
\definemeasure[w2][0.6667\paperwidth]
\definemeasure[h1][1.2\measured{w1}+26mm]
\definemeasure[h2][1.2\measured{w2}+26mm]
\setuplayout
[width=\measure{w1},
height=\measure{h1}]
\definelayout
[luxury]
[width=\measure{w2},
height=\measure{h2
Hi all,
calling fontloader.to_table() appears to be redundant when
extracting font names, see the attached patch. On my system I
measured 42 (patched) vs 59 (vanilla) seconds for rebuilding the
entire index:
mtxrun --script fonts --reload --force
The resulting index is -- except for the uuid
On 11/9/2013 6:45 PM, Philipp Gesang wrote:
Hi all,
calling fontloader.to_table() appears to be redundant when
extracting font names, see the attached patch. On my system I
measured 42 (patched) vs 59 (vanilla) seconds for rebuilding the
entire index:
mtxrun --script fonts --reload --force
···date: 2013-11-09, Saturday···from: Hans Hagen···
On 11/9/2013 6:45 PM, Philipp Gesang wrote:
Hi all,
calling fontloader.to_table() appears to be redundant when
extracting font names, see the attached patch. On my system I
measured 42 (patched) vs 59 (vanilla) seconds for rebuilding
measured 42 (patched) vs 59 (vanilla) seconds for rebuilding the
entire index:
mtxrun --script fonts --reload --force
The resulting index is -- except for the uuid, naturally --
identical in both cases.
Okay.
In fact this fullinfo was meant as temporary hack
Hi Pablo,
I think this is a problem with the Unifraktur Maguntia font. I just
downloaded it [1], and measured it using \blackrule -- and the
x-height is indeed ridiculously low.
[1] from here: http://unifraktur.sourceforge.net/maguntia.html
\setupinterlinespace[line=3.2ex]
\usemodule
On 24/06/13 10:26, Sietse Brouwer wrote:
Hi Pablo,
I think this is a problem with the Unifraktur Maguntia font. I just
downloaded it [1], and measured it using \blackrule -- and the
x-height is indeed ridiculously low.
[1] from here: http://unifraktur.sourceforge.net/maguntia.html
up so there is no interference but it guarantees to stop scanning.
(I've been wondering if we should make measured \the\dimexpr..\relax
internally which can save dimexpr at the user end.)
A \ColumnA% ok
B \ColumnB% ok
% I sadly get only errors when I delete the comments:
%ColumnABi
it normally goes okay,
personally I always use \relax as terminator; the \relax will be eaten up so
there is no interference but it guarantees to stop scanning.
AFAIR the etex already mentions it.
(I've been wondering if we should make measured \the\dimexpr..\relax
internally which can save dimexpr
On 2013-04-22, at 6:43 AM, Wolfgang Schuster schuster.wolfg...@gmail.com
wrote:
(I've been wondering if we should make measured \the\dimexpr..\relax
internally which can save dimexpr at the user end.)
+1
+1 from me as well. Having to use \dimexpr...\relax in definemeasure ISS bit
in most cases faster (I
measured upto 3 times) but it also permits us to support some more:
integer %...i number
integer %...d number
unsigned %...u number
utf character%...c number
hexadecimal %...x number
HEXADECIMAL %...X number
octal
Hi,
I uploaded a beta. The most important change is that the 'context'
function now uses the formatters mechanism instead of Lua's format.
This has several benefits. First of all it's in most cases faster (I
measured upto 3 times) but it also permits us to support some more:
integer
Hello,
On Tue, 04 Sep 2012 05:02:01 +0200, Rogers, Michael K mrog...@emory.edu wrote:
That's what I was afraid. It's just I had the same problem last week, and a
deadline made me settle for the ad hoc approach.
I was trying to solve the same situation several week ago.
Finally, I measured
Dear ConTeXt folks,
could you please share your experiences with or point me to a resource
dealing with the following issue.
I need to evaluate some physics experiments where I have some values
which got measured. I thought I could use ConTeXt with LuaTeX to do all
the calculations instead
Am 16.02.2011 um 18:47 schrieb Paul Menzel:
Dear ConTeXt folks,
could you please share your experiences with or point me to a resource
dealing with the following issue.
I need to evaluate some physics experiments where I have some values
which got measured. I thought I could use ConTeXt
On 16-2-2011 6:47, Paul Menzel wrote:
Dear ConTeXt folks,
could you please share your experiences with or point me to a resource
dealing with the following issue.
I need to evaluate some physics experiments where I have some values
which got measured. I thought I could use ConTeXt with LuaTeX
measured. I thought I could use ConTeXt with LuaTeX to do all
the calculations instead of the calculator and enter the results by hand
or a spreadsheet program.
Would I enter the values (not many) at the top of the TeX document and
refer to them in the other places? Is an extra file a better
---
The problem is that the space between the subsection number and the text
differs (and it doesn't depend on whether 'distance' was set to '1.5em' or
not).
You can also see the picture with measured values.
Why this effect? And how to make both distances equal?
Can you change your
is ended and a new one is started.
hsize and vsize are more general and depend on where one accesses them,
setting them will seldom work out well as they get set (and
synchronized) depending on \setuplayout asignments
The actual page size of the finished document is measured with
\pdfpagewidth
.
The actual page size of the finished document is measured with
\pdfpagewidth and \pdfpageheight. For most documents this is the last
set of dimensions needed. In a few cases camera ready copy is
required which means that the final printed page image is centered on a
larger piece of paper stock, often
to read it in the
Post office in case the addressee is wrong?
i measured one envelope DIN Lang
+Top
|
|
| 50mm
|
|
+
|
| 45mm Window
|
+
|
| 15mm
|
+Bottom
That fits perfect with Koma scrltr2. I have not (yet) tried
it in Context, but i will soon.
Perhaps
the substitutions themselves can be sped up a little with no
effort, by using the normal string.gsub. That function is 8bit clean, so
there is no need for the added complication of utf8 processing.
You're right again, I measured 33% shorter execution time in an extreme
case with string.gsub; done
vertical offset (measured from the top) which causes lengthy address
data to look slightly off balance …
Try the following settings. The names can change.
\setupletterstyle
[address][dispatch]
[height=0pt]
\setupletterstyle
[address][content]
[location=normal,
align={right,lohi
On Tue, Jul 8, 2008 at 2:49 PM, Oliver Buerschaper
[EMAIL PROTECTED] wrote:
Dear Wolfgang,
is it possible to centre the text block in the address field
vertically? At the moment the address is typeset with a constant
vertical offset (measured from the top) which causes lengthy address
data
be
105mm from papertop. It is 110mm from top.
The horizontal offset (3.5mm) of foldmarks ist to small. A
laserprinter often is not able to print 5mm or more from
paperedge.
So the foldmarks are invisibel.
I never measured the real values and it should be simple
whitespace
problem somewhere
.
I never measured the real values and it should be simple whitespace
problem somewhere in the code.
Have you found that whitespace?
Aren't the foldmarks positioned in absolute values relative to the
page? There is no whitespace involved, isn't it?
So I don't understand this 5mm offset
or more from paperedge.
So the foldmarks are invisibel.
I never measured the real values and it should be simple whitespace
problem somewhere in the code.
The address field was wrong placed and I corrected it, the place for the
referenece line should work but I change the position dependen
between 10- and 40-percent and can allow
those previously savings-challenged industrial manufacturing companies to
participate in demand response programs, he said. Do the math. The
financial benefits, measured by dramatically reduced demand charges and the
opportunity to participate in DR programs
programs, he said. Do the math. The
financial benefits, measured by dramatically reduced demand charges and the
opportunity to participate in DR programs, are substantial, often creating a
project payback in the range of 1 to 18 months, - not to mention the
benefits to local energy utilities
}{#2}{#3}}
Thanks Peter,
I ended up using
\def\doifoneelse#1{\doifelse{#1}{1}}
which saves a few keystrokes :)
\def\doifoneelse{\doifelse{1}}
or
\def\doifoneelse{\doifelse1}
saves you even more keystrokes and also a bit of runtime (measured in
nanoseconds)
Hans
]
\artauthor[]{R.~V.}[R.~V.]{}{Pound}
\artauthor[]{G.~A.}[G.~A.]{}{Rebka}
\pubyear{1959}
\arttitle{Gravitational red-shift in nuclear resonance}
\journal{Physical Review Letters}
\volume{3}
\pages{439--441}
\stoppublication
\starttext
An incredibly tiny effect! To find out how it was measured, see
should be.
One possibility is to create a new metapost figure and draw the circle
on it using the measured coordinates:
(This circles the blue tulip on
http://contextgarden.net/images/6/65/Kochloewe_c.jpg.)
\setupcolors[state=start]
\starttext
\startuseMPgraphic{CircleBlueTulip}
% center point
the center of circle should be.
One possibility is to create a new metapost figure and draw the circle
on it using the measured coordinates:
(This circles the blue tulip on
http://contextgarden.net/images/6/65/Kochloewe_c.jpg.)
\setupcolors[state=start]
\starttext
\startuseMPgraphic{CircleBlueTulip
Hi!
I have some problems using units or cite commands in combination
with line breaks.
Using:
... energies up to 3 \EVolt were measured
will produce no whitespace between eV and were
... energies up to 3 eVwere measured .
In order to get the space correct between
Michael Fuchs said this at Thu, 10 Mar 2005 16:11:10 +0100:
How can I create a space after the unit and have correct
line breaking at the same time?
Hallo, Michael.
This is a standard TeX thing. Follow the macro with \ .
(backslash-space). So:
... energies up to 3 \EVolt\ were measured
, Michael.
This is a standard TeX thing. Follow the macro with \ .
(backslash-space). So:
... energies up to 3 \EVolt\ were measured
The TeXBook (look in your local library) gives a pretty lucid
description
of how this works
91 matches
Mail list logo
