1

I had been using the flushend package to even out the final page, which contained references, but I think I need to drop that if I don't find an answer to this. It seems when using that along with IEEEtran and bibtex, specifically the acm bibliography style, one of two bad things would happen in the right column. Depending on how things laid out, I might wind up with the final line of the right column not being indented like all other lines. Using leading periods to represent whitespace:

[29] ZHU, B., LI, K., AND PATTERSON, H. Avoiding the disk bottleneck in
.....the data domain deduplication file system. In USENIX Conference on
File and Storage Technologies (FAST), 2008.

Or, I might have the final line suppressed entirely, even stranger!

[29] ZHU, B., LI, K., AND PATTERSON, H. Avoiding the disk bottleneck in
.....the data domain deduplication file system. In USENIX Conference on

I can't post my entire paper but perhaps I can show a minimal example. I want to start by asking if anyone has come across this and, hopefully, solved it. (Other than dropping flushend, which is obvious, but unsatisfactory.)

Here is a MWE template:

\documentclass[letterpaper,twocolumn,10pt,conference]{IEEEtran}

\usepackage{lipsum}
\usepackage{flushend}

\begin{document}

\lipsum
\cite{
% add a bunch of references from mwe.bib here -- 
% don't matter which as long as they appear before the one I see breaking 
% each time, zhu
zhu
}

  \bibliographystyle{acm}
  \bibliography{mwe}    
\end{document}

mwe.bib should include enough citations to go to 2 columns of the second page, including:

@inproceedings{zhu,
  author =        {Benjamin Zhu and Kai Li and Hugo Patterson},
  booktitle =     {USENIX Conference on File and Storage Technologies
                   (FAST'08)},
  month =         {Feb},
  title =         {Avoiding the Disk Bottleneck in the {D}ata {D}omain
                   Deduplication File System},
  year =          {2008},
}

I can't with this force the example where I was seeing the final line not appear, though I consistently see the indentation messed up. Copy some bibliography to mwe.bib and add a number of citations in the body of the document.

PS. This is likely related to Incompatibility between 'flushend' and 'lineno' packages! -- I am guessing flushend is breaking multiple things -- but I didn't see an appropriate answer there.

UPDATE: Just noticed that this problem occurs in a newly built system using a version of flushend with copyright through 2016, but does not occur in an older system using a version with copyright through 2014.

  • 1
    Why don't you add the cite commands? – Ulrike Fischer Apr 12 '17 at 15:59
  • Because it was a long list of citations from this paper, which would also require all the bibliography entries. It's possible that a different set of citations would somehow not result in either of the two odd behaviors I listed there, but I've certainly seen this before as well. How about if I put in the final bib entry that it breaks on, with the assumption that N other citations to things appearing before Zhu are equivalent? – Fred Douglis Apr 12 '17 at 16:02
  • 2
    If you want help you should provide an example that demonstrates the problem so that we can reproduce it. If this involves a long list of citations then you should spent the time to insert it, not we. And if the problem appears only with a specific set of citations then it is even more necessary that you build the test example. – Ulrike Fischer Apr 12 '17 at 16:11
  • @UlrikeFischer, this is why I said I hoped this was simply a known problem, and not something I needed to provide a MWE for, regardless of the "norms" of the site. My bib file is 300+ lines; including it in my question would simply scare anyone viewing it away or in any case decrease the number who would read it. Is there a way to attach such things rather than inline? I missed it if so. – Fred Douglis Apr 12 '17 at 16:28
3
\usepackage[keeplastbox]{flushend}

can fix the problem. See Balancing the last page in twocolumn LaTeX documents

UPDATE: Example (omit most comments); it seems that using tikz package causes the problem in my case.

%% bare_conf.tex
%% V1.4b
%% 2015/08/26
%% by Michael Shell
%% See:
%% http://www.michaelshell.org/
%% for current contact information.
%%
%% This is a skeleton file demonstrating the use of IEEEtran.cls
%% (requires IEEEtran.cls version 1.8b or later) with an IEEE
%% conference paper.
%%
%% Support sites:
%% http://www.michaelshell.org/tex/ieeetran/
%% http://www.ctan.org/pkg/ieeetran
%% and
%% http://www.ieee.org/


\documentclass[conference]{IEEEtran}

\hyphenation{op-tical net-works semi-conduc-tor}

\usepackage{tikz}
\usepackage{flushend}
%\usepackage[keeplastbox]{flushend}

\usepackage{filecontents}
\begin{filecontents*}{test.bib}

@inproceedings{zhu,
  author =        {Benjamin Zhu and Kai Li and Hugo Patterson},
  booktitle =     {USENIX Conference on File and Storage Technologies
                   (FAST'08)},
  month =         {Feb},
  title =         {Avoiding the Disk Bottleneck in the {D}ata {D}omain
                   Deduplication File System},
  year =          {2008},
}
\end{filecontents*}




\begin{document}

\title{Bare Demo of IEEEtran.cls\\ for IEEE Conferences}

\author{\IEEEauthorblockN{Michael Shell}}

\maketitle

\begin{abstract}
The abstract goes here.
\end{abstract}

\IEEEpeerreviewmaketitle

\section{Introduction}

This demo file is intended to serve as a ``starter file''
for IEEE conference papers produced under \LaTeX\ using
IEEEtran.cls version 1.8b and later.

I wish you the best of success.

\hfill mds

\hfill August 26, 2015

\subsection{Subsection Heading Here}
Subsection text here. Citations here \cite{zhu}.

\subsubsection{Subsubsection Heading Here}
Subsubsection text here.

\section{Conclusion}
The conclusion goes here.

\section*{Acknowledgment}
The authors would like to thank...

\bibliographystyle{IEEEtran}
\bibliography{test}


\end{document}

output is : \usepackage{flushend}

if using \usepackage[keeplastbox]{flushend}, results is: keeplastbox

  • 1
    I add the example. Although I don't know the reason, I think I encountered the same problem as Fred Douglis, and hope the answer can help. – Htallone Jul 5 '17 at 8:45
  • Thanks so much! I was holding off on acknowledging this as an accepted answer until I could repeat the problem and the fix, but since I posed it, things have changed, and repeating it seems nontrivial. I'll take your posted example (which wasn't there when I first looked) as sufficient evidence. Appreciate it!! – Fred Douglis Jul 5 '17 at 15:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.