March 2010 - ntg-context - NTG Mailing Lists

Breaking textframes across pages
by Matthias Weber 05 Mar '10

05 Mar '10

Dear all, if I understand correctly, framed texts (\startframedtext ... startframedtext) are not broken across pages. In contrast, when I set up an emumeration to to be framed, it is broken, but in such a way that the bottom margin of the first part and the top margin of the second part are inconsistent with any values I imposed. Below is a minimal example. I can see that this might be on purpose, but when I have $e^{e^x}$ and the like in the first line on the new page, it gets too close to the default margin. Is there an option that sets the broken margins? Thanks, Matthias \setupcolors[state=start] \setupbodyfont[10pt] \definetextbackground [defbackground] [ before=\blank, after=\blank, leftoffset=5pt, rightoffset=5pt, topoffset=25pt, % I exaggerate here of course bottomoffset=25pt, frame=on, framecolor=black, location=paragraph] \defineenumeration [myframe] [text=Note, before={\starttextbackground[defbackground]}, after={\stoptextbackground}, way=bysection, location=hanging, letter=rm] \starttext \startmyframe \input tufte \stopmyframe \input knuth \input knuth \input knuth % make sure the next frame breaks \startmyframe \input tufte \stopmyframe \input knuth \stoptext

1 0

suggestions for context documentation
by Michael Saunders 05 Mar '10

05 Mar '10

> You mean like the beginner's manual > > http://www.pragma-ade.com/general/manuals/ms-cb-en.pdf > > and the user manual > > http://www.pragma-ade.com/general/manuals/cont-eni.pdf > ... > > amongst 46 others by Pragma No, not like those. I mean like a real manual. I read the book about Hasselt---a few examples without explanations. I've looked at most of the fifty or so documents over which this virtual manual is supposed to be spread. They are about as informative. Most of these documents seem to be 5--12 years old. The wiki is even more patchy. The idea that a computer manual is something that exists implicitly in the discussions of a mailing list is a new idea to me. You can't be serious about "mk.pdf" being a manual. Even it admits, "This document is not so much a users manual as a history of the development." Little after that point is intelligible. Compared with the clear, abundant documentation of the LaTeX world, Context seems like a secret that a small club is trying to keep. It's not even clear from the manuals that development is ongoing, much less that there is some advantage in using it. So, will there ever be a manual to MK IV? In how many years?

9 9

Re: [NTG-context] [OT] Lua sponsors
by Vyatcheslav Yatskovsky 05 Mar '10

05 Mar '10

" We are pleased to announce that Adobe has joined our corporate >> > sponsorship program." >> > http://www.lua.org/sponsors.html >> > Oh, I already see Hans replacing his "javascript in pdf documents" > strategy with "fun with lua scripts in pdf documents" now:) > > Wow. I first decided that Adobe became the sponsor of LuaTeX. ) Vyatcheslav

2 1

Re: [NTG-context] suggestions for context documentation
by richard.stephens＠converteam.com 05 Mar '10

05 Mar '10

1 0

Re: [NTG-context] Occasional words sticking out from flush-right
by Vyatcheslav Yatskovsky 05 Mar '10

05 Mar '10

On 03.03.2010 22:41, ntg-context-request(a)ntg.nl wrote: > Stymies me how people on this mailing list know this stuff -- even a > Google search for "setbreakpoints", assuming I knew the command in > advance, returns nada. This all is sacred knowledge, for devoted seekers :o) (Arthur, what about your church of TeX?) Vyatcheslav

5 21

suggestions for context documentation
by Michael Saunders 04 Mar '10

04 Mar '10

The important thing is: is there _ever_ going to be a manual? I want to try Context, but I've been putting it off for years because it's not really practical without documentation. There must be many others in the same situation.

4 6

[OT] Lua sponsors
by luigi scarso 04 Mar '10

04 Mar '10

" We are pleased to announce that Adobe has joined our corporate sponsorship program." http://www.lua.org/sponsors.html -- luigi

2 2

using `` '' the output is wrong.
by views63 04 Mar '10

04 Mar '10

Hi all, I'm using `` complex analysis'' the output is wrong. but using \ quotation (... ...) can output the correct quotation marks The example: \starttext `` complex analysis'' \quotation{complex analysis} \stoptext -- Best Regards

10 28

Differences in smart quotes MKII -> MKIV
by James Fisher 04 Mar '10

04 Mar '10

Hi, (Forgetting our documentation philosophy session for a minute,) I'm experiencing issues in MKIV with smart quotes. Specifically, opening quotes. Compare the output of `texexec dash-test' and `context quote-test' on the following: \starttext `Yes, but --- ' `--- this is an interruption! Get down on the floor!' The interjection was quite {\em unexpected} --- indeed, `shocking'. \stoptext And the following with double quotes: \starttext ``Yes, but --- '' ``--- this is an interruption! Get down on the floor!'' The interjection was quite {\em unexpected} --- indeed, ``shocking''. \stoptext In both cases, MKIV treats the opening grave character (is that the name? backtick?) literally rather than as an opening smart quote. James

2 2

suggestions for context documentation
by Peter Münster 04 Mar '10

04 Mar '10

Hello, These suggestions are a bit a reply to the thoughts of James Fisher. It would be nice, to have once in the future at least 2 up to date context documentations: - a context user manual For me, it's the merge of all scattered articles and manuals. Each chapter treats a particular subject, such as "columns" or "footnotes". It seems, that Taco is working on such a manual. - a context command reference manual This is just the xml-database used by texshow. Each command should be described in detail with every possible options. On the one hand, texshow uses this database, on the other hand a well structured command reference can be generated as pdf-file. Filling in all the details in both projects is a lot of work, so perhaps it would be a good idea, to set up a system, that makes it easy for users to contribute to these projects (patches) and easy for Taco and Hans to acknowledge or reject those patches. This "system" would be nothing else as some vcs (git or svn for example) with some commit-hooks, that manage the acknowledgement by Hans and Taco (and perhaps others). The tex-files of the user-manual are already under version control, and the xml-database is only the cont-en.xml file, that would need to be put under version control too. So, perhaps with not too much effort, users can be easily invited to contribute to the documentation projects and the quality can be assured through the acknowledgements of the developers. Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/

2 1