ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Zhichu Chen" <zhichu.chen@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: ConTeXt on Excursion: translations in the Garden
Date: Thu, 10 May 2007 09:05:46 +0800	[thread overview]
Message-ID: <769ba7780705091805g5bd24c10w2ebc21f522ee9037@mail.gmail.com> (raw)
In-Reply-To: <4640B66A.6020901@seznam.cz>


[-- Attachment #1.1: Type: text/plain, Size: 3029 bytes --]

Hi Taco,

I've registered the project to translate it into Chinese. Anyhow, I have
some questions now:
1, I'm using WinXP, so I downloaded gnu make and other core files for
windows from gnuwin32.sourceforge.net. I don't know if it will work well.
But I think I can compile it manually.
2, When I run "make en" or manually compile ma-cb-en, I got an error that
\secretsetup is undefined. I think my ConTeXt is new enough:
ConTeXt  ver: 2007.04.17 12:51 MKII  fmt: 2007.4.20  int: english/english
3, I've never used svn before, so I'm afraid if I upload my source to the
svn server, would it harm other files? I only made change to makefile and
create a folder called cn (for Chinese).


On 5/9/07, Vit Zyka <vit.zyka@gmail.com> wrote:
>
> 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
>
> ___________________________________________________________________________________
>



-- 
Best Regards
Chen
----------------------------------------------------------------

          Zhi-chu Chen | Shanghai Synchrotron Radiation Facility
         No. 2019 | Jialuo Rd. | Jiading | Shanghai | P.R. China
             tel: 086 21 5955 3405 | zhichu.chen.googlepages.com
                                               | www.sinap.ac.cn
----------------------------------------------------------------

[-- Attachment #1.2: Type: text/html, Size: 4491 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2007-05-10  1:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 17:42 Vit Zyka
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 [this message]
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=769ba7780705091805g5bd24c10w2ebc21f522ee9037@mail.gmail.com \
    --to=zhichu.chen@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).