PageKicker v2.1.1-Keats improves acronym suggester

Version 2.1.1 of PageKicker replaces an acronym-identifying regex with a narrower one that produces better results.  It is still far from perfect.

#sed 's/[[:space:]]\+/\n/g' $txtinfile  | sort -u | \
 egrep  '[[:upper:]].*[[:upper:]]' | sed 's/[\(\),]//g' | uniq
sed 's/[[:space:]]\+/\n/g' $txtinfile  | sort -u | \
  egrep [A-Z][a-zA-Z0-9+\.\&]*[A-Z0-9] | sed 's/[\(\),]//g' | uniq

I reviewed a number of text analytics approaches prior to selecting this simpler and stupider regex approach.  Most of the available tools require that the full phrase be immediately followed by the acronym, often in parentheses.  There’s one that doesn’t require that but it is in Java which means I’d have to traverse a learning curve to plug it in.   Also, I’m not really looking just for acronyms, I’m also looking for technical initialisms such as B8 or B-8.

There is a very simple test file included in the commit that includes these terms:

cat 
dog 
fool 
M21a 
M21A 
SSN 
SSN21 
V-8 
GOLLY
V8

Output from old version:

GOLLY
M21A
SSN
SSN21

Output from new version:

GOLLY
M21A
M21a
SSN
SSN21
V8

PageKicker v2.01-Keats is now available

After a year of leaving it fallow, I have had enough hobby time to update the open source version of PageKicker to version 2.0.1-Keats.  The key new features are that it runs interchangeably on Linux and Mac versions of bash; replaces the (deprecated) Alchemy API Named Entity Recognizer with the well-known Stanford NER; and adds the booktype “draft-report”, which produces the first draft of a term-paper style report without the front and back matter of a book: a great way to jump-start a writing project.

Stay tuned for more about the significance of this for Nimble Books authors and readers.

Enabling SSL

Enabling SSL is always a bit of an adventure, but it went pretty smoothly this time for https://www.nimblebooks.com.  Two hours of googling, thirty minutes on the phone with customer service.  However, there are still things broken.  I am running a single WP multisite installation and want to have two distinct TLDs: nimblebooks.com and fredzannarbor.com.  I don’t actually need SSL for fredzannarbor.com just yet (no commerce or sensitive info), but things seem to be getting confused when I jump from https:nimblebooks pages to http:fredzannarbor ones because the server is looking for https:fredzannarbor.  Will probably bit the bullet and get an SSL cert for fredzannarbor.com.