Adobe, Acrobat, 9 Pro (Macintosh) unable to interpret "page-break-after:always from HTML

in Acrobat 8 if you had the following in your HTML head:

<style>
p.pagebtreak
{
page-break-after:always;
}
.
.
.
<style>

and then in the body html file put:

<p class="pagebreak"></p>

you would force a new  page begining with the text immediately following.

This does not work in Acrobat 9 (or at least not for me in Windows) What is wrong with the code? Or what does work in Acrobat 9

DD
Deputy-DawgAsked:
Who is Participating?
 
scrathcyboyConnect With a Mentor Commented:
If you didn't uninstall 8 from the system, 9 will use the same drivers and not work correctly.  This is an ongoing problem with Acrobat, I just got a call about it tonight, where the user could not get rid of the old drivers even after an uninstall.  Put it on system that has NEVER had any version.  Being active at the same time is not the issue, it is totally removing the previous version.  Anyway, it might not work in 9 regardless.
0
 
scrathcyboyCommented:
"p.pagebtreak"  -- I presume that is a typo?

Pagebreak after simply does not work on all browsers.  It works on some, but not others.  If you want the page breaks to be guaranteed at the right place on all user systems, simply save the page as a PDF and let the user download it and print it.  THat is the only way to guarantee the print layout you want.  CSS styling really messes up printed output on many platforms, which is why all major news sites provide a priint button, which removes all DIVs (big cause of print problems) and images, and makes a new page of just the text.  This is the other way to do it, if you want to write double code for every page.
0
 
Deputy-DawgAuthor Commented:
I guess I wasn't clear enough on what the project is. It is to convert a some files in HTML to pdf using in the first instance Acrobat 8 as the "printer" and in the second Acrobat 9 as the printer. The code given cause a page feed in documents created in Acrobat 8 (and in Acrobat 6 as well. It does not work in documents create in Acrobat 9 using the same files used in Acrobat 8 (and 6). According to Adobe it should but it doesn't for me.

And, yes, I agree presenting the documents as Adobe pdf files is the best and cleanest solution for distributing files when it is desired to control the visual appearance of the document. Which is why we desire to convert the HTML into pdf.d
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
scrathcyboyCommented:
do you have both 8 and 9 on the same system?  If so, it will not work, can only use one set of drivers
0
 
Deputy-DawgAuthor Commented:
As it happens they are on different systems, in fact 8 is on a Mac and 9 (a 30 day trial version) is on a Windows XP machine. The driver problem does not seem to exist in the Mac world. At least not with 6 and 8. I must admit, out of an abundance of caution I have never had both programs active at the same time. So I would hazard that there would be no difficulty with 8 and 9 under the same circumstances..

DD
0
 
Karl Heinz KremerCommented:
This is not a driver problem - creating PDFs from HTML is done in Acrobat, and not via a driver, so even if you have two different versions installed on the same system, it should not matter.

As far as I know, Acrobat 9 uses WebKit as it's rendering engine, so if the same constructs work in Safari, there is something wrong with how Adobe is using WebKit. I also think that the rendering engine was changed from Acrobat 8 to 9 - in general, it's now doing a much better job than the one in Acrobat 8.

I assume you came across a bug in Acrobat 9. I'm not an expert on HTML or CSS, so I cannot help you with coming up with a workaround.
0
 
Karl Heinz KremerConnect With a Mentor Commented:
As I've indicated, the behavior seems to be due to a bug in Acrobat's rendering engine, and there is nothing that the user can do about this besides waiting for Adobe to come up with a fix.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.