From: Philippe Figon <philippe.figon@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Blank page
Date: Wed, 19 Mar 2014 14:53:01 +0100 [thread overview]
Message-ID: <0A4C013B-1789-48A3-9038-2ABE20FE23AC@passager.org> (raw)
In-Reply-To: <4709498C-46F6-4036-B86F-1AD14F8406D9@gmail.com>
Thanks Wolfgang.
It was indeed a file problem. I opened and resaved the same files in Sublime text in place of Texshop
and ran context from the terminal. Everything's just fine know. So I guess Texshop added some extra invisible
character that made chapter start on a new page.
Le 19 mars 2014 à 12:48, Wolfgang Schuster <schuster.wolfgang@gmail.com> a écrit :
>
> Am 18.03.2014 um 23:39 schrieb Philippe Figon <philippe.figon@gmail.com>:
>
>> Hello to you all,
>>
>> Forgive me if this is a newbie question, but I can't understand why when I try to compile this :
>>
>> --------------------------------------
>> \environment simple-env
>> \starttext
>> \chapter{}
>>
>> This is an example
>>
>> \stoptext
>> ----------------------------------------
>>
>> with simple-env file containing only
>>
>> -----------------------------------------------------------------
>> \startenvironment simple-env
>> \setuppagenumbering[alternative=doublesided]
>> \setuphead
>> [chapter] [page=right]
>> \stopenvironment
>> -----------------------------------------------------------------
>>
>> The text only appears on page 3 and I can't never make start on page 1.
>>
>> But if I try this :
>>
>> ----------------------------------------------------------------
>> \setuppagenumbering[alternative=doublesided]
>> \setuphead
>> [chapter] [page=right]
>>
>> \starttext
>> \chapter{}
>>
>> This is an example
>>
>> \stoptext
>>
>> ------------------------------
>>
>> It starts on page 1 as wanted.
>>
>> Is there something with the environment inclusion?
>
> I can’t reproduce you problem. To say what’s wrong you have to provide more information.
>
> 1. Which version do you use?
>
> ConTeXt ver: 2014.03.16 19:58 MKIV beta fmt: 2014.3.19 int: english/english
>
> 2. Send us the test files (make a zip out of them) from your system because sometimes invisible characters are the cause for such problems.
>
> 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
___________________________________________________________________________________
prev parent reply other threads:[~2014-03-19 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 22:39 Philippe Figon
2014-03-19 11:48 ` Wolfgang Schuster
2014-03-19 13:53 ` Philippe Figon [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=0A4C013B-1789-48A3-9038-2ABE20FE23AC@passager.org \
--to=philippe.figon@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).