Re: [NTG-context] post-commit hook for contextman
Fixed. Fabrice 2010/6/27 Taco Hoekwater t...@elvenkind.com Hi Fabrice, On 06/27/2010 09:13 AM, Peter Münster wrote: On Mon, Jun 07 2010, Taco Hoekwater wrote: Is it possible, to get email on every commit to http://foundry.supelec.fr/gf/project/contextman ? Sure. Subscribe to the Lists - contextman-commits mailing list Hello, The list seems to be broken. I don't get any email... Can you check this list please? The last message I have received from it was in April last year, so I guess that was still on the old software. TIA, Taco ___ 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 ___
Re: [NTG-context] s-pre-02 looks a bit weird in TL2010
On 06/27/2010 11:14 AM, Vedran Miletić wrote: Hi, upon compiling s-pre-02 with TL2010 ConTeXt, I get the attached file which is very narrow and text gets cut off (at least when viewed in Evince). Is this a bug? Yeah, I would say so. Same thing happens in the latest beta context. Best wishes, Taco ___ 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 ___
Re: [NTG-context] Page numbering in Adobe Reader
Am 28.06.2010 um 07:45 schrieb Steffen Wolfrum: But the example file that is mentioned in that link don't produce anything with MkII either: TeXExec | no ctx file found TeXExec | nothing to process Ahh! There was a space in the file's name, thus... Now it works. Steffen ___ 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 ___
[NTG-context] unusable PDF bookmarks
Hi,
is there a way to avoid bookmark entries like this?
With language is german and encoding utf8 MkII compiles this ...
\section{Test~–~Nummer §\,613\,a}
... to:
TestCCC:4:126 dochar {123}CCC:4:126 Nummer elax $unhbox vo...@x hbox
{$mathsurround z@ mathchar 278$}$ extormathspace + hinmuskip 1613
extormathspace + hinmuskip 1a
Steffen
___
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
___
[NTG-context] Tagged PDF
Am 20.01.2009 um 16:19 schrieb Arthur Reutenauer: Tagged PDF is indeed a problem for the moment, but it's clearly not the feature your printer asks for, and as a rule, you can be sure that if some functionality is essential to publishers, it will be added quickly to ConTeXt :-) Hi Hans, these wise words were written 1 1/2 years ago ... and publishers indeed more and more often ask for that! For me, the only way to do tagging is with AcrobatPro. But as LuaTeX made so much progress in the last 18 month, maybe is there also some break-through on this topic? Steffen ___ 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 ___
Re: [NTG-context] Tagged PDF
--- Original message --- Subject: Tagged PDF From: Steffen Wolfrum cont...@st.estfiles.de To: mailing list for ConTeXt users ntg-context@ntg.nl Cc: Hans Hagen pra...@wxs.nl Date: Monday, 28/06/2010 7:17 AM Am 20.01.2009 um 16:19 schrieb Arthur Reutenauer: Tagged PDF is indeed a problem for the moment, but it's clearly not the feature your printer asks for, and as a rule, you can be sure that if some functionality is essential to publishers, it will be added quickly to ConTeXt :-) Hi Hans, these wise words were written 1 1/2 years ago ... and publishers indeed more and more often ask for that! For me, the only way to do tagging is with AcrobatPro. But as LuaTeX made so much progress in the last 18 month, maybe is there also some break-through on this topic? no as i don't need it and it's not something you implement for fun (only as part of a project) .. it's quite doable (unrelated to luatex i think) but boring Hans ___ 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 ___
Re: [NTG-context] unusable PDF bookmarks
On Monday 28/06/2010 at 4:50 am, Steffen Wolfrum wrote:
Hi,
is there a way to avoid bookmark entries like this?
With language is german and encoding utf8 MkII compiles this ...
\section{Test~–~Nummer §\,613\,a}
\startsection[...,bookmark=]
___
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
___
[NTG-context] \numstr errors out in chapter star logic
\numstr seems to work fine in the body of text but errors out as if #1 was
not a number when it is used in chapter start loc. Here is an example:
%\numstr begins here
\unprotect
\def\numstring#1{\expandaft...@numstring\csname c...@#1\endcsname}
\d...@numstring#1{\ns@numstr{#1}...@nineteens{null}{}}
\let\nums...@numstring%
\def...@numoutofrange#1#2{\number#1#2}
\def...@numstr#1#2#3#4%
{\ifnum\number#1\plusone%
#3%
\else\ifnum\number#110 %
\expandafter...@numstring\expandafter{\number#1}#2%
\else%
\...@numoutofrange{#1}{#4}%
\fi\fi}
\def...@numstring#1#2{%
\expandafter\ns@@numstring%
\ifcase%
\ifnum#110 1%
\else\ifnum#1100 2%
\else\ifnum#1\...@m 3%
\else\ifnum#1\...@m 4%
\else\ifnum#110 5%
\else\ifnum#1100 6%
\else\ifnum#11000 7%
\else\ifnum#11 8%
\else9%
\fi\fi\fi\fi\fi\fi\fi\fi %
\or#1% case 1: Add 8 leading zeros
\or000#1% case 2: Add 7 leading zeros
\or00#1% case 3: Add 6 leading zeros
\or0#1%case 4: Add 5 leading zeros
\or#1% case 5: Add 4 leading zeros
\or000#1% case 6: Add 3 leading zeros
\or00#1% case 7: Add 2 leading zeros
\or0#1%case 8: Add 1 leading zero
\or#1% case 9: Add no leading zeros
\or%
\...@nil#2%
\fi}
\def\ns@@numstring#1#2#3#4#5#6#7\or...@nil#9%
{\ifnum#1#2#3\z@
\...@million#1#2#3%
\ifnum#4#5#6\...@\space\fi%
\fi%
\ifnum#4#5#6\...@%
\...@hundred#4#5#6{#1#2#3}{#4#5}\ns@nineteen%
\ifnum#4#5#6\...@\space\fi%
thousand%
\ifnum#7\...@\space\fi%
\fi%
\...@hundred#7{#4#5#6}1#9}
\def...@million#1#2#3%
{\ifnum#1#2#3=\plusone%
\...@hundred#1#2#301\ns@nineteene%
\space%
million%
\else%
\...@hundred#1#2#301\ns@nineteens%
\space%
millions%
\fi}
\def...@hundred#1#2#3#4#5#6%
{\ifnum#1\...@%
\ifnum#4#1\...@\ns@nineteen#1\space\fi%
hundred%
\ifnum#2#3\...@\space and\space\fi%
\fi%
\ifnum#2#320 %
\ifnum#5#2#3\...@#6{#2#3}\fi%
\else%
\...@ninety#2\ifnum#3\...@-\ns@nineteen#3\fi%
#60%
\fi}
\def...@nineteen#1%
{\ifcase#1\empty\or one\or two\or three\or four\or five\or six\or%
seven\or eight\or nine\or ten\or eleven\or twelve\or thirteen\or%
fourteen\or fifteen\or sixteen\or seventeen\or%
eighteen\or nineteen\fi}
\def...@nineteens#1{\ns@nineteen{#1}}
\def...@nineteene#1{\ns@nineteen{#1}}
\def...@ninety#1%
{\ifcase#1
\or
\or twenty%
\or thirty%
\or forty%
\or fifty%
\or sixty%
\or seventy%
\or eighty%
\or ninety%
\fi}
\protect
\def\MyChapterCommandA#1#2% #1 is number, #2 is text
{\numstr{#1}}
\def\MyChapterCommandB#1#2% #1 is number, #2 is text
{#1 #2}
\setuphead[chapter]
[command=\MyChapterCommandA] %change A to B to eliminate \substr call
\starttext
\chapter{First Chapter}
Some sample text. Chapter \numstr{1} numstr logic works correctly when
embedded in the text. Chapter title displays correctly when numstr not in
chapter start logic. Errors out when numstr is in chapter start logic as if
parameter is not a number.
\stoptext
Tom Benjey
717-258-9733 voice
717-243-0074 fax
Twitter: @TomBenjey
___
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
___
[NTG-context] direction in columnset (MKII)
Hi all, Is it possible to tell columnsets which column is the first one? I use columnset in MKII to typeset Arabic text in a multicolumn layout and the text starts in the left column. Is there a nice way to force the text to start in the right column? Something like \definecolumnset[arabic][n=2,direction=right] doesn't work. (A nasty, ugly hack is fine too ;-) Example: \starttext \definecolumnset[arabic][n=2,direction=right] \startcolumns[arabic] Oeps. In Arabic the 'first' column is on the right: \input knuth \stopcolumns \stoptext Thanks, Jelle ___ 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 ___
Re: [NTG-context] \numstr errors out in chapter star logic
Am 28.06.10 17:59, schrieb Tom: \numstr seems to work fine in the body of text but errors out as if #1 was not a number when it is used in chapter start loc. Here is an example: [...] \setuphead[chapter] [command=\MyChapterCommandA] %change A to B to eliminate \substr call Try \setuphead[chapter][deepnumbercommand=\numstr] Wolfgang ___ 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 ___
Re: [NTG-context] direction in columnset (MKII)
Am 28.06.10 18:39, schrieb Jelle Huisman: Hi all, Is it possible to tell columnsets which column is the first one? I use columnset in MKII to typeset Arabic text in a multicolumn layout and the text starts in the left column. Is there a nice way to force the text to start in the right column? Something like \definecolumnset[arabic][n=2,direction=right] doesn't work. (A nasty, ugly hack is fine too ;-) Example: \starttext \definecolumnset[arabic][n=2,direction=right] \startcolumns[arabic] Oeps. In Arabic the 'first' column is on the right: \input knuth \stopcolumns \stoptext It makes no sense to set values for columnset but use regular columns in your document and the correct value for direction you want is 'left' not 'right'. \starttext % columnset \definecolumnset[arabic][n=2,direction=left] \startcolumnset[arabic] Oeps. In Arabic the 'first' column is on the right:\par\column\input knuth \stopcolumnset \page % columns \startcolumns[direction=left] Oeps. In Arabic the 'first' column is on the right:\par\column\input knuth \stopcolumns \stoptext Wolfgang ___ 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 ___
Re: [NTG-context] \numstr errors out in chapter star logic
Am 28.06.10 17:59, schrieb Tom:
\numstr seems to work fine in the body of text but errors out as if #1 was
not a number when it is used in chapter start loc. Here is an example:
[...]
\setuphead[chapter]
[command=\MyChapterCommandA] %change A to B to eliminate \substr call
Try \setuphead[chapter][deepnumbercommand=\numstr]
Wolfgang
Making the following changes resulted in ! Missing Number, treated as zero.
%\def\MyChapterCommandA#1#2% #1 is number, #2 is text
% {\numstr{#1}}
%\def\MyChapterCommandB#1#2% #1 is number, #2 is text
% {#1 #2}
\setuphead[chapter]
[deepnumbercommand=\numstr]
Tom Benjey
717-258-9733 voice
717-243-0074 fax
Twitter: @TomBenjey
___
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
___
Re: [NTG-context] \numstr errors out in chapter star logic
Am 28.06.10 23:03, schrieb Tom:
Making the following changes resulted in ! Missing Number, treated as zero.
I’m lazy:
\defineconversion[numstring][One,Two,Three,Four,Five,Six,Seven,Eight,Nine,Ten,...]
\setuphead[chapter][conversion=numstring]
\starttext
\dorecurse{11}{\chapter{Chapter #1}}
\stoptext
Wolfgang
___
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
___
Re: [NTG-context] Problem with large space after section header
On Mon, Jun 28 2010, Aditya Mahajan wrote:
On Mon, 28 Jun 2010, Jason Earl wrote:
In my defense, part of the reason that I did not think of putting in a
manual page break before the section is that my real context documents
are generated from a script, and I did not want to have to process the
output by hand to solve these sorts of problems. I was hoping for some
sort of magic that I could put after every section heading that would
make Context try harder to keep the content close to the header.
However, while I don't pretend to be an expert at typesetting I do
understand that automating this stuff is hard, and sometimes there is no
real way to fix issues like this. If I have to do a little hand
massaging of the output that's acceptable.
In an automated setup, you can try
\setuphead[section][before={\blank\testpage[4]}]
\testpage[n] tests if there is enough space to put n lines in the
current page. If not, it insearts a pagebreak. Play around with n to
see what gives best result.
Thank you so much. That looks like it is going to solve the most
problematic spaces without having to manually insert page breaks. In
fact, to my untutored eye even without playing with the numbers it looks
perfect. That was precisely the magic I needed, and it even came with
an explanation that should help me solve similar problems myself in the
future.
Thanks to Wolfgang for responding as well. I am sorry I was not more
clear with my original report.
Thanks again,
Jason
___
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
___
