Re: [NTG-context] multipage tables
On Wed, Oct 11, 2006 at 10:47:45AM +0200, Wolfgang Schuster wrote: You should download the latest stable version from pragma. In my private system I now have apgraded to Debian Etch. I hope it is sufficient. I'm hesitating to upgrade in my office because Debian Etch is in an unstable stage. I am not used to upgrade single packages besides the system. If you want a repeated header on every page try to put \setuptables[split=repeat] into your document. With new versions from ConTeXt you do no longer the \starttables ... \stoptables command. Where are the definitions of the columns and their width in this case? Is there a brief docu and an example of this version of tables? Hans changed it to control table splitting completely with split-option in \setuptables and makes to let the normal \starttable-environment split when neccessary. Is there no longer a starttables but simply a starttable initialisation? And a last question: Why is there a \start - \stop in the example at the Wiki side? Gerhard -- Gerhard Kugler Psychotherapeut Bensheim (Germany) http://www.psychotherapie-kugler.de ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
On Mon, 16 Oct 2006, Aditya Mahajan wrote:
On Sun, 15 Oct 2006, Vit Zyka wrote:
Great, thank you Hans!
Let us process to teh next two problems also visible in the test file.
1. [snip]
2. Accented characters inside \typebuffer are type set as
\dochar {225}
This seems to be a bug. In utf-8 encoding, if an accented character is
the first character of a buffer, it gets typed correctly. All other
accented charaters come out as \dochar {225}. \getbuffer works fine.
I forgot to attach the test file. I am attaching it, hoping that the
encoding will come out correctly.
Can TeX choose the input encoding while writing files? If not, there
may be really no robust way to solve this problem.
Aditya\enableregime[utf]
\starttext
\startbuffer
ábout Whát
\stopbuffer
\typebuffer \getbuffer
\startbuffer
Whát
\stopbuffer
\typebuffer \getbuffer
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] minimal app to control layers
Dear all, Following the thread on layers: (1. thanks to all) 2. I use ConTeXt for many things, but quantitatively mostly for slides. Powerpoint is rude in its graphic abiltities but it has two features ConTeXt has not. First, you can draw on the screen. Second, you can import and stack images as you prefer. I'm not interested in the first feature, as I use a specific sw for drawing, and then import the result. But I am (sometimes) interested in the second one (let's call it compositing). In ConTeXt one can evidently use layers to exactly place and stack everything as needed (images, text). But, especially while preparing slides (a book worth the efforts indeed), it can be tedious to wrote all the code stuff. So, I created a minimal app in python using tkinter which allows to manipulate visually areas (boxes in the app terms) which can the be filled with images. The app has a second window which continuously updates with conTeXt code generated by the gui. The idea is that the user prepares a visual layer, then switches to code window, copy the generated code and paste it in the .tex file. Finally code is definitively modified it in the source, as usual. It's very simple, I've tested and it seems to work. But it can be buggy. I don't know if it can of any interest to anyone in the communities. In any case, comments related to whatsoever aspect are welcome. Actually, I've not documented it but it should be obvious. GUI should be completely portable. Sources are here: http://www.semiotiche.it/andrea/membrana/boxer.zip To run: python boxerController.py Best -a- Andrea Valle DAMS - Facoltà di Scienze della Formazione Università degli Studi di Torino http://www.semiotiche.it/andrea [EMAIL PROTECTED] ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
Aditya Mahajan wrote:
On Mon, 16 Oct 2006, Aditya Mahajan wrote:
On Sun, 15 Oct 2006, Vit Zyka wrote:
Great, thank you Hans!
Let us process to teh next two problems also visible in the test file.
1. [snip]
2. Accented characters inside \typebuffer are type set as
\dochar {225}
This seems to be a bug. In utf-8 encoding, if an accented character is
the first character of a buffer, it gets typed correctly. All other
accented charaters come out as \dochar {225}. \getbuffer works fine.
I forgot to attach the test file. I am attaching it, hoping that the
encoding will come out correctly.
Can TeX choose the input encoding while writing files? If not, there
may be really no robust way to solve this problem.
Aditya
in core-buf we need to treat the upper half of the vector:
\recatcodeuppercharacterstrue % ---
\setcatcodetable\vrbcatcodes
in startbuffer
(i cannot post a fixed file yet because buffers and verbatim is being
reshuffled due to mkii/mkiv preparations)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
Aditya Mahajan wrote:
On Sun, 15 Oct 2006, Vit Zyka wrote:
Great, thank you Hans!
Let us process to teh next two problems also visible in the test file.
1. [snip]
2. Accented characters inside \typebuffer are type set as
\dochar {225}
This seems to be a bug. In utf-8 encoding, if an accented character is
the first character of a buffer, it gets typed correctly. All other
accented charaters come out as \dochar {225}. \getbuffer works fine.
Can TeX choose the input encoding while writing files? If not, there
may be really no robust way to solve this problem.
a solution if to completely move to utf-8 internally and then make chars 127
unexpandable ; the problem is that whatever input encoding does not mix well
with multipass utf data then
in mkiv we will follow a different route since luatex is utf internally
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \showgrid question
Marcus Vinicius Mesquita de So wrote:
Hi!
Is there an option for the \showgrid command for showing only the line
numbers (no lines) ?
no, but it's easy to add that option,
put this in cont-new.tex (after \unprotect)
\chardef\gridboxlinenomode\plusone
\chardef\gridboxlinemode \plusone % 0:nothing 1:all 2:lines 3:frame
\def\gridboxvbox
{\ifcase\gridboxlinemode\vbox\or\ruledvbox\or\vbox\or\ruledvbox\else\ruledvbox\fi}
\def\gridboxwidth{\ifcase\gridboxlinemode0\or.5\or.5\or0\else.5\fi\testrulewidth}
\def\setgridbox#1#2#3%
{\setbox#1\gridboxvbox to #3 % given size
{\forgetall
\resetteststrut
\offinterlineskip
\hsize#2%
\baselinerulefalse
\gridboxvbox % calculated size
{\getrawnoflines{#3}% \getnoflines{#3}%
\vskip\topskip
\vskip-\strutht
\scratchdimen#2\advance\scratchdimen \lineheight
\dorecurse\noflines
{\strut
\hskip-.5\lineheight
\ifcase\gridboxlinenomode\or
\rlap
{\hskip.2\bodyfontsize\hskip\scratchdimen
\infofont\hbox to 1em{\hss\recurselevel}}%
\or
\llap
{\infofont\hbox to 1em{\hss\recurselevel}%
\hskip.2\bodyfontsize}%
\fi
\vrule
\!!height \gridboxwidth
\!!depth \gridboxwidth
\!!width \scratchdimen
\par}}
\vfill}}
\def\doshowgrid[#1]%
{\chardef\showgridstate\plusone % downward compatible default
\chardef\gridboxlinemode \plusone
\chardef\gridboxlinenomode\plusone
\processallactionsinset
[#1]%
[ \v!reset=\chardef\showgridstate\zerocount,
\v!bottom=\chardef\showgridstate\plusone,
\v!top=\chardef\showgridstate\plustwo,
\v!none=\chardef\gridboxlinemode \zerocount,
\v!all=\chardef\gridboxlinemode \plusone,
\v!lines=\chardef\gridboxlinemode \plustwo,
\v!frame=\chardef\gridboxlinemode \plusthree,
\v!nonumber=\chardef\gridboxlinenomode\zerocount,
\v!right=\chardef\gridboxlinenomode\plusone,
\v!left=\chardef\gridboxlinenomode\plustwo]}
now you can use keywords, like
\showgrid[lines.left]
\input tufte
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
Vit Zyka wrote:
Hans Hagen wrote:
Wolfgang Schuster wrote:
On Fri, 13 Oct 2006 19:16:58 -0400 (EDT)
Aditya Mahajan [EMAIL PROTECTED] wrote:
On Fri, 13 Oct 2006, Vit Zyka wrote:
Hans Hagen wrote:
Vit Zyka wrote:
Hans Hagen wrote:
Vit Zyka wrote:
Hi all,
there is some deep bug that was discovered translating
Beginners manual. Let take single chapter e.g.
ma-cb-cz-alignments.tex
With today beta I got .log attached (error ! Extra \else)
This will appear in both modes screen and normal.
Interesting is that no error appears in context 2006-05-28.
quite some code is being rewritten / adapted to context mkiv so
there could be low level differences
can you make a small example, since this else problem can come
from other places than reported
There are demonstrative files. Please, run
texmfstart texexec --pdf ma-cb-cz-test.tex
and
texmfstart texexec --pdf --mode=screen ma-cb-cz-test.tex
this file: ma-cb-env-cz.tex refers to itself and probably should
be :
\startenvironment ma-cb-env-cz
\environment ma-cb.tex
\mainlanguage[cz]
\language[en]
\enableregime[latin2]
\stopenvironment
Sorry, my fault but it does not solve the problem. I obtain the
same error with fresh context and corrected version of this file:
-
\startenvironment ma-cb-env-cz
\mainlanguage[cz]
\language[en]
\enableregime[latin2]
\stopenvironment
-
There is something wrong with ma-cb environment files. The file
ma-cb-en does not compile. I get an error
! Undefined control sequence.
\@@olbackground -\StatusAchtergrond
\doifvaluesomething ...inga {\csname #1\endcsname
}\ifx \!!stringa
\empty \e...
\stoplocalframed ...ing {\@@framed \c!background }
\dobackedbox
\handleframed...
\PlaatschapterStatus ... [\v!chapter \v!number ]}}
\vskip 0pt plus
\scratchc...
argument \PlaatschapterStatus
{}{}{}
\firstoftwoarguments #1#2-#1
...
l.19 \Introduction {Introduction}
I tried making minimal example of the file that you posted, but
always get the same error. I am pretty certain that ma-cb-en.tex
used to compile in the past.
Aditya
Hi Aditya,
I had the same problems in past in solved them by myself. The problems
are dutch commands in the style-files and a typo.
I attached my corrected style-files, because it is faster to replace
send you the files than I need to look where I made corrections.
The files did not correct the problem with the backgrounds in the
headers Vit has mentioned.
\edef\StatusAchtergrond
{StatusAchtergrond%
\ifodd\realpageno R\else\ifdoublesided L\else R\fi\fi}%
\ifdubbelzijdig - \ifdoublesided
this low level if has been changed, ad a result tex's 'fast if then
else ' skip routine does not see the \ifdubbelzijdig is if and gets
confused
Hans
Great, thank you Hans!
Let us process to teh next two problems also visible in the test file.
1. In the chapter ornament (a gray spiral with red dots) the red dots
are not dots but lines.
that was a tough one (esp because my by-now reference mkiv converter
also had this problem)
in meta-pdf.mkii patch:
\def\flushconcatMPsegment
{\ifcase\getMPkeyword\relax
\flushMPconcatmoveto
\resetMPmoveto
\doMPconcat{\gMPs1}\a{\gMPs2}\b%
\PDFcode{\!MP\a\space\!MP\b\space l}%
\or
\flushMPconcatmoveto
\resetMPmoveto
\doMPconcat{\gMPs1}\a{\gMPs2}\b%
\doMPconcat{\gMPs3}\c{\gMPs4}\d%
\doMPconcat{\gMPs5}\e{\gMPs6}\f%
\PDFcode{\!MP\a\space\!MP\b\space
\!MP\c\space\!MP\d\space
\!MP\e\space\!MP\f\space c}%
\or
\bgroup
\noMPtranslate
\flushMPconcatmoveto
\PDFcode{\!MP\lastMPmoveX\space \!MP\lastMPmoveY\space l S}
\egroup
\resetMPmoveto
\or
% \flushMPconcatmoveto
% \resetMPmoveto
\fi}
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] multipage tables
Gerhard Kugler wrote: On Wed, Oct 11, 2006 at 10:47:45AM +0200, Wolfgang Schuster wrote: You should download the latest stable version from pragma. In my private system I now have apgraded to Debian Etch. I hope it is sufficient. I'm hesitating to upgrade in my office because Debian Etch is in an unstable stage. I am not used to upgrade single packages besides the system. updating context is not that much related to debian; - make sure that you have the latest latin modern fonts installed (can be fetched from ctan) - then unzip the context zip in some local tree - make sure that the stubs are ok (there are stubs in the zip) the only debian specific thing (i guess) is the pdftex binary and context should adapt to that automatically If you want a repeated header on every page try to put \setuptables[split=repeat] into your document. With new versions from ConTeXt you do no longer the \starttables ... \stoptables command. Where are the definitions of the columns and their width in this case? Is there a brief docu and an example of this version of tables? often in the file (in this case core-tab) ; you can still use the plural commands, but splitting is no longer dependent on them Hans changed it to control table splitting completely with split-option in \setuptables and makes to let the normal \starttable-environment split when neccessary. Is there no longer a starttables but simply a starttable initialisation? similar key/val's in setuptables|setuptabulate|setupTABLE And a last question: Why is there a \start - \stop in the example at the Wiki side? because someone needs to edit it -) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
