Roman Schechtel wrote:
Hello from a new ConTeXt user!
I've read the wiki-page on how to separate input files into
a project structure (http://wiki.contextgarden.net/Project_structure)
and now I have the problem that:
- I can compile an individual component (resulting in a PDF)
- I also can
Hans Hagen wrote:
yeah, a nice job for the coming winter, in my just finished library
anex study annex attic annex music room -)
More I see style.pdf, more I like it (...about colors:with xpdf it's
not easy to read)
I'm sure that we need it : it will fill a hole.
For programmer ,we have
Hello,
I think this is due to the folder structure. When you copy everythin
into the same folder it works (at leat project and product must be in
the same folder).
I don't know if this is supposed to be this way.
Wolfgang
Taco Hoekwater schrieb:
Roman Schechtel wrote:
Hello from a
Greetings,
I think this is due to the folder structure. When you copy everythin
into the same folder it works (at leat project and product must be in
the same folder).
Thanks for the idea! Yes, now I get a PDF, even when the component
resides where it was.
/project.tex
/product.tex
Brooks Moses said:
(Andre: I'm sending this reply back to the ConTeXt list, because I think a
fair bit of my reply might be generally useful to other people who want to
try to convert LaTeX packages to ConTeXt. I hope that's ok!)
Yep. I just didn't want to contaminate the list with my
Mojca Miklavec wrote:
I'm sorry, I was first confused by this example:
\switchtobodyfont[10pt]\setupinterlinespace\page
\input tufte
\switchtobodyfont[10dd]\setupinterlinespace\page
\input tufte
% interlinespace remained the same for both pt and dd
which (for whatever reason) lead to
Hans Hagen wrote:
Concerning the 'construct a key' approach, how about the following:
- provide shapes for a single, double-wide, tripple-wide, tripple
height, enter-shape keys.
Wouldn't it be reasonable to just create these borders via MetaFun?
That way, I can have \key{\triangleleft
Christopher Creutzig wrote:
Hans Hagen wrote:
Concerning the 'construct a key' approach, how about the following:
- provide shapes for a single, double-wide, tripple-wide, tripple
height, enter-shape keys.
Wouldn't it be reasonable to just create these borders via MetaFun?
That way,
Taco Hoekwater wrote:
Those executabless are now part of the minimal distribution:
http://context.aanhet.net/context/install/linux64tex.zip
$uname -a
Linux stanley.log.net 2.6.11-6mdksmp #1 SMP Tue Mar 22 15:40:42 CET 2005
i686 Intel(R) Xeon(TM) CPU 3.00GHz unknown GNU/Linux
$ ldd
luigi.scarso wrote:
Taco Hoekwater wrote:
Those executabless are now part of the minimal distribution:
http://context.aanhet.net/context/install/linux64tex.zip
$uname -a
Linux stanley.log.net 2.6.11-6mdksmp #1 SMP Tue Mar 22 15:40:42 CET 2005
i686 Intel(R) Xeon(TM) CPU 3.00GHz unknown
Thomas A. Schmitz wrote:
Mojca,
I'm not sure I've understood all you're trying to do, but I feel kind
of responsible for the Greek.
Thank you very much, Thomas!
I took the polutonic/ancient Greek
basically from the Unicode names, but I left modern/monotonic Greek
alone because the
For those who use it: what are the main highlights of lgrind? I only
googled a bit, but I didn't install it yet, so I can't say anything
about it yet.
What do you think about idea of letting the code pass through vim? I
already asked about it, but here are also some preliminary results:
Mojca Miklavec wrote:
What do you think about idea of letting the code pass through vim? I
already asked about it, but here are also some preliminary results:
http://pub.mojca.org/tex/vim/fromlgrind/
Just to show that it's not that hard. I only deleted 70% of the
2html.vim and replaced one
Hi,
There is a new feature + manual, for those who love obscure mechanisms.
http://www.pragma-ade.com/general/manuals/xmanipulate.pdf
Even if you dislike manipulations ... the manual mixes iwona and the new
condensed latin modern monospace font.
The preprocess feature is only supported by
14 matches
Mail list logo
