View Single Post
Old 04-03-2016, 11:20 AM   #9
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,705
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Doitsu View Post
If you used Sigil 0.9.4, there's a bug in the Metadata Editor. It'll delete & entities if you open and close the Metadata Editor.
(There was also different & bug in an earlier version.)
The workaround is to enter & directly into the .opf file.
BTW, even though Calibre and other tools use an ampersand for two authors, I remember having read somewhere that the proper way would be to have two author metadata entries.
The current Sigil bug (v0.9.5) doesn't rear it's ugly head quite that easily. You can, in fact, enter an ampersand character in the metadata editor in most fields, and it will be properly saved to the OPF as an & entity. And vice-versa: manually entering an & entity in the OPF will still allow you to later edit the metadata with Sigil's Metadata Editor without fear of & entities being deleted.

The bug only occurs when & entities occur in an attribute string value (typically the opf:file-as attribute) and the Metadata Editor is used. That is when & entities will disappear from your OPF file. Entering an ampersand character in a "opf:file-as" string value in the Metadata Editor will also trigger it. And it's been fixed for the next release as BetterRed mentioned.

In the meantime, KevinH's workaround (as, again, BetterRed mentioned) will work. If you need two authors in one dc:creator tag, just use a different separator for the opf:file-as attribute string, such as a semi-colon (either manually or WITH the Metadata Editor) and you'll be fine:
Code:
<dc:creator opf:role="aut" opf:file-as="One, Author; Two, Author">Author One &amp; Author Two</dc:creator>

Last edited by DiapDealer; 04-03-2016 at 11:27 AM.
DiapDealer is offline   Reply With Quote