View Single Post
Old 04-04-2016, 10:38 AM   #12
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,816
Karma: 6000000
Join Date: Nov 2009
Device: many
What do you mean "&" doesn't work?

If this is a dc:title metadata entry entered directly into the opf then "&" is the only correct way I know to handle that. It is an official xml escape sequence that is recognized and understood by html, html5, xml, xhtml, etc.

Alternatively, you can try replacing the "&" with a numeric entity "& # 38 ;" (without the spaces) but if "&" doesn't work I have my doubts that "& # 38 ;" (again without the spaces) will work either.

And specifically what do you mean, it doesn't work? What are you viewing the opf or metadata with that is showing it doesn't work?

KevinH

Last edited by KevinH; 04-04-2016 at 10:41 AM.
KevinH is offline   Reply With Quote