Bug setting custom paper sizes in landscape mode

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Simply set a custom paper size in landscape mode, i.e. 
\documentclass[landscape,paperwidth=XX,paperheight=YY]{baposter}.  The bug also 
appears to affect the archE paper setting in landscape mode.  The bug occurs 
for any dimension units (inches, cm, or points) used.

What is the expected output? What do you see instead?

Expect a landscape poster laid out with the specified dimensions.  Instead, 
produces poster laid out with either wildly scaled top/bottom or left/right 
margins (as a sanity check, I checked either permutation of the width/height 
dimension, to make sure I wasn't just misunderstanding the implementation of 
width vs height dimensions).  Attempts to typeset poster within an oddly scaled 
box oriented at 90 degrees to the apparent paper size.

What version of the product are you using? On what operating system?

written in Kile running on ubuntu 11.04.  Bug occurs when compiled with either 
latex or pdflatex.  Using the newest version of class file.  Note that the bug 
also occurs when compiling the sample posters included in the download package.

Please provide any additional information below.

My surmise, based on a quick reading of the class file, is that at some point 
the dimensions are transposed improperly when converting to landscape mode, in 
which the class file "flips" all of the paper dimensions.  It seems that the 
base paper size and final paper size end up at odds with each other, as seems 
to try to lay out an X by Y poster on Y by X paper and vice versa, thereby 
producing the odd margins.  This seems supported by a workaround of simply 
using portrait mode (so the dimensions are not transposed in the class file) 
and manually setting the desired dimensions - for example, using 
\documentclass[portrait,paperwidth=48in,paperheight=36in]{baposter} produces a 
properly typeset archE *landscape* poster.  However, this workaround could 
likely cause problems for printers, so a less hacked fix is necessary.

Original issue reported on code.google.com by johnrw...@gmail.com on 28 Sep 2011 at 6:10

[GoogleCodeExporter]

Fixed the bug. It required different handling of paper sizes known to geometry 
and custom sizes.

Original comment by brian.amberg@gmail.com on 4 Oct 2011 at 7:08

• Changed state: Fixed