ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: ntg-context@ntg.nl
Subject: Re: [PATCH] small corrections for the ConTeXt-correspondence manual
Date: Tue, 17 Aug 2010 23:17:50 +0200	[thread overview]
Message-ID: <1282079870.4314.5.camel@mattotaupa> (raw)
In-Reply-To: <1281891833.3693.22.camel@mattotaupa>


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

[Adding Wolfgang explicitely to CC.]

Am Sonntag, den 15.08.2010, 19:03 +0200 schrieb Paul Menzel:
> Dear ConTeXt folks,
> 
> 
> this is my first post and I am looking forward to get more acquainted
> with ConTeXt.
> 
> I read the ConTeXt-correspondence manual (module letter [1]) and
> attached you will find some formal fixes for the source files gotten
> from [2]. If I should sent each patch as a separate message, please tell
> me.
> 
> I was not able to get a PDF created with my Debian Sid/unstable system,
> so I could not test my changes.
> 
>         $ texexec correspondence.tex
>         […]
>         ! Undefined control sequence.
>         l.139 \doifolderversionelse
>                                    \contextversion{\currentmoduleparameter\c!context...
> 
> I hope this is the right way to contact the authors and to submit the
> patches. If not, please tell me the preferred way.
> 
> As a last remark, I would really love to see the sources and
> documentation of modules under SCM so contributing would be easier.
> There are some free services for free software projects as for example
> Gitorious [3].

Is everyone busy or was my message overlooked?

> Thanks,
> 
> Paul
> 
> 
> [1] http://modules.contextgarden.net/letter
> [2] ftp://tug.ctan.org/pub/tex-archive/macros/context/contrib/context-letter
> [3] http://www.gitorious.org/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2010-08-17 21:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 17:03 Paul Menzel
2010-08-17 21:17 ` Paul Menzel [this message]
2010-08-18 18:03 ` Wolfgang Schuster
2010-08-18 21:02   ` Paul Menzel
2010-08-18 21:16     ` Taco Hoekwater
2010-08-23 12:30       ` public SCM repositories and how to contribute (was: [PATCH] small corrections for the ConTeXt-correspondence manual) Paul Menzel
2010-08-31  8:56         ` public SCM repositories and how to contribute Taco Hoekwater
2010-08-25 13:33     ` [PATCH] small corrections for the ConTeXt-correspondence manual Wolfgang Schuster

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=1282079870.4314.5.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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).