View Single Post
Old 07-20-2009, 07:27 AM   #5
zelda_pinwheel
zeldinha zippy zeldissima
zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.zelda_pinwheel ought to be getting tired of karma fortunes by now.
 
zelda_pinwheel's Avatar
 
Posts: 27,827
Karma: 921169
Join Date: Dec 2007
Location: Paris, France
Device: eb1150 & is that a nook in her pocket, or she just happy to see you?
i use named entities for all special characters (&mdash, &ldquo etc. but also &agrave, &oelig, and &eacute etc.), it's a habit from coding for the web. i have noticed that when creating an xhtml file in dreamweaver, if you write the special character in the "design" box, it will automatically be encoded with the entity in the code ; however if you are working with the epub dtd most special characters will not be automatically encoded, this may mean that it's not specified as necessary with that doctype. but, since i am wary of (bad) suprises i think it's safer to use the named entities even with the utf-8 encoding. however your question makes me realise i have not verified what the epub standard specifically says about this ; interesting question.
zelda_pinwheel is offline   Reply With Quote