Title: substr encoding problems
Last modified: August 22, 2016

---

# substr encoding problems

 *  Resolved [infanf](https://wordpress.org/support/users/infanf/)
 * (@infanf)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/substr-encoding-problems/)
 * First of all: Thanks for this great and easy to use plugin!
    But I had some issues
   with unicode characters in the portfolio content. I resolved it by changing line
   28 in shortcode-data.php to `$newString = mb_substr($string, 0, 50, mb_detect_encoding(
   $string));` I just wanted to let you know, maybe others have the same problem
   😉
 * [https://wordpress.org/plugins/full-width-responsive-portfolio/](https://wordpress.org/plugins/full-width-responsive-portfolio/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Hardeep Asrani](https://wordpress.org/support/users/hardeepasrani/)
 * (@hardeepasrani)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/substr-encoding-problems/#post-5567017)
 * Amazing! Thanks for the tip and I’ll use it in the next update 🙂
 * Thanks 🙂

Viewing 1 replies (of 1 total)

The topic ‘substr encoding problems’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/full-width-responsive-portfolio.svg)
 * [Full Width Responsive Portfolio](https://wordpress.org/plugins/full-width-responsive-portfolio/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/full-width-responsive-portfolio/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/full-width-responsive-portfolio/)
 * [Active Topics](https://wordpress.org/support/plugin/full-width-responsive-portfolio/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/full-width-responsive-portfolio/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/full-width-responsive-portfolio/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Hardeep Asrani](https://wordpress.org/support/users/hardeepasrani/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/substr-encoding-problems/#post-5567017)
 * Status: resolved