On Thu, Apr 26, 2012 at 11:08 PM, Willi Egger cont...@boede.nl wrote:
It is not possible to make cells spanning more than one column. This is
related to the fact that the cells are on a grid. It is also not possible to
have cells on e.g. half way down/left/right.
Oh well, I can live with
On Thu, Apr 26, 2012 at 1:27 PM, Marco net...@lavabit.com wrote:
You can adjust the distance indirectly with changing the distance
between the cells:
\setupFLOWcharts [dx=8ex, dy=4em]
Ah, that naming does make sense, now that I think of it. It seems that
I'm still (re)learning to think of
On 8-5-2012 08:20, Mari Voipio wrote:
Now, to implementing all this new knowledge in Chart 2.
and after that comes chart 3:
\usemodule[chart]
\startFLOWchart[ABC]
\startFLOWcell
\name{A}
\location{1,1}
\destination{whatever:A}
\text{A}
Yusuke-san,
Thank you too for writing. It seems like one or the other so far, platex
does not give good western style characters but is great for Japanese, which
the other option, simplefonts gives good western characters and according to
you bad Japanese charac
ters. Is it the font or
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words and \WORD macros. But I can’t find a
way to properly combine them with the “style” parameter of
highlights: it breaks frames and enumerations. Example:
Dear Henman-san,
So a question might be can ptex be used with ConTeXt? as the the engine?
Would this wowrk?
With ConTeXt mark II (not mark IV), you can use ptex as the engine. Such
support is included in W32TeX. (I don't know whether TeXLive 2011
supports it.) You can type `texexec
Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words and \WORD macros. But I can’t find a
way to properly combine them with the “style” parameter of
highlights: it breaks frames and
On 7-5-2012 14:54, d.henman wrote:
Yusuke-san,
Thank you too for writing. It seems like one or the other so far, platex
does not give good western style characters but is great for Japanese, which
the other option, simplefonts gives good western characters and according to
you bad
On 2012-05-08 11:07, Wolfgang Schuster wrote:
Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words and \WORD macros. But I can’t find a
way to properly combine them with the “style”
I am attaching five test files including Fig. 3.1, 3.2, 3.3
in http://www.w3.org/TR/jlreq/ . All files but
Fig3_1-different-linebreaks.txt, the positions of linebreaks
are the same as the examples. In writing a manuscript,
we will make linebreaks depending on its context, then
the same results
On 8-5-2012 11:18, Philipp Gesang wrote:
On 2012-05-08 11:07, Wolfgang Schuster wrote:
Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words and \WORD macros. But I can’t find a
way to properly
Am 08.05.2012 um 13:17 schrieb Hans Hagen:
On 8-5-2012 11:18, Philipp Gesang wrote:
On 2012-05-08 11:07, Wolfgang Schuster wrote:
Am 08.05.2012 um 10:35 schrieb Philipp Gesang:
Dear listmates,
I rely on automated uppercasing and lowercasing a lot and I’m
very happy with the \words
On 2012-05-08 13:28, Wolfgang Schuster wrote:
It would be also useful to change the following line in font-pre.mkiv to use
\setcharacterchasing instead of \WORD (won’t work anymore when you remove
\groupedcommand from the \WORD as written in the comments in typo-cap.mkiv)
On 8-5-2012 13:28, Wolfgang Schuster wrote:
The next version will support named casing:
WORD
word
Word
Words
capitals cap
Capitals Cap
none
random
It would be also useful to change the following line in font-pre.mkiv to use
\setcharacterchasing instead of \WORD (won’t work anymore when you
Just a remark: for cjk one can best use the mkiv feature to combine
fonts; there are probably some examples of korean fonts mixed with e.g.
palatino or times in the email archive.
Here is a sample typescript file for mixed Korean and English fonts suggested
by Hans.
Using this file, I
Hi there,
I'm afraid that footnote numbering in body text is wrong in latest beta
(the bug was also in the two previous betas).
Here you have a sample that shows the bug:
\setupnotation[footnote][number=no]
\setuphead[chapter][number=no]
\starttext
\chapter{First chapter}
one\footnote{two}
Hi, Hans,
A question for Yusuke: what script name should we use?
It is a difficult question. In Chinese or Korean case,
what they have chosen? In Japanese, we need to prepare a
lot of characters for font set if they complete Adobe-Japan-1.5
or something. So, some font vendors publish the
Abe-san,
thanks for the suggestion. I will do the reading as you suggested. It's
always good to have backup for now, in case a clean method can't be worked out
with Mark IV right away.
Regards
ABE Noriyuki aben...@math.sci.hokudai.ac.jp wrote:
Dear Henman-san,
So a question might
Hi Yusuke
A question for Yusuke: what script name should we use?
It is a difficult question. In Chinese or Korean case,
what they have chosen? In Japanese, we need to prepare a
lot of characters for font set if they complete Adobe-Japan-1.5
or something. So, some font vendors publish the
On 2012-05-05 Hans Hagen pra...@wxs.nl wrote:
This code fails:
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
draw textext(some text) ;
\stopMPcode
\startMPcode{mympinstance}
draw textext(some text) ;
\stopMPcode
\stoptext
Marco
Hi,
A nice candidate for wikification:
\setupbodyfont[dejavu]
\setupbodyfontenvironment
[default]
[smallsized=1.25,
mediumsized=1.5,
largesized=2.0]
\definefontsize[smallsized]
\definefontsize[mediumsized]
\definefontsize[largesized]
\starttext
\setuphead[chapter]
On 8-5-2012 19:01, Marco wrote:
On 2012-05-05 Hans Hagenpra...@wxs.nl wrote:
Did I?
This code fails:
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
draw textext(some text) ;
\stopMPcode
\startMPcode{mympinstance}
draw textext(some
On 2012-05-08 Hans Hagen pra...@wxs.nl wrote:
On 8-5-2012 19:01, Marco wrote:
On 2012-05-05 Hans Hagenpra...@wxs.nl wrote:
Did I?
My bad ;)
This code fails:
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
draw textext(some text) ;
I do not get lowercase greek letters on the itemize as should happen with
symbol setup g.
A minimal example, showing the demise of lowercase greek against succes for
uppercase.
\starttext
\startitemize[g]
\startitem nr 1\stopitem
\startitem nr 2\stopitem
\startitem nr 3\stopitem
\startitem nr
On 8-5-2012 19:19, Marco wrote:
On 2012-05-08 Hans Hagenpra...@wxs.nl wrote:
On 8-5-2012 19:01, Marco wrote:
On 2012-05-05 Hans Hagenpra...@wxs.nl wrote:
Did I?
My bad ;)
This code fails:
\defineMPinstance [mympinstance] [metafun] [textcolor=red]
\starttext
\startMPcode
On 2012-05-08 Hans Hagen pra...@wxs.nl wrote:
ok, can you add this to cont-new.mkiv (after \unprotect):
\def\m_meta_colo_initializations{%
vardef OverlayLineColor=\MPcolor{\overlaylinecolor} enddef;
vardef OverlayColor=\MPcolor{\overlaycolor} enddef;
}
That works.
As I've used
Am 08.05.2012 um 19:32 schrieb Meer, H. van der:
I do not get lowercase greek letters on the itemize as should happen with
symbol setup g.
A minimal example, showing the demise of lowercase greek against succes for
uppercase.
It’s a font problem because MkII took the greek letters from
On 8-5-2012 16:25, Pablo Rodríguez wrote:
Hi there,
I'm afraid that footnote numbering in body text is wrong in latest beta
(the bug was also in the two previous betas).
Here you have a sample that shows the bug:
\setupnotation[footnote][number=no]
\setuphead[chapter][number=no]
\starttext
Hey list,
Some of my textbackgrounds occupy more than one page and break part way
through them, as expected. Where their containing text is split at the
page break, I am finding that the frame is too close to the contents. So
I'd like to increase the white space of the bottom and top of the
29 matches
Mail list logo
