update to properly handle non-ascii chars in the extension, using double-encoding of problem chars. step 1: double-encode all non-ascii chars on POST/PUT requests.  step 2: run description and notes fields through manual decode call, for proper display on browser extension.
added logging line for string char evaluation and encoding (commented by default)
Merge pull request #56 from mmerriam/develop

update to properly handle non-ascii chars in the extension, using double...