[NTG-context] Unexpected changes with pdfeTeX 1.20 (?)

2005-03-01 Thread Steffen Wolfrum
Hi,
while looking closer at the result of typesetting an older (Nov. 
2004) document with todays pdfeTeX and context stuff I noticed that 
the layout of my TOC changed:

Normally I write all setups in a SetupEnvironment file that is loaded 
at the beginning of a project structure.
Like this:

\startproject WLTHR_1
\environment SetupEnvironment_WLTHR
\startfrontmatter
\component Kapitel/Titelei
\component Kapitel/Vorwort
\completecontent
\stopfrontmatter
\startbodymatter
\component Kapitel/Kap_1
\component Kapitel/Kap_2
\component Kapitel/Kap_3
\component Kapitel/Kap_4
\component Kapitel/Kap_5
\stopbodymatter
\startbackmatter
\component Kapitel/Katalog
\component Kapitel/Literatur
\stopbackmatter
\stopproject
But as in SetupEnvironment also \setupindenting is set, now the TOC 
gets this indenting too!
Once (2004, before pdfeTeX 1.20 ?) this didn't affect the generated 
\completecontent - only the real \component files.

Is this change known? Are there more differences like this, so one 
knows what to look for when typesetting older documents with new TeX 
(ConTeXt?) files?

Steffen

A minimal test looks like this:
\starttext
\showframe
\showgrid
\definecombinedlist[content]
[chapter,section][level=section]
\setupindenting[30pt]% 
\completecontent% ---
%\setupindenting[30pt]% 
\chapter{Kapitel}
text
\section{Unterkapitel}
text
\section{Unterkapitel}
text
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] lettrine.sty, but not LaTeX

2005-03-01 Thread VnPenguin
On Mon, 28 Feb 2005 10:34:44 +0100, Taco Hoekwater [EMAIL PROTECTED] wrote:
 
 
 Mats Broberg wrote:
 
  - I tested with the inital H and
  [Lines=4,Hang=.1,Nindent=20pt,Findent=20pt]. This makes the H itself be
  indented too (see enclosed dump). It seems that Findent adds space both
  before and after the dropcap, when it only should add after the dropcap.
 
 That was a bug, so, although I promised I wouldn't do this ... here is
 version four. ;-)
 
  - The text font seems to be defaulted to small capitals. However, this
  is merely one of the conventions how text after a dropcap is set. Other
  conventions include e.g. roman or italic caps, roman or italic lower
  case etc.
 
 You can set the 'TextFont' parameter to something else.
 
  - Regarding the slope one should be able to set indentation separately
  for each line. This depends on the fact that some characters call for a
  different type of intendation of the lines - e.g. the character L.
 
 I will keep this in mind for a future extension
 
  - Sometimes there is a need to indent the dropcap slightly itself, e.g.
  if one uses a quotation mark before the dropcap. So a parameter to
  control that would be great.
 
 You can set the 'Hang' parameter to a negative value.
 
 Greetings, Taco

Just tried the following code:
-
\starttext
\placefigure[right]{none}{\externalfigure[foo][width=4cm,height=4cm]}
Voici a very silly \input tufte

\blank[1cm]

\placefigure[right]{none}{\externalfigure[foo][width=4cm,height=4cm]}
\lettrine {V}{oici} a very silly \input tufte
\stoptext
--
There is a strange behaviour of \placefigure[right] when using
\lettrine (see PDF at http://people.vnoss.org/~vnpenguin/pub/context/drop.pdf )

Any ideas ?

Thanks,
Q.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] lettrine.sty, but not LaTeX

2005-03-01 Thread Taco Hoekwater
VnPenguin wrote:
There is a strange behaviour of \placefigure[right] when using
\lettrine (see PDF at http://people.vnoss.org/~vnpenguin/pub/context/drop.pdf )
Any ideas ?
Unfortunately, this cannot be helped.  It is a limitation
of the \parshape primitive.
Greetings, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Unexpected changes with pdfeTeX 1.20 (?)

2005-03-01 Thread h h extern
Steffen Wolfrum wrote:
Hi,
while looking closer at the result of typesetting an older (Nov. 2004) 
document with todays pdfeTeX and context stuff I noticed that the layout 
of my TOC changed:

Normally I write all setups in a SetupEnvironment file that is loaded at 
the beginning of a project structure.
Like this:

\startproject WLTHR_1
\environment SetupEnvironment_WLTHR
\startfrontmatter
\component Kapitel/Titelei
\component Kapitel/Vorwort
\completecontent
\stopfrontmatter
\startbodymatter
\component Kapitel/Kap_1
\component Kapitel/Kap_2
\component Kapitel/Kap_3
\component Kapitel/Kap_4
\component Kapitel/Kap_5
\stopbodymatter
\startbackmatter
\component Kapitel/Katalog
\component Kapitel/Literatur
\stopbackmatter
\stopproject
But as in SetupEnvironment also \setupindenting is set, now the TOC gets 
this indenting too!
Once (2004, before pdfeTeX 1.20 ?) this didn't affect the generated 
\completecontent - only the real \component files.

Is this change known? Are there more differences like this, so one knows 
what to look for when typesetting older documents with new TeX 
(ConTeXt?) files?

Steffen

A minimal test looks like this:
\starttext
\showframe
\showgrid
\definecombinedlist[content]
[chapter,section][level=section]
\setupindenting[30pt]% 
\completecontent% ---
%\setupindenting[30pt]% 
\chapter{Kapitel}
text
\section{Unterkapitel}
text
\section{Unterkapitel}
text
\stoptext
fix (\dontleavehmode - \noindent) in core-sec.tex; you can put the patch in 
cont-new.tex if you have a recent version

\def\dodofixdlistelementABC#1#2#3#4#5#6% weeden
  {\endgraf
   \leftskip\listparameter\c!margin% na de \endgraf !
   \listparameter\c!before
   \!!widthc\listparameter\c!distance
   \doifelse{\listparameter\c!width}\v!fit
 {\!!widtha\zeropoint}
 {\doifelsenothing{#3}
{\doifelse{\listparameter\c!aligntitle}\v!yes
   {\!!widtha\zeropoint
\!!widthc\zeropoint}
   {\!!widtha\listparameter\c!width}}
{\!!widtha\listparameter\c!width}}%
   \getvalue{\??li\c!alternative\listparameter\c!alternative}%
   \endgraf
   \def\makelistelement##1##2%
 {\doifelse{\listparameter\c!interaction}{##1}
{\setbox0\hbox{\showcontrastlocation\??ia{#6}{##2}}%
 \linklisttoelement{#2}{#5}{#6}{\box0}}%{\copy0}}%
{\hbox{##2}}}%
   \doif{\listparameter\c!interaction}\v!text % not supported
 {\setlistparameter\currentlist\c!interaction\v!all}%
 % \dontleavehmode % new, else no margin, but wrong
   \noindent
   \makelistelement\v!all
 {\setlocalhsize \hsize\localhsize \hbox to \hsize
{\forgetall
 \dostartlistattributes\c!style\c!color\empty
 \!!widthb\hsize
 \setbox2\hbox \ifdim\!!widtha\zeropoint to \!!widtha \fi
   {\makelistelement\v!sectionnumber
  {\donestedlistattributes\c!numberstyle\c!numbercolor
 {\listparameter\c!numbercommand{\currentlistsymbol}}%
\hfill}}%
 \setbox4\hbox
   {\doif{\listparameter\c!pagenumber}\v!yes
  {\doifsomething{#5}% \listwidth is new ; temp hack
 {\hbox \ifdim\listwidth\zeropoint to \listwidth\fi
{\hfill
 \makelistelement\v!pagenumber
   {\donestedlistattributes\c!pagestyle\c!pagecolor
  {\listparameter\c!pagecommand
 {\pageprefix\??li\currentlist[#5]%
  \translatednumber[#5]}}}%
 \vbox
   {\hsize\!!widthb
\setupalign[\listparameter\c!align]%
\ifdim\!!widtha\hsize
  \hangindent\wd2
  \dimen2=\!!widthc % \listparameter\c!distance
  \advance\hangindent \dimen2
  \hangafter\plusone
  \doif{\listparameter\c!hang}\v!no{\hangafter\zerocount}%
  \ifdim\wd4=\zeropoint % \ifvoid4
% we kunnen gewoon afbreken aan het eind
  \else
\ifdim\listskip\zeropoint\relax
  \rightskip\listskip\!!plus10em\relax
  \parfillskip-\rightskip
\fi
  \fi
\else
  \dimen2\zeropoint
\fi
\parindent\zeropoint\relax
\leavevmode
\box2\relax
\hskip\dimen2
\bgroup
\donestedlistattributes\c!textstyle\c!textcolor
  {\let\\=\newlineinlist
   \dontconvertfont
  %\listparameter\c!textcommand{#4}}%
   \limitatedlistentry{#4}}%
  %\carryoverpar % new otherwise wrong linespacing
\egroup
\ifdim\wd4=\zeropoint\relax % \ifvoid4
  % \ifdim\!!widtha\hsize \hfill\strut \fi % spoils align
\else
  \nobreak\listfill
  \box4\relax
  \relax
\fi}%
 \hss
 \dostoplistattributes}}% new
   

Re: [NTG-context] lettrine.sty, but not LaTeX

2005-03-01 Thread Ciro A. Soto
trivial question from a novice:
What are the steps to use a new module 
like the lettrine.sty? Where do I put this file?
what command should I type to make is available to
context? etc...
thank you
ciro

PS: I am using Fedora Core 3 + texlive2004 + context
from February 2005.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] lettrine.sty, but not LaTeX

2005-03-01 Thread VnPenguin
On Tue, 1 Mar 2005 14:37:21 -0800 (PST), Ciro A. Soto
[EMAIL PROTECTED] wrote:
 trivial question from a novice:
 What are the steps to use a new module
 like the lettrine.sty? Where do I put this file?
 what command should I type to make is available to
 context? etc...
 thank you
 ciro
 
 PS: I am using Fedora Core 3 + texlive2004 + context
 from February 2005.

In teTeX 3.0 (FC3 box) I put the file  t-lettri.tex in
$HOME/texmf/tex/context/user/ and run command texhash. That's all :)

HTH,
Q.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] small caps

2005-03-01 Thread Thomas A . Schmitz
Adam, I feel like a complete idiot now. I had been so proud about this 
idea, but after re-reading you MyWay about OpenType, I see that I had 
been reinventing the wheel: this is exactly the solution you had been 
suggesting almost two years ago. Thanks for being generous about 
this...

However, your post made me think: I know nothing about XSLT, but enough 
perl to shoot myself in the foot. I guess if I had a version of 
texnansi.enc with the unicode values in addition to the names, that 
would be a good starting point. I was thinking of  this route:
1. use ftxdumperfuser to produce cmap.xml,
2. use perl to reduce it to two values: glyphName % UNICODE_VALUE
3. use perl to extract the lines corresponding to a given encoding and 
put them in the right order.

Sounds feasible? Do you know where I could get such a unicode-aware 
version of texnansi.enc?

Best
Thomas
On Feb 27, 2005, at 10:39 AM, Adam Lindsay wrote:
Indeed, that's one of the reasons why I came up with the unicode
(symbol[1]) scripts... there are common utilities (ttx and Apple's 
ftx
suite) that work well at associating canonical characters with glyph
names specific to a font.

I'm sure some enterprising XSLT hacker could take my scripts as a
starting point and make them work with specific TeXy encodings, not 
just
individual Unicode vectors.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] FO and ConTeXt: my new wiki page

2005-03-01 Thread Paul Tremblay
I have a new page on the wiki  

http://contextgarden.net/Page_layout

This page is my best effort at describing how someone who is used to FO
would do the same thing in ConTeXt. The page is just one of many I hope
to write on FO and ConTeXt.

I'm sure I got some things wrong, so any help would be appreciated.

One thing I was not able to do was customize headers and footers for
blank pages that end a part (such as a chapter). I need to include a
section in my page describing my inability to do this.

Thanks

Paul


-- 


*Paul Tremblay *
[EMAIL PROTECTED]*

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context