Re: [NTG-context] minimal example of some problems
1. Leftward protrusion doesn't work.
2. I don't think hz is working in footnotes.
The font I'm using is Adobe Garamond Premiere Pro. If you think there
might be a problem with the typescript, I can show you that too.
These two are related to font. Either show that something is wrong with
default typescripts (lmodern, times, palatino, etc) else it means that
tosmething is wrong with your typescript. But first you have to narrow
down the problem
I take your word for it that it works for the default typescripts;
therefore, the problem must be somewhere in my typescript, but I have
no idea where. It is as follows:
I don't have the font, so I cannot test it.
I should not have been so fast to take your word for it. If I use the
default LM fonts, I get the same problems---no leftward protrusion and
no hz in the footnotes.
You can prevent notes from splitting across pages by
\setupenumerations[footnote]
[before=\vbox\bgroup, after=\egroup]
The footnote may still appear on a different page. If you want to prevent
that add
\setupfootnotes[split=verystrict]
This doesn't work. I'm still getting footnotes appearing on the wrong page.
4. Notice the overprinting near the top of p.2 c.1. That is a
marginal note that should go into the right margin.
\starttext
\startcolumns
\input knuth
\input tufte
\column
\input tufte
\inmargin{This is in wrong margin}
\input knuth
\stopcolumns
\stoptext
The marin note in 2nd column is displayed in the 1st column. This is
artifact of the way in which TeX constructs columns: first creating a
long and narrow page and then splitting it into two. I don't know at
what stage of the OTR are margin notes inserted, and if there is a
workaround. Maybe others can help.
this is the first time someone needs it so indeed there is no mechamism
it's not that complex to deal with it (but i'd only do it in mkiv) gien
time and motivation ... you can put a feature request in the tracker so
that i can look at it when i'm reworking marging notes the mkiv way
(first come floats)
Where is the tracker I should put this in?
I have found another problem which is probably related. In the same
sort of arrangement, two columns with margins on either side, I would
like to place floats like this:
1. If they appear on the left side, they should end at the right edge
of the left column.
2. If they appear on the right side, they should begin at the left
edge of the right column.
Using \placetable[inmargin] (my best guess), this works fine for case
(2), but case (1) begins at the left edge of the left column and can
overprint the right column.
___
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] minimal example of some problems
On Sun, 4 Apr 2010, Michael Saunders wrote: 1. Leftward protrusion doesn't work. 2. I don't think hz is working in footnotes. The font I'm using is Adobe Garamond Premiere Pro. If you think there might be a problem with the typescript, I can show you that too. These two are related to font. Either show that something is wrong with default typescripts (lmodern, times, palatino, etc) else it means that tosmething is wrong with your typescript. But first you have to narrow down the problem I take your word for it that it works for the default typescripts; therefore, the problem must be somewhere in my typescript, but I have no idea where. It is as follows: I don't have the font, so I cannot test it. 3. Observe footnote 1 (the only one). It is breaking between p.1 and p.2. I want to forbid that. I don't know how to prevent this. But again, this has nothing to do with columns or fonts. I want that to work in those columns with that font. If you don't know how to make it work in any font with or without columns, that makes no difference. It looks like it's just one more thing that Context can't do or can't do correctly. You can prevent notes from splitting across pages by \setupenumerations[footnote] [before=\vbox\bgroup, after=\egroup] The footnote may still appear on a different page. If you want to prevent that add \setupfootnotes[split=verystrict] which can mess up the layout. You can slightly salvage things by adding \setuptolerance[vertical, verytolerant] Aditya ___ 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] minimal example of some problems
On Sat, 3 Apr 2010, Michael Saunders wrote:
1. columns and marginal notes conflict:
For some of the issues, it would be perhaps a good idea to make proper
bug-reports (with minimal example of course).
In some other venue?
In a separate thread, with a minimal example, that one can copy-paste and
see the error. Trying to guess what is wrong is difficult.
I tried that several times and got no response. Since you insist on
seeing lots of lorem ipsum, the following example:
This example is not minimal. You are mixing four things
together, and still not giving complete information. Ideally you should
have one **minimal** example for each problem. See below for an
example.
is meant to illustrate four problems:
1. Leftward protrusion doesn't work.
2. I don't think hz is working in footnotes.
The font I'm using is Adobe Garamond Premiere Pro. If you think there
might be a problem with the typescript, I can show you that too.
These two are related to font. Either show that something is wrong with
default typescripts (lmodern, times, palatino, etc) else it means that
tosmething is wrong with your typescript. But first you have to narrow
down the problem
3. Observe footnote 1 (the only one). It is breaking between p.1 and
p.2. I want to forbid that.
I don't know how to prevent this. But again, this has nothing to do with
columns or fonts.
4. Notice the overprinting near the top of p.2 c.1. That is a
marginal note that should go into the right margin.
Here is a minimal example (no page setup, font setup, or styles needed to
show the problem)
\starttext
\startcolumns
\input knuth
\input tufte
\column
\input tufte
\inmargin{This is in wrong margin}
\input knuth
\stopcolumns
\stoptext
The marin note in 2nd column is displayed in the 1st column. This is
artifact of the way in which TeX constructs columns: first creating a long
and narrow page and then splitting it into two. I don't know at what stage
of the OTR are margin notes inserted, and if there is a workaround. Maybe
others can help.
What is the proper way to raise or lower a bit of text? I just spent
...
\raisebox{1ex}{?}
When I try:
\raisebox{1ex}{--}
Context stops on the error:
A box was supposed to be here
\raisebox{1ex}{
--}
Provide a box :-) \raisebox{1ex}{\hbox{--}} (untested)
\raisebox{1em}\hbox{--}
Aditya
___
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] minimal example of some problems
1. Leftward protrusion doesn't work. 2. I don't think hz is working in footnotes. The font I'm using is Adobe Garamond Premiere Pro. If you think there might be a problem with the typescript, I can show you that too. These two are related to font. Either show that something is wrong with default typescripts (lmodern, times, palatino, etc) else it means that tosmething is wrong with your typescript. But first you have to narrow down the problem I take your word for it that it works for the default typescripts; therefore, the problem must be somewhere in my typescript, but I have no idea where. It is as follows: \starttypescript [serif] [optical] [size] \definebodyfont [4pt,5pt,6pt,7pt,8pt,9pt,10pt] [rm] [tf=SerifCaption-Regular sa 1, it=SerifCaption-Italic sa 1] \definebodyfont [11pt,12pt,13pt,14pt,14.4pt] [rm] [tf=SerifRegular-Regular sa 1, it=SerifRegular-Italic sa 1] \definebodyfont [15pt,16pt,17pt,17.3pt,18pt,19pt,20pt,21pt,22pt] [rm] [tf=SerifSubhead-Regular sa 1, it=SerifSubhead-Italic sa 1] \definebodyfont [23pt,24pt,30pt,36pt,48pt,51pt,60pt] [rm] [tf=SerifDisplay-Regular sa 1, it=SerifDisplay-Italic sa 1] \stoptypescript %I don't know what this block is for, but I think it is needed only once. \starttypescript [serif] [garamond] \definefontsynonym [Serif] [SerifRegular-Regular] \definefontsynonym [SerifItalic] [SerifRegular-Italic] \stoptypescript %Garamond (Book)garamond \starttypescript [serif] [garamond] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-Capt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-ItCapt] [features=body] \definefontsynonym [SerifRegular-Regular][file:GaramondPremrPro] [features=body] \definefontsynonym [SerifRegular-Italic] [file:GaramondPremrPro-It] [features=body] \definefontsynonym [SerifSubhead-Regular] [file:GaramondPremrPro-Subh] [features=body] \definefontsynonym [SerifSubhead-Italic] [file:GaramondPremrPro-ItSubh] [features=body] \definefontsynonym [SerifDisplay-Regular] [file:GaramondPremrPro-Disp] [features=body] \definefontsynonym [SerifDisplay-Italic] [file:GaramondPremrPro-ItDisp] [features=body] \stoptypescript \starttypescript [garamond] \definetypeface [garamond] [rm] [serif] [garamond] [optical] \stoptypescript %Garamond MediumgaramondMD \starttypescript [serif] [garamondMD] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-MedCapt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-MedItCapt] [features=body] \definefontsynonym [SerifRegular-Regular] [file:GaramondPremrPro-Med][features=body] \definefontsynonym [SerifRegular-Italic] [file:GaramondPremrPro-MedIt] [features=body] \definefontsynonym [SerifSubhead-Regular] [file:GaramondPremrPro-MedSubh] [features=body] \definefontsynonym [SerifSubhead-Italic] [file:GaramondPremrPro-MedItSubh] [features=body] \definefontsynonym [SerifDisplay-Regular] [file:GaramondPremrPro-MedDisp] [features=body] \definefontsynonym [SerifDisplay-Italic] [file:GaramondPremrPro-MedItDisp] [features=body] \stoptypescript \starttypescript [garamondMD] \definetypeface [garamondMD] [rm] [serif] [garamondMD] [optical] \stoptypescript %Garamond Semi-Bold garamondSB \starttypescript [serif] [garamondSB] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-SmbdCapt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-SmbdItCapt] [features=body] \definefontsynonym [SerifRegular-Regular] [file:GaramondPremrPro-Smbd][features=body] \definefontsynonym [SerifRegular-Italic] [file:GaramondPremrPro-SmbdIt] [features=body] \definefontsynonym [SerifSubhead-Regular] [file:GaramondPremrPro-SmbdSubh] [features=body] \definefontsynonym [SerifSubhead-Italic] [file:GaramondPremrPro-SmbdItSubh] [features=body] \definefontsynonym [SerifDisplay-Regular] [file:GaramondPremrPro-SmbdDisp] [features=body] \definefontsynonym [SerifDisplay-Italic] [file:GaramondPremrPro-SmbdItDisp] [features=body] \stoptypescript \starttypescript [garamondSB] \definetypeface [garamondSB] [rm] [serif] [garamondSB] [optical] \stoptypescript %Garamond Bold garamondBD \starttypescript [serif] [garamondBD] \definefontsynonym [SerifCaption-Regular] [file:GaramondPremrPro-BdCapt] [features=body] \definefontsynonym [SerifCaption-Italic] [file:GaramondPremrPro-BdItCapt] [features=body] \definefontsynonym [SerifRegular-Regular] [file:GaramondPremrPro-Bd][features=body] \definefontsynonym [SerifRegular-Italic]
