ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: beginners manual
Date: Wed, 23 Nov 2005 21:15:45 +0100	[thread overview]
Message-ID: <6faad9f00511231215l6d33cf57weba9331057c33b34@mail.gmail.com> (raw)
In-Reply-To: <43824445.4000905@wxs.nl>

Hans Hagen wrote:
> Hi,
>
> I'm going to clean up the beginners manual (at least the source code) so
> i think this s a good moment to pick up the 'translation' thread
>
> So the question is:
>
> - what can go out
> - what should go in
> - what should be updated

31.2. \showbodyfont[cmr]
32.2. has to be rewritten I guess (write something about
\enableregime[utf-8] and something about encodings)
38 (using modules): to be rewritten
C (auxilary files): mention texutil --purge[all]

What could be added:
- Tables: Natural tables (already mentioned by Taco). I just realized
that this is the only manual where the "usual" tables are actually
explained. I was looking for the explanation in cont-eni before.
- Bibliography
- Slides: some basic example with \usemodule[pre-whatever] to show the
user that making slides is no more difficult than making an A4
document
- Metafun: some basic examples and a reference to the manual
- XML: a basic example
- mention XeTeX & Aleph somewhere (at least under section with fonts
or lnguage-specific issues)

> as well as:
>
> - who will participate (in translation)

Slovenian translation is not rentable yet :(

> - how to deal with localization (maybe dedicated language related chapters)

Not a bad idea. Encodings, regimes, \mainlanguage, using different
interface, French "active characters", quotations, Greek, Vietnamese,
Russian, ... under the same hood.

Mojca

  parent reply	other threads:[~2005-11-23 20:15 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 [this message]
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
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=6faad9f00511231215l6d33cf57weba9331057c33b34@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).