From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: List of bugs and quirks
Date: Wed, 27 Mar 2013 21:11:21 +0100 [thread overview]
Message-ID: <51535269.9040507@wxs.nl> (raw)
In-Reply-To: <20130327185522.GP9268@homerow>
On 3/27/2013 7:55 PM, Marco Patzer wrote:
> Hi Hans,
>
>> maybe after the current is made (which happens sometime within the
>> next two weeks)
>>
>> best make sure that we have no serious bugs (experimental features apart)
>
> I think it's better to start a new thread for this issue.
>
> I maintain a small list of bugs and quirks which I would like to
> share. I don't know if the issues are considered bugs or not. I
> posted most of them to the mailing list at some point, but AFAIK
> they have not been fixed for whatever reason. Usually there are
> simple workarounds or I have some code which fixes the issue. Others
> are still unresolved. Act upon as you see fit.
well, if something really crashes due to some 'programming' error it's
indeed a bug (i tend to add such tests then to the test suite so that it
gets checked)
other cases depend a bit on how complex it is to deal with it given the
tex language, take this one:
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> %% Newline after \placelegend fails
> \starttext
> \startplacelegend
>
> \startcontent
> Foo
> \stopcontent
> \startcaption
> Bar
> \stopcaption
> \stopplacelegend
> \stoptext
If you want that, you also want
\starttext
\startplacelegend
\startcontent
Foo Bar
\stopcontent
\startcaption
Bar Foo
\stopcaption
\stopplacelegend
\stoptext
That's actually a side effect of how such a mechanism is implemented but
in this case it can be catched (at the cost of a bit less efficiency).
The problem then is that after a while one wonders why the particular
lines of code were there.
(you can test / look into the zip on the ftp server)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-27 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 18:55 Marco Patzer
2013-03-27 20:11 ` Hans Hagen [this message]
2013-03-27 20:52 ` Hans Hagen
2013-03-27 21:06 ` Hans Hagen
2013-03-27 22:00 ` Hans Hagen
2013-03-27 22:55 ` Marco Patzer
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=51535269.9040507@wxs.nl \
--to=pragma@wxs.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).