Mixing
Why does the baseline skip depend on the letters depth in some fonts?
Clash Royale CLAN TAG#URR8PPP
up vote
4
down vote
favorite
I have some trouble with the line high using an OTF with fontspec package.
The baseline skip of a line differs depending on the depth of the used letter. So for example a line containing a »g« is some points higher than another one containing only letters without a depth.
The screen shot shows the strange behavior: You can easily see that on the second page the first line is a little lower than on the first page. The only difference between both is the lowercase »g« in the title.
The font I am actually using is »Adobe Garamond Pro« but I have tested with other fonts such as »Minion Pro« experiencing the same effect.
However, the effect does not occur without using fontspec. Here is an example, that of course only works were the font is present:
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
Can somebody explain to me, what is happening here, dnd give me a hint, how to work around?
xetex fontspec grid-typesetting baseline
asked 1 hour ago
user5950
693521
add a comment |Â
up vote
4
down vote
favorite
I have some trouble with the line high using an OTF with fontspec package.
The baseline skip of a line differs depending on the depth of the used letter. So for example a line containing a »g« is some points higher than another one containing only letters without a depth.
The screen shot shows the strange behavior: You can easily see that on the second page the first line is a little lower than on the first page. The only difference between both is the lowercase »g« in the title.
The font I am actually using is »Adobe Garamond Pro« but I have tested with other fonts such as »Minion Pro« experiencing the same effect.
However, the effect does not occur without using fontspec. Here is an example, that of course only works were the font is present:
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
Can somebody explain to me, what is happening here, dnd give me a hint, how to work around?
xetex fontspec grid-typesetting baseline
asked 1 hour ago
user5950
693521
I don't have Garamond Pro, but problem confirmed for another common font,setmainfontPalatino Linotype, using XeLaTeX
– Steven B. Segletes
1 hour ago
2
For reference, the problem also arises withbegindocument chapterTest what ever but lonsmashger even lonsmashger much lonsmashger Test lipsum[2-4] chapterTest what ever but longer even longer much longer Test lipsum[2-4] enddocument
– Steven B. Segletes
1 hour ago
It would be easier to debug if you could show an example with a generally available font, but I would guess looking at the image that if you addshowoutputyou will seelineskipglue being added.lineskipis only added when tex has an otherwise infeasible constraint and the material it is adding is already larger than the specified baselineskip, so it gives up trying to maintain an even baseline and just insertslineskipbetween the rows. If that is the case you just need to make the text smaller or thebaselineskiplarger, depending...
– David Carlisle
56 mins ago
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I have some trouble with the line high using an OTF with fontspec package.
The baseline skip of a line differs depending on the depth of the used letter. So for example a line containing a »g« is some points higher than another one containing only letters without a depth.
The screen shot shows the strange behavior: You can easily see that on the second page the first line is a little lower than on the first page. The only difference between both is the lowercase »g« in the title.
The font I am actually using is »Adobe Garamond Pro« but I have tested with other fonts such as »Minion Pro« experiencing the same effect.
However, the effect does not occur without using fontspec. Here is an example, that of course only works were the font is present:
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
Can somebody explain to me, what is happening here, dnd give me a hint, how to work around?
xetex fontspec grid-typesetting baseline
asked 1 hour ago
user5950
693521
I have some trouble with the line high using an OTF with fontspec package.
The baseline skip of a line differs depending on the depth of the used letter. So for example a line containing a »g« is some points higher than another one containing only letters without a depth.
The screen shot shows the strange behavior: You can easily see that on the second page the first line is a little lower than on the first page. The only difference between both is the lowercase »g« in the title.
The font I am actually using is »Adobe Garamond Pro« but I have tested with other fonts such as »Minion Pro« experiencing the same effect.
However, the effect does not occur without using fontspec. Here is an example, that of course only works were the font is present:
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
Can somebody explain to me, what is happening here, dnd give me a hint, how to work around?
xetex fontspec grid-typesetting baseline
xetex fontspec grid-typesetting baseline
asked 1 hour ago
user5950
693521
asked 1 hour ago
user5950
693521
asked 1 hour ago
user5950
693521
asked 1 hour ago
user5950
693521
asked 1 hour ago
user5950
693521
693521
I don't have Garamond Pro, but problem confirmed for another common font,setmainfontPalatino Linotype, using XeLaTeX
– Steven B. Segletes
1 hour ago
2
For reference, the problem also arises withbegindocument chapterTest what ever but lonsmashger even lonsmashger much lonsmashger Test lipsum[2-4] chapterTest what ever but longer even longer much longer Test lipsum[2-4] enddocument
– Steven B. Segletes
1 hour ago
It would be easier to debug if you could show an example with a generally available font, but I would guess looking at the image that if you addshowoutputyou will seelineskipglue being added.lineskipis only added when tex has an otherwise infeasible constraint and the material it is adding is already larger than the specified baselineskip, so it gives up trying to maintain an even baseline and just insertslineskipbetween the rows. If that is the case you just need to make the text smaller or thebaselineskiplarger, depending...
– David Carlisle
56 mins ago
add a comment |Â
I don't have Garamond Pro, but problem confirmed for another common font,setmainfontPalatino Linotype, using XeLaTeX
– Steven B. Segletes
1 hour ago
2
For reference, the problem also arises withbegindocument chapterTest what ever but lonsmashger even lonsmashger much lonsmashger Test lipsum[2-4] chapterTest what ever but longer even longer much longer Test lipsum[2-4] enddocument
– Steven B. Segletes
1 hour ago
It would be easier to debug if you could show an example with a generally available font, but I would guess looking at the image that if you addshowoutputyou will seelineskipglue being added.lineskipis only added when tex has an otherwise infeasible constraint and the material it is adding is already larger than the specified baselineskip, so it gives up trying to maintain an even baseline and just insertslineskipbetween the rows. If that is the case you just need to make the text smaller or thebaselineskiplarger, depending...
– David Carlisle
56 mins ago
I don't have Garamond Pro, but problem confirmed for another common font,
setmainfontPalatino Linotype, using XeLaTeX– Steven B. Segletes
1 hour ago
I don't have Garamond Pro, but problem confirmed for another common font,
setmainfontPalatino Linotype, using XeLaTeX– Steven B. Segletes
1 hour ago
2
2
For reference, the problem also arises with
begindocument chapterTest what ever but lonsmashger even lonsmashger much lonsmashger Test lipsum[2-4] chapterTest what ever but longer even longer much longer Test lipsum[2-4] enddocument– Steven B. Segletes
1 hour ago
For reference, the problem also arises with
begindocument chapterTest what ever but lonsmashger even lonsmashger much lonsmashger Test lipsum[2-4] chapterTest what ever but longer even longer much longer Test lipsum[2-4] enddocument– Steven B. Segletes
1 hour ago
It would be easier to debug if you could show an example with a generally available font, but I would guess looking at the image that if you add
showoutput you will see lineskip glue being added. lineskip is only added when tex has an otherwise infeasible constraint and the material it is adding is already larger than the specified baselineskip, so it gives up trying to maintain an even baseline and just inserts lineskip between the rows. If that is the case you just need to make the text smaller or the baselineskip larger, depending...– David Carlisle
56 mins ago
It would be easier to debug if you could show an example with a generally available font, but I would guess looking at the image that if you add
showoutput you will see lineskip glue being added. lineskip is only added when tex has an otherwise infeasible constraint and the material it is adding is already larger than the specified baselineskip, so it gives up trying to maintain an even baseline and just inserts lineskip between the rows. If that is the case you just need to make the text smaller or the baselineskip larger, depending...– David Carlisle
56 mins ago
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
3
down vote
Taking Steven's modified example, as I hav ethe font, then if you add some debug messages
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapter[zz]Test what ever but lon er even lon er much lon er
Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
chapterTest what ever but longer even longer much longer Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
enddocument
Then you get
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
0.78989pt
7.94809pt
[1]
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
5.54956pt
12.70776pt
[2]
TeX is being asked to set the first line of the paragraph to a 12pt baselineskip from the baseline of the previous thing. In the first case that means that the actual added baselineskip glue will be just over 4pt, however in the second case even if teh line was abutted directly after the heading there would be 12.7pt baseline separation, in this case TeX does not back up and over-print to force the requested baseline, instead it gives up on baselineskip and inserts the fixed lineskip glue that does not depend on the heigh and depth of the lines it is separating. lineskip is usually 0pt or 1pt but whatever value it has, if it is added it means that there is inconsistent spacing in the output.
answered 33 mins ago
David Carlisle
468k3810961821
add a comment |Â
up vote
3
down vote
Apparently, the font has large descenders (and perhaps also large ascenders).
A small adjustment of the leading will solve the issue. In this example I used Minion Pro, as I don't have Adobe Garamond Pro.
The humoungous setting to lineskip is meant to show that the parameter doesn't enter into action (if it does, you'd see a very big vertical space).
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec
setmainfontMinion Pro
linespread1.02 % increase the leading by 2%
begindocument
setlengthlineskip30pt % just for testing
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
With the linespread adjustment
Without the linespread adjustment
Here you see the 30pt added space because of lineskip entering the scene.
answered 32 mins ago
egreg
684k8418243069
add a comment |Â
up vote
2
down vote
As noted in my comment, I don't have Garamond Pro, but problem confirmed for another common font, setmainfontPalatino Linotype, using XeLaTeX
I presume the chapter title is placed in a box without a strut, so that descender depth affects the overall box depth. One solution is to add a strut to the end of each chapter title.
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er
Teststrut
lipsum[2-4]
chapterTest what ever but longer even longer much longer Teststrut
lipsum[2-4]
enddocument
answered 56 mins ago
Steven B. Segletes
147k9186389
@DavidCarlisle I have never usedshowoutputbefore. What exactly am I looking for? I see a line..glue(lineskip) 0.0another...glue(lineskip) 1.0, then..glue(lineskip) 0.0and again a...glue(lineskip) 1.0
– Steven B. Segletes
50 mins ago
yep I have the font (didn't realise:-) adding the strut makes the descender on thegnot matter but at the cost of giving the bad case all the time (so it's consistent but ...)
– David Carlisle
49 mins ago
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Taking Steven's modified example, as I hav ethe font, then if you add some debug messages
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapter[zz]Test what ever but lon er even lon er much lon er
Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
chapterTest what ever but longer even longer much longer Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
enddocument
Then you get
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
0.78989pt
7.94809pt
[1]
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
5.54956pt
12.70776pt
[2]
TeX is being asked to set the first line of the paragraph to a 12pt baselineskip from the baseline of the previous thing. In the first case that means that the actual added baselineskip glue will be just over 4pt, however in the second case even if teh line was abutted directly after the heading there would be 12.7pt baseline separation, in this case TeX does not back up and over-print to force the requested baseline, instead it gives up on baselineskip and inserts the fixed lineskip glue that does not depend on the heigh and depth of the lines it is separating. lineskip is usually 0pt or 1pt but whatever value it has, if it is added it means that there is inconsistent spacing in the output.
answered 33 mins ago
David Carlisle
468k3810961821
add a comment |Â
up vote
3
down vote
Taking Steven's modified example, as I hav ethe font, then if you add some debug messages
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapter[zz]Test what ever but lon er even lon er much lon er
Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
chapterTest what ever but longer even longer much longer Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
enddocument
Then you get
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
0.78989pt
7.94809pt
[1]
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
5.54956pt
12.70776pt
[2]
TeX is being asked to set the first line of the paragraph to a 12pt baselineskip from the baseline of the previous thing. In the first case that means that the actual added baselineskip glue will be just over 4pt, however in the second case even if teh line was abutted directly after the heading there would be 12.7pt baseline separation, in this case TeX does not back up and over-print to force the requested baseline, instead it gives up on baselineskip and inserts the fixed lineskip glue that does not depend on the heigh and depth of the lines it is separating. lineskip is usually 0pt or 1pt but whatever value it has, if it is added it means that there is inconsistent spacing in the output.
answered 33 mins ago
David Carlisle
468k3810961821
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Taking Steven's modified example, as I hav ethe font, then if you add some debug messages
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapter[zz]Test what ever but lon er even lon er much lon er
Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
chapterTest what ever but longer even longer much longer Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
enddocument
Then you get
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
0.78989pt
7.94809pt
[1]
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
5.54956pt
12.70776pt
[2]
TeX is being asked to set the first line of the paragraph to a 12pt baselineskip from the baseline of the previous thing. In the first case that means that the actual added baselineskip glue will be just over 4pt, however in the second case even if teh line was abutted directly after the heading there would be 12.7pt baseline separation, in this case TeX does not back up and over-print to force the requested baseline, instead it gives up on baselineskip and inserts the fixed lineskip glue that does not depend on the heigh and depth of the lines it is separating. lineskip is usually 0pt or 1pt but whatever value it has, if it is added it means that there is inconsistent spacing in the output.
answered 33 mins ago
David Carlisle
468k3810961821
Taking Steven's modified example, as I hav ethe font, then if you add some debug messages
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapter[zz]Test what ever but lon er even lon er much lon er
Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
chapterTest what ever but longer even longer much longer Test
expandaftertypeoutexpandafterthefont
expandaftertypeoutexpandafterthebaselineskip
expandaftertypeoutexpandafterthefontcharhtfont`N
expandaftertypeoutexpandaftertheprevdepth
expandaftertypeoutexpandafterthedimexprprevdepth +fontcharhtfont`Trelax
lipsum[2-4]
enddocument
Then you get
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
0.78989pt
7.94809pt
[1]
TU/PalatinoLinotype(0)/m/n/10
12.0pt
7.1582pt
5.54956pt
12.70776pt
[2]
TeX is being asked to set the first line of the paragraph to a 12pt baselineskip from the baseline of the previous thing. In the first case that means that the actual added baselineskip glue will be just over 4pt, however in the second case even if teh line was abutted directly after the heading there would be 12.7pt baseline separation, in this case TeX does not back up and over-print to force the requested baseline, instead it gives up on baselineskip and inserts the fixed lineskip glue that does not depend on the heigh and depth of the lines it is separating. lineskip is usually 0pt or 1pt but whatever value it has, if it is added it means that there is inconsistent spacing in the output.
answered 33 mins ago
David Carlisle
468k3810961821
answered 33 mins ago
David Carlisle
468k3810961821
answered 33 mins ago
David Carlisle
468k3810961821
answered 33 mins ago
David Carlisle
468k3810961821
468k3810961821
add a comment |Â
add a comment |Â
up vote
3
down vote
Apparently, the font has large descenders (and perhaps also large ascenders).
A small adjustment of the leading will solve the issue. In this example I used Minion Pro, as I don't have Adobe Garamond Pro.
The humoungous setting to lineskip is meant to show that the parameter doesn't enter into action (if it does, you'd see a very big vertical space).
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec
setmainfontMinion Pro
linespread1.02 % increase the leading by 2%
begindocument
setlengthlineskip30pt % just for testing
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
With the linespread adjustment
Without the linespread adjustment
Here you see the 30pt added space because of lineskip entering the scene.
answered 32 mins ago
egreg
684k8418243069
add a comment |Â
up vote
3
down vote
Apparently, the font has large descenders (and perhaps also large ascenders).
A small adjustment of the leading will solve the issue. In this example I used Minion Pro, as I don't have Adobe Garamond Pro.
The humoungous setting to lineskip is meant to show that the parameter doesn't enter into action (if it does, you'd see a very big vertical space).
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec
setmainfontMinion Pro
linespread1.02 % increase the leading by 2%
begindocument
setlengthlineskip30pt % just for testing
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
With the linespread adjustment
Without the linespread adjustment
Here you see the 30pt added space because of lineskip entering the scene.
answered 32 mins ago
egreg
684k8418243069
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Apparently, the font has large descenders (and perhaps also large ascenders).
A small adjustment of the leading will solve the issue. In this example I used Minion Pro, as I don't have Adobe Garamond Pro.
The humoungous setting to lineskip is meant to show that the parameter doesn't enter into action (if it does, you'd see a very big vertical space).
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec
setmainfontMinion Pro
linespread1.02 % increase the leading by 2%
begindocument
setlengthlineskip30pt % just for testing
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
With the linespread adjustment
Without the linespread adjustment
Here you see the 30pt added space because of lineskip entering the scene.
answered 32 mins ago
egreg
684k8418243069
Apparently, the font has large descenders (and perhaps also large ascenders).
A small adjustment of the leading will solve the issue. In this example I used Minion Pro, as I don't have Adobe Garamond Pro.
The humoungous setting to lineskip is meant to show that the parameter doesn't enter into action (if it does, you'd see a very big vertical space).
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec
setmainfontMinion Pro
linespread1.02 % increase the leading by 2%
begindocument
setlengthlineskip30pt % just for testing
chapterTest what ever but lon er even lon er much lon er Test
lipsum[2-4]
chapterTesting what ever but longer even longer much longer
lipsum[2-4]
enddocument
With the linespread adjustment
Without the linespread adjustment
Here you see the 30pt added space because of lineskip entering the scene.
answered 32 mins ago
egreg
684k8418243069
answered 32 mins ago
egreg
684k8418243069
answered 32 mins ago
egreg
684k8418243069
answered 32 mins ago
egreg
684k8418243069
684k8418243069
add a comment |Â
add a comment |Â
up vote
2
down vote
As noted in my comment, I don't have Garamond Pro, but problem confirmed for another common font, setmainfontPalatino Linotype, using XeLaTeX
I presume the chapter title is placed in a box without a strut, so that descender depth affects the overall box depth. One solution is to add a strut to the end of each chapter title.
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er
Teststrut
lipsum[2-4]
chapterTest what ever but longer even longer much longer Teststrut
lipsum[2-4]
enddocument
answered 56 mins ago
Steven B. Segletes
147k9186389
@DavidCarlisle I have never usedshowoutputbefore. What exactly am I looking for? I see a line..glue(lineskip) 0.0another...glue(lineskip) 1.0, then..glue(lineskip) 0.0and again a...glue(lineskip) 1.0
– Steven B. Segletes
50 mins ago
yep I have the font (didn't realise:-) adding the strut makes the descender on thegnot matter but at the cost of giving the bad case all the time (so it's consistent but ...)
– David Carlisle
49 mins ago
add a comment |Â
up vote
2
down vote
As noted in my comment, I don't have Garamond Pro, but problem confirmed for another common font, setmainfontPalatino Linotype, using XeLaTeX
I presume the chapter title is placed in a box without a strut, so that descender depth affects the overall box depth. One solution is to add a strut to the end of each chapter title.
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er
Teststrut
lipsum[2-4]
chapterTest what ever but longer even longer much longer Teststrut
lipsum[2-4]
enddocument
answered 56 mins ago
Steven B. Segletes
147k9186389
@DavidCarlisle I have never usedshowoutputbefore. What exactly am I looking for? I see a line..glue(lineskip) 0.0another...glue(lineskip) 1.0, then..glue(lineskip) 0.0and again a...glue(lineskip) 1.0
– Steven B. Segletes
50 mins ago
yep I have the font (didn't realise:-) adding the strut makes the descender on thegnot matter but at the cost of giving the bad case all the time (so it's consistent but ...)
– David Carlisle
49 mins ago
add a comment |Â
up vote
2
down vote
up vote
2
down vote
As noted in my comment, I don't have Garamond Pro, but problem confirmed for another common font, setmainfontPalatino Linotype, using XeLaTeX
I presume the chapter title is placed in a box without a strut, so that descender depth affects the overall box depth. One solution is to add a strut to the end of each chapter title.
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er
Teststrut
lipsum[2-4]
chapterTest what ever but longer even longer much longer Teststrut
lipsum[2-4]
enddocument
answered 56 mins ago
Steven B. Segletes
147k9186389
As noted in my comment, I don't have Garamond Pro, but problem confirmed for another common font, setmainfontPalatino Linotype, using XeLaTeX
I presume the chapter title is placed in a box without a strut, so that descender depth affects the overall box depth. One solution is to add a strut to the end of each chapter title.
documentclass[a4paper,10pt,oneside]memoir
usepackagelipsum
usepackagefontspec, calc
setmainfontPalatino Linotype
%setmainfontAdobe Garamond Pro
begindocument
chapterTest what ever but lon er even lon er much lon er
Teststrut
lipsum[2-4]
chapterTest what ever but longer even longer much longer Teststrut
lipsum[2-4]
enddocument
answered 56 mins ago
Steven B. Segletes
147k9186389
edited 47 mins ago
answered 56 mins ago
Steven B. Segletes
147k9186389
answered 56 mins ago
Steven B. Segletes
147k9186389
answered 56 mins ago
Steven B. Segletes
147k9186389
147k9186389
@DavidCarlisle I have never usedshowoutputbefore. What exactly am I looking for? I see a line..glue(lineskip) 0.0another...glue(lineskip) 1.0, then..glue(lineskip) 0.0and again a...glue(lineskip) 1.0
– Steven B. Segletes
50 mins ago
yep I have the font (didn't realise:-) adding the strut makes the descender on thegnot matter but at the cost of giving the bad case all the time (so it's consistent but ...)
– David Carlisle
49 mins ago
add a comment |Â
@DavidCarlisle I have never usedshowoutputbefore. What exactly am I looking for? I see a line..glue(lineskip) 0.0another...glue(lineskip) 1.0, then..glue(lineskip) 0.0and again a...glue(lineskip) 1.0
– Steven B. Segletes
50 mins ago
yep I have the font (didn't realise:-) adding the strut makes the descender on thegnot matter but at the cost of giving the bad case all the time (so it's consistent but ...)
– David Carlisle
49 mins ago
@DavidCarlisle I have never used
showoutput before. What exactly am I looking for? I see a line ..glue(lineskip) 0.0 another ...glue(lineskip) 1.0, then ..glue(lineskip) 0.0 and again a ...glue(lineskip) 1.0– Steven B. Segletes
50 mins ago
@DavidCarlisle I have never used
showoutput before. What exactly am I looking for? I see a line ..glue(lineskip) 0.0 another ...glue(lineskip) 1.0, then ..glue(lineskip) 0.0 and again a ...glue(lineskip) 1.0– Steven B. Segletes
50 mins ago
yep I have the font (didn't realise:-) adding the strut makes the descender on the
g not matter but at the cost of giving the bad case all the time (so it's consistent but ...)– David Carlisle
49 mins ago
yep I have the font (didn't realise:-) adding the strut makes the descender on the
g not matter but at the cost of giving the bad case all the time (so it's consistent but ...)– David Carlisle
49 mins ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f452402%2fwhy-does-the-baseline-skip-depend-on-the-letters-depth-in-some-fonts%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I don't have Garamond Pro, but problem confirmed for another common font,
setmainfontPalatino Linotype, using XeLaTeX– Steven B. Segletes
1 hour ago
2
For reference, the problem also arises with
begindocument chapterTest what ever but lonsmashger even lonsmashger much lonsmashger Test lipsum[2-4] chapterTest what ever but longer even longer much longer Test lipsum[2-4] enddocument– Steven B. Segletes
1 hour ago
It would be easier to debug if you could show an example with a generally available font, but I would guess looking at the image that if you add
showoutputyou will seelineskipglue being added.lineskipis only added when tex has an otherwise infeasible constraint and the material it is adding is already larger than the specified baselineskip, so it gives up trying to maintain an even baseline and just insertslineskipbetween the rows. If that is the case you just need to make the text smaller or thebaselineskiplarger, depending...– David Carlisle
56 mins ago