ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared KAVIAN <otared@gmail.com>
Subject: Re: beginners manual
Date: Thu, 24 Nov 2005 23:29:47 +0100	[thread overview]
Message-ID: <3cb063a60511241429h1ed51589y9b4bd7e40f415a3a@mail.gmail.com> (raw)
In-Reply-To: <BABAFCF2-2106-4220-A76C-CB408A3B700C@gmail.com>

Hi Hans,

Thank you for your great work.
Regarding the beginners manual your are going to update, I have two
or three suggestions.
To begin with, I think we should designate a volunteer group of
people on this list to do some tasks in "parallel":

1) Since the installation of ConTeXt seems to be not so easy for
everyone, we should have at least three subgroups of people
experimenting, and then explaining, how to install and update ConTeXt
on Linux, Windows, MacOS X.
Once each subgroup has carried out the experimentation of the "How
to..." instructions, they would send them to you so that you can
include them in the Beginners Manual (abbreviated BM in the sequel...).
It is important to include in each subgroup a "wizard" and an
"amateur beginner": otherwise the "How to..." instructions may result
in something not really usable by real beginners.
For my part I am volunteering to be a (rather dumb...) beginner
regarding installation on MacOS X, and its use with XeTeX.
The same observation applies for the use of ConTeXt with non roman
languages under various operating systems.

2) We should divide the BM in $n$ parts ($n \geq 2$... but maybe $n=10
$) and designate one or two individuals for each part to test ALL the
codes and examples you give in the BM to make sure that they work
fine with a "basic" install of ConTeXt.

3) Two great features of ConTeXt are its versatility regarding
Metapost and presentations. In the BM these features should be
presented in a transparent way, since most beginners would not have
the patience or the technical knowledge of going through the source
files.

Best regards: OK

On 21 nov. 2005, at 23:03, 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
>
> as well as:
>
> - who will participate (in translation)
> - how to deal with localization (maybe dedicated language related
> chapters)
>
> Hans

  reply	other threads:[~2005-11-24 22:29 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 [this message]
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=3cb063a60511241429h1ed51589y9b4bd7e40f415a3a@mail.gmail.com \
    --to=otared@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).