Ghost lettrines with lettrine package

[coopermj]

When pairing with lettrine.sty, ghosts appear after the first or second chapter -- attempting to typeset an entire Bible with fancy drop caps at the beginning of each chapter like the 1611 KJV.

Example:

\documentclass[twocolumn,paper=a4,oneside,pagesize=pdftex,12pt,headinclude=on]{scrbook}

\usepackage{scripture}
\usepackage{lettrine}

\usepackage{GoudyIn}

\usepackage[x11names]{xcolor} 
\renewcommand{\LettrineFontHook}{\color{SteelBlue4}\GoudyInfamily{}}
\setcounter{DefaultLines}{4}%


\begin{document}
\begin{scripture}[][chapter/para,chapter/format=CHAPTER~#1]

\ch{1}

\lettrine{L}{orem} ipsum dolor sit amet, consectetur adipiscing elit. \vs{2} Pellentesque dictum tellus id dui hendrerit semper. \vs{3} Quisque vulputate accumsan porttitor. \vs{4} Fusce tempor libero vel iaculis lobortis. \vs{5} Donec hendrerit quam ut ante convallis volutpat. \vs{6} Phasellus maximus sollicitudin pellentesque. \vs{7} Donec ligula est, ullamcorper at massa quis, eleifend laoreet leo. \vs{8} Vivamus faucibus leo elit. \vs{9} Maecenas tristique dui lorem, in ornare erat egestas vitae. \vs{10}

Nulla facilisi. \vs{11} Praesent dui tortor, aliquam et convallis quis, pretium id nisl. \vs{12} Nunc in ultrices ligula. \vs{13} Curabitur et auctor sapien. \vs{14} Vestibulum sit amet interdum quam. \vs{15} Vestibulum quis ex sed leo molestie consectetur. \vs{16} Proin massa odio, gravida a imperdiet quis, feugiat a augue. \vs{1} Maecenas lectus turpis, ullamcorper eu sapien sed, molestie tempus risus. \vs{1} Nam id libero libero. \vs{1} Vestibulum a turpis quis metus fringilla sodales. \vs{1} Vivamus a egestas purus. \vs{1} Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Nulla elementum mattis turpis quis suscipit. \vs{1} Sed lacinia egestas magna, quis tempus ex maximus vitae. \vs{1}

\ch{2}
\lettrine{N}{unc} pharetra ante ac lacinia egestas. \vs{1} Curabitur pellentesque eleifend justo, tempor bibendum nulla hendrerit vitae. \vs{1} Maecenas commodo, nisi et fermentum accumsan, lectus diam pellentesque arcu, non aliquam ipsum quam in nunc. \vs{1} Etiam sed mollis ligula. \vs{1} Suspendisse potenti. \vs{1} Donec sagittis odio eu risus eleifend dapibus. \vs{1} Duis eu bibendum lorem, vel consequat libero. \vs{1} Maecenas molestie euismod ex, non porta dolor viverra id. \vs{1} Maecenas semper ac mauris id gravida. \vs{1} Curabitur luctus magna ut eleifend egestas. \vs{1} Aliquam venenatis, eros eu ornare volutpat, enim magna euismod massa, sed semper nunc libero et lectus. \vs{1} Etiam lorem elit, mollis sed odio quis, suscipit faucibus massa. \vs{1} Pellentesque lorem sapien, sodales vel molestie a, hendrerit in nisi. \vs{1}

Maecenas in ipsum et tortor dignissim sodales. \vs{1} Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Integer ac massa nisi. \vs{1} In arcu enim, tempor nec ex vitae, finibus venenatis neque. \vs{1} Integer sed blandit tellus, in condimentum eros. \vs{1} Etiam id commodo tortor. \vs{1} Suspendisse potenti. \vs{1} Fusce turpis turpis, pulvinar vitae ligula nec, tincidunt posuere nibh. \vs{1} Phasellus id faucibus ipsum. \vs{1} Praesent pulvinar consequat dolor in rhoncus. \vs{1} Proin semper sem a elit volutpat ornare. \vs{1} Proin pharetra metus et vestibulum accumsan. \vs{1} Etiam sagittis mauris nulla, vel tempus tellus pharetra ut. \vs{1} Sed in hendrerit nulla, sed tempor mi. \vs{1} Suspendisse fringilla pharetra nulla. \vs{1} Curabitur nisl nibh, maximus ut nisl vitae, vehicula hendrerit justo. \vs{1}

Nunc pharetra ante ac lacinia egestas. \vs{1} Curabitur pellentesque eleifend justo, tempor bibendum nulla hendrerit vitae. \vs{1} Maecenas commodo, nisi et fermentum accumsan, lectus diam pellentesque arcu, non aliquam ipsum quam in nunc. \vs{1} Etiam sed mollis ligula. \vs{1} Suspendisse potenti. \vs{1} Donec sagittis odio eu risus eleifend dapibus. \vs{1} Duis eu bibendum lorem, vel consequat libero. \vs{1} Maecenas molestie euismod ex, non porta dolor viverra id. \vs{1} Maecenas semper ac mauris id gravida. \vs{1} Curabitur luctus magna ut eleifend egestas. \vs{1} Aliquam venenatis, eros eu ornare volutpat, enim magna euismod massa, sed semper nunc libero et lectus. \vs{1} Etiam lorem elit, mollis sed odio quis, suscipit faucibus massa. \vs{1} Pellentesque lorem sapien, sodales vel molestie a, hendrerit in nisi. \vs{1}

Maecenas in ipsum et tortor dignissim sodales. \vs{1} Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Integer ac massa nisi. \vs{1} In arcu enim, tempor nec ex vitae, finibus venenatis neque. \vs{1} Integer sed blandit tellus, in condimentum eros. \vs{1} Etiam id commodo tortor. \vs{1} Suspendisse potenti. \vs{1} Fusce turpis turpis, pulvinar vitae ligula nec, tincidunt posuere nibh. \vs{1} Phasellus id faucibus ipsum. \vs{1} Praesent pulvinar consequat dolor in rhoncus. \vs{1} Proin semper sem a elit volutpat ornare. \vs{1} Proin pharetra metus et vestibulum accumsan. \vs{1} Etiam sagittis mauris nulla, vel tempus tellus pharetra ut. \vs{1} Sed in hendrerit nulla, sed tempor mi. \vs{1} Suspendisse fringilla pharetra nulla. \vs{1} Curabitur nisl nibh, maximus ut nisl vitae, vehicula hendrerit justo. \vs{1}

Nunc pharetra ante ac lacinia egestas. \vs{1} Curabitur pellentesque eleifend justo, tempor bibendum nulla hendrerit vitae. \vs{1} Maecenas commodo, nisi et fermentum accumsan, lectus diam pellentesque arcu, non aliquam ipsum quam in nunc. \vs{1} Etiam sed mollis ligula. \vs{1} Suspendisse potenti. \vs{1} Donec sagittis odio eu risus eleifend dapibus. \vs{1} Duis eu bibendum lorem, vel consequat libero. \vs{1} Maecenas molestie euismod ex, non porta dolor viverra id. \vs{1} Maecenas semper ac mauris id gravida. \vs{1} Curabitur luctus magna ut eleifend egestas. \vs{1} Aliquam venenatis, eros eu ornare volutpat, enim magna euismod massa, sed semper nunc libero et lectus. \vs{1} Etiam lorem elit, mollis sed odio quis, suscipit faucibus massa. \vs{1} Pellentesque lorem sapien, sodales vel molestie a, hendrerit in nisi. \vs{1}

Maecenas in ipsum et tortor dignissim sodales. \vs{1} Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Integer ac massa nisi. \vs{1} In arcu enim, tempor nec ex vitae, finibus venenatis neque. \vs{1} Integer sed blandit tellus, in condimentum eros. \vs{1} Etiam id commodo tortor. \vs{1} Suspendisse potenti. \vs{1} Fusce turpis turpis, pulvinar vitae ligula nec, tincidunt posuere nibh. \vs{1} Phasellus id faucibus ipsum. \vs{1} Praesent pulvinar consequat dolor in rhoncus. \vs{1} Proin semper sem a elit volutpat ornare. \vs{1} Proin pharetra metus et vestibulum accumsan. \vs{1} Etiam sagittis mauris nulla, vel tempus tellus pharetra ut. \vs{1} Sed in hendrerit nulla, sed tempor mi. \vs{1} Suspendisse fringilla pharetra nulla. \vs{1} Curabitur nisl nibh, maximus ut nisl vitae, vehicula hendrerit justo. \vs{1}

\end{scripture}
\end{document}

[dcpurton]

Yeah - I'm not surprised that there are problems with lettrine. I have thought about allowing drop chapters with more than 2 lines in scripture, then you could just use the scripture interface. But it becomes complicated to track the drop chapter through the other inner environments that scripture supports.

Since you're not using the inner environments, it's probably possible to come up with a work around, so that lettrine can be used.

I'll see if I can track down where things go wrong.

[coopermj]

That would be so much appreciated. This is an amazing style package that immediately inspired me to want to typeset a Bible for my Remarkable device. You should know that Claude and ChatGPT have foundered against this problem and it’s well beyond my beginner LaTeX skills. :) Thank you for any time you can put into it!

…

Message ID: ***@***.***>

[dcpurton]

This is not specifically a problem with the scripture package, but rather a general problem with how lettrine interacts with LaTeX list environments. The scripture package is implemented using a LaTeX list environment, so you get the same problems.

The problem can be simplified to something like this:

\documentclass[twocolumn]{article}
\usepackage{lettrine}
\begin{document}
\begin{quotation}
  \makeatletter
  Test\@afterheading
  \makeatother

  \lettrine{L}{orem} ipsum dolor sit amet, consectetur adipiscing elit.
  Pellentesque dictum tellus id dui hendrerit semper.

  Quisque vulputate accumsan porttitor. Fusce tempor libero vel iaculis
  lobortis.

  \lettrine{D}{onec} hendrerit quam ut ante convallis volutpat. Phasellus
  maximus sollicitudin pellentesque. Donec ligula est, ullamcorper at massa
  quis, eleifend laoreet leo.

  Vivamus faucibus leo elit. Maecenas tristique dui lorem, in ornare erat
  egestas vitae.
\end{quotation}
\end{document}

The @afterheading macro is used by LaTeX to prevent a page break after a heading. You see the same thing with \section{Test}. If you remove:

\makeatletter
Test\@afterheading
\makeatother

the document will not compile at all.

I think the the problems relate to \everypar which lettrine, LaTeX list environments, and \@afterheading all manipulate. The new hook implementation is supposed to work around these issues, but lettrine doesn't use these hooks and directly manipulates \everypar.

[dcpurton]

Try using this for your \LettrineFontHook:

\makeatletter
\renewcommand{\LettrineFontHook}{%
  \AddToHookNext{para/begin}{%
    \AddToHookNext{para/begin}{%
      \everypar{}%
      \parshape \@ne \@totalleftmargin \linewidth}}%
  \color{SteelBlue4}%
  \GoudyInfamily{}}
\makeatother

I don't know how reliable this will be though and it isn't well tested.

You could try asking a question on https://tex.stackexchange.com/ if you still have problems. If you do this, try to reproduce the problem just using a quotation environment rather than the scripture environment.

[dcpurton]

BTW, it's not finished yet, but the plan is for the next release to include a collection of features for setting entire Bibles. Things like auto numbering of chapters and verses and marks that can be used in headings. I've implemented the auto numbering, but I've been working on other projects recently and haven't had time to dig into how ltmarks works. There are some bug fixes in the version on GitHub too.

[coopermj]

You are truly a LaTeX genius! That hook worked a treat. Thank you so very much! I look forward to your future updates for setting entire Bibles!