10-14-2012, 06:18 AM | #16 |
♫
Posts: 660
Karma: 506380
Join Date: Aug 2010
Location: Germany
Device: Kobo Aura / PB Lux 2 / Bookeen Frontlight / Kobo Mini / Nook Color
|
Thanks Kiwidude & John!
|
10-14-2012, 09:18 AM | #17 | |
Addict
Posts: 320
Karma: 56788
Join Date: Jun 2011
Device: Kindle
|
Quote:
eg: Code:
1 <h3>A Wise Child</h3> 2 <h3>A (Wise) Child</h3> EDIT: I've found 5 (or 6, depending on how you count) more characters that break the application of a clip: square brackets, carets, asterisks, back-slashes (\), and vertical slashes (|) (in this last instance, the clip is applied, but only to part of the selected text). Basically, it looks like it's having trouble escaping special characters when it applies the regex contained within the clip. Since my own understanding of reg-ex is still in what i'd consider "early stages", I'm not sure if there are other special characters, or combinations of characters that will trigger this error. EDIT2: additional characters that cause the error: "$", "+", "?". Periods, however, don't seem to be causing a problem. Last edited by ElMiko; 10-14-2012 at 09:35 AM. |
|
Advert | |
|
10-14-2012, 09:26 AM | #18 |
Calibre Plugins Developer
Posts: 4,637
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
|
@ElMiko - ahhh, that is an interesting one. And I know exactly why that would be happening too. Behind the scenes when you apply one of those fancy \1 substitution "clips", it turns the selected text into a regular expression. The PCRE engine cannot cope with the unicode line feeds which is why your first problem occurred. However it also will of course get itself confused when being passed text that contains text like your example, as it must make sure to escape the text first in case there are any other regular expression characters in it.
I will sort it out for the next build, that is a very subtle and nice bug to find, well done . |
10-14-2012, 09:27 AM | #19 |
Berti
Posts: 1,196
Karma: 4985964
Join Date: Jan 2012
Location: Zischebattem
Device: Acer Lumiread
|
|
10-14-2012, 09:41 AM | #20 |
Addict
Posts: 320
Karma: 56788
Join Date: Jun 2011
Device: Kindle
|
my... pleasure?? I wish i could say i'd found it in the course of diligent and professionally-minded beta testing. But it was pure dumb luck. still, let's go with "diligent and professionally minded".
|
Advert | |
|
10-14-2012, 09:55 AM | #21 |
Well trained by Cats
Posts: 29,803
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
|
10-14-2012, 09:55 AM | #22 |
Calibre Plugins Developer
Posts: 4,637
Karma: 2162064
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
|
Awesome, about time for the good news to start appearing on this thread. A slight worry that a couple of users had problems finding the expand button. Perhaps we should leave it expanded for first time use so worst case people at least know where those options are available.
Yeah well we have spent a silly amount of hours in our own testing, which while it brought out dozens of things we could catch there was always going to be something we didn't think to try. |
10-14-2012, 10:05 AM | #23 | |
Well trained by Cats
Posts: 29,803
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
Quote:
It is amazing the number of users that do not explore, or even recognize markings that mean more. (Of coarse, there is a chance that they will also never close it . These are probably the same people that still have all the feature advertising stickers on their 5 year old VCR |
|
10-14-2012, 10:21 AM | #24 |
Sigil developer
Posts: 1,275
Karma: 1101600
Join Date: Jan 2011
Location: UK
Device: Kindle PW, K4 NT, K3, Kobo Touch
|
So much for trying to make it subtle so it wouldn't get in the way
Thanks for the feedback so far - its annoying that a few things were missed in all the latest changes and testing, but they should be minor or avoidable. As user_none said - only bug fixes from this point on. And with the plan to release the final version in a week we really need everyone to try it out and comment. We'll list anything found under known issues in the first post. |
10-14-2012, 02:40 PM | #25 |
Sigil developer
Posts: 1,275
Karma: 1101600
Join Date: Jan 2011
Location: UK
Device: Kindle PW, K4 NT, K3, Kobo Touch
|
The Sigil User Guide will take some time to update, but you can view the What's New page for a list of features and updates for 0.6.0.
|
10-14-2012, 05:07 PM | #26 | |
Berti
Posts: 1,196
Karma: 4985964
Join Date: Jan 2012
Location: Zischebattem
Device: Acer Lumiread
|
Quote:
"Replace" / "Replace&Find Next" seems not to work properly find:<p>(Chapitre[^–]+?)\K ([^–]) Replace: – (read: blank Ndash blank) Options: Single Line, Regex, Current File The Position is located correctly. With "Replace" nothing is replaced. With "Replace&Find Next" it just jumps to the next position. "Replace all" works and saves the day |
|
10-14-2012, 05:15 PM | #27 |
Sigil developer
Posts: 1,275
Karma: 1101600
Join Date: Jan 2011
Location: UK
Device: Kindle PW, K4 NT, K3, Kobo Touch
|
Could you provide some text that you are trying to match?
EDIT: I'm not sure what text you are matching, but if I use the following then I do see a difference in 0.5.906 and 0.5.907 (.e. it change to ndash in 906 but not the current beta). Will look into it. <p>Chapitre - 1</p> Last edited by meme; 10-14-2012 at 05:36 PM. |
10-15-2012, 06:34 AM | #28 |
Zealot
Posts: 107
Karma: 554
Join Date: Oct 2008
Device: none
|
The first exploration of this beta: Click the chevron button (what a beautiful subtle button), hover over DotAll and Minimal Match checkboxes (require patience for one second)... tada, their tooltips magically change places.
PS: Still exploring this wonderful beta land. |
10-15-2012, 07:04 AM | #29 |
eBook FANatic
Posts: 18,301
Karma: 16071131
Join Date: Apr 2008
Location: Alabama, USA
Device: HP ipac RX5915 Wife's Kindle
|
Failure of URI in LOI
The attached EPUB has an in-line LOI. The latest Sigil inserts the correct path for the first image and no paths for the remainder of images.
First Image: Code:
<div class="justify"> <a href="../Text/The%20Enchanted%20Typewriter_0004.xhtml#front">FRONTISPIECE: I GAZED IN OPEN-MOUTHED IN WONDER</a> </div> Code:
<div class="justify"> <a href="#image01">"TATTOOED THE JINGLE BETWEEN MY SHOULDER BLADES"</a> </div> Validation reports no problems. |
10-15-2012, 07:23 AM | #30 |
Grand Sorcerer
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Probably need to take a look at the original html before you started editing with Sigil. I'd wager to say you did some file-splitting, as well.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
KinCleaner 1.1 Beta | SteveEisenberg | Kindle Developer's Corner | 0 | 12-20-2011 10:39 PM |
New Beta for BB? | FF2 | Amazon Kindle | 2 | 05-28-2011 10:21 AM |
Beta Beta Test of Major New Features | Starson17 | Calibre | 45 | 05-17-2010 10:55 AM |
0.6 out of beta? | Nate the great | Calibre | 3 | 07-17-2009 02:45 AM |