From c942ac0623b93fec8f58b04a7800dd6411587642 Mon Sep 17 00:00:00 2001
From: AE Creations <aecreations@server.fake>
Date: Fri, 6 Jun 2014 20:57:19 -0700
Subject: [PATCH] Additional fix for issue #2 - add pref to allow disabling of
 double-encoding special chars, if necessary in future.  Also, replace a few
 more special chars

---
 src/chrome/content/submit.js | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/src/chrome/content/submit.js b/src/chrome/content/submit.js
index b30358f..69a381f 100755
--- a/src/chrome/content/submit.js
+++ b/src/chrome/content/submit.js
@@ -73,6 +73,11 @@ function delicious_post_dialog_accept() {
 
   function getEncodedStr(aString)
   {
+    let isDblEncodeSpecChars = Application.prefs.getPref("extensions.aecreations.deliciouspost.double_encode_special_chars", true);
+    if (! isDblEncodeSpecChars) {
+      return aString;
+    }
+
     // See <https://github.com/zmanring/chrome-ext-delicious/pull/56> for
     // how an author of a Delicious extension for Google Chrome handled an
     // issue similar to Delicious Post issue #2.
@@ -96,7 +101,11 @@ function delicious_post_dialog_accept() {
 	  case 0x00BB:  // Right-pointing double angle quotation mark
 	    chr = ">>";
 	    break;
+	  case 0x25B6:  // Black right-pointing triangle
+	    chr = "";   // (used in YouTube page titles for playing videos)
+	    break;
 	  case 0x2022:  // Bullet
+	  case 0x00B7:  // Middle dot
 	    chr = "-";
 	    break;
 	  default: