Title: Same hyphen problem here
Last modified: February 16, 2020

---

# Same hyphen problem here

 *  Resolved [tolddsm](https://wordpress.org/support/users/tolddsm/)
 * (@tolddsm)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/same-hyphen-problem-here/)
 * Hi!
 * I’ve read about the related posts about the “hyphen issue” you mentioned, but
   I am still trying to add hyphen rather than en/em dash if there is a way..
    Heyphen
   looks just neater and more elegant than dashes, I wish you agree!
 * Have tried added html code &#8208 ; for hyphen in the seo titles but it automatically
   changes to non-breaking hyphen &#8209, looks thinner than hyphen.
 * I know there are issues and the hyphen is really not a big thing to consider 
   and to invest much time into, but I am still wondering(and hoping) if there is
   one day that we can get hyphen back in TSF future version?
 * TSF is so great that I cannot reject but the hyphen thing is just itching me 
   non-stop..
 * What do you say？ Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/same-hyphen-problem-here/#post-12443651)
 * Hello!
 * You switched on a new lightbulb above my head. 💡
 * When you enter either `-` or `-` (different from `‐` or `&#
   8208;`) in the title/description fields, the hyphen will be maintained, as it’ll
   bypass WordPress’ texturization protocol.
 * Is that the hyphen you were looking for?
 * In that, I think I can reintroduce the hyphen as a separator 🙂 Thanks!
    -  This reply was modified 6 years, 3 months ago by [Sybre Waaijer](https://wordpress.org/support/users/cybr/).
      Reason: bbPress formatting
    -  This reply was modified 6 years, 3 months ago by [Sybre Waaijer](https://wordpress.org/support/users/cybr/).
      Reason: bbPress please :(
    -  This reply was modified 6 years, 3 months ago by [Sybre Waaijer](https://wordpress.org/support/users/cybr/).
      Reason: New hyphen
 *  Thread Starter [tolddsm](https://wordpress.org/support/users/tolddsm/)
 * (@tolddsm)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/same-hyphen-problem-here/#post-12443879)
 * Hi Sybre,
 * Yes it works!
 * When added in title/description, the first time it will show correctly as hyphen,
   but if you update the page again, then the hyphen cannot pass wordpress texturization
   and will be transferred to en dash again. but that’s not a problem, i can alwasy
   add unicode everytime when I have to change title/description, not very often
   though.
 * Thanks!
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [6 years, 3 months ago](https://wordpress.org/support/topic/same-hyphen-problem-here/#post-12444160)
 * Awesome!
 * I got a patch ready, where I’ve reintroduced the hyphen option, and that’ll allow
   you to edit the titles without the cumbersome HTML-character pasting 🙂
 * [The patch.](https://github.com/sybrew/the-seo-framework/commit/892351c6d55b09bf47b94eec8c73233878bedd7a)
 * It’ll be shipped in the next minor update (ETA unknown). Cheers!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Same hyphen problem here’ is closed to new replies.

 * ![](https://ps.w.org/autodescription/assets/icon.svg?rev=3000376)
 * [The SEO Framework – Fast, Automated, Effortless.](https://wordpress.org/plugins/autodescription/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autodescription/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autodescription/)
 * [Active Topics](https://wordpress.org/support/plugin/autodescription/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autodescription/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autodescription/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * Last activity: [6 years, 3 months ago](https://wordpress.org/support/topic/same-hyphen-problem-here/#post-12444160)
 * Status: resolved