ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Willi Egger <w.egger@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Finalizing a module
Date: Thu, 13 Jan 2011 20:55:04 +0100	[thread overview]
Message-ID: <9EE4DEF6-EF36-47F9-81C1-25D81A28BA90@boede.nl> (raw)
In-Reply-To: <7EFF3357-F272-4E98-B4E7-454569C4C66B@gmail.com>

Hallo Wolfgang,

thank you for your reply. It looks already promising, however I get the following error and I do not know how to fix:

Running context --ctx=s-mod t-pocketdiary.tex

! String contains an invalid utf-8 sequence.
l.113 
      ?
\dodotypeblockverbatim ..., nature = "display", }}
                                                  \dostoptagged \endofverbat...
l.152 \stopdefinition


When looking at s-mod-00.mkiv it appears that the \startdefinition macro is only available in mode [nocode] 
Commenting the \startmode[nocode] and \stopmode does not solve the problem:

Runaway argument?
\setvari[PocketDiaryColo\ETC.
! File ended while scanning use of \dododowithbuffer.
<inserted text> 
                \par 
\inputgivenfile #1->\normalinput {#1}
                                     
\doreadfileyes ...x \inputgivenfile \readfilename 
                                                  \relax \the \everyafterrea...
l.2 \readfile{t-pocketdiary.tex.prep}{}{}

Looking at the *.tex.prep file it does not appear that there is something wrong with it. I am also a bit surprised about the error message in the line after the Runaway argument?. The command is crippled: it should be \setvariables


Puzzled, kind regards

Willi
On 12 Jan 2011, at 23:23, Wolfgang Schuster wrote:

> 
> Am 12.01.2011 um 21:11 schrieb Willi Egger:
> 
>> Hi,
>> 
>> I would like to finalize my module...
>> I still got a couple of questions:
>> 
>> 1. How is the module documentation compiled? 
> 
> context --ctx=s-mod <mymodule>
> 
> with “--mode=nocode” you can hide the source and output only the documentation
> 
>> 2. How is a module packaged for uploading?
> 
> zip file with tds structure
> 
> Wolfgang
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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:[~2011-01-13 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 20:11 Willi Egger
2011-01-12 22:23 ` Wolfgang Schuster
2011-01-13 19:55   ` Willi Egger [this message]
2011-01-13 21:23     ` Wolfgang Schuster
2011-01-12 23:19 ` Mojca Miklavec

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=9EE4DEF6-EF36-47F9-81C1-25D81A28BA90@boede.nl \
    --to=w.egger@boede.nl \
    --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).