03-23-2008, 06:30 PM | #16 | |
GuteBook/Mobi2IMP Creator
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
|
Quote:
Loose the 'debug info' option and the "top of the screen" will not be pushed off to oblivion! The 'verbose' alone should give you more than you need! |
|
03-23-2008, 06:53 PM | #17 |
Resident Curmudgeon
Posts: 76,310
Karma: 136006010
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
03-23-2008, 06:54 PM | #18 |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
Hi Zelda, when pronounced the letter GUI sound like Gooey but in text they should be GUI as nobody will make the association you spell it gooey. GUI mean Graphic User Interface. Thanks for the efforts on the books.
Dale |
03-23-2008, 06:59 PM | #19 | |
zeldinha zippy zeldissima
Posts: 27,827
Karma: 921169
Join Date: Dec 2007
Location: Paris, France
Device: eb1150 & is that a nook in her pocket, or she just happy to see you?
|
Quote:
[EDIT i know it means Graphic User Interface, that's why i was surprised the first time i heard "gooey"] Last edited by zelda_pinwheel; 03-23-2008 at 07:12 PM. |
|
03-23-2008, 07:00 PM | #20 | |||
GuteBook/Mobi2IMP Creator
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
|
Quote:
The installer is just a smart uncompressor! I assume (wrongly so in your situation and JSWolf's situation) that the home directory will be "C:\Program Files\Mobi2IMP". Moving the program, GUI, bin directory will most certainly break this setup! The problem is that the 'Mobi2IMP.exe' in the bin directory (the work-horse routine!) is not placed in your path by the installer. If YOU place 'Mobi2IMP.exe' in another directory in your path (or add "C:\Program Files\Mobi2IMP\bin"; to your path), then you can call the (recursive) batch file from anywhere! Just put the 'prc2imp.bat' in the directory where your .prc files reside (NOT THE OTHER WAY AROUND. That is like "Letting the mountain come to Mohammad!"). Quote:
Quote:
Last edited by nrapallo; 03-23-2008 at 10:36 PM. Reason: fixed typos |
|||
03-23-2008, 07:11 PM | #21 |
zeldinha zippy zeldissima
Posts: 27,827
Karma: 921169
Join Date: Dec 2007
Location: Paris, France
Device: eb1150 & is that a nook in her pocket, or she just happy to see you?
|
well, since the original mobi files were made with BookDesigner sometimes there are odd things in the code. i'm not being very thorough today but in the output window of eBook Publisher there is a huge list of things i *could* fix, like open tags or text not inside a tag... and in addition, if i were being picky, for example, i should correct the paragraph indent, so that it is made with css and not several non-breaking spaces.
however, the books i am converting today are more or less readable directly from conversion, so, i am only fixing some small details : 1. add a "a name=TOC" tag before the TOC, for those people who like to jump back to it 2. change header to "smallfont" (personal preference) and remove the unnecessary bgcolor indication (since i chose white) 3. move image link anchors to *before* illustrations, instead of after (otherwise, if you click on the link, the illustration is not actually visible, it is on the previous page) 4. close the open <p> tags around the illustrations 5. fix the double <i> tags around the image captions with a ctrl+H replace all (and 6. fixing the image sizes, but i think you mean specifically with the code). if you want to see the output results, just do a conversion using mobi2imp and then open the opf file with eBook Publisher, and do "preview". |
03-23-2008, 07:15 PM | #22 |
GuteBook/Mobi2IMP Creator
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
|
EDIT: Was DELETED as zelda_pinwheel already answered this, but on second thoughts, I'll just add that I also ensure that there are no stray blank lines BEFORE a page break. That means that any:
Code:
<div> </div> before a <p style="page-break-before:always"> This is sometimes unavoidable when the image used is longer than wider and bleeds into the bottom. This situation can only be fixed by re-sizing the image to the device's dimensions or inserting width/height specifications within the <img> tag. Either way you loose the generality of the code and need to re-do this resizing for the other .IMP device (REB1200). Likewise, I also like remove stray blank lines after "THE END". Nothing more annoying than reaching "THE END" and there being one more page to read; only to find out its BLANK! Last edited by nrapallo; 03-24-2008 at 11:10 AM. Reason: fixed typo |
03-23-2008, 07:48 PM | #23 | |||
zeldinha zippy zeldissima
Posts: 27,827
Karma: 921169
Join Date: Dec 2007
Location: Paris, France
Device: eb1150 & is that a nook in her pocket, or she just happy to see you?
|
Quote:
Quote:
[EDIT : ARG !! watch out, the batch file looks in sub-directories as well !!! and if you already re-formatted those other opf files, well, you can start over again from a completely new source code... thank god it's not any faster.] currently, mobi2imp is installed in the default location (C drive) ; but i don't like to mix my system with my other files, that's why the books are on the I drive. no worries ; now i think i have it figured out, and soon i will have written your tutorial for you Quote:
|
|||
03-23-2008, 08:01 PM | #24 |
GuteBook/Mobi2IMP Creator
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
|
|
03-23-2008, 08:14 PM | #25 |
zeldinha zippy zeldissima
Posts: 27,827
Karma: 921169
Join Date: Dec 2007
Location: Paris, France
Device: eb1150 & is that a nook in her pocket, or she just happy to see you?
|
|
03-23-2008, 09:40 PM | #26 | |
Resident Curmudgeon
Posts: 76,310
Karma: 136006010
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
03-23-2008, 10:07 PM | #27 | |
GuteBook/Mobi2IMP Creator
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
|
Quote:
These stray blank lines take many forms '<div> </div>' or '<BR><BR>' or '<br /><br /></font>' or '<br /></span>' and so on... I just visually inspect each '<p style="page-break-before:always">' to see if I should remove any preceding blank lines. It's tedious but safer! The link to AFTER an illustration problem is not easily detectable since I do not parse the HTML code in Mobi2IMP. I think it would be hard to automate since I just gloably search and replace to 'fix' things! In the end, it should be the preparer of the .prc (or BookDesigner program) that should fix these (broken) things. |
|
03-26-2008, 01:03 AM | #28 |
GuteBook/Mobi2IMP Creator
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
|
Development Hub repository for Mobi2IMP operational!
Please check out the Development Hub repository for Mobi2IMP.
This repository will host the most current source, programs, and documentation as well as unreleased source revisions. There you can fill out "tickets" for Bugs Reports / Feature Requests / Help Requests ... I uploaded all my previous versions except for version 3 to 5, which were overwritten by version 6. Oh well, otherwise, it's pretty complete. To have a look around is "free", but to create "tickets" requires (free) registration. |
03-26-2008, 01:04 PM | #29 | |
GuteBook/Mobi2IMP Creator
Posts: 2,958
Karma: 2530691
Join Date: Dec 2007
Location: Toronto, Canada
Device: REB1200 EBW1150 Device: T1 NSTG iLiad_v2 NC Device: Asus_TF Next1 WPDN
|
Quote:
If so, there is a shortcut, namely, when the dos box/command prompt window is open, right-menu click on that window, select Mark, then highlight the area you want to copy with the mouse (only line blocks are copied so start at the beginning of the line). When done highlighting, press Enter key and the contents will be copied to your clipboard. Now you can paste it where you please. **DOS 101 is now out on hiatus** |
|
03-26-2008, 01:29 PM | #30 | |
zeldinha zippy zeldissima
Posts: 27,827
Karma: 921169
Join Date: Dec 2007
Location: Paris, France
Device: eb1150 & is that a nook in her pocket, or she just happy to see you?
|
Quote:
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
DR800 Future GUI enhancements: pop-ups, fly-outs, toolbars & more | jm35 | iRex | 3 | 05-25-2010 01:41 PM |
GUI doesn't show up in Windows | morphine | Calibre | 3 | 09-04-2009 05:44 AM |
GUI Frontend for python scripts [windows] - seeking mod input first | sherman | Workshop | 7 | 04-27-2009 01:04 AM |
[Librie-Dev] Librie RSS Reader (Windows GUI) v0.31b | quantumskie | Legacy E-Book Devices | 0 | 11-30-2006 10:37 AM |
[Librie-Dev] Librie RSS Reader v0.2b (Windows GUI) *needs XylogParser.dll* | quantumskie | Legacy E-Book Devices | 0 | 11-27-2006 01:34 PM |