Has anyone been having problems with footnotes disappearing on export or on compile draft? That’s been happening here since upgrading to 1.5, not before.
B DaCosta
What are you exporting to? RTF fully supports these features, other formats not so much so (or rather, the OS X export engine doesn’t support them as well as RTF, even though some of the formats support them). Also make sure that you are opening the file in a word processor that supports footnotes - i.e. not TextEdit.
All the best,
Keith
I’m having trouble with this as well – exporting to RTF, and then opening the RTF in Pages. Annotations make the transition, but footnotes disappear. I think the problem is with Pages’s import, rather than the draft compilation, as opening the RTF in Mellel produces a document with footnotes included. So I think I’m going to go have to fuss at the Pages people…
Precisely. The FAQ, under “Best way to export to word processors” has a table listing which programs can read RTF footnotes and which cannot. You get annotations because Scrivener turns them into coloured text unless you check the box saying to turn them into RTF Comments. Don’t do that unless you are using Word, though, support for them is even less than footnotes/endnotes.
And do fuss at the Pages people. Footnotes are not the only RTF feature they blithely ignore.
Pages doesn’t fully support RTF. And the OS X text engine doesn’t support footnotes, annotations or images for .doc or .docx. So I’m afraid there is no way to get annotations, footnotes or images exported to Pages. Please do post your feedback to Apple asking them to add better RTF support (or to provide developers with a .pages importer/exporter). Unfortunately this lies in the hands of Apple.
All the best,
Keith
Actually you can get images if you use RTFD, at least you could in version 2. And as noted elsewhere it is possible to get footnotes into Pages, but you have to route through OpenOffice.org or NeoOffice in order to create a well formed DOC file, which can then be imported into Pages 3. This workaround does not work in Pages 1 or 2, I believe.