[MidnightRose]

I have no idea why, but this specific webnovel is producing a file that Calibre seems unable to parse.

https://www.royalroad.com/fiction/10...f-gold-digging

Trying to do any kind of conversion or using calibre's internal book editor gives this error:

calibre, version 8.11.0
ERROR: Failed to open book: Failed to open book, click "Show details" for more information.

Traceback (most recent call last):
  File "calibre\gui2\tweak_book\job.py", line 33, in run
  File "calibre\gui2\tweak_book\boss.py", line 101, in get_container
  File "calibre\ebooks\oeb\polish\container.py", line 1639, in get_container
  File "calibre\ebooks\oeb\polish\container.py", line 1232, in __init__
  File "calibre\ebooks\oeb\polish\container.py", line 279, in __init__
  File "calibre\ebooks\oeb\polish\container.py", line 282, in refresh_mime_map
  File "calibre\ebooks\oeb\polish\container.py", line 544, in opf_xpath
  File "calibre\ebooks\oeb\polish\container.py", line 649, in opf
  File "calibre\ebooks\oeb\polish\container.py", line 632, in parsed
  File "calibre\ebooks\oeb\polish\container.py", line 603, in parse
  File "calibre\ebooks\oeb\polish\container.py", line 179, in parse_xml
  File "calibre\utils\xml_parse.py", line 26, in safe_xml_fromstring
  File "src/lxml/etree.pyx", line 3428, in lxml.etree.fromstring
  File "src/lxml/parser.pxi", line 2059, in lxml.etree._parseMemoryDocument
  File "src/lxml/parser.pxi", line 1914, in lxml.etree._parseDoc
  File "src/lxml/parser.pxi", line 1930, in lxml.etree._parseDoc_unicode
  File "src/lxml/parser.pxi", line 1133, in lxml.etree._BaseParser._parseUnicodeDoc
  File "src/lxml/parser.pxi", line 647, in lxml.etree._ParserContext._handleParseResultDoc
  File "src/lxml/parser.pxi", line 765, in lxml.etree._handleParseResult
  File "src/lxml/parser.pxi", line 689, in lxml.etree._raiseParseError
  File "<string>", line 6
lxml.etree.XMLSyntaxError: internal error, line 6, column 3040

Meanwhile when I take the internal EPUB file and stick it into kindle previewer, it's able to open the file just fine.

Could it be the emoji in the description?