Taking into account web browsers, operating systems, iphone, blackberries, etc
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Taking into account web browsers, operating systems, iphone, blackberries, etc
While “safe” — either by correctly setting the encoding when delivering the page or by escaping using
&#xxx;— not all users will have fonts that can render these characters. Particularly “dingbat” characters (accented Western text characters are generally supported anywhere).So as long as you’re OK with some (relatively small) percentage of your users seeing a box rather than a glyph, go ahead.