Am Tue, 21 Dec 2010 18:37:12 +0100 schrieb Thomas Schmitz:
I know that with the font fallback mechanism, it's
trivial to change fonts for unicode ranges,
Do you know where (roughly) the code for the fallback is? I would
like to know how it work.
--
Ulrike Fischer
On Wed, 22 Dec 2010 11:02:03 +0100
Ulrike Fischer ne...@nililand.de wrote:
Do you know where (roughly) the code for the fallback
is? I would
like to know how it work.
--
You mean where it is actually defined in the core files? A
quick grep for fontfallback shows that it's in
Mojca, Hans, Wolfgang and all other users:
1. Get minimals, I used context-setup-mswin
2. Follow setup install for windows.
3. Using Winedt:
a. go to options, execution modes
b. in full executeables...enter full path where you installed minimals
c. Now in TeX\MikTeX\Options...Add a search root
On 22-12-2010 12:22, barndog1...@gmail.com wrote:
Mojca, Hans, Wolfgang and all other users:
1. Get minimals, I used context-setup-mswin
2. Follow setup install for windows.
3. Using Winedt:
a. go to options, execution modes
b. in full executeables...enter full path where you installed minimals
On 21-12-2010 1:04, Marco Pessotto wrote:
Is this going to happen or there are serious reasons not to have it as
default?
The problem with automatisms is that they need a lot of testing and have
the disadvantage that when one is unaware of it and doesn't want its
effects it can take ages to
Hans Hagen pra...@wxs.nl writes:
On 21-12-2010 1:04, Marco Pessotto wrote:
Is this going to happen or there are serious reasons not to have it as
default?
The problem with automatisms is that they need a lot of testing and
have the disadvantage that when one is unaware of it and doesn't
On Tue, Dec 21 2010, Bill O'Connor wrote:
Shouldn't that be:
\starttext
X\vcenter{\hbox{X}}{X}
X\vcenter{\hbox{X}}{X}
\showboxes
\stoptext
No, it shouldn't.
Peter
--
Contact information: http://pmrb.free.fr/contact/
2010/12/21 Wolfgang Schuster schuster.wolfg...@googlemail.com
For mkii you need the texnansi encoding for the fonts, mkiv has no problems
with \type
but haven’t told which engine you use neither did you provide a full
example.
Run this and you will get the correct output for \type:
Am 21.12.2010 um 13:32 schrieb Hans Hagen:
On 21-12-2010 12:31, Wolfgang Schuster wrote:
With the new beta you can add
\defineconversion[continued][{},{ (continued)},{ (continued)},{
(continued)},{ (continued)},{ (continued)}]
\setupfloatsplitting[conversion=continued]
to your
On 22-12-2010 1:35, Wolfgang Schuster wrote:
Am 21.12.2010 um 13:32 schrieb Hans Hagen:
On 21-12-2010 12:31, Wolfgang Schuster wrote:
With the new beta you can add
\defineconversion[continued][{},{ (continued)},{ (continued)},{
(continued)},{ (continued)},{ (continued)}]
On 22-12-2010 1:01, Marco Pessotto wrote:
Is it correct? (I've looked in the source, but just to be sure).
yes
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt |
Hi Contexters!
Consider the following snippet in a cld-file:
context.framed({frame=on,width= 5cm},
function() ... end
)
This works fine so far. I would like to pass the width of the framed text in
terms of a fraction of the textwidth e.g. .25\textwidth. How must this be coded?
KR
Willi
Answering myself:
width= number.todimen(0.25*tex.dimen.textwidth)
On 22 Dec 2010, at 14:10, Willi Egger wrote:
Hi Contexters!
Consider the following snippet in a cld-file:
context.framed({frame=on,width= 5cm},
function() ... end
)
This works fine so far. I would like to pass the
Hi again,
hm, I need to pass a \setupTABLE command ...
context.setupTABLE({column}{each}{width=number.todimen(.041*tex.dimen.textwidth),align=flushright,offset=1pt})
However this does not work. How must this be done?
KR
Willi
On Wed, Dec 22, 2010 at 2:59 PM, Willi Egger w.eg...@boede.nl wrote:
Hi again,
hm, I need to pass a \setupTABLE command ...
context.setupTABLE({column}{each}{width=number.todimen(.041*tex.dimen.textwidth),align=flushright,offset=1pt})
Are you sure of this syntax ?
--
luigi
On Wed, Dec 22 2010, Willi Egger wrote:
context.setupTABLE({column}{each}{width=number.todimen(.041*tex.dimen.textwidth),align=flushright,offset=1pt})
context.setupTABLE({column}, {each}, {width=...
(not tested...)
Peter
--
Contact information: http://pmrb.free.fr/contact/
Am Wed, 22 Dec 2010 12:38:49 +0100 schrieb Hans Hagen:
1. Get minimals, I used context-setup-mswin
2. Follow setup install for windows.
3. Using Winedt:
a. go to options, execution modes
b. in full executeables...enter full path where you installed minimals
c. Now in
Hi Peter,
thanks for the tip, indeed the {} must be separated by , - this works!
Willi
On 22 Dec 2010, at 15:07, Peter Münster wrote:
On Wed, Dec 22 2010, Willi Egger wrote:
context.setupTABLE({column}{each}{width=number.todimen(.041*tex.dimen.textwidth),align=flushright,offset=1pt})
Hi Luigi,
deducing from what is written in the cld-manual it is at least the direction of
looking...
Willi
On 22 Dec 2010, at 15:03, luigi scarso wrote:
On Wed, Dec 22, 2010 at 2:59 PM, Willi Egger w.eg...@boede.nl wrote:
Hi again,
hm, I need to pass a \setupTABLE command ...
As usual Ulrike is correct. I got context beta working BUT I LOST lucida
math even though lucida text is working. as an aside bibliography IS sorted
on author which does NOT work in the normal MikTeX release
just hacking my way through in my meager attempt to get a book published
which was
On 22-12-2010 4:20, Willi Egger wrote:
Hi Peter,
thanks for the tip, indeed the {} must be separated by , - this works!
more precise: multiple arguments to a function
f({1}{2}) is no valid lua, while f({1},{2}) is
-
On Wed, Dec 22, 2010 at 4:32 PM, Hans Hagen pra...@wxs.nl wrote:
On 22-12-2010 4:20, Willi Egger wrote:
Hi Peter,
thanks for the tip, indeed the {} must be separated by , - this works!
more precise: multiple arguments to a function
f({1}{2}) is no valid lua, while f({1},{2}) is
that's
Am 22.12.2010 um 16:28 schrieb barney schwartz:
As usual Ulrike is correct. I got context beta working BUT I LOST lucida math
even though lucida text is working. as an aside bibliography IS sorted on
author which does NOT work in the normal MikTeX release
Give us more information, this
Am 22.12.2010 um 13:13 schrieb Philipp A.:
i now found out that the simplefonts module cuses this:
I’ll fix this, \setmonofont use the wrong font features.
Wolfgang
___
If your question is of interest to others
Hello all,
I have problem with PDF generating module documentation.
When I use command:
context --autopdf --ctx=x-ldx.ctx t-fancybreak.mkiv,
then is all right, but if I use commands:
context --autopdf --ctx=s-mod.ctx --nomode t-fancybreak.mkiv
context --autopdf --ctx=s-mod.ctx t-fancybreak.mkiv
Am 22.12.2010 um 17:29 schrieb Jaroslav Hajtmar:
Hello all,
I have problem with PDF generating module documentation.
When I use command:
context --autopdf --ctx=x-ldx.ctx t-fancybreak.mkiv,
The x-ldx.ctx file is to produce documentation from lua files.
then is all right, but if I use
2010/12/22 barndog1...@gmail.com:
et voila you now have Context latest beta running under MikTeX via
Winedt!
Why do you use Winedt with ConTeXt? Winedt is shareware and doesn't
really do Unicode.
Best
Martin
On Wed, Dec 22, 2010 at 23:43, Martin Schröder wrote:
2010/12/22 barndog1...@gmail.com:
et voila you now have Context latest beta running under MikTeX via
Winedt!
Why do you use Winedt with ConTeXt? Winedt is shareware and doesn't
really do Unicode.
I'm not Barney, but I use a
28 matches
Mail list logo
