![]() |
#676 |
Running with scissors
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,587
Karma: 14328510
Join Date: Nov 2019
Device: none
|
doesn't handle subtitles well
Using Sigil's metadata editor I added a second title metadata element and added to it the attribute subtitle. When I ran the Generate Cover plugin it used the subtitle. Back in Sigil's metadata editor I used the arrows to move the subtitle below the main title and that fixed it.
Code:
<dc:title>Fishpingle</dc:title> <dc:title id="tle">A romance of the countryside</dc:title> <meta refines="#tle" property="title-type">subtitle</meta> |
![]() |
![]() |
![]() |
#677 |
Plugin Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,973
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
|
To the best of my knowledge, the GC plugin only uses Calibre's metadata.
I don't know what impact Sigil has on Calibre's metadata. I wouldn't have expected it to have any. |
![]() |
![]() |
Advert | |
|
![]() |
#678 |
Well trained by Cats
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 31,062
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Jimm has it
![]() Generate cover uses Calibre, not the book I add {Series} to my generated covers, and {#subtitle} <<my custom column That uses the Custom Text block in Generate Cover |
![]() |
![]() |
![]() |
#679 |
Running with scissors
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,587
Karma: 14328510
Join Date: Nov 2019
Device: none
|
So are you saying that calibre is using the first title metadata it finds? The subtitle was first in the content.opf file.
|
![]() |
![]() |
![]() |
#680 |
Running with scissors
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,587
Karma: 14328510
Join Date: Nov 2019
Device: none
|
Yes, Calibre is using the first title it finds in the metadata. When I posted about the order problem with this plugin I hadn't noticed that Calibre's Title column was using the subtitle.
|
![]() |
![]() |
Advert | |
|
![]() |
#681 |
Mouse Army
![]() Posts: 3
Karma: 10
Join Date: Jan 2012
Device: Kobo Forma
|
I really like this plugin, but was wondering. Is there a way to have a random image chosen when you generate a cover? For example, if I choose generate cover for multiple books at once, can it randomly select an image?
|
![]() |
![]() |
![]() |
#682 |
Plugin Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,973
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
|
Generate Cover plugin does not do random images.
Calibre built-in cover generate can do random styles, but I don't think you can choose images for it? |
![]() |
![]() |
![]() |
#683 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,012
Karma: 500000
Join Date: Jun 2015
Device: Rocketbook, kobo aura h2o, kobo forma, kobo libra color
|
Quote:
I can see generating covers from a random image in an epub, that might be interesting. When I do it by hand for epubs, I typically use the book editor, and browse the images, usually picking the second or third one (or first one after the current cover), copy it, set it as cover in the metadata editor, and then use generate covers using the current cover as image. This is a bit tedious, but luckily only has to be done once per book. If I import a big batch, I end up poking at them over a couple of weeks until they all have useful covers. Last edited by compurandom; 10-16-2020 at 02:05 PM. |
|
![]() |
![]() |
![]() |
#684 |
Plugin Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,973
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
|
New Test Version Attached
2020-10-26 - Translation enabling code changes - Translations for French & Spanish @dunhill popped up in my PMs with a (mostly) translatable enabled version of GC, along with a couple (partial) translations: Frances by un_pogaz Spanish by Dunhill Unfortunately, Dunhill's version didn't get all the translatable strings. I had to add or fix ~1/3 of the total, so the fr & es versions dunhill gave me are incomplete. A few important notes:
You can use the CALIBRE_OVERRIDE_LANG environment var to test different languages. I use the fake language 'zz' for testing translation code. (Google it if you need help with CALIBRE_OVERRIDE_LANG. ![]() Last edited by JimmXinu; 10-28-2020 at 11:06 AM. Reason: Remove obsolete test version |
![]() |
![]() |
![]() |
#685 | |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 893
Karma: 810834
Join Date: Sep 2017
Location: Buenos Aires, Argentina
Device: moon+ reader, kindle paperwhite
|
Quote:
First of all I want to thank un_pogaz for the French translation of the plugin. And another thing that I wanted to clarify is that with the intention of not hurting the plugin code, I was translating the text that I was seeing simultaneously on the plugin screens. Thank you in advance for your comments. |
|
![]() |
![]() |
![]() |
#686 |
Chalut o/
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 439
Karma: 145424
Join Date: Dec 2017
Device: Kobo
|
Ah... Yes... there is "somes" missings strings, I will complete this.
For the "Field Order" problem, during the first translation I encountered a similar problem for the iterator: Code:
for name, display_name in DIC_name_font: If the texts for "Field Order" are fixed and determinate (which seems to be the case), a similar solution could be applied. EDIT: I just took a look: It's going to be a bit more complicated >_> Last edited by un_pogaz; 10-27-2020 at 06:18 AM. |
![]() |
![]() |
![]() |
#687 |
Plugin Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,973
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
|
New Test Version Attached
2020-10-27 - Update Spanish translation - thanks dunhill! 2020-10-26 - Translation enabling code changes - Translations for French & Spanish Last edited by JimmXinu; 10-28-2020 at 11:07 AM. Reason: Remove obsolete test version |
![]() |
![]() |
![]() |
#688 |
Plugin Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,973
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
|
New Test Version Attached
2020-10-28 - Add a missed string for translation - thanks un-pogaz! - Update French translation - thanks un-pogaz! 2020-10-27 - Update Spanish translation - thanks dunhill! 2020-10-26 - Translation enabling code changes - Translations for French & Spanish Last edited by JimmXinu; 11-04-2020 at 12:53 PM. Reason: Remove obsolete test version |
![]() |
![]() |
![]() |
#689 |
Member
![]() Posts: 12
Karma: 10
Join Date: Jun 2019
Device: none
|
![]()
Hi,
![]() Back in June 2019, on post 639 in this thread, I submitted a bugfix for a centering issue when having a certain combination of settings activated. Unfortunately it was not incorporated yet. Can it (or some other suitable fix) be included so I can stop manually patching draw.py whenever a new version comes out? ![]() Thanks for updating this plugin for Calibre v5 however; it means I can finally make the upgrade plunge. ![]() |
![]() |
![]() |
![]() |
#690 |
Plugin Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 6,973
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
|
New Test Version Attached
2020-10-31 - Fix for border causing img to move horz. - Remove draw_old.py, not needed in Cal v2+ - min valid calibre is v2.85.1 2020-10-28 - Add a missed string for translation - thanks un-pogaz! - Update French translation - thanks un-pogaz! 2020-10-27 - Update Spanish translation - thanks dunhill! 2020-10-26 - Translation enabling code changes - Translations for French & Spanish worstje: Sorry, I don't remember anything about that. ![]() Your change corrects the left-right shift, but in turn introduces a similar up-down shift. Instead, the issue is that the code didn't use the available size for width. See github commit Last edited by JimmXinu; 11-07-2020 at 01:56 PM. Reason: Remove obsolete test version |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
[GUI Plugin] Open With | kiwidude | Plugins | 404 | 02-21-2025 05:42 AM |
[GUI Plugin] Goodreads Sync | kiwidude | Plugins | 1781 | 02-12-2025 07:09 PM |
[GUI Plugin] Clipboard Search | kiwidude | Plugins | 29 | 04-02-2024 10:05 PM |
[GUI Plugin] User Category | kiwidude | Plugins | 123 | 03-16-2024 11:59 PM |
[GUI Plugin] Quick Preferences | kiwidude | Plugins | 62 | 03-16-2024 11:47 PM |