Am 14.02.2009 um 10:09 schrieb Wolfgang Schuster:
Hi Hans,
why is \setbuffer not defined as \long, I want to use it as part
of a macro and need it to allow paragraphs as content.
Can you change this?
TIA,
Wolfgang
Hi all,
I have to write a letter to a few dozens candidates in which some
parts are not identical. I may have the list of the persons, and the
changing part for each of them in a file (named for instance list-of-
candidates.tex) on which each line corresponds to one person and the
fields
Am 10.05.2009 um 14:32 schrieb Otared Kavian:
Hi all,
I have to write a letter to a few dozens candidates in which some
parts are not identical. I may have the list of the persons, and the
changing part for each of them in a file (named for instance list-
of-candidates.tex) on which each
Dear Wolfgang,
Many thanks! As usual you are clear and sharp…
Your code works and does exactly what I need… Moreover I learned from
it several clean tricks in order to use the way one can write macros
in ConTeXt.
I have just to understand different parts of the code in order to
wikify it.
Dear all,
Text in component files are not included in the attached example. I also put
the log
file in it. The log shows that the component files were found and complied but
their
texts were not present in the generated pdf file.
I'm not sure whether I did anything wrong in the example or
Wolfgang Schuster wrote:
Am 14.02.2009 um 10:09 schrieb Wolfgang Schuster:
Hi Hans,
why is \setbuffer not defined as \long, I want to use it as part
of a macro and need it to allow paragraphs as content.
Can you change this?
no need as \dosetbuffer is defined as \long and \setbuffer
Yue Wang wrote:
- It is ugly to produce a paragraph whose last line only consists one
Chinese character. In order to avoid that, tex82 programmers should
write very complicated macros. So many developers here tend to ignore
this problem. However, in LuaTeX, this is quite easy. It is simple to
Wei-Wei Guo wrote:
Dear all,
Text in component files are not included in the attached example. I also
put the log
file in it. The log shows that the component files were found and
complied but their
texts were not present in the generated pdf file.
I'm not sure whether I did anything wrong
On May 9, 2009, at 3:05 PM, Thomas A. Schmitz wrote:
maybe Hans can say which files are likely to be the culprit so I
can run a diff between these two versions?
most likely font-ini.mkiv
Hans
Thanks Hans, I'll see if I can find anything!
Thomas
OK, first result: if I simply put my old
Thomas A. Schmitz wrote:
On May 9, 2009, at 3:05 PM, Thomas A. Schmitz wrote:
maybe Hans can say which files are likely to be the culprit so I can
run a diff between these two versions?
most likely font-ini.mkiv
Hans
Thanks Hans, I'll see if I can find anything!
Thomas
OK, first
Hi all,
I have `onum=yes' in my font features and it works great. But how can
I type a capital number in this case? I want to use capital numbers
in pagenumbers.
Thanks!
Corsair Sun
--
There is no emotion; there is peace.
There is no ignorance; there is knowledge.
There is no passion; there
Am 10.05.2009 um 17:29 schrieb Wei-Wei Guo:
Dear all,
Text in component files are not included in the attached example. I
also put the log
file in it. The log shows that the component files were found and
complied but their
texts were not present in the generated pdf file.
I'm not sure
Dear context users,
at first a lot of warm thanks for help and comments on using
t-simpleslides.
On a different matter, I now have the following problem :
I do a lot of testing trying compiling my slides (using the following
command : context essai.tex). Sometimes, I get errors and an
interactive
Sometimes, I get errors and an
interactive prompt that I kill with either ctrl+C or ctrl+Z (at random).
You shouldn't do that. Type 'x' at the error prompt, it makes
(Lua)TeX terminate. Ctrl+C sometimes isn't enough to kill LuaTeX,
though I have no idea why;
I've also noticed something along those lines. I've also found that
CTRL+Z/C doesn't really exit the program --- there are stale processes
still lying around.
What I described is general, it tends to happen across big documents.
Is this a known problem?
� Broustet wrote:
Dear context
Thank you !
it's ok now.
Le dimanche 10 mai 2009 à 20:14 +0200, Arthur Reutenauer a écrit :
Sometimes, I get errors and an
interactive prompt that I kill with either ctrl+C or ctrl+Z (at random).
You shouldn't do that. Type 'x' at the error prompt, it
On a small example : ctrl+C works, ctrl+Z leaves unkillable (either -15
or -1) luatex and texlua process. kill -9 leaves zombies.
killing the parent shell clean everything.
Le dimanche 10 mai 2009 à 19:25 +0100, Mohamed Bana a écrit :
I've also noticed something along those lines. I've also
On a small example : ctrl+C works, ctrl+Z leaves unkillable (either -15
or -1) luatex and texlua process.
Again, that's because Ctrl+Z, in a normal Unix environment, only
suspends the process, it never kills it. Try kill -19 first (SIGCONT),
then kill -15 or -1.
You can try the following
Thomas A. Schmitz wrote:
On May 9, 2009, at 3:05 PM, Thomas A. Schmitz wrote:
maybe Hans can say which files are likely to be the culprit so I can
run a diff between these two versions?
most likely font-ini.mkiv
Hans
Thanks Hans, I'll see if I can find anything!
Thomas
OK, first
2009/5/10, Amaël Broustet cont...@amael.net:
killall luatex and kill -15 PID does nothing.
Don't use killall. Linux != Unix.
Best
Martin
___
If your question is of interest to others as well, please add an entry
Corsair wrote:
Hi all,
I have `onum=yes' in my font features and it works great. But how can
I type a capital number in this case? I want to use capital numbers
in pagenumbers.
can you be a bit more explicit?
to what extend smallcaps are implemented is font dependent
\mframed misbehaves under mkiv (latest minimals)
minimal example:
\setupcolors[state=start]
\starttext
\mframed[frame=off,background=color,backgroundcolor=yellow]{k_2 \propto \langle
N \rangle^{\alpha}}
\stoptext
- framed text, white background
(works correctly under mkii: no frame, yellow
\setupinteractionscreen[option=max] no longer works under mkiv.
Thanks,
Alan
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
On May 10, 2009, at 9:38 PM, Hans Hagen wrote:
how do you use rscale?
\definetypeface [] [rm] [serif] [times] [default]
\definetypeface [] [ss] [sans] [helvetica] [default] [rscale=5]
\starttext
\setupbodyfont[] \rm test \ss test
\stoptext
works ok
I think I have found
Hans Hagen 写道:
Text in component files are not included in the attached example. I
also put the log
file in it. The log shows that the component files were found and
complied but their
texts were not present in the generated pdf file.
I'm not sure whether I did anything wrong in the example
Wolfgang Schuster 写道:
Text in component files are not included in the attached example. I
also put the log
file in it. The log shows that the component files were found and
complied but their
texts were not present in the generated pdf file.
I'm not sure whether I did anything wrong in the
On Sun, May 10, 2009 at 09:44:58PM +0200, Hans Hagen wrote:
Corsair wrote:
Hi all,
I have `onum=yes' in my font features and it works great. But how can
I type a capital number in this case? I want to use capital numbers
in pagenumbers.
can you be a bit more explicit?
to what
27 matches
Mail list logo