From: Mari Voipio <mari.voipio@iki.fi>
Subject: Re: beginners manual
Date: Mon, 28 Nov 2005 13:46:42 +0200 [thread overview]
Message-ID: <438AEE22.205@iki.fi> (raw)
In-Reply-To: <43824445.4000905@wxs.nl>
Hans Hagen wrote:
> I'm going to clean up the beginners manual
Yippee! :-)
Having read one printout to shreds I really appreciate this...
> - what should go in
As has been suggested here to an extent, there should be attachments (or
separate smaller manuals) on how to install and update ConTeXt in
different operating systems (Mac OS 10.4 was a breeze even for a new Mac
user, Windows is a great pain in the butt every time; still running
TeXLive 2004 ConTeXt on this machine because I can't afford to break
anything). As I probably should do it for work anyway, I'm willing to
write the part for MsWinConTeXt (for Win 2000/XP) as long as I get at
least until the end of the year.
I also suggest writing a separate set of instructions for those people
who migrate from LaTeX (like my brother did) and for those who migrate
from MSWord (like I did) or Apple's Pages (or similar word processing
software). I strongly feel that the beginners' manual per se should be
for ALL beginners and shouldn't refer to either Word or LaTeX.
Again, as I probably have to write it at some point anyway, I'm willing
to chip in for the MS Word part and I might even be able to write a
draft for others to fill in with.
> - what should be updated
Tables is what would be really useful. This far I've only used tabulate
and \table, but I have a faint idea that "natural tables" would be the
real solution to my problems - but finding info on them has been so
challenging that I've given up this far.
I also personally feel that a totally different approach to the fonts
chapter would make my life a lot easier. I'm sure this partly relates to
my Windows background, but for example the term "font family" was
totally alien to me when I started using ConTeXt.
And of course, much of the first weeks with ConTeXt (in Windows) were
overshadowed by the important question of "how to make the fonts and
font switches work at all". I still don't understand the system at all,
so even though I've successfully gotten a few of the TeXLive fonts to
work, I always have to refer to my older ConTeXt documents to copy the
code that has worked at least at some stage.
[In Word, you switch the font of the Normal style from Times New Roman
to Century Schoolbook with about three clicks of the mouse - in ConTeXt
the same may be a three-hour or three-day operation, at least with my
not-even-intermediate skills... I love ConTeXt, I hate fonts.]
The order of things in the beginners' manual has often frustrated me as
I feel that "same stuff" is split in different places all over manual. I
have not dealt with math, but when I taught word processing with Word,
these would be things that come up in the very, very beginning:
- how to change the font (family, size, emphasis)
- how to change the paragraph (line spacing, paragraph spacing, indents,
alignment)
- how to print preview i.e. see the document as laid out on paper (in
ConTeXt this would be "how to compile and view; maybe put more detailed
instructions into the ConTeXt in Unix/Linux/Mac/Windows
attachment/manual and just refer to these)
- how to change the margins [I had REAL problems with this in ConTeXt,
the whole context is so different; but this should probably go into the
"ConTeXt for word processor users" chapter]
[- how to save and retrieve a document; not really an issue with
ConTeXt, I suspect all users are this much computer literate]
Next step is often additional text features:
- headings (in Word, "header" is only top part of page, the
section/chapter titles are called headings)
- lists (i.e. itemize in ConTeXt)
- page numbers (many Word users never use their header/footer for
anything else!)
- page breaking
- hyphenation
And, as many people migrate to ConTeXt when having to deal with large
documents and/or math, the next step for many would probably be:
- figures (i.e. graphics)
- tables
- footnotes
- header & footer
- formulae, units, math otherwise
- special characters!
- registers, references
- interactivity?
If ConTeXt comes nowadays with modules, those should probably get a more
prominent position in the manual and obviously a lot more detailed
explanation than the current one. If I've understood the concept
correctly, the modules are comparable to Word templates, but this far
the information has been so split that I haven't bothered to piece it
together to actually even try to use a module, not to talk about making
one (although that bit probably belongs to the big manual).
> - who will participate (in translation)
I can do Finnish, it shouldn't take that long once the English original
is ready. A bunch of LaTeX stuff exists in Finnish and that should help
with the terminology (should probably try to stick to existing stuff)
and I can possibly enlist brother to review what I've done, if there're
no other Finnish speakers on this list.
I'll also be quite happy to proof the Swedish manual but as there are
native speakers of Swedish on this list, I'd rather leave the actual
translation work to them (especially when I use Swedish as spoken in
Finland, which sometimes makes a difference).
> - how to deal with localization (maybe dedicated language related chapters)
Yes, definitely. Having now worked with translations of originally
English ConTeXt document to German and Spanish I've had to look for
answers for the following problems:
- hyphenation (how to turn it on and how to prevent it)
- labels in captions and references
(how to switch language, how to adjust)
- regiments
- character sets (especially non-Latin stuff)
- punctuation rules (for example one vs. two spaces after period)
Sometimes I'd really, really love to have a list of what characters and
languages ConTeXt is/is not capable of coping with, just a quick
reference would help...
A few thoughts from the Windows front,
Mari
next prev parent reply other threads:[~2005-11-28 11:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:03 Hans Hagen
2005-11-22 16:00 ` VnPenguin
2005-11-22 16:39 ` Olivier
2005-11-23 10:33 ` Hans Hagen
2005-11-22 16:56 ` Jose Antonio Rodriguez
2005-11-22 17:15 ` Mikael Persson
2005-11-24 15:38 ` Johan Sandblom
2005-11-22 19:32 ` Taco Hoekwater
2005-11-22 20:51 ` Tobias Burnus
2005-11-23 20:15 ` Mojca Miklavec
2005-11-24 22:39 ` Maurice Diamantini (dom)
2005-11-25 9:47 ` Wolfgang Zillig
2005-11-25 14:02 ` beginners manual (xml input versus html output) Maurice Diamantini
2005-11-24 1:44 ` beginners manual - Install Miguel Queiros
2005-11-24 8:53 ` Wolfgang Zillig
2005-11-25 3:04 ` Miguel Queiros
2005-11-24 11:18 ` beginners manual Otared Kavian
2005-11-24 22:29 ` Otared KAVIAN
2005-11-25 4:41 ` Xiao Jianfeng
2005-11-25 13:10 ` Patrick Gundlach
2005-11-25 14:24 ` Hans Hagen
2005-11-25 18:22 ` VnPenguin
2005-11-25 14:05 ` Xiao Jianfeng
2005-11-28 11:46 ` Mari Voipio [this message]
2005-11-26 0:53 Hans Hagen
2005-11-26 8:11 ` VnPenguin
2005-11-26 11:07 ` Taco Hoekwater
2005-11-26 12:57 ` VnPenguin
2005-11-27 23:29 ` Hans Hagen
2005-11-28 7:27 ` VnPenguin
2005-11-28 10:27 ` Hans Hagen
2005-11-26 19:46 ` David Arnold
2005-11-26 23:12 ` VnPenguin
2005-11-27 23:26 ` Hans Hagen
2005-11-28 20:16 ` VnPenguin
2005-11-27 13:27 ` Vit Zyka
2005-11-27 22:34 ` Hans Hagen
2005-11-28 10:03 ` Vit Zyka
2005-11-28 13:13 ` Mari Voipio
2005-11-28 13:56 ` Taco Hoekwater
2005-11-28 14:08 ` Wolfgang Zillig
2005-11-28 15:09 ` Hans Hagen
2005-11-28 19:45 ` VnPenguin
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=438AEE22.205@iki.fi \
--to=mari.voipio@iki.fi \
--cc=ntg-context@ntg.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).