ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Paranormal bug in TL 2016
Date: Wed, 12 Oct 2016 08:58:05 +0200	[thread overview]
Message-ID: <BB92628C-474A-41B4-AAD5-D47C306BB20E@gmail.com> (raw)
In-Reply-To: <f97e6815-85c0-a50e-7962-8f7166f236af@gmail.com>

On 11 Oct 2016, at 15:58, Henri Menke <henrimenke@gmail.com> wrote:
>> […]
> 
> I have to correct myself, it just looked like it worked.  It didn't generate the PDF due to
> 
> Fatal Error     > Your format does not match the base files!
> 
> The search continues.

Hi Henri,

The error is indeed extremely bizarre, and maybe funny, but if you want just to find a temporary solution in order to finish your project, it seems that adding a special word (or maybe something else…) allows the typesetting of your file. 

I tried the following modification of your sample with ConTeXt  ver: 2016.05.17 19:20 (and LuaTeX Version 0.95.0) from TeX Live 2016.
The file name is bizarre-error.tex (if there no hyphen in the file name everything is allright).
It compiles both with the latest beta in standalone ConTeXt, as well as with the stable one from TeXLive 2016.

It is important to have a blank line before the line containing «  \phantom{Junior} ».
If I remove the line «  \phantom{Junior} » then the file does not compile with the version of ConTeXt from TeXLive… (but it does with the latest beta)
If I replace it with the word « Junior », again it compiles fine. 
However if I replace that line with «  \phantom{Bizarre} » or even the word « Bizarre », the file does not compile :-)
But if your replace it with « Bizarre \phantom{Junior} » or with « \phantom{Bizarre} \phantom{Junior} » it compiles again…

All this seems funny to me, but I understand that it might stress you!

Best regards: OK

% begin bizarre-error.tex
\version[temporary]

\setbreakpoints[compound]

\setuppagenumbering[alternative=doublesided]

\starttext

\startstandardmakeup
\stopstandardmakeup

{\em Detailtypografie} by Friedrich Frossman 

\phantom{Junior}

\stoptext
% end bizarre-error.tex
___________________________________________________________________________________
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://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2016-10-12  6:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 10:14 Henri Menke
2016-10-10 10:31 ` Thomas A. Schmitz
2016-10-10 11:49   ` Henri Menke
2016-10-10 12:03     ` Thomas A. Schmitz
2016-10-10 13:31       ` Henri Menke
2016-10-10 13:59         ` Mojca Miklavec
2016-10-11  9:10           ` Henri Menke
2016-10-11 10:01           ` Henri Menke
2016-10-11 13:33           ` Henri Menke
2016-10-11 13:45             ` Mojca Miklavec
2016-10-11 13:58               ` Henri Menke
2016-10-11 14:01                 ` luigi scarso
2016-10-12  6:58                 ` Otared Kavian [this message]
2016-10-12  9:19               ` Henri Menke
2016-10-11 13:57             ` Arthur Reutenauer
2016-10-10 12:19     ` Ulrike Fischer

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=BB92628C-474A-41B4-AAD5-D47C306BB20E@gmail.com \
    --to=otared@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).