I have two different folders saved on my flash drive. One is "compiled." The other is "converted." They both have .mobi files in them. The most recently made .mobi is in the "converted" folder, and that's the one I'd like to go with, but I'd like to know what the difference is between compiled and converted is and if that has any bearing on the .mobi files within. (see screenshot--it's from the flashdrive) Thanks.
↧
what's the difference between "compiled" and "converted" folders?
↧
Kindle Fire - Displaying map image pages
Hello All,
I have 25 map images arranged in a 5x5 layout.
Is it possible to create a mobi file (maybe from HTML) that will display each map image on its own Kindle screen and allow the user to swipe vertically and horizontally to see the adjacent page.
Any tips or pointers to an answer would be much appreciated.
Thanks in advance
I have 25 map images arranged in a 5x5 layout.
Is it possible to create a mobi file (maybe from HTML) that will display each map image on its own Kindle screen and allow the user to swipe vertically and horizontally to see the adjacent page.
Any tips or pointers to an answer would be much appreciated.
Thanks in advance
↧
↧
What should be in a MOBI file?
This a bit of an odd question, but my experience of MOBI is a bit limited and I wasnt 100% sure if this file was as strange as it seems.
From the quality of their ePUB, Im guessing that this new publisher doesnt quite know what hes doing, but anyway heres whats Calibres KindleUpack gives me...
\mobi7\
\mobi8\
kindlegenbuild.log
kindlegensrc.zip
Is it normal to include this source file in the MOBI? Its 4MB of the files ~5MB.
The ePUB edition is ~3.5MB because it has a huge resolution cover (3.2MB vs. 111KB in MOBI edition). There doesnt seem to be a very coherent strategy here.
From the quality of their ePUB, Im guessing that this new publisher doesnt quite know what hes doing, but anyway heres whats Calibres KindleUpack gives me...
\mobi7\
\mobi8\
kindlegenbuild.log
kindlegensrc.zip
Is it normal to include this source file in the MOBI? Its 4MB of the files ~5MB.
The ePUB edition is ~3.5MB because it has a huge resolution cover (3.2MB vs. 111KB in MOBI edition). There doesnt seem to be a very coherent strategy here.
↧
can I sell mobi-files (and epubs) in my shop? legal issues?
Hi there,
This is a question concerning the legal rights and the format mobipocket itself.
We produce epubs and mobis for a customer. Now he asks me, if it is ok for him to sell the mobis in his shop.
I am not sure if there are any legal problems in doing this.
As much as I see the format mobi belongs to Amazon.
I am sure, that Amazon is not happy if some else sells mobis, but might it be a legal issue?
I have not found anything that says, that it is illegal so sell a mobi-file, but you never know...
thanks
Georg
This is a question concerning the legal rights and the format mobipocket itself.
We produce epubs and mobis for a customer. Now he asks me, if it is ok for him to sell the mobis in his shop.
I am not sure if there are any legal problems in doing this.
As much as I see the format mobi belongs to Amazon.
I am sure, that Amazon is not happy if some else sells mobis, but might it be a legal issue?
I have not found anything that says, that it is illegal so sell a mobi-file, but you never know...
thanks
Georg
↧
Mobi with Asin and CDE
Hi Guys,
is there a way how to change mobi to be address as ebook in Amazon, not as personal kindle file? I tried with java metaeditor to change and add asin, but still no luck.
is there a way how to change mobi to be address as ebook in Amazon, not as personal kindle file? I tried with java metaeditor to change and add asin, but still no luck.
↧
↧
KF8 and raised cap
I would like to have a "raised cap" for the chapter starting paragraphs of my KF8-book.
is one version I tested. I tried span, various line-height settings etc but Kindle Paperwhite is stubborn: the height of the first line is always computed from the first letter font-size. So the first line has a greater height than the other lines of the paragraph.
I know about the 1.2em / 120% line-height minimum of KF8, but perhaps someone has some css to get nice looking raised caps.
Thanks in advance.
Code:
.parafirst {font-size: 100%;line-height: 120% ..}
.parafirst:first-letter {font-size: 300% ...}I know about the 1.2em / 120% line-height minimum of KF8, but perhaps someone has some css to get nice looking raised caps.
Thanks in advance.
↧
Would these dropcaps work for Kindle formats?
Am editing my book as an epub in Sigil and plan to create the Kindle format using Kindlegen.
I found this CSS for creating dropcaps. It seems to work on my Kindle3 device - how safe is this to use?
There are two styles, I'm guessing to allow for different letter shapes.
.dropcap {
float: left;
font-size: 4.9437rem;
font-style: normal;
font-variant: normal;
font-weight: normal;
margin: -0.2em 0.1em -0.25em 0
}
.dropcap1 {
float: left;
font-size: 1.5em;
font-style: normal;
font-variant: normal;
font-weight: normal;
line-height: 1.2;
margin: -0.2em 0.1em -0.25em 0
}
I found this CSS for creating dropcaps. It seems to work on my Kindle3 device - how safe is this to use?
There are two styles, I'm guessing to allow for different letter shapes.
.dropcap {
float: left;
font-size: 4.9437rem;
font-style: normal;
font-variant: normal;
font-weight: normal;
margin: -0.2em 0.1em -0.25em 0
}
.dropcap1 {
float: left;
font-size: 1.5em;
font-style: normal;
font-variant: normal;
font-weight: normal;
line-height: 1.2;
margin: -0.2em 0.1em -0.25em 0
}
↧
show hide button in ebook?
can i create a show and hide button for portions of text, (similar to MobileReads wiki indexes,) in a AZW3 format ebook?
↧
Font tests: results and query
Last year I designed a book for client that involved a dialogue between two people, differentiated by a font change. In order to achieve our goal, I included the font definition {font-family: Palatino, serif;} in my CSS paragraph definitions for the main text; for my secondary text I embedded the open-source font SourceSansPro-Regular and its italic counterpart, SourceSansPro-Italic, and coded accordingly: {font-family: SourceSansPro-Regular;}. The results were tested in my Kindle Fire, and on both Kindle for Mac and Kindle for PC. I relied on Kindle Previewer for results on Paperwhite and Kindle, though Previewer is often not a reliable tool. The results were:
With some recent updates to Kindles programming, and hoping to find a way to achieve uniformity across devices, I recently performed various tests, unfortunately with the same mixed results. The first test was:
No font definitions included for primary text; SourceSansPro embedded and coded for secondary text. The results were:
Next test was: No font definitions included at all for primary text, and Amazons recommended Monospace font (an unattractive Courier-like font) was used for the secondary text. The results were:
Next test used the Primary and Secondary font codes as recommended by the Kindle Publishing Guide. The results were:
Lastly, I tried mixing the Primary/Secondary method with the embedded secondary font ({font-family:"SecondaryFont", "SourceSansPro-Regular";} and vice versa), as well as combining Monospace and SourceSansPro, hoping one would work for Paperwhite and Kindle while the other would work for the Fire and the Kindle apps. Alas, this has no effect.
Has anyone else done similar tests and who has an actual Kindle or Paperwhite to test on instead of relying on Previewer? I would be interested to hear your results.
Michelle
Kindle Fire: the ebook displays as designed. User cannot change the primary font (which may irritate some) and the SourceSansPro displays correctly.
Kindle for Mac/PC app: both apps use their default (and only) font for the main text, but the SourceSansPro displays correctly.
X Paperwhite: the ebook does not display correctly. User can select the font but all text displays the same. The embedded font is ignored.
X Kindle: the ebook does not display correctly. All text displays in Caecilia. The embedded font is ignored.
Kindle for Mac/PC app: both apps use their default (and only) font for the main text, but the SourceSansPro displays correctly.
X Paperwhite: the ebook does not display correctly. User can select the font but all text displays the same. The embedded font is ignored.
X Kindle: the ebook does not display correctly. All text displays in Caecilia. The embedded font is ignored.
With some recent updates to Kindles programming, and hoping to find a way to achieve uniformity across devices, I recently performed various tests, unfortunately with the same mixed results. The first test was:
No font definitions included for primary text; SourceSansPro embedded and coded for secondary text. The results were:
Kindle Fire: the ebook displays as designed. User can change their primary font but the SourceSansPro displays correctly.
Kindle for Mac/PC app: both apps use their default (and only) font for the main text, but SourceSansPro displays correctly.
X Paperwhite: the ebook does not display correctly. User can select the font but all text displays the same. The embedded font is ignored.
X Kindle: the ebook does not display correctly. All text displays in Caecilia. The embedded font is ignored.
Kindle for Mac/PC app: both apps use their default (and only) font for the main text, but SourceSansPro displays correctly.
X Paperwhite: the ebook does not display correctly. User can select the font but all text displays the same. The embedded font is ignored.
X Kindle: the ebook does not display correctly. All text displays in Caecilia. The embedded font is ignored.
Next test was: No font definitions included at all for primary text, and Amazons recommended Monospace font (an unattractive Courier-like font) was used for the secondary text. The results were:
Kindle Fire: the font differentiation is there but its ugly. The user can change their primary font and the ugly Monospace font displays correctly.
X Kindle for Mac/PC app: the ebook does not display correctly. Everything is displayed in the apps default font.
Paperwhite: same as the Kindle Fire.
Kindle: Default font is Caecilia but the Monospace font displays correctly and is different enough from Caecilia to create visual separation.
X Kindle for Mac/PC app: the ebook does not display correctly. Everything is displayed in the apps default font.
Paperwhite: same as the Kindle Fire.
Kindle: Default font is Caecilia but the Monospace font displays correctly and is different enough from Caecilia to create visual separation.
Next test used the Primary and Secondary font codes as recommended by the Kindle Publishing Guide. The results were:
Kindle Fire: the font differentiation is there. The user can change their primary font and the default secondary font is Verdana.
X Kindle for Mac/PC app: the ebook does not display correctly. Everything is displayed in the apps default font.
Paperwhite: same as on the Kindle Fire except that the default secondary font is Helvetica.
X Kindle: the ebook does not display correctly. All text displays in Caecilia. The secondary font code is ignored.
X Kindle for Mac/PC app: the ebook does not display correctly. Everything is displayed in the apps default font.
Paperwhite: same as on the Kindle Fire except that the default secondary font is Helvetica.
X Kindle: the ebook does not display correctly. All text displays in Caecilia. The secondary font code is ignored.
Lastly, I tried mixing the Primary/Secondary method with the embedded secondary font ({font-family:"SecondaryFont", "SourceSansPro-Regular";} and vice versa), as well as combining Monospace and SourceSansPro, hoping one would work for Paperwhite and Kindle while the other would work for the Fire and the Kindle apps. Alas, this has no effect.
Has anyone else done similar tests and who has an actual Kindle or Paperwhite to test on instead of relying on Previewer? I would be interested to hear your results.
Michelle
↧
↧
Help! How to make Publishers Default available on Kindle Dictionary
Hi All,
How to make Publisher's Default available on Kindle Dictionary? When I converted the OPF file from EPUB to mobi, the publishers default is available but when I inserted IDX tags, the publisher's default is no longer available.
Thanks
How to make Publisher's Default available on Kindle Dictionary? When I converted the OPF file from EPUB to mobi, the publishers default is available but when I inserted IDX tags, the publisher's default is no longer available.
Thanks
↧
Two Page Spread in Fixed Layout Kindle Fire?
Been having a heck of a time trying to find out how I can make the book open automatically in a two page spread. I've got a fixed layout epub for ibooks, and I've set it to automatically open so that you can see both pages of a landscape style picture book. Then you double click if you want to zoom in on a particular page.
When I did the conversion using KindlePreviewer it knocked that formatting out and made it single page again (and jacked up the images too, but I'm assuming that's just a sizing thing).
The other question I have: Is there a way to embed Read Aloud narration into the book in kindle format, like I have in the iPad version? I've got the highlighting and narration for every page as a separate sound file, but all I'm seeing is the ability to upload a whole book to Audible, and make people buy both ebook and audiobook, then their software syncs them up. No way to just embed it within the file like in epub?
When I did the conversion using KindlePreviewer it knocked that formatting out and made it single page again (and jacked up the images too, but I'm assuming that's just a sizing thing).
The other question I have: Is there a way to embed Read Aloud narration into the book in kindle format, like I have in the iPad version? I've got the highlighting and narration for every page as a separate sound file, but all I'm seeing is the ability to upload a whole book to Audible, and make people buy both ebook and audiobook, then their software syncs them up. No way to just embed it within the file like in epub?
↧
Anyone know what these tags will do in a KF8 book
<menu>
Is this a pop-up menu? if yes, can i make a submenu and links inside?
<hgroup>
??
<header>
Does this get attached to the top of every page?
<section>
What's the difference between this and splitting the html into two?
Is this a pop-up menu? if yes, can i make a submenu and links inside?
<hgroup>
??
<header>
Does this get attached to the top of every page?
<section>
What's the difference between this and splitting the html into two?
↧
PW 'Page Flip' feature not recognizing chapters
I've realized that the "Page Flip" feature from firmware 5.4.4.1 does not work in some of my books, meaning it does not recognize chapters past the first toc.ncx entry even though the chapters show just fine when I access them through Go To>Contents.
My guess is that when I convert my epubs to azw3 using Calibre something in the toc gets 'corrupted' but I'm not sure which file the "Page Flip" feature uses for input. Do you guys have any idea what could be causing this?
My guess is that when I convert my epubs to azw3 using Calibre something in the toc gets 'corrupted' but I'm not sure which file the "Page Flip" feature uses for input. Do you guys have any idea what could be causing this?
↧
↧
PDF to Mobi/AZW3
Hi guys so I'm trying to convert two files, I'll try and and just get help with the first one for now. It's only 6mb in size. I've tried using Calibre, and converted it to both a Mobi and AZW3 file. The font seems like it would be fine, but all the links don't work. Like when I'm at the contents page and I click 1.1 it doesn't bring me to that section like it does in the pdf file on my computer. Instead it brings me to the first page, it doesn't matter what section I click on 5.6, etc, it will just bring me to the first page.. what can I do?
↧
Picture/ Carousel
Hi all.
I'm using the latest version of Calibre E-book Management, version 1.35.
I use it to convert epub to mobi to read it on my Kindle Fire HD.
After recently converting an epub to mobi on my computer, I then copied the file over to by Kindle Fire HD via a USB cable (like I usually do) into the "Book" folder. In the carousel, instead of the book's picture/ cover being displayed, there's just this generic blank picture; it has the title of the book, but no picture.
If I open the book itself in the Calibre program, I can see the book's picture/ cover just fine.
I remember coming across something once where people were having trouble period getting books (mobi) to show up at all in the carousel. The instructions were to go to "Convert" in Calibre, then click on "Mobi Output", and then in "Personal Doc tag" where it says [PDOC] to replace it with [EBOK]; or some say to just delete [PDOC] and don't replace it with anything.
I don't have a problem with it showing up in the carousel, there's just no cover picture displayed.
I even tried "Edit Metadata" and downloading a new cover; nope, nothing.
Anyone have any ideas? Suggestions? Tips?
Thanks,
Pez
I'm using the latest version of Calibre E-book Management, version 1.35.
I use it to convert epub to mobi to read it on my Kindle Fire HD.
After recently converting an epub to mobi on my computer, I then copied the file over to by Kindle Fire HD via a USB cable (like I usually do) into the "Book" folder. In the carousel, instead of the book's picture/ cover being displayed, there's just this generic blank picture; it has the title of the book, but no picture.
If I open the book itself in the Calibre program, I can see the book's picture/ cover just fine.
I remember coming across something once where people were having trouble period getting books (mobi) to show up at all in the carousel. The instructions were to go to "Convert" in Calibre, then click on "Mobi Output", and then in "Personal Doc tag" where it says [PDOC] to replace it with [EBOK]; or some say to just delete [PDOC] and don't replace it with anything.
I don't have a problem with it showing up in the carousel, there's just no cover picture displayed.
I even tried "Edit Metadata" and downloading a new cover; nope, nothing.
Anyone have any ideas? Suggestions? Tips?
Thanks,
Pez
↧
Convert 200M HTML document to .mobi
I have a 200M HTML document that I would like to read on my Kindle Touch. Calibri seems to import it but reports a file size of 4M.
How can I (or can I) convert the 200M HTML document to .mobi, .epub, or other format appropriate to a slightly old Kindle Touch?
Thanks,
Jonathan Hayward
How can I (or can I) convert the 200M HTML document to .mobi, .epub, or other format appropriate to a slightly old Kindle Touch?
Thanks,
Jonathan Hayward
↧
Image sizing ignored by old Kindles and iOS app - please help
Hi all,
New member here with a first post asking for some help. Ive searched the forums and cant find this specific question, but apologies in advance if its been asked before.
Ive created an EPUB (using Calibre which has passed validation) and have converted it to a MOBI file with Kindle Previewer and its rendering properly on the majority of Kindle devices and the Kindle app for Android. The issue Im having is that images are too large on the older Kindles (1 and DX, I believe) and, more importantly, on the Kindle app for iOS. Also, the same devices are ignoring the small caps opening each chapter.
Ive attached screenshots of what its supposed to look like (Kindle app for Android) and the unacceptable results on the old Kindle and iOS devices. The images are the decorative designs to the left and right of the chapter head, and the Persian word. Every chapter begins in this manner.
Im using image width percentages to size the images, and the font-variant: small-caps span tag for the chapter openings. My image coding looks something like this:
<p class="chapter2"><span class="centered"><img src="leaf.jpg" alt="leaf" width="16%"/>Chapter 2<img src="leaf.jpg" alt="leaf" width="16%"/></span></p>
<p class="subhead4"><span class="centered">Virgin—<img src="virgin.jpg" alt="virgin" width="18%"/></span></p>
Is there a way to alter the coding to make the images render properly on Kindle for iOS and older Kindles? Ive read possibly using <img hisrc> in addition to <img src> and defining the width as well as the height="auto". Also, do iOS devices use the new AZK format instead of the MOBI/KF8, and is this why they are ignoring the image width coding? Or is AZK only for previewing purposes?
The small caps are a secondary issue, but if anyone has ideas to fix that as well Im all ears. Sorry for the novice questions. Im hoping theres an easy fix for this.
- M
New member here with a first post asking for some help. Ive searched the forums and cant find this specific question, but apologies in advance if its been asked before.
Ive created an EPUB (using Calibre which has passed validation) and have converted it to a MOBI file with Kindle Previewer and its rendering properly on the majority of Kindle devices and the Kindle app for Android. The issue Im having is that images are too large on the older Kindles (1 and DX, I believe) and, more importantly, on the Kindle app for iOS. Also, the same devices are ignoring the small caps opening each chapter.
Ive attached screenshots of what its supposed to look like (Kindle app for Android) and the unacceptable results on the old Kindle and iOS devices. The images are the decorative designs to the left and right of the chapter head, and the Persian word. Every chapter begins in this manner.
Im using image width percentages to size the images, and the font-variant: small-caps span tag for the chapter openings. My image coding looks something like this:
<p class="chapter2"><span class="centered"><img src="leaf.jpg" alt="leaf" width="16%"/>Chapter 2<img src="leaf.jpg" alt="leaf" width="16%"/></span></p>
<p class="subhead4"><span class="centered">Virgin—<img src="virgin.jpg" alt="virgin" width="18%"/></span></p>
Is there a way to alter the coding to make the images render properly on Kindle for iOS and older Kindles? Ive read possibly using <img hisrc> in addition to <img src> and defining the width as well as the height="auto". Also, do iOS devices use the new AZK format instead of the MOBI/KF8, and is this why they are ignoring the image width coding? Or is AZK only for previewing purposes?
The small caps are a secondary issue, but if anyone has ideas to fix that as well Im all ears. Sorry for the novice questions. Im hoping theres an easy fix for this.
- M
↧
↧
Libmobi C library
Hi,
I just want to say that I started working on a C library for handling MOBI files.
It is in a very initial state. I just put my libmobi project to github. I am working on reading and parsing of mobi documents now. Next step would be writing mobi format files.
In the project there is a mobitool program which is meant to be an example of usage and a tool for testing the library. It is able to load and parse basic mobi files now. It partially recreates and dumps original markup.
All credit goes to users of this forum and authors of KindleUnpack and Calibre the only source of information about MOBI format.
Anybody who would like to test or contribute to the project is welcome :)
I just want to say that I started working on a C library for handling MOBI files.
It is in a very initial state. I just put my libmobi project to github. I am working on reading and parsing of mobi documents now. Next step would be writing mobi format files.
In the project there is a mobitool program which is meant to be an example of usage and a tool for testing the library. It is able to load and parse basic mobi files now. It partially recreates and dumps original markup.
All credit goes to users of this forum and authors of KindleUnpack and Calibre the only source of information about MOBI format.
Anybody who would like to test or contribute to the project is welcome :)
↧
embed video in Kindle/mobi?
Having some trouble here. Have a .epub with 2 videos embedded, compiles fine for epub 3.0, works properly in iBooks etc.
Trying to convert to kf8/.mobi for Kindle Fire (using Kindle Previewer 2.921), videos don't appear, despite following Amazon's vague instructions and non-html5 and code.
Feel like I am missing something obvious. Thoughts? I am going to re-encode the videos to non-.mov to see if that helps.
Thanks,
Pete
Trying to convert to kf8/.mobi for Kindle Fire (using Kindle Previewer 2.921), videos don't appear, despite following Amazon's vague instructions and non-html5 and code.
Feel like I am missing something obvious. Thoughts? I am going to re-encode the videos to non-.mov to see if that helps.
Thanks,
Pete
↧
Tagging files to show up in the "Docs"-lists
Hello there,
before asking my question, I humbly ask you to read these posts:
Number 1
Number 2
As you just (hopefully) read, I manage my content locally and actually do want to use the "Docs"-category on my PW2. Simply because it makes managing collections on the device easier.
Putting everything in the "Books"-category, switching to a collection and then use "Add/Remove Items", will show me a list where sideloaded ebooks and cloud-stored ebooks are mixed up, without any possibility to filter them.
Putting stuff into the "Docs"-category will show me a list with sideloaded ebooks only.
Doing this with Calibre and mobi-7-files is quite easy, since it has an output-option called "Personal Doc Tag". This doesn't even alter the original file in the library, since it just tags the copy transferred to the device.
__________________________________________________ ________________________________________________
But what about KF8-formatted AZW3-files? How to I force them to appear in the "Docs"-category? Reading this post looks like I have to alter the original AZW3-file.
An example would be a fixed-layout epub or similar. Some kind of file that is not supported by the PW2 natively, but would be fine using the KF8-formatting.
This is all giving me a headache.
before asking my question, I humbly ask you to read these posts:
Number 1
Number 2
As you just (hopefully) read, I manage my content locally and actually do want to use the "Docs"-category on my PW2. Simply because it makes managing collections on the device easier.
Putting everything in the "Books"-category, switching to a collection and then use "Add/Remove Items", will show me a list where sideloaded ebooks and cloud-stored ebooks are mixed up, without any possibility to filter them.
Putting stuff into the "Docs"-category will show me a list with sideloaded ebooks only.
Doing this with Calibre and mobi-7-files is quite easy, since it has an output-option called "Personal Doc Tag". This doesn't even alter the original file in the library, since it just tags the copy transferred to the device.
__________________________________________________ ________________________________________________
But what about KF8-formatted AZW3-files? How to I force them to appear in the "Docs"-category? Reading this post looks like I have to alter the original AZW3-file.
An example would be a fixed-layout epub or similar. Some kind of file that is not supported by the PW2 natively, but would be fine using the KF8-formatting.
This is all giving me a headache.
↧