Command/ startxtable
Command/ stoplinenote
Command/ style
Command/ synonym
Command/ textbackground
Command/ textnote
Command/ tooltip
Command/ type
Command/ typebuffer
Command/ unit
___
If your question is of interest to ot
On 3/23/2024 8:31 PM, Hraban Ramm wrote:
Am 23.03.24 um 19:05 schrieb Hans Hagen:
On 3/23/2024 2:27 PM, Wolfgang Schuster wrote:
Regarding the dk unit: https://tug.org/TUGboat/tb42-3/tb132hagen-dk.pdf
The es, ts and eu are discussed here:
https://tug.org/TUGboat/tb44-2/tb137egger-edith.pdf
Am 23.03.24 um 19:05 schrieb Hans Hagen:
On 3/23/2024 2:27 PM, Wolfgang Schuster wrote:
Regarding the dk unit: https://tug.org/TUGboat/tb42-3/tb132hagen-dk.pdf
The es, ts and eu are discussed here:
https://tug.org/TUGboat/tb44-2/tb137egger-edith.pdf
In German, I call these "Spaßeinh
=MyColors:4,
backgroundoffset=1dk,
frame=off]
The units "es" and "dk" are unknown to me.
What does they mean?
Regarding the dk unit: https://tug.org/TUGboat/tb42-3/tb132hagen-dk.pdf
The es, ts and eu are discussed here:
https://tug.org/TUGboat/tb44-2/tb137egger-edith.pdf
i
]
The units "es" and "dk" are unknown to me.
What does they mean?
Regarding the dk unit: https://tug.org/TUGboat/tb42-3/tb132hagen-dk.pdf
A quote from the Luametatex source regarding the es unit:
The Edith and Tove were introduced at BachoTeX 2023 and because the
error message
d. In principe the input
+assumptions to how numbers are constructed. In principal, the input
assumes a comma to separate thousands and a period to separate the
fraction.
-\getbuffer
-
You can swap periods and commas in the output. In fact there are a
few methods available. For instance we can separ
On Tue, 5 Dec 2023 20:06:46 +0100
Wolfgang Schuster wrote:
> > That doesn't make sense, inch and mm are different units. I'd rather
> > add:
> >
> >\registerunit
> > [inHg=inchmercury]
> >
> >\setupunittext
> > [en]
> > [inchmercury=inHg]
>
> It's just a stupid example
Marco Patzer schrieb am 05.12.2023 um 19:58:
\setupunittext[en][millimetermercury=inHg]
That doesn't make sense, inch and mm are different units. I'd rather
add:
\registerunit
[inHg=inchmercury]
\setupunittext
[en]
[inchmercury=inHg]
It's just a stupid example to show
On Tue, 5 Dec 2023 17:27:59 +0100
Wolfgang Schuster wrote:
> None of your examples work because millimetermercury and mercury are
> the names for the labels
> and the units are accessed with hg and mmhg.
Ok, that makes sense. And it works, thanks for the explanation and
the quick reply.
>
Marco Patzer schrieb am 05.12.2023 um 15:19:
Hi!
I'm struggling with the rendering of a particular liquid metal:
%% renders as m (meter), not as Hg
\unit{mercury}
%% renders as mm·m, not as mmHg
\unit{millimetermercury}
This is strange, since both “mercury” and “millimetermercury
Hi!
I'm struggling with the rendering of a particular liquid metal:
%% renders as m (meter), not as Hg
\unit{mercury}
%% renders as mm·m, not as mmHg
\unit{millimetermercury}
This is strange, since both “mercury” and “millimetermercury” are
defined in phys-dim.lua. To get mercury
hub.io/pandoc-crossref
- https://github.com/tomduck/pandoc-eqnos
I'm leaning towards the following syntax:
Markdown Item (table, blockquote, TeX block, figure, code, R chunk, etc.)
: caption text {#type:label}
See [@type:label] for details.
There's a unit test that shows what's currently
e. I think
they are generated but maybe they are placed on top of each other, maybe?
I'm not sure why my logic is not working.
Also, if I change the amount for ascenders, descenders of x-height, the
marks are not drawn correctly.
My current path for a mark is a custom path emulating two unit sq
of wordprocessors to be sure it is not
such different.
The unit ex uses the x-height value of the font as dimension, the
x-height is the height of the lowercase x (actually it's a value in the
font which is most cases equal to the height of the lowercase x) as can
be seen in the output of the following
On Tue, 3 Oct 2023 16:27:22 +0200
Marco Patzer wrote:
> What about:
>
> \unit{10 um}
> \unit{10 µm}
>
> Can I assign µ to mean micro (prefix)?
Found it:
\registerunit [prefix] [µ=micro]
\starttext
\unit{10 micro meter} \crlf
\unit{10 µm}
\stoptext
Should this be the d
On Tue, 3 Oct 2023 15:42:57 +0200
Wolfgang Schuster wrote:
> Marco Patzer schrieb am 03.10.2023 um 12:31:
> > Hi!
> >
> > I struggle using the unit Farad (unit of capacitance):
>
> The unit "farad" exists.
You're right \unit{10 Farad} works.
Marco Patzer schrieb am 03.10.2023 um 12:31:
Hi!
I struggle using the unit Farad (unit of capacitance):
The unit "farad" exists.
\starttext
%% prints 10 10 ft
\unit{10 F}
\unit{20 ft}
\registerunit [F=Farad]
\setupunittext [Farad=F]
%% prints 10 F 20 F⋅t
\unit{10 F}
\
Hi!
I struggle using the unit Farad (unit of capacitance):
\starttext
%% prints 10 10 ft
\unit{10 F}
\unit{20 ft}
\registerunit [F=Farad]
\setupunittext [Farad=F]
%% prints 10 F 20 F⋅t
\unit{10 F}
\unit{20 ft}
\stoptext
When registering Farad as new unit it messes up feet. This looks
like
ection 6 of the manual.
> \startTEXpage[offset=1ex]
> x\vrule height 1fa depth 1fd\relax x % \ascender \descender
> x\vrule height 1sh depth 1sd\relax x % \strutht \strutdp
> x\vrule height 1fc depth 0pt\relax x % \capheight
> \stopTEXpage
>
> you can also run s-sys
depth 0pt\relax x % \capheight
\stopTEXpage
you can also run s-system-units.mkxl and get a unit map
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
On 8/15/2023 10:54 PM, Pablo Rodriguez wrote:
On 8/15/23 22:16, Hans Hagen via ntg-context wrote:
On 8/15/2023 9:27 PM, Pablo Rodriguez wrote:
[...]
I wonder whether we could have (current) frame width and height as unit.
we can have
fw fh fo lw (width height offset linewidth)
but keep
On 8/15/23 22:16, Hans Hagen via ntg-context wrote:
> On 8/15/2023 9:27 PM, Pablo Rodriguez wrote:
>> [...]
>> I wonder whether we could have (current) frame width and height as unit.
> we can have
>
>fw fh fo lw (width height offset linewidth)
>
> but kee
body) font size
tw : (layout) text width
th : (layout) text height
hs : (current) hsize
vs : (current) vsize
cd : (when set) column distance
cw : (when set) column width
cx : combination cell width
uu : user unit (\METAFUN)
Many thanks for the new release, Hans.
I wonder whether we could have
font size
> tw : (layout) text width
> th : (layout) text height
> hs : (current) hsize
> vs : (current) vsize
> cd : (when set) column distance
> cw : (when set) column width
> cx : combination cell width
> uu : user unit (\METAFUN)
Many thanks for the new release, Hans.
I wo
20xx with xx being a (sort
of) unit, one can do the same in tex. Think of
\newdimension \MyUnitA \MyUnitA 1.23pt
\pushoverloadmode % just in case
\newuserunit\MyUnitA ua % binds the unit to the variable
\popoverloadmode
x\hskip 10ua\relax x
The units starting with 'u' are considered user
ha un
relleu: se'n van 2 i en vénen 3 \item La tripulació resultant es queda durant
5 dies més \item Tots els astronautes tornen. L'estació espacial queda buida
\stopitemize \par Els bastarà el menjar que s'enduen al principi si sabem que
quatre astronautes mengen en promig 20 kg per dia? \st
minuts. Quant tardaria aquesta
persona per anar a Inca? Quan dugui 10 minuts després de partir, a quina distÃ
ncia estarà ? \\par \\bigskip Dades necessà ries: \\startitemize [a, packed]
\\item Distà ncia Palma-Campos: $38,7 \\unit {kilo meter}$ \\item Distà ncia
Palma-Inca: $33,4 \\unit
Xavier B. schrieb am 13.08.2023 um 23:19:
Thanks, Wolfgang.
You are referring to this [https://wiki.contextgarden.net/Command/_unit]
Yes, the \unit command works out of the box without the need to load a
module.
Wolfgang
since a few years a built-in \unit command which
made the module obsolete.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https
WRT to funny units consider this thread (in German):
https://ruhrpott.social/@Matze/110812742577889798
Matze wrote:
I read the 'as big as a song thrush' as a size and I find that we should
set 'song thrush' as a standard unit for 20-22 cm.
Text problem:
Calculate how many square song thrush
length of an inchworm. My question is, what is the appropriate
unit for inching forward or inching along? Would this be one inch per
fortnight?
Alan
___
If your question is of interest to others as well, please
beers, so effectively that unit would then be a multiplier
of zero, but I'm sure you can find a usage for that.
I forgot to check what the pct was of the wine at the (as usual) huge
dinner but I can check the bottle I got from DT. Talking percentages,
maybe some high res percentage primitive
no real unit (just
like feet is no unit in tex but used in the message)
of course
concerning precission, indeed there was a real beautiful handcrafted
measuring device but as with much research one could sort of predict the
median outcome esp after the main sample was made beforehand
ds for, it seems to be country-dependent ;)
The problem with introducing the theodore is that it introduces another
'male name' unit while actually the new ones got 'female names' in order
to counter the didot and cicero (and dk although we considere that a
neutral unit), which was one of the proje
in reporting an overflow so no real unit (just
like feet is no unit in tex but used in the message)
an article is chicken-egg ... it goes into the tugboat (already checked
and prepared, read peer reviewed) but it is no big deal if the ctx
journal takes it afterwards (plenty of time
On 5/7/2023 2:10 AM, skyhorse--- via ntg-context wrote:
Hans Hagen via ntg-context wrote:
..
Oh, so a bug, I'll fix the message. Not really a unit but then, feet
is also not one.
That is incorrect. Feet is an establish and proper unit of measurement, which
consists of 12 inches
= 422042sp
but for a real unit you need to adapt the original engine and that will
not happen because it's in bug fix only mode.
Anyway, you can try it in lmtx:
\startTEXpage[offset=1dk]
\number\dimexpr1dk
\stopTEXpage
As introduced in:
https://www.tug.org/TUGboat/tb42-3/tb132hagen-dk.pdf
Like
On Sat, 06 May 2023 16:10:31 -0800
skyhorse--- via ntg-context wrote:
>
>
> Hans Hagen via ntg-context wrote:
> >..
> > Oh, so a bug, I'll fix the message. Not really a unit but then, feet
> > is also not one.
> >
>
> That is incorrect
Hans Hagen via ntg-context wrote:
>..
> Oh, so a bug, I'll fix the message. Not really a unit but then, feet
> is also not one.
>
That is incorrect. Feet is an establish and proper unit of measurement, which
consists of 12 inches. It is used by, at least, several hun
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
On Thu, May 04, 2023 at 10:01:25AM +0200, Hans Hagen via ntg-context wrote:
> These units can be used in the current upload. In a next upload the "19 feet
> max" message that tex issues when reaching a maximum will be adapted to a
> more realistic variant. (Actually, because t
articipate in the discussions of the committee of
four)
Well, the Polish oversight seemed to a agree and the team was awarded by
arthur who donated cute "Let's make TeX little again" hats, but more
about that later. The unit was applied by the main presenter when the
big cake got cut into pieces mea
is the most boring part.
>
> \starttext
>
> \startTEXpage[offset=1ts]
> Hello World!
>
> \the\dimexpr 1ts
>
> \the\dimexpr 1es
>
> \the\dimexpr 1eu
>
> \eufactor20
>
> \the\dimexpr 1eu
> \stopTEXpage
>
> \stoptext
>
On 5/2/2023 8:09 AM, Aditya Mahajan via ntg-context wrote:
Hi,
As I was testing circuitikz, I realized that the following don't work:
\unit{1V}
\unit{100 kΩ}
In phys-dim.lmt, we need to change line 467:
v = "volt",
to
V = "volt",
and perhaps add (not su
1es
\the\dimexpr 1eu
\eufactor20
\the\dimexpr 1eu
\stopTEXpage
\stoptext
The es (Edith) unit replaces the inch, and the ts (Tove) is one tenths
of than (just like we have cm and mm). The eu (European Unit) is an
adaptive one that defaults to 10 ts == 1es and can be multiplied
Hi,
As I was testing circuitikz, I realized that the following don't work:
\unit{1V}
\unit{100 kΩ}
In phys-dim.lmt, we need to change line 467:
v = "volt",
to
V = "volt",
and perhaps add (not sure if lua allows utf variable n
ore, we are confident that what we are
> doing is the way
> it should have been done when math was upgraded. Hopefully users
> will notice
> the improvements.
> \stopitem
>
> \startitem
> Math also means physics and units (that topic was brought up
&g
ully users will
> notice
>the improvements.
> \stopitem
>
> \startitem
>Math also means physics and units (that topic was brought up recently on
> the
>list by Gavin). Therefore, because we're in cleanup mode, we decided to
>eliminate some more. With \ISO\ no
avin). Therefore, because we're in cleanup mode, we decided to
eliminate some more. With \ISO\ now in place for a long time, we
are going to
ignore the existence of the inch as unit from now on. The unit will
probably
remain in the engine for nostalgic reasons, but it will no be
acce
Le Système international d'unités
>
> Maybe the french title is one of the reasons for the USA not picking up on
> these units? (So let me threaten once again to kick the "in" unit out of
> context.)
>
>> I believe that this point is essential,….
Alan and I will come
on these units? (So let me threaten once again to kick the "in" unit out
of context.)
I believe that this point is essential, regardless of history of use of
the \unit{} command. Non-standard use of units can be *tolerated* as
long as they do not conflict with the SI and do not impose no
On 3/14/2023 7:03 PM, Gavin via ntg-context wrote:
I’d like to better understand how the \unit{} command works and why those
choices were made. Some of the choices seem to be “asking for troubles,” but
perhaps they are essential for some users.
I wonder if Alan was using context when
On Tue, 14 Mar 2023 12:03:23 -0600
Gavin wrote:
> I’d really like one of the acceptable forms to be the form prescribed
> by Le Système international d'unités
I believe that this point is essential, regardless of history of use of
the \unit{} command. Non-standard use of units can be *tol
On Mar 14, 2023, at 10:08 AM, Alan Braslau via ntg-context
wrote:
> Right now, \unit{1 mm-1} and \unit{1 m m-1} give the same result:
> inverse millimeters (whereas the second should be m•m^{-1}…)
>
> Alan
Alan,
I’d like to better understand how the \unit{} command works a
nd “c”, but it doesn’t. Is
that intended?
Indeed, \unit{} should allow (and presently does not) K, C, etc.
I agree. I added the following lines to phys-dim.lua, following line 461
C = "coulomb",
K = "kelvin",
N = "newton",
This provided the desired cap
I wrote
> Perhaps we could use a \registershortcut command that does not get the
> “lower" treatment.
without seeing that Hans had already read my mind and provided:
\registerunitshortcut
[unit]
[C=coulomb]
That should work great.
Th
uish between the “C” and “c”, but it doesn’t. Is
>> that intended?
>
> Indeed, \unit{} should allow (and presently does not) K, C, etc.
I agree. I added the following lines to phys-dim.lua, following line 461
C = "coulomb",
K = "kelvin",
N = "ne
for, formally,
c should be 1/100
C should be Coulomb
k should be 1000
K should be Kelvin
n should be 10^{-9}
N should be Newton
m should be meter
M should be 10^6
(but m also means 10^{-3})
etc.
The problems arise as \unit{} presently accepts
Kelvin and kelvin
Newton and newton
Coulomb and c
On 3/13/2023 10:55 PM, Gavin wrote:
On Mar 13, 2023, at 3:44 PM, Hans Hagen via ntg-context
wrote:
On 3/9/2023 2:04 PM, Gavin via ntg-context wrote:
\startformula
\unit{3 meter} \qquad
\unit{6 Meter} \qquad
\unit{3 mEtEr} \qquad
\stopformula
Units with lowercase prefixes (c, k, n
ntly, when I register an upper case key (C=coulomb) it messes up
> the lower case prefix (“cm" gets typeset as C•m). I was expecting the
> parser to distinguish between the “C” and “c”, but it doesn’t. Is
> that intended?
Indeed, \unit{} should allow (and p
> On Mar 13, 2023, at 3:44 PM, Hans Hagen via ntg-context
> wrote:
>
> On 3/9/2023 2:04 PM, Gavin via ntg-context wrote:
>> \startformula
>> \unit{3 meter} \qquad
>> \unit{6 Meter} \qquad
>> \unit{3 mEtEr} \qquad
>> \stopformula
On 3/9/2023 2:04 PM, Gavin via ntg-context wrote:
\startformula
\unit{3 meter} \qquad
\unit{6 Meter} \qquad
\unit{3 mEtEr} \qquad
\stopformula
Units with lowercase prefixes (c, k, n).
\startformula
\unit{3cm} \qquad
\unit{6kg} \qquad
\unit{3ns} \qquad
\stopformula
Units
Hello list,
I continue to work with the \unit command, and found some behavior very
surprising. When I try to register units with capital letter names, it breaks
lowercase metric prefixes. For example, registering C=coulomb, K=kelvin and
N=newton breaks metric units cm, kg, and ns. The file
\starttext
\starttikzpicture
\draw (0, 0) circle (3cm);
\stoptikzpicture
\starttikzpicture
\startaxis
\addplot+[domain=0:360]
{sin(x)};
\stopaxis
\stoptikzpicture
\stoptext
ERROR:
tex error > tex error on line 15 in file ./TikZTest.tex: Illegal unit of
measure (pt inser
On 10/27/2022 8:11 AM, Max Chernoff via ntg-context wrote:
Hi Hans,
The unit scanner in LuaMetaTeX fails for any of the "true" dimensions.
With this test file:
\starttext
\vrule width 1truein height 1pt depth 0pt\relax
\vrule width 1in height 1pt depth
Hi Hans,
The unit scanner in LuaMetaTeX fails for any of the "true" dimensions.
With this test file:
\starttext
\vrule width 1truein height 1pt depth 0pt\relax
\vrule width 1in height 1pt depth 0pt\relax
\stoptext
I get this output:
tex error &
Hans,
I made a small mistake in the phys-dim.mkxl file I sent you. I removed a % at
the end of lines 469 and 485. Without the %, using alternative=text causes
extra space before the unit. A corrected phys-dim.mkxl is attached.
Gavin
phys-dim.mkxl
Description: application/applefile
units-spacing.tex, is for testing spacing
for \unit used in text, inline math, and display math. The second,
units-linebreaks.tex, tests line breaks when \unit. is used in text or in
inline math. Line breaks were not my primary interest, but Max and Alan were
quite interested. My proposed fixes for s
On 10/13/2022 1:52 PM, Gavin via ntg-context wrote:
Hi Oli,
Thank four your effort. I found out, that the following definition of a new
unit, i called it SI, results also in a correct spaceing in the math
environment:
\defineunit[SI][alternative=text]
It seems, that the option alternative
On Wed, 12 Oct 2022 21:14:52 -0600
Gavin wrote:
> As a recovering string theorist, I cannot help but speculate that
> this rule extends to spherical coordinates in any number of
> dimensions. However, if you don’t want the space, you can use
> 135\unit{℃}, which does not add a spac
Hi Oli,
> Thank four your effort. I found out, that the following definition of a new
> unit, i called it SI, results also in a correct spaceing in the math
> environment:
>
> \defineunit[SI][alternative=text]
>
> It seems, that the option alternative=text solves the p
Hi Gavin
Thank four your effort. I found out, that the following definition of a new
unit, i called it SI, results also in a correct spaceing in the math
environment:
\defineunit[SI][alternative=text]
It seems, that the option alternative=text solves the problem with no spaces
between value
Hi Alan
> On Oct 12, 2022, at 5:55 PM, Alan Braslau via ntg-context
> wrote:
>
> \unit{135℃} adds a space after the digits 135.
> I do not believe that this is correct
> (for ℃ is *not* a "real" unit, unlike \unit{408.15 K} which *is* a real
> unit).
According
ntentional?
>
> I believe that that is intentional. From the earlier email:
>
>> removed an overzealous backspace before division symbols.
>
> This new spacing looks much more even to me, especially around the
> exponents.
It was intentional. I didn’t add space. I removed a
Further \unit question(s):
\unit{135℃} adds a space after the digits 135.
I do not believe that this is correct
(for ℃ is *not* a "real" unit, unlike \unit{408.15 K} which *is* a real
unit).
Also,
\unit{135°C} drops the "C". Is this a parsing bug?
Related,
\unit{90°} does n
Hi Gavin,
On Wed, 2022-10-12 at 15:54 -0600, Gavin wrote:
> Hi Max, Alan, Bruce, Hans, et.al
>
> I solved my four issues with \unit spacing. In the process, I
> prevented unwanted line breaks and removed an overzealous backspace
> before division symbols. Below is a MWE
On 2022-10-12 17:54, Gavin via ntg-context wrote:
Hi Max, Alan, Bruce, Hans, et.al
I solved my four issues with \unit spacing. In the process, I prevented
unwanted line breaks and removed an overzealous backspace before division
symbols. Below is a MWE that shows all of these issues, as well
Hi Max, Alan, Bruce, Hans, et.al
I solved my four issues with \unit spacing. In the process, I prevented
unwanted line breaks and removed an overzealous backspace before division
symbols. Below is a MWE that shows all of these issues, as well as pictures of
the result with the unmodified phys
Hi List,
I am trying to improve the spacing produced by the \unit command. I have solved
three of my four issues by modifying phys-dim.mkxl, but the fourth issue has me
stumped. Consider this example:
\showmakeup[mathglue] \mathspacingmode=1
\starttext
\startformula
\unit{1.23e5 kg m^2/s^2
. Maybe it uses unbreakable
> spaces, maybe not. I would never use it unless it could be configured
> to only use nonbreakable spaces.
The current behaviour doesn't break the unit from the number, but it
does split the scientific notation.
This test file:
\starttext
\hsize=0
On Sat, 8 Oct 2022 11:59:04 -0600
Gavin via ntg-context wrote:
> I’m trying to fix four issues:
> - No space between the number and the following units. Should be a
> thin space.
> - No space between the units and the following symbol (+ and =
> above). Should be appropriate “bin" or “rel"
Hi list,
I made a small example with all of the issues I am trying to fix for the \units
command. The first formula below uses the \unit command, but produces strange
spacing. The second formula produces the desired spacing, without using the
\unit command.
\showmakeup[mathglue
Hi list,
I have been trying to understand the workings of the \unit command, which is
producing strange spacing in math mode. In an effort to be more systematic, I
began by investigating the related \digit command. \digit works well in text,
but in math mode the comma separators produce
> On 25 Sep 2022, at 14:30, Gavin via ntg-context wrote:
>
> Hello list,
>
> I have a few questions about space produced by the unit command. Consider
> this MWE
>
> \starttext
> \unit{3.00e8 kg m/s}
>
> $\unit{3.00e8 kg m/s}$
> \stoptext
>
>
On 9/25/2022 5:29 PM, Gavin via ntg-context wrote:
Hi Hans,
I also just noticed that the space between the number and the unit is missing
when I typeset with ConTeXt ver: 2022.09.11 20:44 LMTX fmt: 2022.9.25. This
space was present in with the ConTeXt version I was using earlier, from
Hi Hans,
I also just noticed that the space between the number and the unit is missing
when I typeset with ConTeXt ver: 2022.09.11 20:44 LMTX fmt: 2022.9.25. This
space was present in with the ConTeXt version I was using earlier, from a
couple months ago. Thanks for putting it on the math todo
On 9/25/2022 3:30 PM, Gavin via ntg-context wrote:
Hello list,
I have a few questions about space produced by the unit command. Consider this
MWE
\starttext
\unit{3.00e8 kg m/s}
$\unit{3.00e8 kg m/s}$
\stoptext
The dot between “kg” and “m” has different spacing depending on whether
Hello list,
I have a few questions about space produced by the unit command. Consider this
MWE
\starttext
\unit{3.00e8 kg m/s}
$\unit{3.00e8 kg m/s}$
\stoptext
The dot between “kg” and “m” has different spacing depending on whether the
\unit command is in text or math mode. I think
> 1. I want the baseline grid to evenly (vertically) divide the text
>> > area, but my code produces a smaller height of the first line and an
>> > additional space at the bottom.
>>
>> You did not set footerdistance to zero. So, that takes up some space.
&g
> 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.
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]{}
code produces a smaller height of the first line and an
> > additional space at the bottom.
>
> You did not set footerdistance to zero. So, that takes up some space.
>
> > 2. The number of columns is 21.5, that is the first column is 0.5
> units
> > wide and the rest are
y) divide the text
> area, but my code produces a smaller height of the first line and an
> additional space at the bottom.
You did not set footerdistance to zero. So, that takes up some space.
> 2. The number of columns is 21.5, that is the first column is 0.5 units
> wide and the re
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
on my previous question about Jean-Luc
>> > Doumont and his grid layouts. This time I have concrete questions. I
>> > reverse engineered his slide (slide_grid_overlay.pdf). All his units
>> are
>> > based on inches, because the inch is an integer multiple (72) of the
&
ion on my previous question about Jean-Luc
> > Doumont and his grid layouts. This time I have concrete questions. I
> > reverse engineered his slide (slide_grid_overlay.pdf). All his units are
> > based on inches, because the inch is an integer multiple (72) of the TeX
> >
are
based on inches, because the inch is an integer multiple (72) of the TeX
point. His base unit is 0.1in. I tried implementing the layout first,
but the pdf dimensions do not match the ones I set up. For example the
width should be 8 inches, but the pdf is over 11 inches wide. I wish to
shut off all
point. His
base unit is 0.1in. I tried implementing the layout first, but the pdf
dimensions do not match the ones I set up. For example the width should be
8 inches, but the pdf is over 11 inches wide. I wish to shut off all
margins and similar things and only have a text area with an offset of
0.2in
the grains contain,
> one has different amount of the real stuff. If one measures the volume of
> the grains, then according how compressed they are, the amount of the
> grains may be different… (at some point there was a law which stated that
> when a unit vessel of grains was to
stuff. If one measures the volume of the grains,
then according how compressed they are, the amount of the grains may be
different… (at some point there was a law which stated that when a unit vessel
of grains was to be sold, the seller should struck the bottom of the vessel on
a table three times
, the amount of the grains may be
different… (at some point there was a law which stated that when a unit vessel
of grains was to be sold, the seller should struck the bottom of the vessel on
a table three times and then refill again sthe vessel for it to be full).
The measure of the distan
1 - 100 of 694 matches
Mail list logo
