You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Transferred from Bugzilla, bug #37, 24 July 2014. )
This book is made up of four files, all xhtml, which contain a JPG. There are rendition page spread position on each of the spine items, asking the jpgs to be either a right or a left hand page.
What is happening is they are being rendered as four consecutive pages, ignoring the left/right information in BOTH single pages and synthetic spreads
Repro Steps
Be sure synthetic spreads are off
Open 9_Fixed_Spreads_JPG_XHTML
Note that the JPGS follow one right after another
Go back to the first page and enable synthetic spreads
Note that the content becomes two spreads
It should be a left page, a left page, a right page, and a left page
Also, why area the circles disproportionally reduced into ovals? They should fit in the viewport without being altered.
The text was updated successfully, but these errors were encountered:
Patrick explained to me why the shape might be distorted. Please ignore the comment on the shape of the JPG.
Additionally, Patrick mentioned that to get a blank right between two rights, the author would need to insert a blank page. Is this true? It seems to defeat the point of having positioned spreads. Please let me know.
(Transferred from Bugzilla, bug #37, 24 July 2014. )
This book is made up of four files, all xhtml, which contain a JPG. There are rendition page spread position on each of the spine items, asking the jpgs to be either a right or a left hand page.
What is happening is they are being rendered as four consecutive pages, ignoring the left/right information in BOTH single pages and synthetic spreads
Repro Steps
It should be a left page, a left page, a right page, and a left page
Also, why area the circles disproportionally reduced into ovals? They should fit in the viewport without being altered.
The text was updated successfully, but these errors were encountered: