Page Breaks

abarrow · 22 March 2013 13:29

Hi all,

I know page breaks don't work that well in HTML. I've added breaks to my results publishing options, and I can see them in the source, but I never seem be able to get them to work when printing. I just get a long continuous page with inconvenient breaks. I use Chrome - this might have something to do with it.

Anyone have any suggestions?

Also, for Jon, assuming I can get page breaks to print properly, what are the chances of getting the same page break code added to the Populated Sign on / Sign off sheet?

Andy

abarrow · 22 March 2013 13:48

Just to (somewhat) answer my own question, I changed the page break code in an example results like this:

<!DOCTYPE html>

<html>
  <head>
    <meta http-equiv="content-type" content="text/html;charset=UTF-8" />
    <title>Paginated HTML</title>
    <style type="text/css" media="print">
      div.page
      {
        page-break-after: always;
        page-break-inside: avoid;
      }
    </style>
  </head>
  <body>
    <div class="page">
      <h1>This is Page 1</h1>
    </div>
    <div class="page">
      <h1>This is Page 2</h1>
    </div>
    <div class="page">
      <h1>This is Page 3</h1>
    </div>
  </body>
</html>

It worked much, much better, even in Chrome. Pagination worked just as I expected it to.

Andy

···

--- In sailwave@yahoogroups.com, "Andy" <andy@...> wrote:

Hi all,

I know page breaks don't work that well in HTML. I've added breaks to my results publishing options, and I can see them in the source, but I never seem be able to get them to work when printing. I just get a long continuous page with inconvenient breaks. I use Chrome - this might have something to do with it.

Anyone have any suggestions?

Also, for Jon, assuming I can get page breaks to print properly, what are the chances of getting the same page break code added to the Populated Sign on / Sign off sheet?

Andy

Sailwave · 22 March 2013 13:57

Hi Andy,

I personally use Firefox for printing from Sailwave as I find it gives the best flexibility as you can preview it and scale it to get page breaks better before you print it.

How would you envisage the page break working with the Sign on/off declaration?

Jon

···

Jon Eskdale
07976 709777

Skype “eskdale”

On 22 March 2013 13:29, Andy andy@sailor.nu wrote:

Hi all,

I know page breaks don’t work that well in HTML. I’ve added breaks to my results publishing options, and I can see them in the source, but I never seem be able to get them to work when printing. I just get a long continuous page with inconvenient breaks. I use Chrome - this might have something to do with it.

Anyone have any suggestions?

Also, for Jon, assuming I can get page breaks to print properly, what are the chances of getting the same page break code added to the Populated Sign on / Sign off sheet?

Andy

MalcolmO · 22 March 2013 21:01

Using your example, the output shows as one page, with your style statements (div.page ... ) showing on the page (in FF and Chrome). Doesn't seem like they are being interpreted correctly.

regards,
Malcolm Osborne
Sedgefield South Africa

···

On 2013/03/22 15:48, Andy wrote:

Just to (somewhat) answer my own question, I changed the page break code in an example results like this:

<!DOCTYPE html>

<html>
<head>
<meta http-equiv="content-type" content="text/html; />
<title>Paginated HTML</title>
<style type="text/css" media="print">
div.page
{
page-break-after: always;
page-break-inside: avoid;
}
</style>
</head>
<body>
<div class="page">
<h1>This is Page 1</h1>
</div>
<div class="page">
<h1>This is Page 2</h1>
</div>
<div class="page">
<h1>This is Page 3</h1>
</div>
</body>
</html>

It worked much, much better, even in Chrome. Pagination worked just as I expected it to.

Andy

--- In sailwave@yahoogroups.com <mailto:sailwave%40yahoogroups.com>, "Andy" <andy@...> wrote:
>
> Hi all,
>
> I know page breaks don't work that well in HTML. I've added breaks to my results publishing options, and I can see them in the source, but I never seem be able to get them to work when printing. I just get a long continuous page with inconvenient breaks. I use Chrome - this might have something to do with it.
>
> Anyone have any suggestions?
>
> Also, for Jon, assuming I can get page breaks to print properly, what are the chances of getting the same page break code added to the Populated Sign on / Sign off sheet?
>
> Andy
>

Sailwave · 22 March 2013 21:54

Hi Andy,

Yes your code does produce 3 pages and it works in IE10, Chrome and Firefox. But I’m not sure how you would intend it to work, would you want to be able to specify the number of lines before a page break. The trouble is there is no easy way that I know of when you are generating html code to know when it is going to be at the end of a page because this will depend on the font size and the CSS code. By specifying the number of lines before a page break this would work but you would have to adjust it by trial and error.

Jon

···

Jon Eskdale
07976 709777

Skype “eskdale”

On 22 March 2013 21:01, Malcolm Osborne malcolmo@telkomsa.net wrote:

  Using your example, the output shows as
one page, with your style statements (div.page … ) showing on
the page (in FF and Chrome). Doesn’t seem like they are being
interpreted correctly.
regards,
Malcolm Osborne
Sedgefield South Africa
On 2013/03/22 15:48, Andy wrote:

          Just to (somewhat) answer my own question, I changed the

page break code in an example results like this:

          <!DOCTYPE html>



          <html>

          <head>

          <meta http-equiv="content-type" content="text/html;

/>

          <title>Paginated HTML</title>

          <style type="text/css" media="print">

          div.page

          {

          page-break-after: always;

          page-break-inside: avoid;

          }

          </style>

          </head>

          <body>

          <div class="page">

          <h1>This is Page 1</h1>

          </div>

          <div class="page">

          <h1>This is Page 2</h1>

          </div>

          <div class="page">

          <h1>This is Page 3</h1>

          </div>

          </body>

          </html>



          It worked much, much better, even in Chrome. Pagination

worked just as I expected it to.

          Andy



          --- In sailwave@yahoogroups.com              ,

“Andy” <andy@…> wrote:

          >

          > Hi all,

          >

          > I know page breaks don't work that well in HTML. I've

added breaks to my results publishing options, and I can
see them in the source, but I never seem be able to get
them to work when printing. I just get a long continuous
page with inconvenient breaks. I use Chrome - this might
have something to do with it.

          >

          > Anyone have any suggestions?

          >

          > Also, for Jon, assuming I can get page breaks to

print properly, what are the chances of getting the same
page break code added to the Populated Sign on / Sign off
sheet?

abarrow · 23 March 2013 04:35

Good point. I guess I was thinking just to do the number selection as in the results. I'd be willing to figure out what the optimum lines per page should be with whatever font is coming out. As long as the headers were printed on each page properly, and there aren't breaks in the tables in the middle of rows.

Andy

···

--- In sailwave@yahoogroups.com, Jon Eskdale <jon@...> wrote:

Hi Andy,

Yes your code does produce 3 pages and it works in IE10, Chrome and
Firefox. But I'm not sure how you would intend it to work, would you want
to be able to specify the number of lines before a page break. The trouble
is there is no easy way that I know of when you are generating html code to
know when it is going to be at the end of a page because this will depend
on the font size and the CSS code. By specifying the number of lines
before a page break this would work but you would have to adjust it by
trial and error.

Jon

Jon Eskdale
07976 709777
Skype "eskdale"

On 22 March 2013 21:01, Malcolm Osborne <malcolmo@...> wrote:

> **
>
>
> Using your example, the output shows as one page, with your style
> statements (div.page ... ) showing on the page (in FF and Chrome). Doesn't
> seem like they are being interpreted correctly.
>
> regards,
> Malcolm Osborne
> Sedgefield South Africa
>
> On 2013/03/22 15:48, Andy wrote:
>
>
>
> Just to (somewhat) answer my own question, I changed the page break code
> in an example results like this:
>
> <!DOCTYPE html>
>
> <html>
> <head>
> <meta http-equiv="content-type" content="text/html; />
>
> <title>Paginated HTML</title>
> <style type="text/css" media="print">
> div.page
> {
> page-break-after: always;
> page-break-inside: avoid;
> }
> </style>
> </head>
> <body>
> <div class="page">
> <h1>This is Page 1</h1>
> </div>
> <div class="page">
> <h1>This is Page 2</h1>
> </div>
> <div class="page">
> <h1>This is Page 3</h1>
> </div>
> </body>
> </html>
>
> It worked much, much better, even in Chrome. Pagination worked just as I
> expected it to.
>
> Andy
>
> --- In sailwave@yahoogroups.com, "Andy" <andy@> <andy@> wrote:
> >
> > Hi all,
> >
> > I know page breaks don't work that well in HTML. I've added breaks to my
> results publishing options, and I can see them in the source, but I never
> seem be able to get them to work when printing. I just get a long
> continuous page with inconvenient breaks. I use Chrome - this might have
> something to do with it.
> >
> > Anyone have any suggestions?
> >
> > Also, for Jon, assuming I can get page breaks to print properly, what
> are the chances of getting the same page break code added to the Populated
> Sign on / Sign off sheet?
> >
> > Andy
> >
>
>
>
>

Sailwave · 29 March 2013 23:12

I’ve spent the last few evenings updating my Competitor list program to work well with the latest version of Sailwave. Partly because I want to use it myself at the Youth Nationals in Largs next week (If anyone else is in Largs next week feel free to say hello)

For those that would like to play with it as it is now you can download it from here

Download SWCList

There are still a few things left to do with it but it is fully functional and I’d like some feedback as to any changes you would like to see.

Andy has been talking of page breaks and this program does support them

For those of you who haven’t used it before I wrote it couple of years ago and use it regularly myself especially for Tally list and producing lists of 4 digit sail no’s for Lasers. And also checking for Duplicate sail numbers

A quick summary of some of the features :-

Ability to sort on 3 Columns
Ability to Create and sort on last 4 or 3 digits of sail number
Can sort on Lastname (HelmNameRev) when Sailwave format is “Firstname Lastname”
Highlights in Bold any duplicate sail numbers full and shortened
Ability to add Headings on changes of Sort key
Adds Count to Headings
Can produce page breaks and adds column headers for multiple pages
Only temporarily opens file in read only mode so can be used in Multiuser situations
Sorts Gold Silver Bronze in correct order ( not alphabetical ) Also Yellow Blue Red and Green

Details of Orginal Version 1 can be found here

Going back to page breaks have a look at this VIDEO

It shows how you can use it to generate a Sign out / Sign in sheet with page breaks and headings repeated on following pages. Is this what you had in mind Andy? (The Browser I’m using for the Demo is IE10 but Firefox is similar and perhaps better in my personal opinion)

Click the following link to watch the video

SWCList demo video of page breaks using Sign out sheet

Jon

···

— In sailwave@yahoogroups.com, “Andy” <andy@…> wrote:

Just to (somewhat) answer my own question, I changed the page break code in an example results like this:
Paginated HTML div.page { page-break-after: always; page-break-inside: avoid; }

This is Page 1

This is Page 2

This is Page 3

It worked much, much better, even in Chrome. Pagination worked just as I expected it to.

Andy

— In sailwave@yahoogroups.com, “Andy” andy@ wrote:

Hi all,

I know page breaks don’t work that well in HTML. I’ve added breaks to my results publishing options, and I can see them in the source, but I never seem be able to get them to work when printing. I just get a long continuous page with inconvenient breaks. I use Chrome - this might have something to do with it.

Anyone have any suggestions?

Also, for Jon, assuming I can get page breaks to print properly, what are the chances of getting the same page break code added to the Populated Sign on / Sign off sheet?

Andy