From: Wouter Verheijen <wouter.verheijen@worldmail.nl>
Subject: beginner's questions
Date: Thu, 9 Nov 2000 17:51:17 +0100 [thread overview]
Message-ID: <20001109175117.A942@wouter.verheijen.nl> (raw)
Hi,
I am trying context at the moment, after experimenting somewhat with
LaTeX.
- Although I am Dutch, I have no problem at all with using the English
words (e.g. \starttext instead of \starttekst). I think this way, I
can avoid language conflicts. Do the Dutch people agree or is it
normal to use the dutch words. Most of my texts are in Dutch, so
the spelling and hypenating language should remain Dutch.
I did texexec --make en, but my standard language interface is still
nl. It only works with texexec --int=en. How do I specify the
default?
- The DVI files produced with context show up completely blank in
KDVI. They do work in Xdvi, and my Latex files always worked in Kdvi
as well. Who's to blame?
- Most of the work I plan to make with context are small (<20pages)
reports. Mostly text with some tables and pictures, and a few
graphs. Is context the program to handle this, or should I choose
latex? After a quick look at the docs, it seems context is easier to
do most things. Is this correct?
Thanks for your opinions!
--
Wouter Verheijen
wouter.verheijen@worldmail.nl
next reply other threads:[~2000-11-09 16:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 16:51 Wouter Verheijen [this message]
2000-11-09 17:20 ` Frans Goddijn
2000-11-09 17:54 ` Hans Hagen
2000-11-09 17:40 ` Hans Hagen
2000-11-09 19:25 ` Ed L Cashin
2000-11-11 17:34 ` siepo
2000-11-11 17:56 ` Frans Goddijn
2000-11-24 12:51 ` Christopher Tipper
2000-11-11 19:41 ` Berend de Boer
2000-11-12 11:34 ` siepo
2000-11-12 18:56 ` Denis B. Roegel
2000-11-13 9:37 ` Hans Hagen
2000-11-13 16:54 ` multi-column spread control (was Re: beginner's questions) Ed L Cashin
2000-11-13 17:17 ` Hans Hagen
2000-11-13 18:43 ` Ed L Cashin
2000-11-13 18:44 ` Ed L Cashin
2000-11-14 7:49 ` Hans Hagen
2000-11-14 13:27 ` Ed L Cashin
2000-11-14 14:13 ` Hans Hagen
2000-11-14 14:49 ` Ed L Cashin
2000-11-14 15:49 ` Hans Hagen
2000-11-14 16:45 ` Ed L Cashin
2000-11-14 17:12 ` Hans Hagen
2000-11-14 18:25 ` Ed L Cashin
2000-11-15 0:23 ` Hans Hagen
2000-11-15 1:15 ` Ed L Cashin
2000-11-15 17:20 ` voting & form design (was: multi-column spread control) Hraban
2000-11-14 21:51 ` multi-column spread control (was Re: beginner's questions) Denis B. Roegel
2000-11-15 0:20 ` Hans Hagen
2000-11-15 23:28 ` Denis B. Roegel
2000-11-19 19:31 ` Hans Hagen
2000-11-12 14:04 ` Documentation Tasks (was: " Hraban
2000-11-13 7:38 ` beginner's questions Hans Hagen
2000-11-13 21:26 ` siepo
2000-11-09 19:19 ` Berend de Boer
-- strict thread matches above, loose matches on Subject: below --
2002-09-27 21:14 Michael Na Li
2002-09-28 9:07 ` Michael Na Li
2002-09-28 9:35 ` Jens-Uwe Morawski
2002-09-29 6:38 ` Michael Na Li
2002-09-29 16:35 ` Henning Hraban Ramm
2002-09-30 8:11 ` Taco Hoekwater
[not found] <Hans Hagen's message of "Tue, 14 Nov 2000 18:12:11 +0100">
[not found] ` <Hans Hagen's message of "Tue, 14 Nov 2000 16:49:12 +0100">
[not found] ` <Hans Hagen's message of "Tue, 14 Nov 2000 15:13:29 +0100">
[not found] ` <Hans Hagen's message of "Tue, 14 Nov 2000 08:49:03 +0100">
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001109175117.A942@wouter.verheijen.nl \
--to=wouter.verheijen@worldmail.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).