[Plugin] PunctuationSmarten Sigil plugin

[DiapDealer]

Updated to v0.3.1 in the first post.

Changes are mostly cosmetic, but they include:

- update to make use of Sigil's upcoming autostart/autoclose feature for plugins

- files selected in Book Browser are pre-selected in plugin widget

- add update check for plugin

[DiapDealer]

Well so much for that update!

Reverting back to v0.3.0 until I work out a module dependency issue.

Sorry for any confusion.

[DiapDealer]

New version 0.3.2 in the the first post.
(replaces faulty v0.3.1)

[bookman156]

This is a great plugin. Works wonderfully.

I have only discovered, so far, one instance where it doesn't work, in map coordinates, which I expected and went back to correct to a prime, eg: 51° 28′ 38″ N

I was wondering whether it might not be a good idea to compile a list of instances like this where this plugin needs to be cleaned up after, so one can make an effort to find such things.

Any others to add to the list?

[BetterRed]

IIRC imperial inch and foot should be designated by double and single prime respectively, although they're most often represented as straight single and double quote, or increasingly 'in' and 'ft'.

[bookman156]

It occurs to me that one can 'clean up' before running this plugin. If I change to a prime in a coordinate first, then the prime will be left untouched when I run the plugin. Similarly for any other candidates for the single and double prime symbol, such as Imperial feet and inches.

Useful compendium of prime uses:

https://en.wikipedia.org/wiki/Prime_(symbol)

[BetterRed]

Originally Posted by bookman156

It occurs to me that one can 'clean up' before running this plugin.

via saved search(es)

psst: your Wikip link is 'broken' should be - Prime (symbol)

BR

[bookman156]

What would be a handy addition to this plugin would be the ability to replace a hyphen in date ranges with an en dash, as in for example: 1921-1985.

Presumably something could be written that recognises that it is numbers on either side of the hyphen and not letters as in a hyphenated word?

[bookman156]

This would also be useful to change from hyphen to en dash in page rages: pp 94-96.

http://www.thepunctuationguide.com/en-dash.html

That would be such a useful ability to have in the book I'm editing now. Currently I'm planning to replace them manually, hundreds of the damn things, so if anyone has any idea of how to do it easier I'd love to hear. (Although I'll probably just be satisfied with the hyphen until I can work out a way not to have to do it manually.)

[DiapDealer]

I've bent and twisted the SmartyPants algorithm was far as I'm willing to. Every new addition seems to come at the cost of breaking something else at this point.

[Doitsu]

Originally Posted by bookman156

What would be a handy addition to this plugin would be the ability to replace a hyphen in date ranges with an en dash, as in for example: 1921-1985.

Originally Posted by bookman156

This would also be useful to change from hyphen to en dash in page rages: pp 94-96.

@bookman156: Since Sigil supports regular expressions, you could fix both issues with a simple regex search:

4-digit date ranges:

Find:(\d{4})-(\d{4})
Replace:\1–\2

Page numbers:

Find:pp (\d+)-(\d+)
Replace:pp \1–\2

There's also a Sigil regex thread.

[bookman156]

Originally Posted by Doitsu

@bookman156: Since Sigil supports regular expressions, you could fix both issues with a simple regex search

Fascinating. Thanks! I'll try that out.

[bookman156]

I guess I could do any number range, page numbers and dates and whatever else, with:

Find: (\d+)-(\d+)
Replace: \1–\2

Then I'd only have to find things like BC years.

[bookman156]

Works a treat!

And I don't have to find BC years either because they would be in the form: 722-481BC

Although 2BC-AD5 would require some effort.

[bookman156]

Originally Posted by DiapDealer

I've bent and twisted the SmartyPants algorithm was far as I'm willing to. Every new addition seems to come at the cost of breaking something else at this point.

Yes, best not to fix what isn't broken, and, luckily, no need to anyway now I've discovered the joy of regex.