Closed GoogleCodeExporter closed 9 years ago
Adapt It internally does use the \f* marker to end footnotes. Also footnotes are
displayed in a special text color which defaults to red text. So the end of
footnotes
should be easy to see because the end of the footnote would normally would be
the
last word of special (red) text. However, I think we might consider putting a
marker
in the navigation text area as an additional way to indicate the end of a
footnote,
which would help to distinguish the end of a footnote when it occurs within some
other special test such as a section heading.
Original comment by adaptitbill@gmail.com
on 12 Mar 2009 at 2:19
So I probably missed something to let the footnote text show up in a different
color.
In my setting it shows at the same color as the running text. This was the
reason, I
created this issue.
Checking in Edit/preferences/Font there options to set/change colors of fonts
Now, where to change the one for footnotes?
Searching in Help for 'footnotes', also gives the page: 'Fonts Tab' with the
info:
'Special text is text such as footnotes or editorial comments that have been
inserted
into the Source but is not part of the original document. ....'
I did not think that 'Special text' was something to include footnotes.
-> Add a page in Help about Special text and give a list, what all considered
to be
Special Text (e.g. footnotes, cross-references, title, headings ....)
Add a paragraph to tell the user how to change the color of special text and
what the
advantage is of this.
-> Perhaps give by default (if no choice is made for special text) a different
color
to special text than to the source and target text, which can be changed, if
needed.
Anyhow, if you add an indication of the end of a footnote (I think the same
also for
cross-references) would help too
Original comment by wolfgang...@gmx.de
on 12 Mar 2009 at 7:02
I have added "end fn" to the navigation text of the last source phrase of a
footnote.
This addition will appear in version update 4.1.2.
Original comment by adaptitbill@gmail.com
on 13 Mar 2009 at 2:24
Original issue reported on code.google.com by
wolfgang...@gmx.de
on 10 Mar 2009 at 11:24