Split file doesn't start new page - reader gets stuck

JLius · 03-15-2014, 05:18 PM

Hi

I'm new here, first post, not native speaker, but here it goes.

I'm creating an ebook from docx, using calibre book editor.
Managed to clean up css nicely, everything looks good, but I have one problem:

I tried to split a html file, as to make it two separate pages, but when I open the epub on my sony reader prs t1, I can't browse past the split file (only when I use the navigate to page I can get passed).
When I use the prs t2 from my wife, I can get passed the split, but it displays a blank page after every split file.

I really don't understand the problem. I've tried page breaks etc, but that doesn't work either. I have split some other pages in the epub, an there's no problem there, just here. Html looks just the same...

I checked the epub with calibre, epub validator and flightcrew, they all say my epub is fine.

Can anybody help me please?

Here is the html from the split file:

<?xml version='1.0' encoding='utf-8'?>
<html xmlns="http://www.w3.org/1999/xhtml">

<head>
<title>Promo</title>
<link href="stylesheet.css" rel="stylesheet" type="text/css"/>
</head>

<body>

‘text here’ – De Morgen



‘text here



‘text here

</body>

</html>

JLius · 03-15-2014, 05:33 PM

O, and this is the CSS for this eput:

@namespace h "http://www.w3.org/1999/xhtml";
@font-face {
font-family: "Alegreya";
font-weight: normal;
font-style: normal;
src: url(Alegreya-Regular.otf);
}
@font-face {
font-family: "Alegreya";
font-weight: bold;
font-style: normal;
src: url(Alegreya-Bold.otf);
}
@font-face {
font-family: "Alegreya";
font-weight: normal;
font-style: italic;
src: url(Alegreya-Italic.otf);
}
@font-face {
font-family: "Alegreya SC";
font-weight: normal;
font-style: normal;
src: url(AlegreyaSC-Regular.otf);
}
@font-face {
font-family: "Alegreya SC";
font-weight: normal;
font-style: italic;
src: url(AlegreyaSC-Italic.otf);
}
html, body {
margin: 0;
padding: 0;
border-width: 0;
height: 100%;
text-align: left;
font-weight: normal;
font-style: normal;
font-family: "Alegreya", serif;
}
@page {
margin: 20pt 6pt 6pt 12pt;
}
h2 {
padding-bottom: 40px;
}
h3 {
font-style: italic;
}
p {
font-size: 1em;
text-indent: 0;
line-height: 1.35em;
margin: 0;
}
em {
font-style: italic;
}
.p-foto {
text-align: center;
text-indent: 0;
}
.italic {
font-family: "Alegreya", serif;
font-style: italic;
}
.witregel {
padding-top: 1.35em;
}
.copyright {
font-family: "Alegreya SC", serif;
font-size: 0.75em;
}
.smallcap {
font-family: "Alegreya SC", serif;
}
sup {
line-height: normal;
vertical-align: text-top;
}
.S-Internet20link {
color: #00f;
text-decoration: underline;
}

theducks · 03-15-2014, 11:27 PM

The spine section of the OPF is not correct.

If you had split using Sigil or Calibre ebook-editor, the split action would have made the proper entry adjustments

Toxaris · 03-16-2014, 02:53 AM

That is not the problem Ducks. It is the height: 100% in the body/html part of the CSS. It is a known bug for this reader, or at least known by me. I have reported about it way back.
Anyway, the height: 100% serves no purpose here anyway.

JLius · 03-16-2014, 06:06 AM

@Toxaris
Don't know how to thank you! It works like a charm! I 've visited your website in the past, you taught me a lot about epubs.

Toxaris · 03-16-2014, 05:21 PM

Glad to help!

JLius · 03-17-2014, 03:47 AM

The rest of the CSS looks okay though? Or is it gonna conflict with other reading systems too?

Toxaris · 03-17-2014, 04:53 AM

Well, not in itself. However, be aware that some readers (the nook I believe) ignore font-family settings in the body and HTML class.

Another thing would be your line for a 'witregel'. The way you define it in your HTML might result that some reader systems would actually ignore the line since it has no content. You would be best of by either putting a   in the paragraph tag or have the paragraph following the 'witregel' a margin-top to create the effect. The choice is yours, depends on how much a purist you are.

JLius · 03-17-2014, 07:05 AM

Okay, so I can avoid this when I put the font-family in the p, h2 and h3? Should I include !important for font family? I've read that Ibooks ignores the fonts.

Do you forsee a problem with the class italic? I've read a post where someone suggests to define the class as i.italic, so that when a reader ignores the css you don't lose your italics.

For the witregel: If I define witregel in css as margin-top: 1,35 em, and include is as a class in the p like this: . Would this solve that problem too?

Thanks again!

Toxaris · 03-17-2014, 01:30 PM

For iBooks you need an additional file in your ePUB. If you do a quick search on the forum, you can find it quick enough. ePUB's created with my Word Add-in have this file already present.

Readers that ignore css are not good readers anyway. Perhaps some very lame readers don't support it. I personally use .

Font family in the p, h2, etc is fine. You could include !important. Some readers work better with it. I know that some readers (again Nook I believe) overrule certain book styling without it.

With regards to the 'witregel' I can say that it would solve it. In that case you can delete .

JLius · 03-18-2014, 04:23 AM

Sadly I have no ms word. I use libreoffice. Thank you for the tips, I'll try and find the file for ibooks you're referring to.

Toxaris · 03-18-2014, 08:04 AM

I searched for you. You need to add the file com.apple.ibooks.display-options.xml in the META-INF folder with the following content:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<display_options>
<platform name="*">
<option name="specified-fonts">true</option>
</platform>
</display_options>

JLius · 03-18-2014, 09:25 AM

I bet you're getting tired of hearing 'thank you', so I'll just say it in Dutch: bedankt!

03-15-2014, 05:18 PM	#1
JLius Village idiot Posts: 157 Karma: 519566 Join Date: Mar 2014 Location: Belgium Device: sony PRS T-1	Split file doesn't start new page - reader gets stuck Hi I'm new here, first post, not native speaker, but here it goes. I'm creating an ebook from docx, using calibre book editor. Managed to clean up css nicely, everything looks good, but I have one problem: I tried to split a html file, as to make it two separate pages, but when I open the epub on my sony reader prs t1, I can't browse past the split file (only when I use the navigate to page I can get passed). When I use the prs t2 from my wife, I can get passed the split, but it displays a blank page after every split file. I really don't understand the problem. I've tried page breaks etc, but that doesn't work either. I have split some other pages in the epub, an there's no problem there, just here. Html looks just the same... I checked the epub with calibre, epub validator and flightcrew, they all say my epub is fine. Can anybody help me please? Here is the html from the split file: <?xml version='1.0' encoding='utf-8'?> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Promo</title> <link href="stylesheet.css" rel="stylesheet" type="text/css"/> </head> <body> <p class="italic">‘text here’<span class="smallcap"> – De Morgen</span></p> <p class="witregel"></p> <p class="italic">‘text here</span></p> <p class="witregel"></p> <p class="italic">‘text here</span></p> </body> </html> Last edited by JLius; 03-17-2014 at 08:51 AM. Reason: privacy

03-17-2014, 07:05 AM	#9
JLius Village idiot Posts: 157 Karma: 519566 Join Date: Mar 2014 Location: Belgium Device: sony PRS T-1	Okay, so I can avoid this when I put the font-family in the p, h2 and h3? Should I include !important for font family? I've read that Ibooks ignores the fonts. Do you forsee a problem with the class italic? I've read a post where someone suggests to define the class as i.italic, so that when a reader ignores the css you don't lose your italics. For the witregel: If I define witregel in css as margin-top: 1,35 em, and include is as a class in the p like this: <p class="italic witregel">. Would this solve that problem too? Thanks again!

03-17-2014, 01:30 PM	#10
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	For iBooks you need an additional file in your ePUB. If you do a quick search on the forum, you can find it quick enough. ePUB's created with my Word Add-in have this file already present. Readers that ignore css are not good readers anyway. Perhaps some very lame readers don't support it. I personally use <i></i>. Font family in the p, h2, etc is fine. You could include !important. Some readers work better with it. I know that some readers (again Nook I believe) overrule certain book styling without it. With regards to the 'witregel' I can say that it would solve it. In that case you can delete <p class="witregel"></p>.

03-18-2014, 08:04 AM	#12
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	I searched for you. You need to add the file com.apple.ibooks.display-options.xml in the META-INF folder with the following content: Code: <?xml version="1.0" encoding="UTF-8"?> <display_options> <platform name="*"> <option name="specified-fonts">true</option> </platform> </display_options>

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
File split sometimes shows more split lines	DrChiper	Editor	1	12-23-2013 06:38 PM
Can I split one epub into more than one file?	ChrisKaos	ePub	10	04-05-2012 07:05 AM
Classic Nook Classic stuck in start up cycle	Tattncat	Barnes & Noble NOOK	5	12-02-2011 02:53 AM
Split page in half	Zorz	PDF	1	01-27-2010 01:16 PM
Problem with html->epub: reader can't page through file	horseflesh	Calibre	5	10-20-2009 01:22 AM

03-15-2014, 05:33 PM	#2
JLius Village idiot Posts: 157 Karma: 519566 Join Date: Mar 2014 Location: Belgium Device: sony PRS T-1	O, and this is the CSS for this eput: @namespace h "http://www.w3.org/1999/xhtml"; @font-face { font-family: "Alegreya"; font-weight: normal; font-style: normal; src: url(Alegreya-Regular.otf); } @font-face { font-family: "Alegreya"; font-weight: bold; font-style: normal; src: url(Alegreya-Bold.otf); } @font-face { font-family: "Alegreya"; font-weight: normal; font-style: italic; src: url(Alegreya-Italic.otf); } @font-face { font-family: "Alegreya SC"; font-weight: normal; font-style: normal; src: url(AlegreyaSC-Regular.otf); } @font-face { font-family: "Alegreya SC"; font-weight: normal; font-style: italic; src: url(AlegreyaSC-Italic.otf); } html, body { margin: 0; padding: 0; border-width: 0; height: 100%; text-align: left; font-weight: normal; font-style: normal; font-family: "Alegreya", serif; } @page { margin: 20pt 6pt 6pt 12pt; } h2 { padding-bottom: 40px; } h3 { font-style: italic; } p { font-size: 1em; text-indent: 0; line-height: 1.35em; margin: 0; } em { font-style: italic; } .p-foto { text-align: center; text-indent: 0; } .italic { font-family: "Alegreya", serif; font-style: italic; } .witregel { padding-top: 1.35em; } .copyright { font-family: "Alegreya SC", serif; font-size: 0.75em; } .smallcap { font-family: "Alegreya SC", serif; } sup { line-height: normal; vertical-align: text-top; } .S-Internet20link { color: #00f; text-decoration: underline; }

03-15-2014, 11:27 PM	#3
theducks Well trained by Cats Posts: 30,627 Karma: 58055868 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	The spine section of the OPF is not correct. If you had split using Sigil or Calibre ebook-editor, the split action would have made the proper entry adjustments

03-16-2014, 02:53 AM	#4
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	That is not the problem Ducks. It is the height: 100% in the body/html part of the CSS. It is a known bug for this reader, or at least known by me. I have reported about it way back. Anyway, the height: 100% serves no purpose here anyway.

03-16-2014, 06:06 AM	#5
JLius Village idiot Posts: 157 Karma: 519566 Join Date: Mar 2014 Location: Belgium Device: sony PRS T-1	@Toxaris Don't know how to thank you! It works like a charm! I 've visited your website in the past, you taught me a lot about epubs.

03-16-2014, 05:21 PM	#6
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	Glad to help!

03-17-2014, 03:47 AM	#7
JLius Village idiot Posts: 157 Karma: 519566 Join Date: Mar 2014 Location: Belgium Device: sony PRS T-1	The rest of the CSS looks okay though? Or is it gonna conflict with other reading systems too?

03-17-2014, 04:53 AM	#8
Toxaris Wizard Posts: 4,520 Karma: 121692313 Join Date: Oct 2009 Location: Heemskerk, NL Device: PRS-T1, Kobo Touch, Kobo Aura	Well, not in itself. However, be aware that some readers (the nook I believe) ignore font-family settings in the body and HTML class. Another thing would be your line for a 'witregel'. The way you define it in your HTML might result that some reader systems would actually ignore the line since it has no content. You would be best of by either putting a   in the paragraph tag or have the paragraph following the 'witregel' a margin-top to create the effect. The choice is yours, depends on how much a purist you are.

03-18-2014, 04:23 AM	#11
JLius Village idiot Posts: 157 Karma: 519566 Join Date: Mar 2014 Location: Belgium Device: sony PRS T-1	Sadly I have no ms word. I use libreoffice. Thank you for the tips, I'll try and find the file for ibooks you're referring to.

03-18-2014, 09:25 AM	#13
JLius Village idiot Posts: 157 Karma: 519566 Join Date: Mar 2014 Location: Belgium Device: sony PRS T-1	I bet you're getting tired of hearing 'thank you', so I'll just say it in Dutch: bedankt!

Advert

Advert