![]() |
#151 | |
frumious Bandersnatch
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,560
Karma: 20150435
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Quote:
|
|
![]() |
![]() |
![]() |
#152 | |
want to learn what I want
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,641
Karma: 7908443
Join Date: Sep 2020
Device: none
|
Quote:
Last edited by Comfy.n; 07-13-2023 at 12:42 PM. |
|
![]() |
![]() |
Advert | |
|
![]() |
#153 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
You can control this process using a template that uses the template shorten() function for each name segment. The function lets you decide how many characters to remove from each segment, removing the randomness of the default process. If done correctly then the total length is guaranteed to be less than the maximum. |
|
![]() |
![]() |
![]() |
#154 |
frumious Bandersnatch
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,560
Karma: 20150435
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Just to clarify, when I say "what's happening", it's just an explanation of why the path name is not the full author/title, which is fine and expected as per chaley's explanation. I don't mean that is the problem. It still puzzles me that you get different lengths, but that may be just my ignorance when using the template in the plugin's code. The problem seems to be that Prince itself (or the command-line interpreter that runs Prince) chokes on the path that's being passed. It could be that I'm not ensuring it's short enough, or it could be that Prince requires it shorter than the system limit, or it could be something else.
|
![]() |
![]() |
![]() |
#155 |
want to learn what I want
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,641
Karma: 7908443
Join Date: Sep 2020
Device: none
|
Hi Jellby,
For most conversions, I'm using this CSS: PHP Code:
Is there some CSS styling I can apply to get the cover to fit the page size (17cm x 32cm, in most cases)? Last edited by Comfy.n; 07-13-2023 at 07:01 PM. |
![]() |
![]() |
Advert | |
|
![]() |
#156 |
frumious Bandersnatch
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,560
Karma: 20150435
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
I don't think there's a general solution. It depends on how the books is coded (and also Prince's behaviour has changed between versions in the past).
In many of my books I have something like: Code:
/* specific code for the cover image */ @page cover { size: 600px 800px; /* hard-coded cover image size */ margin: 0 -100px; /* make virtual page width 800px */ } body.cover { page: cover; } * The cover image being in a <body class="cover"> tag. * The cover image being 600x800 px exactly. * The cover image being coded to use the full page. At least at some point this worked fine for me. |
![]() |
![]() |
![]() |
#157 |
want to learn what I want
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,641
Karma: 7908443
Join Date: Sep 2020
Device: none
|
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
[GUI Plugin] KindleUnpack - The Plugin | DiapDealer | Plugins | 527 | 08-15-2025 01:36 PM |
[GUI Plugin] EpubMerge | JimmXinu | Plugins | 560 | 06-09-2025 03:46 PM |
[GUI Plugin] Ex Libris | AlPe | Plugins | 87 | 10-10-2020 03:10 PM |
[GUI Plugin] Wordpress | frescogamba | Plugins | 11 | 04-06-2015 09:09 PM |
[GUI Plugin] Plugin Updater **Deprecated** | kiwidude | Plugins | 159 | 06-19-2011 12:27 PM |