For most of us who have websites which exclusively use western character set, the change of character set is of no consequence.
Thanks Ross. What’s interesting though, is that when I went into my local install today and landed on my homepage, there was an error. Guess what! it was related to emojis. Even though I had utf-8, and previously when I had made my 4.2 update, there was no such error. The error pointed to the formatting.php file in the includes folder, line 4144:
if ( SCRIPT_DEBUG ) {// line 4144
$settings['source'] = array(
/** This filter is documented in wp-includes/class.wp-scripts.php */
'wpemoji' => apply_filters( 'script_loader_src', includes_url( "js/wp-emoji.js?$version" ), 'wpemoji' ),
/** This filter is documented in wp-includes/class.wp-scripts.php */
'twemoji' => apply_filters( 'script_loader_src', includes_url( "js/twemoji.js?$version" ), 'twemoji' ),
);
It was kind of funny. Then I updated to 4.2.1, and it was gone. I was just wondering about this because of those of us that might want to internationalize our themes or applications. I am definitely considering doing that down the road, and maybe sooner rather than later. That’s why I asked. And in 4.2, there were issues with implementation of emojis etc. as evidenced by the error I received when I landed on my test site. Funny that it took so long to show up! Didn’t happen on my live sites, so I’m wondering if it was a theme issue. Didn’t check against default themes however. Next time I will have to. BTW, this code is post update. Just wanted to point to the area that was pointed to on my website. Sorry I can’t link to this local install, but next time I encounter something I will share screenshots.