Re: Creating footnotes on import

From: "Martin Sevior" <msevior@gmail.com>
Subject: Re: Creating footnotes on import

> It is important that each footnote has a footnote-id attribute that is
> unique and where the footnote anchors and reference match. It sounds
> like you are not doing this. Have a look at the *.abw file with a text
> editor with a few footnotes in them. You'll quickly see what is
> needed. Otherwise it looks like you are doing the right thing.
>
> On Wed, Jan 19, 2011 at 7:29 AM, ????? <eskaer_spamsink@ngs.ru> wrote:
>> Which is the correct algorithm for import filter to create footnotes?
>>
>> I tried:
>>
>> // when parsing body text
>>
>> if (footnote marker encountered)
>> appendObject(PTO_Field,{"type","footnote_ref","footnote-id",<ordinal>})
>>
>> // after parsing body text
>>
>> for each (footnote text)
>> appendStrux(PTX_SectionFootnote,{"footnote-id",<ordinal>}
>> appendObject(PTO_Field,{"type","footnote_anchor","footnote-id",<ordinal>})
>> // parse footnote contents
>> appendStrux(PTX_EndFootnote)
>>
>>
>> The resulting document looks weird, the footnotes after 1st are unfocusable, and when editing document occasionally crash. Since no document format specification is available, I would like to know the correct procedure.
>

Yes, I'm using unique (and matching) footnote-id:s.
But is it important that <foot> element was in the same <p> as its marker? It seems that app is confused by all footnotes being inside of the last paragraph in document, is it possible?.

 
Received on Wed Jan 19 01:45:04 2011