Mojca Miklavec wrote:
Dear Bernhard others,
Thanks a lot for reporting the problem.
Please wait for a fix from Hans or (in case that you need to update
for some reason) first disable updating stuff in bin (comment out a
line in first-setup) and then copy the old mtxrun from
Hello,
I see that context minimals is at 2010-06-05 version, hovewer git repo
[1] is last updated on 2010-05-29.
http://contextgarden.wordpress.com/2009/07/29/news-from-the-git-repository/
Marius
___
If your
On 5-6-2010 10:07, Marius wrote:
Hello,
I see that context minimals is at 2010-06-05 version, hovewer git repo
[1] is last updated on 2010-05-29.
http://contextgarden.wordpress.com/2009/07/29/news-from-the-git-repository/
the repos updates at midnight (so, once per day)
Hans
On 5-6-2010 8:04, Taco Hoekwater wrote:
Mojca Miklavec wrote:
Dear Bernhard others,
Thanks a lot for reporting the problem.
Please wait for a fix from Hans or (in case that you need to update
for some reason) first disable updating stuff in bin (comment out a
line in first-setup) and then
? 2010?06?05? 10:56, Adam Fuller ??:
my initial post had a mistake: i meant to refer to the /Metafun/
manual, not the Metapost manual. that probably didn't help.
Actually, I know that you mean the /Metafun/ manual.
i guess what i should have said is, i know that pxy can give me the
bounding
Hello,
Please, advise me.
Is there a way to keep margin text and body text on the same line in the
following situation?
\define[0]\chorus{\startnarrower{\itx CHORUS}\stopnarrower}
\starttext
\chorus
\chorus
\inmargin{B}\chorus
\stoptext
Now B is above CHORUS, I want it to be exactly on
Hello all,
in the process of learning macro programming in context i encountered the
following problem (minimal example is attached):
when i have \setuphead[section][color={red}] the color key influences in a
strange way my „novice macro“ (see the text which should be black but is red).
Hello all,
in the process of learning macro programming in context i encountered the
following problem (minimal example is attached):
When i have \setuphead[section][color={red}] the color key influences in a
strange way my „novice macro“ (see the text which should be black but is red).
Bernhard Rosensteiner wrote:
Hello all,
in the process of learning macro programming in context i encountered the
following problem (minimal example is attached):
When i have \setuphead[section][color={red}] the color key influences in a strange way my „novice macro“ (see the text which
Vyatcheslav Yatskovsky (2010-06-05 14:25):
Hello,
Please, advise me.
Is there a way to keep margin text and body text on the same line in
the following situation?
\define[0]\chorus{\startnarrower{\itx CHORUS}\stopnarrower}
\starttext
\chorus
\chorus
\inmargin{B}\chorus
deleting the \def\Mycolor line does not help - same result.
best regards
Bernhard
Am 05.06.2010 um 14:34 schrieb Taco Hoekwater:
Bernhard Rosensteiner wrote:
Hello all,
in the process of learning macro programming in context i encountered the
following problem (minimal example is
Am 05.06.2010 um 11:04 schrieb Hans Hagen:
On 5-6-2010 8:04, Taco Hoekwater wrote:
Mojca Miklavec wrote:
Dear Bernhard others,
Thanks a lot for reporting the problem.
Please wait for a fix from Hans or (in case that you need to update
for some reason) first disable updating stuff in
Bernhard Rosensteiner wrote:
deleting the \def\Mycolor line does not help - same result.
No, that would definitely not help. Your problem was not the
definition, but that you never actually called the macro.
You should put the definition back, and add \Mycolor to the
\OpticalTest macro,
Hi!
\dodosetreference is not defined, but \dododosetreference is defined twice
in strc-ref.mkiv. This breaks \pagereference, hence t-fixme. I think that
the first definition should be replaced with \def\dodosetreference.
On Saturday 05 June 2010 15:29:06 Yury G. Kudryashov wrote:
Hi!
\dodosetreference is not defined, but \dododosetreference is defined twice
in strc-ref.mkiv. This breaks \pagereference, hence t-fixme. I think that
the first definition should be replaced with \def\dodosetreference.
Indeed,
Am 05.06.2010 um 15:04 schrieb Taco Hoekwater:
Bernhard Rosensteiner wrote:
deleting the \def\Mycolor line does not help - same result.
No, that would definitely not help. Your problem was not the
definition, but that you never actually called the macro.
You should put the definition
No, no, your idea is exactly what I missed! :) Thanks!
I somehow feel that this is not what you want:
\def\chorus#1{\startnarrower{\itx
CHORUS}\doiftext{#1}{\inmargin{#1}}\stopnarrower}
\starttext
\chorus{}
\chorus{B}
\stoptext
--
Best Regards,
Vyatcheslav Yatskovsky
Hi!
Are there any automatic unit test for ConTeXt distribution? At least the bug
with referenceformat can be catched using something like
context test
pdftotext test.pdf test.txt
diff test.txt test.txt-good
And the bug with broken footnote can be catched using just context test.
If there are
On Sat, Jun 5, 2010 at 17:13, Yury G. Kudryashov wrote:
If there are no, any objections against adding them, and testing before
releasing new beta?
No, just go on. Any volunteer with some ideas to start a project is welcome.
Mojca
On Fri, Jun 4, 2010 at 21:32, Hans Hagen wrote:
Keep in mind that as we're now in beta mode again, we also need luatex
0.60 and we will deviate from the tex live current.
Is the required luatex already available as a released beta or is it
only in trunk? Are we talking of 0.60.1 or higher?
Hi Yuri and Mojca,
As far as I am concerned, I have a little file named « basic-test.tex »
containing the lines below: eveytime I update the minimals (well… almost
everytime), before doing so, I proceed as follows:
1) I make a backup copy of my existing and working context-minimals
2) I run
On Sat, Jun 5, 2010 at 11:04, Hans Hagen pra...@wxs.nl wrote:
On 5-6-2010 10:07, Marius wrote:
Hello,
I see that context minimals is at 2010-06-05 version, hovewer git repo
[1] is last updated on 2010-05-29.
http://contextgarden.wordpress.com/2009/07/29/news-from-the-git-repository/
the
On Fri, 4 Jun 2010, Aditya Mahajan wrote:
Does
\setupmathematics[autopunctuation=no] % or yes
give better result? (Are you using MKIV or MKII)?
Aditya
\setupmathematics[autopunctuation=no] seems to fix the spaces before the
x, but ..., is still bit ugly. I'm using MkIV, sorry for not
yes we have. At next ctx meeting i will show something.(post from mobile sorry)
On 6/5/10, Yury G. Kudryashov ur...@ya.ru wrote:
Hi!
Are there any automatic unit test for ConTeXt distribution? At least the bug
with referenceformat can be catched using something like
context test
pdftotext
Hi,
I did a Lua application for ConTeXt, and now I wanted to adapt it to
work even LuaLaTeX.
On what needs to be careful? Compiling by LuaLaTeX specific messages
appear as if the Lua in LuaLaTeX didnt know some Lua commands (i.e.
split, find ).
On what needs to be careful generaly when
\starttext
\reference[test]{test}
\stoptext
Has the syntax of \reference changed?
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
Hi,
I am sending examples of functions:
The first function is functional in ConTeXt MKIV even LuaLaTeX.
-- Global variables for setup in library (it be used when glob. vars
Sep, Ld, Rd is not setting in main aplication):
UserCSVSeparator=';'
UserCSVLeftDelimiter=''
UserCSVRightDelimiter=''
On Sun, Jun 06, 2010 at 01:35:23AM +0200, Jaroslav Hajtmar wrote:
Hi,
I am sending examples of functions:
The first function is functional in ConTeXt MKIV even LuaLaTeX.
-- Global variables for setup in library (it be used when glob. vars
Sep, Ld, Rd is not setting in main aplication):
28 matches
Mail list logo
