mysql - php - utf8 encoding the text twice. Will it have any negative effect? -


this question has answer here:

mysql database returns utf8 encoded text. basically, used pdo attribute mysql_attr_init_command , passed:

set character set utf8

it returns utf8 encoded text. text in database plain utf8, &alum; returned is.

so need call utf8_encode again in php actual utf8 char. working fine.

i know, if have negative effect encoding text twice or not affect other encoding non-encoded text above?

thanks!

edit:

i using following code right characters:

 $val = utf8_encode(addslashes(html_entity_decode(strip_tags($val))));

so convert following text from:

<font color=\"#222222\" face=\"arial, sans-serif\" size=\"2\"> test event  &nbsp; &nbsp;</font><span style=\"color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 13px;\">pers&ouml;nlichkeit universit&auml;t&quot;</span>

(this text coming database, after calling set character set utf8)

to:

test event persönlichkeit universität\"

&auml; html entity shouldn't have made database in first place. has nothing utf-8.

if call utf8_encode on "&auml;" nothing happen encoding same iso-8859-1 , utf-8. see character represents in browser because interpreted html.

you should never, normal web app developer, call utf8_encode. don't need iso-8859-1 utf-8 conversion, firstly because browsers , mysql not support it. alias latin1 , iso-8859-1 windows-1252 compatibility. secondly, can cause browsers , database send data in utf-8 utf-8 , no conversion necessary.

you shouldn't convert html entities either - unnecessary because utf-8 can represent characters.

the data in database should not have concern html - data there should canonical authorative as-is representation of data. right there confusion whether data literally meant &auml; or ä causes problems this:

enter image description here

image thedailywtf


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers ...
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());...
Read more