From: "Tomi Lindberg" <tomi.lindberg@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: LuaTeX problems
Date: Sat, 28 Jun 2008 06:50:57 +0300 [thread overview]
Message-ID: <ee1daa530806272050s53aadd03y632c8493ed3ad93b@mail.gmail.com> (raw)
In-Reply-To: <115224fb0806262259ibeb4162v81d3b139f7c5d528@mail.gmail.com>
2008/6/27, Wolfgang Schuster <schuster.wolfgang@googlemail.com>:
> Both files work for me but I don't have your component or environment
> files and there is a problem with the content in one of the files but as
> long as you don't give us more information we can't help you.
>
> Instead of sending us all other files you should make a minimal example
> where we can reproduce the error.
Seems that my problem was just an error of mine - one the components
had a missing \stopitemize and adding it fixed the compile errors
(somehow I assumed that if it compiles with texexec it should be
syntactically correct but looks like I was wrong). Now
"context/texexec <product-name>" and "context/texexec <project-name"
all create identical .pdf files except the following:
texexec seems to fill pages better while context at times leaves a lot
of air at the end of page if in middle of a list.
Indexes are definately in favor of texexec. context fails to order 'ä'
and 'ö' correctly - it just thinks they're 'a' and 'o' while texexec
works as it should. Also context doesn't add 'titles' for letters. And
finally there's a weird 'unknown' entry at the start of context index.
texexec makes an extra empty page at the end of document while context
doesn't. Compared to the above this seems a minor gain though.
Thanks,
Tomi Lindberg
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-28 3:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 6:57 Tomi Lindberg
2008-06-26 7:05 ` Wolfgang Schuster
2008-06-26 11:41 ` Diego Depaoli
2008-06-26 11:50 ` Tomi Lindberg
2008-06-26 12:46 ` Wolfgang Schuster
2008-06-26 19:11 ` Diego Depaoli
2008-06-26 19:56 ` Diego Depaoli
2008-06-27 5:56 ` Wolfgang Schuster
2008-06-30 17:55 ` Diego Depaoli
2008-06-30 18:49 ` Hans Hagen
2008-06-30 19:24 ` Diego Depaoli
2008-06-26 12:17 ` Jean Magnan de Bornier
2008-06-27 5:59 ` Wolfgang Schuster
2008-06-28 3:50 ` Tomi Lindberg [this message]
2008-06-28 12:09 ` Hans Hagen
2008-06-30 7:31 ` Wolfgang Schuster
2008-07-02 19:46 ` Tomi Lindberg
2008-07-02 22:08 ` Hans Hagen
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=ee1daa530806272050s53aadd03y632c8493ed3ad93b@mail.gmail.com \
--to=tomi.lindberg@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).