twoside option breaks sidenote placement

[GoogleCodeExporter]

* What steps will reproduce the problem?

Use the [twoside] document class option.

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

Expect that the second page is formatted as every other even page. 
Instead, the second page (only) has its three sidenotes cut off on the
right-hand side, and the larger left-hand margin is empty.

On the last page (a right-hand page), the first sidenote is cut off on the
left-hand side, but the larger right-hand margin has another three
sidenotes.  Expect all four sidenotes in the larger right-hand margin.

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

2007/09/24 v1.0.1 Tufte-handout class, on Red Hat Enterprise Linux 4.

* Please provide any additional information below.

Thanks for making a consistent, beautiful class!  It's significantly better
than the ACM Transactions style I use.

Original issue reported on code.google.com by jason.ca...@gmail.com on 26 Sep 2007 at 6:05

[GoogleCodeExporter]

Yes, known behavior; will consider generalizing. Patch welcome.

Original comment by Bil.K...@gmail.com on 27 Sep 2007 at 12:42

• Changed state: Accepted

[GoogleCodeExporter]

I found the following in Robin Fairbairns' footmisc package -- it doesn't bode 
well
for making sidenotes and twoside live in harmony:

 1.3 Option side

 This option (suggested by Frank Mittelbach) causes footnotes
 to be typeset using the \marginpar command: this has the advantage
 that the note appears close to its "call-up", but has all the
 disadvantages associated with the \marginpar command (which consumes
 `float' slots, and doesn’t always place itself correctly at the top
 of pages in two-sided documents). Since the measure in which the
 footnote is to be typeset is likely to be pretty narrow, users of
 the side option are recommended also to use the ragged option, to
 avoid ugly spacing and line breaks.

 There is a further problem (apart from the occasional failure to
 place the marginal note on the correct side of the page) in two-
 sided documents: one would like `raggedness' to appear differently
 in different margins (setting the left, rather than the right,
 side ragged in the left margin). (The author would welcome
 suggestions on means of addressing the problem.)

Original comment by Bil.K...@gmail.com on 30 Sep 2007 at 4:00

[GoogleCodeExporter]

Should be fixed in r51.  Adding the `asymmetry' option to the `geometry' package
keeps the marginpars in the right side of the page, regardless of the 
oneside/twoside
option.

Original comment by godbyk@gmail.com on 16 May 2008 at 12:07

• Changed state: Fixed