ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.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:39:59 +0200	[thread overview]
Message-ID: <4642CC4F.2040800@elvenkind.com> (raw)
In-Reply-To: <769ba7780705091805g5bd24c10w2ebc21f522ee9037@mail.gmail.com>

Zhichu Chen wrote:
> 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.

Vit write the makefile. Is all of that actually make syntax? wow.

> But I think I can compile it manually.

I would think so too. But if it is all proper makefile stuff, then
it will run fine with the gnuwin toolkit.

> 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).

It is (supposed to be) impossible to mess up version controlled
files completely, after all: that is the point of using a version
control system in the first place. At worst, you can create some
temporary chaos that an expert needs to look at.

I firmly agree with Arthur on the zh vs. cn issue, btw.

Best, Taco
___________________________________________________________________________________
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  7:39 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
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 [this message]

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=4642CC4F.2040800@elvenkind.com \
    --to=taco@elvenkind.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).