Flowfram no pasa de un flowframe a otro después de actualizar el paquete flowfram

Flowfram no pasa de un flowframe a otro después de actualizar el paquete flowfram

Hoy actualicé mi distribución TeX debido a otro problema, de una distribución TL13 alrededor de septiembre de 2013 a una distribución TL14 (la más reciente).

Después de actualizar, flowframignora una de mis \newflowframedeclaraciones, lo que provoca flowframque continúe usando el diseño de tres columnas imitado de declaraciones anteriores. Esto sólo parece suceder con mi bibliografía, usando natbib.

El siguiente código:

\documentclass{article}
\usepackage[margin=2cm]{geometry}
\usepackage{flowfram}
\usepackage{lipsum}
\usepackage{kantlipsum}
\usepackage[bitstream-charter]{mathdesign}
\usepackage[square, numbers, sort]{natbib}
\usepackage{hyperref}

\newflowframe[1,2]{\dimexpr\textwidth/3-2\columnsep/3}{\textheight}{0pt}{0pt}
\newflowframe[1,2]{\dimexpr\textwidth/3-2\columnsep/3}{\textheight}{\dimexpr\textwidth/3-2\columnsep/3+\columnsep}{0pt}
\newflowframe[1,2]{\dimexpr\textwidth/3-2\columnsep/3}{\textheight}{\dimexpr2\textwidth/3-4\columnsep/3+2\columnsep}{0pt}

\newflowframe[3]{\textwidth}{\textheight}{0pt}{0pt}% or \newflowframe*[>2]{\textwidth}{\textheight}{0pt}{0pt}

\begin{document}
\tolerance=4000

When considering the EoL phase, it's desirable to initially consider the shortest possible cycles of energy, namely reuse, and in closing consider the largest possible cycle, which would be recycling. Case studies in the UK have mapped the waste problem to comprise as much as 15 million discarded mobile phones each year\citep{website:fonebak}. Large scale reuse brings problems, however. A variety of problems arise when considering reuse of mobile phones, such as their low residual value, their small size or the complexity of channels through which they are distributed\citep{ends1997}. Furthermore, a case study reveals most private customers prefer to give mobile phones away\citep{ends2000}, making the previously mentioned legislation of EPR a considerably hard task to achieve. Currently, manufacturers, retails and mobile phone operators. Figures from Foneback\citep{website:fonebak} suggest this to be inadequate. One suggestion would be to promote horizontal collaboration between competitors\citep{canning2006}. Coercion among competitors puts forward a problem in the same fashion as that of renewable energy in the industry sector, namely the problem of managing and putting constraints on collective goods: to promote a change, everybody has to invest into renewable energy. So even though competitors would want to make a change, that change hits a threshhold. A consequence of such constraints is a hit to the economy as we know it now, which inherently forces a gradual change. One recommendation would be to develop a mathematical model, determining how steep this gradual change would have to be to compensate for the need for change currently. Removing a such barrier would be vital to success of reuse practices as we know them now.

\lipsum[1-8]
\cleardoublepage
\small
\bibliographystyle{unsrtnat}
\bibliography{paper}
\end{document}

Con algunas entradas bibliográficas, por lo que en realidad compone una bibliografía:

@misc{website:fonebak,
  title = {Fonebak - Facts},
  url = {http://www.fonebak.com/},
  note = {(accessed 28-9-2014)},
  year = {2014}
}

@REPORT{ends1997,
    author = {Environmental Data Services (ENDS)},
    title = {Take back schemes launched for mobile phones},
    issue = {264},
    year = {1997},
    month = {January}
}

@REPORT{ends2000,
    author = {Environmental Data Services (ENDS)},
    title = {Compliance scheme envisaged for mobile phone recycling},
    issue = {304},
    year = {2000},
    month = {May}
}

@ARTICLE{canning2006,
    author = {Louise Canning},
    title = {Rethinking market connections: mobile phone recovery, reuse and recycling in the {UK}},
    journal = {Journal of Business \& Industrial Marketing},
    volume = {21},
    issue = {5},
    year = {2006},
    pages = {320--329}
}

Ambos archivos también se pueden obtener a través del siguiente enlace: (paquete zip)

El marco de flujo de diseño de una sola columna declarado anteriormente ( \newflowframe[3]{\textwidth}{\textheight}{0pt}{0pt}% or \newflowframe*[>2]{\textwidth}{\textheight}{0pt}{0pt}) se ignora (aparentemente). En cambio, continúa escribiendo un diseño de tres columnas:

http://i.imgur.com/Y2ZKF8G.png

Anteriormente, el resultado simplemente obedecía el diseño que declaré, algo como esto (del documento principal; obviamente ya no puedo imitar el resultado):

http://i.imgur.com/8UWfRU8.png?1

Respuesta1

Este es un efecto secundario no deseado de una corrección de error que era necesaria para solucionar un problema cuando los entornos de lista abarcaban dos marcos de flujo de diferentes anchos. Aquí hay un ejemplo mínimo que ilustra el problema:

\documentclass{article} 

\usepackage{flowfram}
\usepackage{lipsum}

\twocolumn[1,2]
\onecolumn[>2]

\begin{document}

\lipsum[1-10]
\clearpage
\lipsum[1]

\begin{itemize}
 \item \lipsum*[2]
\end{itemize}

\end{document}

El problema sólo afecta a los entornos de lista y dado que la bibliografía está en uno de estos entornos, esa es la causa del problema en su documento. Puede solucionarlo insertándolo \linewidth\columnwidthantes del entorno de la lista. Por ejemplo:

\documentclass{article} 

\usepackage{flowfram}
\usepackage{lipsum}

\twocolumn[1,2]
\onecolumn[>2]

\begin{document}

\lipsum[1-10]
\clearpage
\lipsum[1]

\linewidth\columnwidth

\begin{itemize}
 \item \lipsum*[2]
\end{itemize}

\end{document}

Para su documento de ejemplo colocado \linewidth\columnwidthdelante de \bibliography.

Editar: Solucioné este error y cargué la versión 1.17 en CTAN. Es posible que pasen algunos días antes de que lleguen las distribuciones.

información relacionada