Title: Encoding
Last modified: August 21, 2016

---

# Encoding

 *  Resolved [aaron@rossano.com.au](https://wordpress.org/support/users/aaronrossanocomau/)
 * (@aaronrossanocomau)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/encoding-7/)
 * Hi, The encoding seems to be wrong. The text appears as: we're
 * [https://wordpress.org/plugins/timeline-twitter-feed/](https://wordpress.org/plugins/timeline-twitter-feed/)

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

 *  Thread Starter [aaron@rossano.com.au](https://wordpress.org/support/users/aaronrossanocomau/)
 * (@aaronrossanocomau)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/encoding-7/#post-5036388)
 * funny enough it’s the symbols that are encoding correctly.
 * plain: ‘
    symbol: ‘
 * This is how the tweet came out: Plain: ' Symbol: ‘
 *  Thread Starter [aaron@rossano.com.au](https://wordpress.org/support/users/aaronrossanocomau/)
 * (@aaronrossanocomau)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/encoding-7/#post-5036394)
 * identified the issue is related to hashtags converted to links before the text
   is set as html symbols.
 *  Thread Starter [aaron@rossano.com.au](https://wordpress.org/support/users/aaronrossanocomau/)
 * (@aaronrossanocomau)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/encoding-7/#post-5036396)
 * fix: the regular expression needs to exclude tags the start with ‘&’.
    /includes/
   class-timeline-twitter-feed-shortcode.php line 147: `$text = preg_replace( '(#([
   a-zA-Z0-9\_]+))', '<a href="http://twitter.com/search?q=%23\\1" target="_blank"
   rel="nofollow">\</a>', $text );` change to:
 *     ```
       $text = preg_replace( '/(?<!&)#(\w+)/i', '<a href="http://twitter.com/search?q=%23\\1" target="_blank" rel="nofollow">\</a>', $text );
       ```
   
 * It needs to be fixed in other places, hopefully you can implement the solution
   across the plugin on the next update.
 *  Plugin Author [ezraverheijen](https://wordpress.org/support/users/ezraverheijen/)
 * (@ezraverheijen)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/encoding-7/#post-5036651)
 * This is fixed in version 1.0
    Thanks for reporting!

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

The topic ‘Encoding’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/timeline-twitter-feed_9fcce9.svg)
 * [Timeline Twitter Feed](https://wordpress.org/plugins/timeline-twitter-feed/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/timeline-twitter-feed/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/timeline-twitter-feed/)
 * [Active Topics](https://wordpress.org/support/plugin/timeline-twitter-feed/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/timeline-twitter-feed/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/timeline-twitter-feed/reviews/)

## Tags

 * [encoding](https://wordpress.org/support/topic-tag/encoding/)
 * [text](https://wordpress.org/support/topic-tag/text/)

 * 4 replies
 * 2 participants
 * Last reply from: [ezraverheijen](https://wordpress.org/support/users/ezraverheijen/)
 * Last activity: [11 years, 6 months ago](https://wordpress.org/support/topic/encoding-7/#post-5036651)
 * Status: resolved