Re: [NTG-context] getting new font variants to work

2010-06-03 Thread Bernhard Rosensteiner
Am 03.06.2010 um 13:52 schrieb Michael Murphy: Hi all, I'd like to get some new font variants defined, such as Medium, Semibold, etc. What I have so far is the following. \definealternativestyle[medium][\me][] \starttypescript [serif] [minionpro] ...

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Marco
Nobody who knows a solution? Marco ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage :

[NTG-context] status-of-update.lus

2010-06-03 Thread luigi scarso
Today first-setup.sh ended with status-of-update.lus instead of expected status-of-update.lua Is it correct ? -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki!

[NTG-context] URLs [Re: \hyphenatedurl and the '%' character]

2010-06-03 Thread rogutes
Rogutės Sparnuotos (2010-06-03 00:16): Hello, I defined \def\url[#1]{\hyphenatedurl{#1}} for URLs, because I find \useURL[][] \from[] inconvenient (there are ~30 URLs in my document and all of them unique). But \hyphenatedurl doesn't work with '%' (and '\%' gets printed

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Peter Münster
On Tue, Jun 01 2010, Marco wrote: \usemodule [simpleslides] \starttext \SlideTitle {My Topic} \startitemize \item First % Visible by default \item Second % Gray by default \item Third % Gray by default \stopitemize \stoptext Not gray, but white: \usemodule [simpleslides,

Re: [NTG-context] URLs [Re: \hyphenatedurl and the '%' character]

2010-06-03 Thread Otared Kavian
Hi Rogutés, I found two examples in my archives: plesae see below. I hope this will help… Best regards: OK %%% First one: from an answer by Hans to Mojca: %Mojca Miklavec wrote: %hack hack hack hack %I tried solutions with special patterns sveral times but the

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Marco
On Thu, 3 Jun 2010 15:46:17 +0200, Peter Münster pmli...@free.fr wrote: On Tue, Jun 01 2010, Marco wrote: \usemodule [simpleslides] \starttext \SlideTitle {My Topic} \startitemize \item First % Visible by default \item Second % Gray by default \item Third % Gray by

[NTG-context] OSFONTDIR

2010-06-03 Thread Mojca Miklavec
Dear Hans, Some time ago the following code was working. On Mac it seems to have no influence now (OSFONTDIR doesn't get fixed), but if I set it in environment to the same string, it works. local function check_configuration() -- not yet ok, no time for debugging now if os.env[OSFONTDIR] then

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Peter Münster
On Thu, Jun 03 2010, Marco wrote: ConTeXt ver: 2010.05.23 15:03 MKIV My version 2010.05.24 13:05, but I don't think, that this matters. I get exactly the same result as with my code. All items on one page, no steps. Perhaps your pdf-viewer does not support javascript. I use acroread

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Marco
My version 2010.05.24 13:05, but I don't think, that this matters. I also don't think so. I get exactly the same result as with my code. All items on one page, no steps. Perhaps your pdf-viewer does not support javascript. I think that's the reason. I use acroread version 9.3.2 At

[NTG-context] links generated by \in don't work

2010-06-03 Thread Yury G. Kudryashov
Hi! I try the following with current beta: \setupinteraction[state=start] \starttext \placeformula[eq:test] \startformula 1=1 \stopformula \pagebreak \in[eq:test] \stoptext When I click on the link, nothing happens. The links generated by LaTeX+hyperref work in the same viewer (okular,

Re: [NTG-context] links generated by \in don't work

2010-06-03 Thread luigi scarso
On Thu, Jun 3, 2010 at 5:32 PM, Yury G. Kudryashov ur...@ya.ru wrote: Hi! I try the following with current beta: \setupinteraction[state=start] \starttext \placeformula[eq:test] \startformula        1=1 \stopformula \pagebreak \in[eq:test] \stoptext When I click on the link, nothing

[NTG-context] Script to automatically generate typescripts

2010-06-03 Thread Michael Murphy
Hi all, after spending many hours on a typescript only to accidentally delete it, I thought that there should be a better way to write them. Hence I wrote a python script to do just that. It started out as a private project, but I thought that since it might be useful to others, I'd make it

Re: [NTG-context] links generated by \in don't work

2010-06-03 Thread Yury G. Kudryashov
luigi scarso wrote: On Thu, Jun 3, 2010 at 5:32 PM, Yury G. Kudryashov ur...@ya.ru wrote: Hi! I try the following with current beta: \setupinteraction[state=start] \starttext \placeformula[eq:test] \startformula 1=1 \stopformula \pagebreak \in[eq:test] \stoptext When I click on

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Marco
On Thu, 3 Jun 2010 17:02:24 +0200, Peter Münster pmli...@free.fr wrote: [...] Perhaps your pdf-viewer does not support javascript. I use acroread version 9.3.2 Cheers, Peter After short research I found out that most pdf readers don't support Java Script (so do xpdf and sumatra). So, this

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Alan BRASLAU
On Thursday 03 June 2010 19:13:32 Marco wrote: On Thu, 3 Jun 2010 17:02:24 +0200, Peter Münster pmli...@free.fr wrote: [...] Perhaps your pdf-viewer does not support javascript. I use acroread version 9.3.2 Cheers, Peter After short research I found out that most pdf readers

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Marco
On Thu, 3 Jun 2010 20:14:07 +0200, Alan BRASLAU alan.bras...@cea.fr wrote: After short research I found out that most pdf readers don't support Java Script (so do xpdf and sumatra). So, this is not really a portable solution. Any hints for achieving the same result in a portable way

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread taco
Marco wrote: A (universal) solution would be to adapt \StartSteps\StopSteps to generate multiple PAGES that would be progressively filled. That would be the solution I am looking for. But it seems not yet to exist. \usemodule[pre-50] Same interface as pre-60, but using pages (and a bit

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Marco
On Thu, 03 Jun 2010 20:50:33 +0200, taco t...@elvenkind.com wrote: Marco wrote: A (universal) solution would be to adapt \StartSteps\StopSteps to generate multiple PAGES that would be progressively filled. That would be the solution I am looking for. But it seems not yet to exist.

Re: [NTG-context] Slides: uncover things piecewise

2010-06-03 Thread Peter Münster
On Thu, Jun 03 2010, Marco wrote: The first item is placed correctly on the first page. The second item is misplaced, it's also on the first page and (you're right Taco) a paragraph is superfluously introduced. The third item is placed correctly, after the second. You can also look here:

Re: [NTG-context] Script to automatically generate typescripts

2010-06-03 Thread Vyatcheslav Yatskovsky
Hi, Looks very impressive. A lot of code ) Is it usable under Windows? Never run Python scripts before. Hi all, after spending many hours on a typescript only to accidentally delete it, I thought that there should be a better way to write them. Hence I wrote a python script to do just that.

Re: [NTG-context] Script to automatically generate typescripts

2010-06-03 Thread Michael Murphy
On 03/06/2010 23:33, Vyatcheslav Yatskovsky wrote: Hi, Looks very impressive. A lot of code ) Is it usable under Windows? Never run Python scripts before. Hi all, after spending many hours on a typescript only to accidentally delete it, I thought that there should be a better way to write

[NTG-context] Please fill out the following form

2010-06-03 Thread Michael Saunders
I was creating a document with many hyperlinks and tooltips, and everything was working, until it reached a certain size. Two strange behaviors began: 1. At the top of Adobe Reader I get a purple band that says Please fill out the following form... 2. Tooltips no longer appear at the first