I just started re-reading Wind and Tide, with the epub version. It looks like the em dashes were converted to a little box character for unicode 0097. The PDF file is fine. A quick look at Fortune shows double dashes, so maybe this is only an issue with the older files.
I was curious about how you did your conversion. What program do you use? Do you start from the ff.net files (using something like http://fanfictionloader.appspot.com) or from your original documents? ff.net messes with punctuation (e.g. !? to !, -- to -), so I assume that's not the best place to start.
Jeff, did you download the W&T epub version lately or is it an older file? I've updated my conversion process since the early days of ebooking (I say that like it wasn't more than six or seven months ago), so it's possible that I hadn't replaced it with my em dash code in the version you have. I generally copy from ff.net or get the authors to send me the full document, do some replacing in Word, transfer to Open Office to do the html conversion (Word puts lots of trash code in, though I like the interface more than Open Office, hence doing my editing there). I use Text Edit to clear 95% of the HTML codes from the file, leaving the very basic stuff, and then Calibre to make the epub and mobi files. The PDF will always be different: that never leaves MS Word, as my version can save PDFs.
With shorter files, it's easier to add my HTML tags in Word, but Fates isn't a shorter file. And yeah, if there are double dashes in your copy of Fates, that's an old copy or I haven't renovated it yet.
I guess you've already seen this, but I grabbed the latest W&T and it still had the problem. It's timestamped 2010-12-05T18:31:13.405745+00. The Fatesverse file is from twelve hours earlier, but doesn't appear to have the problem.
Thanks for the process description. I agree Word is horrible with HTML. It worries about typesetting too much. I use SeaMonkey for HTML (for work), but I use Word for fanfic because of the better editor, grammar checker, and auto-save. I tried Sigil for epub construction, but it has a couple idiosyncrasies and doesn't appear to support mobi. I'll take a look at Calibre. I can print to PDF using Adobe PDF Converter or PDFCreator, but both drop the TOC/Bookmarks navigation index. The tech writer an my old job used to add it back in manually, not something I see myself doing.
The biggest problem is the conversion doesn't appear automated. I hate having to make fixes it multiple files instead of a single source file.
I guess you've already seen this, but I grabbed the lastest W&T and it still had the problem. It's timestamped 2010-12-05T18:31:13.405745+00. The Fatesverse is from twelve hours earlier, but doesn't appear to have the problem.
Thanks for the process description. I agree Word is horrible with HTML. It worries about typesetting too much. I use SeaMonkey for HTML, but I use Word for fanfic because of the better editor, grammar checker, and auto-save. I tried Sigil for epub construction, but it has a couple idiosyncrasies and doesn't appear to support mobi. I'll take a look at Calibre. I can print to PDF using Adobe PDF Converter or PDFCreator, but both drop the TOC/Bookmarks navigation index. The tech writer at my old job used to manually restore it, but I can't see myself doing that. I also don't like the manually updating process to make fixes in multiple files, but that probably can't be avoided.
I'm getting the full Adobe suite soon, so my PDFs process will change, but until then, I just post PDFs without TOCs because...yeah. Lazy. Anyway. I fixed all of the different Frea stories. The Menoetius documents now include Chapters 47 and 48, there shouldn't be too many errors in those. And the Fatesverse Extended Edition, in addition to a new cover, does include Not in the Stars.
Thanks, Frea.
ReplyDeleteI just started re-reading Wind and Tide, with the epub version. It looks like the em dashes were converted to a little box character for unicode 0097. The PDF file is fine. A quick look at Fortune shows double dashes, so maybe this is only an issue with the older files.
I was curious about how you did your conversion. What program do you use? Do you start from the ff.net files (using something like http://fanfictionloader.appspot.com) or from your original documents? ff.net messes with punctuation (e.g. !? to !, -- to -), so I assume that's not the best place to start.
Apparently Mr. Casey Sir can't say no to Violet either.
ReplyDeleteJeff, did you download the W&T epub version lately or is it an older file? I've updated my conversion process since the early days of ebooking (I say that like it wasn't more than six or seven months ago), so it's possible that I hadn't replaced it with my em dash code in the version you have. I generally copy from ff.net or get the authors to send me the full document, do some replacing in Word, transfer to Open Office to do the html conversion (Word puts lots of trash code in, though I like the interface more than Open Office, hence doing my editing there). I use Text Edit to clear 95% of the HTML codes from the file, leaving the very basic stuff, and then Calibre to make the epub and mobi files. The PDF will always be different: that never leaves MS Word, as my version can save PDFs.
ReplyDeleteWith shorter files, it's easier to add my HTML tags in Word, but Fates isn't a shorter file. And yeah, if there are double dashes in your copy of Fates, that's an old copy or I haven't renovated it yet.
jajaja maaan that was great! love the story, keep up the good work Frea!! =D
ReplyDeleteAnswered my own question, Jeff. Never mind. Got to update some links today, apparently. I'll let everybody know when things are copacetic.
ReplyDeleteI guess you've already seen this, but I grabbed the latest W&T and it still had the problem. It's timestamped 2010-12-05T18:31:13.405745+00. The Fatesverse file is from twelve hours earlier, but doesn't appear to have the problem.
ReplyDeleteThanks for the process description. I agree Word is horrible with HTML. It worries about typesetting too much. I use SeaMonkey for HTML (for work), but I use Word for fanfic because of the better editor, grammar checker, and auto-save. I tried Sigil for epub construction, but it has a couple idiosyncrasies and doesn't appear to support mobi. I'll take a look at Calibre. I can print to PDF using Adobe PDF Converter or PDFCreator, but both drop the TOC/Bookmarks navigation index. The tech writer an my old job used to add it back in manually, not something I see myself doing.
The biggest problem is the conversion doesn't appear automated. I hate having to make fixes it multiple files instead of a single source file.
I guess you've already seen this, but I grabbed the lastest W&T and it still had the problem. It's timestamped 2010-12-05T18:31:13.405745+00. The Fatesverse is from twelve hours earlier, but doesn't appear to have the problem.
ReplyDeleteThanks for the process description. I agree Word is horrible with HTML. It worries about typesetting too much. I use SeaMonkey for HTML, but I use Word for fanfic because of the better editor, grammar checker, and auto-save. I tried Sigil for epub construction, but it has a couple idiosyncrasies and doesn't appear to support mobi. I'll take a look at Calibre. I can print to PDF using Adobe PDF Converter or PDFCreator, but both drop the TOC/Bookmarks navigation index. The tech writer at my old job used to manually restore it, but I can't see myself doing that. I also don't like the manually updating process to make fixes in multiple files, but that probably can't be avoided.
I'm getting the full Adobe suite soon, so my PDFs process will change, but until then, I just post PDFs without TOCs because...yeah. Lazy. Anyway. I fixed all of the different Frea stories. The Menoetius documents now include Chapters 47 and 48, there shouldn't be too many errors in those. And the Fatesverse Extended Edition, in addition to a new cover, does include Not in the Stars.
ReplyDeleteI said it once, I'll say it again. That picture is little short of frightening.
ReplyDeleteWhy, thank you, My Favorite Australian. I'm a little proud of it.
ReplyDeleteThanks for that fantastic story, and for all the ebooks. :)
ReplyDelete