i had issue earlier today couldn't compile static site due non-ascii characters in kramdown file. while writing small script finds these characters in our content, ran across large number of non-html encoded special characters.
what implications in including these characters directly in html? take © character.
if include character directly in html, seems render correctly in browser. being said, don't know side-effects don't have fonts installed support these characters.
what side effects of leaving these non-ascii characters in html? know in situations can lead strange (?) characters showing up, i'd more specific information on how these special characters rendered.
if html encode these special characters , client doesn't have font supports them, show same (?) character? there meaningful difference between using html-encoded vs non encoded characters?usign
is there meaningful difference between using html-encoded vs non encoded characters?
not in terms of browser being able display them in general. if want use these call them "non-standard" characters (which standard characters, not ascii characters), should specify encoding, preferably utf-8. html5 way of doing (which backwards compatible , supported pretty browsers) is
<meta charset="utf-8"> that said, tools compiling static html markdown etc. might have problems it, depends on tool. you're safer using entities © there; can use without specifying encoding.
this not full story, way browser decoding file can influenced other factors, http response headers. also, if omit it, observe, browsers can still parse correctly, there's no guarantee.
