Extra interline spacing in two sided mode with scrlttr2, and tcolorbox environment redefining quoting...
Traversing Africa: A Cryptic Journey
Levi-Civita symbol: 3D matrix
How do ISS astronauts "get their stripes"?
Is there a frame of reference in which I was born before I was conceived?
Heating basement floor with water heater
What is this waxed root vegetable?
Forward slip vs side slip
Difference between 'stomach' and 'uterus'
I can't die. Who am I?
Second-rate spelling
Pure Functions: Does "No Side Effects" Imply "Always Same Output, Given Same Input"?
Erro: incompatible type for argument 1 of 'printf'
Misplaced tyre lever - alternatives?
Why adding the article "the" when it is not needed?
Can I become debt free or should I file for bankruptcy? How do I manage my debt and finances?
Don't know what I’m looking for regarding removable HDDs?
If a set is open, does that imply that it has no boundary points?
How can I handle a player who pre-plans arguments about my rulings on RAW?
Test pad's ESD protection
I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?
Are there any other Chaos-worshipping races?
Detect if page is on experience editor Sitecore 9 via Javascript?
A right or the right?
Six real numbers so that product of any five is the sixth one
Extra interline spacing in two sided mode with scrlttr2, and tcolorbox environment redefining quoting environment
Problems with quoting package and renewing quotation environmentsetspace and quoting environment result in superfluous empty lineChanging the vertical spacing before and after the quoting environment when using parskipQuoting environment and tex4httoo much space between two environment create with tcolorboxdefine environment in tcolorbox with math mode in lowertcolorbox spacing with center environment and centering switchBreakable tcolorbox and centering environment errorSwitching to mode where content is only on right-side pages in a two-sided KOMA scrbookGetting extra spaces in two-sided document, but not in one-sided document
While experimenting with two sided settings in scrlttr2
while using quoting in combination with tcolorbox
, I came across an oddity. The following example shows interline spacing in text outside the quoting environment boxes. This only shows up in two sided mode, and only with beforeafter skip=baselineskip
in the tcolorboxenvironment
invocation that redefines quoting
. I'm puzzled what's causing this, since it's not obviously connected to anything about the quoting environment, or two sidedness.
%documentclass[12pt, sections, headheight=30pt, headinclude,
%firstfoot=false, enlargefirstpage=true,
%foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
%fromemail, version=last, backaddress=false, subject=titled
%{scrlttr2}
documentclass[12pt, sections, headheight=30pt, headinclude,
firstfoot=false, enlargefirstpage=true,
foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
fromemail, version=last, backaddress=false, subject=titled, twoside]
{scrlttr2}
usepackage[most]{tcolorbox}
usepackage{quoting}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
ExplSyntaxOn
NewDocumentCommand{dummy}{m m m}
{
prg_replicate:nn { #3 }
{
prg_replicate:nn { #2 } { #1 hfill } dummy_endline:
}
}
cs_new:Npn dummy_endline:
{ { parfillskip=0ptpar } }
ExplSyntaxOff
begin{document}
setkomavar{fromname}{Name}
setkomavar{fromaddress}{Address}
renewcommand{phonename}{Landline}
renewcommand{mobilephonename}{Mobile}
setkomavar{frommobilephone}{Mobile}
setkomavar{fromemail}{Email}
setkomavar{signature}{(usekomavar{fromname})}
setkomavar{subject}{Subject}
setkomavar{date}{today}
setkomavar{firsthead}{%
parbox{linewidth}{centering
textbf{jobname.tex} input{"| hg log -v -l 1 jobname.tex --template '{node} {date|isodate}'"}
ifhmode \ fi
{fontfamily{pzc}selectfont
hspace{textwidth}
usekomavar{fromname}\
usekomavar{fromaddress}\
usekomavar*{mobilephoneseparator}usekomavar{mobilephoneseparator}usekomavar{frommobilephone}\
usekomavar*{emailseparator}usekomavar{emailseparator}usekomavar{fromemail}
}
}%
}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
deftoday{20th February, 2019}
begin{letter}{
Someone\
Company\
Building\
Street\
City
}
opening{Hi}
dummy{HelloWorld!}{3}{5}
begin{quoting}
dummy{AlohaWorld!}{3}{3}
end{quoting}
dummy{BonjourWorld!}{3}{3}
begin{quoting}
begin{tabular}{p{4.5in}r}
textbf{dummy{CiaoWorld!}{3}{1} } & \
dummy{CiaoWorld!}{3}{2} & dummy{CiaoWorld!}{1}{1}
end{tabular}
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
ADDENDUM: A hopefully simplified version which looks more like what I'm actually seeing.
documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,,version=last, backaddress=false, subject=titled, twoside=semi]{scrlttr2}
%documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,version=last, backaddress=false, subject=titled]{scrlttr2}
usepackage{quoting}
usepackage[most]{tcolorbox}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
begin{document}
%setkomavar{subject}{Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject }
setkomavar{subject}{Subject}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
begin{letter}{
To Address
}
opening{Hi,}
Line 1.\
Line 2.\
Line 3.\
Line 1.\
Line 2.\
begin{quoting}
Line 1\
Line 2\
end{quoting}
Line 1\
Line 2\
begin{quoting}
Line 1\
Line 2\
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
The first page of the resulting 2 page file is shown below, which displays the problem
koma-script tcolorbox double-sided quoting scrlttr2
add a comment |
While experimenting with two sided settings in scrlttr2
while using quoting in combination with tcolorbox
, I came across an oddity. The following example shows interline spacing in text outside the quoting environment boxes. This only shows up in two sided mode, and only with beforeafter skip=baselineskip
in the tcolorboxenvironment
invocation that redefines quoting
. I'm puzzled what's causing this, since it's not obviously connected to anything about the quoting environment, or two sidedness.
%documentclass[12pt, sections, headheight=30pt, headinclude,
%firstfoot=false, enlargefirstpage=true,
%foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
%fromemail, version=last, backaddress=false, subject=titled
%{scrlttr2}
documentclass[12pt, sections, headheight=30pt, headinclude,
firstfoot=false, enlargefirstpage=true,
foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
fromemail, version=last, backaddress=false, subject=titled, twoside]
{scrlttr2}
usepackage[most]{tcolorbox}
usepackage{quoting}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
ExplSyntaxOn
NewDocumentCommand{dummy}{m m m}
{
prg_replicate:nn { #3 }
{
prg_replicate:nn { #2 } { #1 hfill } dummy_endline:
}
}
cs_new:Npn dummy_endline:
{ { parfillskip=0ptpar } }
ExplSyntaxOff
begin{document}
setkomavar{fromname}{Name}
setkomavar{fromaddress}{Address}
renewcommand{phonename}{Landline}
renewcommand{mobilephonename}{Mobile}
setkomavar{frommobilephone}{Mobile}
setkomavar{fromemail}{Email}
setkomavar{signature}{(usekomavar{fromname})}
setkomavar{subject}{Subject}
setkomavar{date}{today}
setkomavar{firsthead}{%
parbox{linewidth}{centering
textbf{jobname.tex} input{"| hg log -v -l 1 jobname.tex --template '{node} {date|isodate}'"}
ifhmode \ fi
{fontfamily{pzc}selectfont
hspace{textwidth}
usekomavar{fromname}\
usekomavar{fromaddress}\
usekomavar*{mobilephoneseparator}usekomavar{mobilephoneseparator}usekomavar{frommobilephone}\
usekomavar*{emailseparator}usekomavar{emailseparator}usekomavar{fromemail}
}
}%
}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
deftoday{20th February, 2019}
begin{letter}{
Someone\
Company\
Building\
Street\
City
}
opening{Hi}
dummy{HelloWorld!}{3}{5}
begin{quoting}
dummy{AlohaWorld!}{3}{3}
end{quoting}
dummy{BonjourWorld!}{3}{3}
begin{quoting}
begin{tabular}{p{4.5in}r}
textbf{dummy{CiaoWorld!}{3}{1} } & \
dummy{CiaoWorld!}{3}{2} & dummy{CiaoWorld!}{1}{1}
end{tabular}
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
ADDENDUM: A hopefully simplified version which looks more like what I'm actually seeing.
documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,,version=last, backaddress=false, subject=titled, twoside=semi]{scrlttr2}
%documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,version=last, backaddress=false, subject=titled]{scrlttr2}
usepackage{quoting}
usepackage[most]{tcolorbox}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
begin{document}
%setkomavar{subject}{Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject }
setkomavar{subject}{Subject}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
begin{letter}{
To Address
}
opening{Hi,}
Line 1.\
Line 2.\
Line 3.\
Line 1.\
Line 2.\
begin{quoting}
Line 1\
Line 2\
end{quoting}
Line 1\
Line 2\
begin{quoting}
Line 1\
Line 2\
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
The first page of the resulting 2 page file is shown below, which displays the problem
koma-script tcolorbox double-sided quoting scrlttr2
add a comment |
While experimenting with two sided settings in scrlttr2
while using quoting in combination with tcolorbox
, I came across an oddity. The following example shows interline spacing in text outside the quoting environment boxes. This only shows up in two sided mode, and only with beforeafter skip=baselineskip
in the tcolorboxenvironment
invocation that redefines quoting
. I'm puzzled what's causing this, since it's not obviously connected to anything about the quoting environment, or two sidedness.
%documentclass[12pt, sections, headheight=30pt, headinclude,
%firstfoot=false, enlargefirstpage=true,
%foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
%fromemail, version=last, backaddress=false, subject=titled
%{scrlttr2}
documentclass[12pt, sections, headheight=30pt, headinclude,
firstfoot=false, enlargefirstpage=true,
foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
fromemail, version=last, backaddress=false, subject=titled, twoside]
{scrlttr2}
usepackage[most]{tcolorbox}
usepackage{quoting}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
ExplSyntaxOn
NewDocumentCommand{dummy}{m m m}
{
prg_replicate:nn { #3 }
{
prg_replicate:nn { #2 } { #1 hfill } dummy_endline:
}
}
cs_new:Npn dummy_endline:
{ { parfillskip=0ptpar } }
ExplSyntaxOff
begin{document}
setkomavar{fromname}{Name}
setkomavar{fromaddress}{Address}
renewcommand{phonename}{Landline}
renewcommand{mobilephonename}{Mobile}
setkomavar{frommobilephone}{Mobile}
setkomavar{fromemail}{Email}
setkomavar{signature}{(usekomavar{fromname})}
setkomavar{subject}{Subject}
setkomavar{date}{today}
setkomavar{firsthead}{%
parbox{linewidth}{centering
textbf{jobname.tex} input{"| hg log -v -l 1 jobname.tex --template '{node} {date|isodate}'"}
ifhmode \ fi
{fontfamily{pzc}selectfont
hspace{textwidth}
usekomavar{fromname}\
usekomavar{fromaddress}\
usekomavar*{mobilephoneseparator}usekomavar{mobilephoneseparator}usekomavar{frommobilephone}\
usekomavar*{emailseparator}usekomavar{emailseparator}usekomavar{fromemail}
}
}%
}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
deftoday{20th February, 2019}
begin{letter}{
Someone\
Company\
Building\
Street\
City
}
opening{Hi}
dummy{HelloWorld!}{3}{5}
begin{quoting}
dummy{AlohaWorld!}{3}{3}
end{quoting}
dummy{BonjourWorld!}{3}{3}
begin{quoting}
begin{tabular}{p{4.5in}r}
textbf{dummy{CiaoWorld!}{3}{1} } & \
dummy{CiaoWorld!}{3}{2} & dummy{CiaoWorld!}{1}{1}
end{tabular}
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
ADDENDUM: A hopefully simplified version which looks more like what I'm actually seeing.
documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,,version=last, backaddress=false, subject=titled, twoside=semi]{scrlttr2}
%documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,version=last, backaddress=false, subject=titled]{scrlttr2}
usepackage{quoting}
usepackage[most]{tcolorbox}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
begin{document}
%setkomavar{subject}{Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject }
setkomavar{subject}{Subject}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
begin{letter}{
To Address
}
opening{Hi,}
Line 1.\
Line 2.\
Line 3.\
Line 1.\
Line 2.\
begin{quoting}
Line 1\
Line 2\
end{quoting}
Line 1\
Line 2\
begin{quoting}
Line 1\
Line 2\
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
The first page of the resulting 2 page file is shown below, which displays the problem
koma-script tcolorbox double-sided quoting scrlttr2
While experimenting with two sided settings in scrlttr2
while using quoting in combination with tcolorbox
, I came across an oddity. The following example shows interline spacing in text outside the quoting environment boxes. This only shows up in two sided mode, and only with beforeafter skip=baselineskip
in the tcolorboxenvironment
invocation that redefines quoting
. I'm puzzled what's causing this, since it's not obviously connected to anything about the quoting environment, or two sidedness.
%documentclass[12pt, sections, headheight=30pt, headinclude,
%firstfoot=false, enlargefirstpage=true,
%foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
%fromemail, version=last, backaddress=false, subject=titled
%{scrlttr2}
documentclass[12pt, sections, headheight=30pt, headinclude,
firstfoot=false, enlargefirstpage=true,
foldmarks=false,foldmarks=blmtP, fromalign=center, fromphone,
fromemail, version=last, backaddress=false, subject=titled, twoside]
{scrlttr2}
usepackage[most]{tcolorbox}
usepackage{quoting}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt, sharp corners, breakable, skin=enhanced, colback=white}
ExplSyntaxOn
NewDocumentCommand{dummy}{m m m}
{
prg_replicate:nn { #3 }
{
prg_replicate:nn { #2 } { #1 hfill } dummy_endline:
}
}
cs_new:Npn dummy_endline:
{ { parfillskip=0ptpar } }
ExplSyntaxOff
begin{document}
setkomavar{fromname}{Name}
setkomavar{fromaddress}{Address}
renewcommand{phonename}{Landline}
renewcommand{mobilephonename}{Mobile}
setkomavar{frommobilephone}{Mobile}
setkomavar{fromemail}{Email}
setkomavar{signature}{(usekomavar{fromname})}
setkomavar{subject}{Subject}
setkomavar{date}{today}
setkomavar{firsthead}{%
parbox{linewidth}{centering
textbf{jobname.tex} input{"| hg log -v -l 1 jobname.tex --template '{node} {date|isodate}'"}
ifhmode \ fi
{fontfamily{pzc}selectfont
hspace{textwidth}
usekomavar{fromname}\
usekomavar{fromaddress}\
usekomavar*{mobilephoneseparator}usekomavar{mobilephoneseparator}usekomavar{frommobilephone}\
usekomavar*{emailseparator}usekomavar{emailseparator}usekomavar{fromemail}
}
}%
}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
deftoday{20th February, 2019}
begin{letter}{
Someone\
Company\
Building\
Street\
City
}
opening{Hi}
dummy{HelloWorld!}{3}{5}
begin{quoting}
dummy{AlohaWorld!}{3}{3}
end{quoting}
dummy{BonjourWorld!}{3}{3}
begin{quoting}
begin{tabular}{p{4.5in}r}
textbf{dummy{CiaoWorld!}{3}{1} } & \
dummy{CiaoWorld!}{3}{2} & dummy{CiaoWorld!}{1}{1}
end{tabular}
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
ADDENDUM: A hopefully simplified version which looks more like what I'm actually seeing.
documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,,version=last, backaddress=false, subject=titled, twoside=semi]{scrlttr2}
%documentclass[12pt,sections,headheight=30pt,headinclude,firstfoot=false,enlargefirstpage=true,foldmarks=false,foldmarks=blmtP,fromalign=center,version=last, backaddress=false, subject=titled]{scrlttr2}
usepackage{quoting}
usepackage[most]{tcolorbox}
usepackage[T1]{fontenc}
usepackage{fouriernc}
tcolorboxenvironment{quoting}{beforeafter skip=baselineskip, boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
%tcolorboxenvironment{quoting}{boxrule=2pt,sharp corners,breakable,skin=enhanced,colback=white}
begin{document}
%setkomavar{subject}{Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject Subject }
setkomavar{subject}{Subject}
makeatletter
@addtoplength{firstheadvpos}{30pt}
@addtoplength{toaddrvpos}{40pt}
@addtoplength{refvpos}{10pt}
@addtoplength{sigbeforevskip}{20pt}
makeatletter@setplength{sigindent}{0.5linewidth}makeatother
makeatother
begin{letter}{
To Address
}
opening{Hi,}
Line 1.\
Line 2.\
Line 3.\
Line 1.\
Line 2.\
begin{quoting}
Line 1\
Line 2\
end{quoting}
Line 1\
Line 2\
begin{quoting}
Line 1\
Line 2\
end{quoting}
closing{Yours Sincerely,}
end{letter}
end{document}
The first page of the resulting 2 page file is shown below, which displays the problem
koma-script tcolorbox double-sided quoting scrlttr2
koma-script tcolorbox double-sided quoting scrlttr2
edited 2 hours ago
Faheem Mitha
asked yesterday
Faheem MithaFaheem Mitha
3,29843964
3,29843964
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
When using twoside the class activates (like other classes often do) flushbottom
. That means that LaTeX will try to fill the page, and for this stretches the parskip.
The effect disappears if you remove the beforeafter skip=baselineskip,
as then the letter fits on one page.
In oneside mode you get the same if add flushbottom
.
To avoid the problem add raggedbottom
Hi Ulrike. Thank you very much for the answer. Can you tell me where I should putraggedbottom
for this to work? And why isflushbottom
used in two sided mode, and not one sided mode? What is the logic?
– Faheem Mitha
11 hours ago
Try it out - there aren't so many sensible places. And flushbottom is used traditionally in twoside mode, as there two pages can be seen side by side - simply open a book to see it.
– Ulrike Fischer
11 hours ago
I tried it in a couple of places, but it doesn't change anything. Where is theflushbottom
placed in the environment? And is there no way to simply switch that off?
– Faheem Mitha
11 hours ago
Add raggedbottom directly after begin{document}.
– Ulrike Fischer
11 hours ago
Ok, I tried putting it just before the beginning of the last para on the first page, and that worked. But a fire-and-forget solution would be preferable. Directly afterbegin{document}
works, but is that a general solution?
– Faheem Mitha
11 hours ago
add a comment |
Using flushbottom
in twoside-mode was a bug in scrlttr2
since version 3.17. It has been fixed in scrlttr2
v3.27.3111 by adding raggedbottom
to the definition of the letter
environment. Before this change
documentclass[twoside]{scrlttr2}
usepackage{mwe}
begin{document}
begin{letter}{You\There}
opening{Hi,}
blindtextparblindtext
noindentrule{textwidth}{.5textheight}
blindtext
closing{Bye}
end{letter}
end{document}
resulted in a warning message:
Underfull vbox (badness 10000) has occurred while output is active [1
and
With KOMA-Script 3.27.3111 (this is a KOMA-Script pre-release), it results in:
without warning message.
Note, there are additional changes in upcoming KOMA-Script 3.27 (linked page in German).
Hi, Schweinebacke, thank you for the answer. The version of KOMA I'm currently using is 2018/03/30 v3.25 (Debian pre-release of TeX LIve 2019).2018.20190227-2
is available in Debian unstable. Would that version contain the KOMA version you mention? And do you concur that addingraggedbottom
directly afterbegin{document}
is the best workaround for now?
– Faheem Mitha
9 hours ago
@FaheemMitha I do not know which version of KOMA-Script is in which version of a Debian package. But I do not think, that any distributor could have packaged on 2019-02-27 a KOMA-Script pre-release that has been made today after the bug has been recognized. And I would never expect (or recommend), that a distributor would package a KOMA-Script pre-release. You either have to wait for the release (and maybe several month until debian make an update) or use the pre-release from the location I gave in my answer.
– Schweinebacke
9 hours ago
Hi Schweinebacke. The fix was made today? Was this in response to my post, then? And if so, can you post a link to an issue, or a VCS diff, or something?
– Faheem Mitha
9 hours ago
@FaheemMitha So, yes, currently with KOMA-Script v3.17–3.26b usingraggedbottom
is the best workaround. Whether you place it afterbegin{documemt}
or useAtBeginLetter{raggedbottom}
is your choice.
– Schweinebacke
8 hours ago
Well, I'm still using v3.25.
– Faheem Mitha
8 hours ago
|
show 2 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477763%2fextra-interline-spacing-in-two-sided-mode-with-scrlttr2-and-tcolorbox-environme%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
When using twoside the class activates (like other classes often do) flushbottom
. That means that LaTeX will try to fill the page, and for this stretches the parskip.
The effect disappears if you remove the beforeafter skip=baselineskip,
as then the letter fits on one page.
In oneside mode you get the same if add flushbottom
.
To avoid the problem add raggedbottom
Hi Ulrike. Thank you very much for the answer. Can you tell me where I should putraggedbottom
for this to work? And why isflushbottom
used in two sided mode, and not one sided mode? What is the logic?
– Faheem Mitha
11 hours ago
Try it out - there aren't so many sensible places. And flushbottom is used traditionally in twoside mode, as there two pages can be seen side by side - simply open a book to see it.
– Ulrike Fischer
11 hours ago
I tried it in a couple of places, but it doesn't change anything. Where is theflushbottom
placed in the environment? And is there no way to simply switch that off?
– Faheem Mitha
11 hours ago
Add raggedbottom directly after begin{document}.
– Ulrike Fischer
11 hours ago
Ok, I tried putting it just before the beginning of the last para on the first page, and that worked. But a fire-and-forget solution would be preferable. Directly afterbegin{document}
works, but is that a general solution?
– Faheem Mitha
11 hours ago
add a comment |
When using twoside the class activates (like other classes often do) flushbottom
. That means that LaTeX will try to fill the page, and for this stretches the parskip.
The effect disappears if you remove the beforeafter skip=baselineskip,
as then the letter fits on one page.
In oneside mode you get the same if add flushbottom
.
To avoid the problem add raggedbottom
Hi Ulrike. Thank you very much for the answer. Can you tell me where I should putraggedbottom
for this to work? And why isflushbottom
used in two sided mode, and not one sided mode? What is the logic?
– Faheem Mitha
11 hours ago
Try it out - there aren't so many sensible places. And flushbottom is used traditionally in twoside mode, as there two pages can be seen side by side - simply open a book to see it.
– Ulrike Fischer
11 hours ago
I tried it in a couple of places, but it doesn't change anything. Where is theflushbottom
placed in the environment? And is there no way to simply switch that off?
– Faheem Mitha
11 hours ago
Add raggedbottom directly after begin{document}.
– Ulrike Fischer
11 hours ago
Ok, I tried putting it just before the beginning of the last para on the first page, and that worked. But a fire-and-forget solution would be preferable. Directly afterbegin{document}
works, but is that a general solution?
– Faheem Mitha
11 hours ago
add a comment |
When using twoside the class activates (like other classes often do) flushbottom
. That means that LaTeX will try to fill the page, and for this stretches the parskip.
The effect disappears if you remove the beforeafter skip=baselineskip,
as then the letter fits on one page.
In oneside mode you get the same if add flushbottom
.
To avoid the problem add raggedbottom
When using twoside the class activates (like other classes often do) flushbottom
. That means that LaTeX will try to fill the page, and for this stretches the parskip.
The effect disappears if you remove the beforeafter skip=baselineskip,
as then the letter fits on one page.
In oneside mode you get the same if add flushbottom
.
To avoid the problem add raggedbottom
answered 12 hours ago
Ulrike FischerUlrike Fischer
194k8302688
194k8302688
Hi Ulrike. Thank you very much for the answer. Can you tell me where I should putraggedbottom
for this to work? And why isflushbottom
used in two sided mode, and not one sided mode? What is the logic?
– Faheem Mitha
11 hours ago
Try it out - there aren't so many sensible places. And flushbottom is used traditionally in twoside mode, as there two pages can be seen side by side - simply open a book to see it.
– Ulrike Fischer
11 hours ago
I tried it in a couple of places, but it doesn't change anything. Where is theflushbottom
placed in the environment? And is there no way to simply switch that off?
– Faheem Mitha
11 hours ago
Add raggedbottom directly after begin{document}.
– Ulrike Fischer
11 hours ago
Ok, I tried putting it just before the beginning of the last para on the first page, and that worked. But a fire-and-forget solution would be preferable. Directly afterbegin{document}
works, but is that a general solution?
– Faheem Mitha
11 hours ago
add a comment |
Hi Ulrike. Thank you very much for the answer. Can you tell me where I should putraggedbottom
for this to work? And why isflushbottom
used in two sided mode, and not one sided mode? What is the logic?
– Faheem Mitha
11 hours ago
Try it out - there aren't so many sensible places. And flushbottom is used traditionally in twoside mode, as there two pages can be seen side by side - simply open a book to see it.
– Ulrike Fischer
11 hours ago
I tried it in a couple of places, but it doesn't change anything. Where is theflushbottom
placed in the environment? And is there no way to simply switch that off?
– Faheem Mitha
11 hours ago
Add raggedbottom directly after begin{document}.
– Ulrike Fischer
11 hours ago
Ok, I tried putting it just before the beginning of the last para on the first page, and that worked. But a fire-and-forget solution would be preferable. Directly afterbegin{document}
works, but is that a general solution?
– Faheem Mitha
11 hours ago
Hi Ulrike. Thank you very much for the answer. Can you tell me where I should put
raggedbottom
for this to work? And why is flushbottom
used in two sided mode, and not one sided mode? What is the logic?– Faheem Mitha
11 hours ago
Hi Ulrike. Thank you very much for the answer. Can you tell me where I should put
raggedbottom
for this to work? And why is flushbottom
used in two sided mode, and not one sided mode? What is the logic?– Faheem Mitha
11 hours ago
Try it out - there aren't so many sensible places. And flushbottom is used traditionally in twoside mode, as there two pages can be seen side by side - simply open a book to see it.
– Ulrike Fischer
11 hours ago
Try it out - there aren't so many sensible places. And flushbottom is used traditionally in twoside mode, as there two pages can be seen side by side - simply open a book to see it.
– Ulrike Fischer
11 hours ago
I tried it in a couple of places, but it doesn't change anything. Where is the
flushbottom
placed in the environment? And is there no way to simply switch that off?– Faheem Mitha
11 hours ago
I tried it in a couple of places, but it doesn't change anything. Where is the
flushbottom
placed in the environment? And is there no way to simply switch that off?– Faheem Mitha
11 hours ago
Add raggedbottom directly after begin{document}.
– Ulrike Fischer
11 hours ago
Add raggedbottom directly after begin{document}.
– Ulrike Fischer
11 hours ago
Ok, I tried putting it just before the beginning of the last para on the first page, and that worked. But a fire-and-forget solution would be preferable. Directly after
begin{document}
works, but is that a general solution?– Faheem Mitha
11 hours ago
Ok, I tried putting it just before the beginning of the last para on the first page, and that worked. But a fire-and-forget solution would be preferable. Directly after
begin{document}
works, but is that a general solution?– Faheem Mitha
11 hours ago
add a comment |
Using flushbottom
in twoside-mode was a bug in scrlttr2
since version 3.17. It has been fixed in scrlttr2
v3.27.3111 by adding raggedbottom
to the definition of the letter
environment. Before this change
documentclass[twoside]{scrlttr2}
usepackage{mwe}
begin{document}
begin{letter}{You\There}
opening{Hi,}
blindtextparblindtext
noindentrule{textwidth}{.5textheight}
blindtext
closing{Bye}
end{letter}
end{document}
resulted in a warning message:
Underfull vbox (badness 10000) has occurred while output is active [1
and
With KOMA-Script 3.27.3111 (this is a KOMA-Script pre-release), it results in:
without warning message.
Note, there are additional changes in upcoming KOMA-Script 3.27 (linked page in German).
Hi, Schweinebacke, thank you for the answer. The version of KOMA I'm currently using is 2018/03/30 v3.25 (Debian pre-release of TeX LIve 2019).2018.20190227-2
is available in Debian unstable. Would that version contain the KOMA version you mention? And do you concur that addingraggedbottom
directly afterbegin{document}
is the best workaround for now?
– Faheem Mitha
9 hours ago
@FaheemMitha I do not know which version of KOMA-Script is in which version of a Debian package. But I do not think, that any distributor could have packaged on 2019-02-27 a KOMA-Script pre-release that has been made today after the bug has been recognized. And I would never expect (or recommend), that a distributor would package a KOMA-Script pre-release. You either have to wait for the release (and maybe several month until debian make an update) or use the pre-release from the location I gave in my answer.
– Schweinebacke
9 hours ago
Hi Schweinebacke. The fix was made today? Was this in response to my post, then? And if so, can you post a link to an issue, or a VCS diff, or something?
– Faheem Mitha
9 hours ago
@FaheemMitha So, yes, currently with KOMA-Script v3.17–3.26b usingraggedbottom
is the best workaround. Whether you place it afterbegin{documemt}
or useAtBeginLetter{raggedbottom}
is your choice.
– Schweinebacke
8 hours ago
Well, I'm still using v3.25.
– Faheem Mitha
8 hours ago
|
show 2 more comments
Using flushbottom
in twoside-mode was a bug in scrlttr2
since version 3.17. It has been fixed in scrlttr2
v3.27.3111 by adding raggedbottom
to the definition of the letter
environment. Before this change
documentclass[twoside]{scrlttr2}
usepackage{mwe}
begin{document}
begin{letter}{You\There}
opening{Hi,}
blindtextparblindtext
noindentrule{textwidth}{.5textheight}
blindtext
closing{Bye}
end{letter}
end{document}
resulted in a warning message:
Underfull vbox (badness 10000) has occurred while output is active [1
and
With KOMA-Script 3.27.3111 (this is a KOMA-Script pre-release), it results in:
without warning message.
Note, there are additional changes in upcoming KOMA-Script 3.27 (linked page in German).
Hi, Schweinebacke, thank you for the answer. The version of KOMA I'm currently using is 2018/03/30 v3.25 (Debian pre-release of TeX LIve 2019).2018.20190227-2
is available in Debian unstable. Would that version contain the KOMA version you mention? And do you concur that addingraggedbottom
directly afterbegin{document}
is the best workaround for now?
– Faheem Mitha
9 hours ago
@FaheemMitha I do not know which version of KOMA-Script is in which version of a Debian package. But I do not think, that any distributor could have packaged on 2019-02-27 a KOMA-Script pre-release that has been made today after the bug has been recognized. And I would never expect (or recommend), that a distributor would package a KOMA-Script pre-release. You either have to wait for the release (and maybe several month until debian make an update) or use the pre-release from the location I gave in my answer.
– Schweinebacke
9 hours ago
Hi Schweinebacke. The fix was made today? Was this in response to my post, then? And if so, can you post a link to an issue, or a VCS diff, or something?
– Faheem Mitha
9 hours ago
@FaheemMitha So, yes, currently with KOMA-Script v3.17–3.26b usingraggedbottom
is the best workaround. Whether you place it afterbegin{documemt}
or useAtBeginLetter{raggedbottom}
is your choice.
– Schweinebacke
8 hours ago
Well, I'm still using v3.25.
– Faheem Mitha
8 hours ago
|
show 2 more comments
Using flushbottom
in twoside-mode was a bug in scrlttr2
since version 3.17. It has been fixed in scrlttr2
v3.27.3111 by adding raggedbottom
to the definition of the letter
environment. Before this change
documentclass[twoside]{scrlttr2}
usepackage{mwe}
begin{document}
begin{letter}{You\There}
opening{Hi,}
blindtextparblindtext
noindentrule{textwidth}{.5textheight}
blindtext
closing{Bye}
end{letter}
end{document}
resulted in a warning message:
Underfull vbox (badness 10000) has occurred while output is active [1
and
With KOMA-Script 3.27.3111 (this is a KOMA-Script pre-release), it results in:
without warning message.
Note, there are additional changes in upcoming KOMA-Script 3.27 (linked page in German).
Using flushbottom
in twoside-mode was a bug in scrlttr2
since version 3.17. It has been fixed in scrlttr2
v3.27.3111 by adding raggedbottom
to the definition of the letter
environment. Before this change
documentclass[twoside]{scrlttr2}
usepackage{mwe}
begin{document}
begin{letter}{You\There}
opening{Hi,}
blindtextparblindtext
noindentrule{textwidth}{.5textheight}
blindtext
closing{Bye}
end{letter}
end{document}
resulted in a warning message:
Underfull vbox (badness 10000) has occurred while output is active [1
and
With KOMA-Script 3.27.3111 (this is a KOMA-Script pre-release), it results in:
without warning message.
Note, there are additional changes in upcoming KOMA-Script 3.27 (linked page in German).
edited 9 hours ago
Faheem Mitha
3,29843964
3,29843964
answered 10 hours ago
SchweinebackeSchweinebacke
21.8k4577
21.8k4577
Hi, Schweinebacke, thank you for the answer. The version of KOMA I'm currently using is 2018/03/30 v3.25 (Debian pre-release of TeX LIve 2019).2018.20190227-2
is available in Debian unstable. Would that version contain the KOMA version you mention? And do you concur that addingraggedbottom
directly afterbegin{document}
is the best workaround for now?
– Faheem Mitha
9 hours ago
@FaheemMitha I do not know which version of KOMA-Script is in which version of a Debian package. But I do not think, that any distributor could have packaged on 2019-02-27 a KOMA-Script pre-release that has been made today after the bug has been recognized. And I would never expect (or recommend), that a distributor would package a KOMA-Script pre-release. You either have to wait for the release (and maybe several month until debian make an update) or use the pre-release from the location I gave in my answer.
– Schweinebacke
9 hours ago
Hi Schweinebacke. The fix was made today? Was this in response to my post, then? And if so, can you post a link to an issue, or a VCS diff, or something?
– Faheem Mitha
9 hours ago
@FaheemMitha So, yes, currently with KOMA-Script v3.17–3.26b usingraggedbottom
is the best workaround. Whether you place it afterbegin{documemt}
or useAtBeginLetter{raggedbottom}
is your choice.
– Schweinebacke
8 hours ago
Well, I'm still using v3.25.
– Faheem Mitha
8 hours ago
|
show 2 more comments
Hi, Schweinebacke, thank you for the answer. The version of KOMA I'm currently using is 2018/03/30 v3.25 (Debian pre-release of TeX LIve 2019).2018.20190227-2
is available in Debian unstable. Would that version contain the KOMA version you mention? And do you concur that addingraggedbottom
directly afterbegin{document}
is the best workaround for now?
– Faheem Mitha
9 hours ago
@FaheemMitha I do not know which version of KOMA-Script is in which version of a Debian package. But I do not think, that any distributor could have packaged on 2019-02-27 a KOMA-Script pre-release that has been made today after the bug has been recognized. And I would never expect (or recommend), that a distributor would package a KOMA-Script pre-release. You either have to wait for the release (and maybe several month until debian make an update) or use the pre-release from the location I gave in my answer.
– Schweinebacke
9 hours ago
Hi Schweinebacke. The fix was made today? Was this in response to my post, then? And if so, can you post a link to an issue, or a VCS diff, or something?
– Faheem Mitha
9 hours ago
@FaheemMitha So, yes, currently with KOMA-Script v3.17–3.26b usingraggedbottom
is the best workaround. Whether you place it afterbegin{documemt}
or useAtBeginLetter{raggedbottom}
is your choice.
– Schweinebacke
8 hours ago
Well, I'm still using v3.25.
– Faheem Mitha
8 hours ago
Hi, Schweinebacke, thank you for the answer. The version of KOMA I'm currently using is 2018/03/30 v3.25 (Debian pre-release of TeX LIve 2019).
2018.20190227-2
is available in Debian unstable. Would that version contain the KOMA version you mention? And do you concur that adding raggedbottom
directly after begin{document}
is the best workaround for now?– Faheem Mitha
9 hours ago
Hi, Schweinebacke, thank you for the answer. The version of KOMA I'm currently using is 2018/03/30 v3.25 (Debian pre-release of TeX LIve 2019).
2018.20190227-2
is available in Debian unstable. Would that version contain the KOMA version you mention? And do you concur that adding raggedbottom
directly after begin{document}
is the best workaround for now?– Faheem Mitha
9 hours ago
@FaheemMitha I do not know which version of KOMA-Script is in which version of a Debian package. But I do not think, that any distributor could have packaged on 2019-02-27 a KOMA-Script pre-release that has been made today after the bug has been recognized. And I would never expect (or recommend), that a distributor would package a KOMA-Script pre-release. You either have to wait for the release (and maybe several month until debian make an update) or use the pre-release from the location I gave in my answer.
– Schweinebacke
9 hours ago
@FaheemMitha I do not know which version of KOMA-Script is in which version of a Debian package. But I do not think, that any distributor could have packaged on 2019-02-27 a KOMA-Script pre-release that has been made today after the bug has been recognized. And I would never expect (or recommend), that a distributor would package a KOMA-Script pre-release. You either have to wait for the release (and maybe several month until debian make an update) or use the pre-release from the location I gave in my answer.
– Schweinebacke
9 hours ago
Hi Schweinebacke. The fix was made today? Was this in response to my post, then? And if so, can you post a link to an issue, or a VCS diff, or something?
– Faheem Mitha
9 hours ago
Hi Schweinebacke. The fix was made today? Was this in response to my post, then? And if so, can you post a link to an issue, or a VCS diff, or something?
– Faheem Mitha
9 hours ago
@FaheemMitha So, yes, currently with KOMA-Script v3.17–3.26b using
raggedbottom
is the best workaround. Whether you place it after begin{documemt}
or use AtBeginLetter{raggedbottom}
is your choice.– Schweinebacke
8 hours ago
@FaheemMitha So, yes, currently with KOMA-Script v3.17–3.26b using
raggedbottom
is the best workaround. Whether you place it after begin{documemt}
or use AtBeginLetter{raggedbottom}
is your choice.– Schweinebacke
8 hours ago
Well, I'm still using v3.25.
– Faheem Mitha
8 hours ago
Well, I'm still using v3.25.
– Faheem Mitha
8 hours ago
|
show 2 more comments
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f477763%2fextra-interline-spacing-in-two-sided-mode-with-scrlttr2-and-tcolorbox-environme%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown