Title: CLRD's Replies | WordPress.org

---

# CLRD

  [  ](https://wordpress.org/support/users/clrd/)

 *   [Profile](https://wordpress.org/support/users/clrd/)
 *   [Topics Started](https://wordpress.org/support/users/clrd/topics/)
 *   [Replies Created](https://wordpress.org/support/users/clrd/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/clrd/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/clrd/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/clrd/engagements/)
 *   [Favorites](https://wordpress.org/support/users/clrd/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Spotlight Social Feeds - Block, Shortcode, and Widget] Update](https://wordpress.org/support/topic/not-recommended-use-at-your-own-risk/)
 *  Thread Starter [CLRD](https://wordpress.org/support/users/clrd/)
 * (@clrd)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/not-recommended-use-at-your-own-risk/#post-13295357)
 * [@markzahra](https://wordpress.org/support/users/markzahra/)
    I was also quick
   to jump to conclusion. Apologies on my end as well. Thanks for looking into this.
    -  This reply was modified 5 years, 9 months ago by [CLRD](https://wordpress.org/support/users/clrd/).
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Spotlight Social Feeds - Block, Shortcode, and Widget] Update](https://wordpress.org/support/topic/not-recommended-use-at-your-own-risk/)
 *  Thread Starter [CLRD](https://wordpress.org/support/users/clrd/)
 * (@clrd)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/not-recommended-use-at-your-own-risk/#post-13293962)
 * [@markzahra](https://wordpress.org/support/users/markzahra/) my emails should’ve
   showed up as CLRD. Replied to your email just about 15min ago on the Legacy API.
   Hope that helps. Thanks.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Spotlight Social Feeds - Block, Shortcode, and Widget] Update](https://wordpress.org/support/topic/not-recommended-use-at-your-own-risk/)
 *  Thread Starter [CLRD](https://wordpress.org/support/users/clrd/)
 * (@clrd)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/not-recommended-use-at-your-own-risk/#post-13293912)
 * [@markzahra](https://wordpress.org/support/users/markzahra/) thanks for the update.
   There are still a few things that needs sorting out, but I emailed you on that.
   Apologies for the misunderstanding.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Text Hover] Works as intended and easy to use.](https://wordpress.org/support/topic/works-as-intended-and-easy-to-use/)
 *  Thread Starter [CLRD](https://wordpress.org/support/users/clrd/)
 * (@clrd)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/works-as-intended-and-easy-to-use/#post-13182531)
 * [@coffee2code](https://wordpress.org/support/users/coffee2code/)
 * That’s a good point. In other languages as well, if spaces were ignored as separators,
   it would also prove problematic for word matching.
 * The current work around of appending/prepending the separator is not bad at all.
   It’s been working well for me so far, and hardly even noticeable actually.
 * The suggestion on using two input fields will definitely offer more flexibility
   for other users; but in my case, I will have to stick with the work around, as
   it may potentially confuse a compound word of multiple characters with those 
   ignoring the space (i.e. the plain form). Resulting in a double hover text, one
   for the compound word, and one within it (in the plain form).
 * Appreciate the suggestion though. As it is, it has been working for my use case.
   So no complaints. Thanks.

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