|
Plantalia, it sounds like you're running into image-format problems — it's another area that RTF can be a bit glitchy, although I've not seen the "losing footnotes/endnotes" issue (believe me, with some of the stuff I've worked with I would have noticed that — I've been the technical editor for several academic journals in both STEM and non-STEM fields). RTF doesn't handle vector image formats, or rather Word's interface with RTF files glitches on vector image formats (LibreOffice does better but has its own, actually worse, problems with crossreferences). Oddly enough, Word's use of RTFs also has trouble with some BMPs (which tend to blow up and cross memory-sector boundaries for no apparent reason)... and with embedded HTML, which may be the real source of your problems.*
A PDF may turn out to be your best end result, but don't use any internal PDF converter or an Adobe product. (For whatever reason, Adobe's own products tend to glitch or fully choke on pages that have both multiple images and either multiple footnotes or a continued footnote.) Instead, use one of the many, many "print to PDF" utilities out there; I use Bullzip for Windows, but there are several others worth considering, and several for both the Mac and Linux-native systems.
* Short version: In Microsoft's infinite wisdom, and to maintain backward compatibility with its own prior decisions back to the 90s, HTML-coded hyperlinks in Office files are not fully W3C compliant (for example, internal link names often begin with numerals, which is a no-no); they'll continue to work inside the program, but results when sent to another program are unpredictable. Which is not at all to say that W3C is perfect, just that epub readers tend to be snooty about it.
|