ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@gmail.com>
To: ConTeXt <ntg-context@ntg.nl>
Subject: ConTeXt on Excursion: translations in the Garden
Date: Tue, 08 May 2007 19:42:02 +0200	[thread overview]
Message-ID: <4640B66A.6020901@seznam.cz> (raw)

Hi all,

there is a new plant in the Garden: 
http://wiki.contextgarden.net/ConTeXt_on_Excursion%2C_translations

It gathers translations of the beginner's manual ConTeXt on Excursion 
(authors Ton Otten and Hans Hagen). Currently there exist Dutch, 
English, and Czech versions. Czech version is a team work of translators 
(Ján Buša, Jiří Hrbek, Martina Plachá, Petr Tesařík, and Vít Zýka) 
supported by Czechoslovac TUG (CSTUG). We use as a model the English 
version (although the original is the Dutch one). A reader can find 
several additional sections dealing with localization and information 
sources.

Non Czech readers have also some benefic as a side effect of this 
project. The English version was slightly actualized and fixed some 
bugs. All versions are acompanied by actual macro syntax and listed in 
the command index.

Sources of all three versions are stored on the public SVN repository as 
a part of the ConTeXt manual project 
(https://foundry.supelec.fr/projects/contextman/), administrated by 
Taco. There is a makefile for an easy manual generation. It is ready for 
adding new stuff/actualizing/fixing bugs and even for new language 
translation. On the Garden page we can find breaf instructions for that.
If you have any question, please do not hesitate to ask me.

Best reading
Vit


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2007-05-08 17:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 17:42 Vit Zyka [this message]
2007-05-09  0:26 ` luigi scarso
2007-05-09  7:34   ` Hans Hagen
2007-05-09  9:55     ` Vit Zyka
2007-05-09 13:41     ` John R. Culleton
2007-05-09 14:26       ` luigi scarso
2007-05-09  6:09 ` Aditya Mahajan
2007-05-10  1:05 ` Zhichu Chen
2007-05-10  1:54   ` Arthur Reutenauer
2007-05-10  4:48     ` Zhichu Chen
2007-05-10  6:38     ` Wolfgang Schuster
2007-05-10 12:42       ` Arthur Reutenauer
2007-05-10 14:06         ` Wolfgang Schuster
2007-05-10 14:44           ` Arthur Reutenauer
2007-05-11  6:44             ` Zhichu Chen
2007-05-15  2:46             ` Aditya Mahajan
2007-05-15 19:51               ` Wolfgang Schuster
2007-05-15 20:41                 ` Arthur Reutenauer
2007-05-15 22:45                   ` Aditya Mahajan
2007-05-16 18:01                   ` Wolfgang Schuster
2007-05-10 18:05           ` Renaud Aubin
2007-05-10  7:39   ` Taco Hoekwater

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=4640B66A.6020901@seznam.cz \
    --to=vit.zyka@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=vit.zyka@seznam.cz \
    /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).