XSL-FO two separate footnote blocks (XEP)
up vote
0
down vote
favorite
XSL-FO (XEP), XSLT 2.0
In academic editions of texts we often have the need for two separate sets of footnotes, one series using letters (a, b, c, etc.) and a series using numbers (1, 2, 3, etc.).
Getting the relative footnote letters and numbers inline in the text with xsl:number inside fo:footnote/fo:inline works fine.
Now I need to get the footnote content into two separate blocks at the bottom of the text, to look like this example: 
But I can't identify a way with fo:footnote/fo:footnote-body to create two separate blocks, lettered notes first, numbered notes second.
Thanks in advance for any ideas.
xslt-2.0 xsl-fo
asked Nov 11 at 14:39
jbrehr
137112
add a comment |
up vote
0
down vote
favorite
XSL-FO (XEP), XSLT 2.0
In academic editions of texts we often have the need for two separate sets of footnotes, one series using letters (a, b, c, etc.) and a series using numbers (1, 2, 3, etc.).
Getting the relative footnote letters and numbers inline in the text with xsl:number inside fo:footnote/fo:inline works fine.
Now I need to get the footnote content into two separate blocks at the bottom of the text, to look like this example:
But I can't identify a way with fo:footnote/fo:footnote-body to create two separate blocks, lettered notes first, numbered notes second.
Thanks in advance for any ideas.
xslt-2.0 xsl-fo
asked Nov 11 at 14:39
jbrehr
137112
Would it be too nonacademic to float the small notes to the side of the page as sidenotes and then use regularfo:footnotefor the block footnotes?
– Tony Graham
Nov 20 at 13:21
Yes, because there is a definite line between the 'text' and its possible marginal annotations (in particular when editing medieval manuscripts) and the critical apparatus. Any marginalia would be considered part of the original text.
– jbrehr
Nov 20 at 13:53
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
XSL-FO (XEP), XSLT 2.0
In academic editions of texts we often have the need for two separate sets of footnotes, one series using letters (a, b, c, etc.) and a series using numbers (1, 2, 3, etc.).
Getting the relative footnote letters and numbers inline in the text with xsl:number inside fo:footnote/fo:inline works fine.
Now I need to get the footnote content into two separate blocks at the bottom of the text, to look like this example:
But I can't identify a way with fo:footnote/fo:footnote-body to create two separate blocks, lettered notes first, numbered notes second.
Thanks in advance for any ideas.
xslt-2.0 xsl-fo
asked Nov 11 at 14:39
jbrehr
137112
XSL-FO (XEP), XSLT 2.0
In academic editions of texts we often have the need for two separate sets of footnotes, one series using letters (a, b, c, etc.) and a series using numbers (1, 2, 3, etc.).
Getting the relative footnote letters and numbers inline in the text with xsl:number inside fo:footnote/fo:inline works fine.
Now I need to get the footnote content into two separate blocks at the bottom of the text, to look like this example:
But I can't identify a way with fo:footnote/fo:footnote-body to create two separate blocks, lettered notes first, numbered notes second.
Thanks in advance for any ideas.
xslt-2.0 xsl-fo
xslt-2.0 xsl-fo
asked Nov 11 at 14:39
jbrehr
137112
asked Nov 11 at 14:39
jbrehr
137112
asked Nov 11 at 14:39
jbrehr
137112
asked Nov 11 at 14:39
jbrehr
137112
asked Nov 11 at 14:39
jbrehr
137112
137112
Would it be too nonacademic to float the small notes to the side of the page as sidenotes and then use regularfo:footnotefor the block footnotes?
– Tony Graham
Nov 20 at 13:21
Yes, because there is a definite line between the 'text' and its possible marginal annotations (in particular when editing medieval manuscripts) and the critical apparatus. Any marginalia would be considered part of the original text.
– jbrehr
Nov 20 at 13:53
add a comment |
Would it be too nonacademic to float the small notes to the side of the page as sidenotes and then use regularfo:footnotefor the block footnotes?
– Tony Graham
Nov 20 at 13:21
Yes, because there is a definite line between the 'text' and its possible marginal annotations (in particular when editing medieval manuscripts) and the critical apparatus. Any marginalia would be considered part of the original text.
– jbrehr
Nov 20 at 13:53
Would it be too nonacademic to float the small notes to the side of the page as sidenotes and then use regular
fo:footnote for the block footnotes?– Tony Graham
Nov 20 at 13:21
Would it be too nonacademic to float the small notes to the side of the page as sidenotes and then use regular
fo:footnote for the block footnotes?– Tony Graham
Nov 20 at 13:21
Yes, because there is a definite line between the 'text' and its possible marginal annotations (in particular when editing medieval manuscripts) and the critical apparatus. Any marginalia would be considered part of the original text.
– jbrehr
Nov 20 at 13:53
Yes, because there is a definite line between the 'text' and its possible marginal annotations (in particular when editing medieval manuscripts) and the critical apparatus. Any marginalia would be considered part of the original text.
– jbrehr
Nov 20 at 13:53
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I do not believe that the structure you show is possible at all, or at least with custom code to manipulate the resulting area tree (intermediate format also called XEPOUT).
1) The first set of "footnotes" you show as inline. I would assume these could run one, two maybe three lines. That alone I could not see how to build properly, without maybe some hack. Such a structure could be possibly accomplished by surrounding each footnote with a marker with fo:inline's and pull those to the footer. In other words, not make them footnotes.
Since they are separate in the document you would need something like make marker A, make marker B, as they occur on the page ... and a footer that would pull the universe of all markers but only on that page (first starting on page without carryover). Now if those markers did not exist, it would pull nothing. So that could be possible to do if you knew for instance that you would never have more than F markers, then pull A through F in the footer.
2) The second part is just footnotes
3) However, the two areas would be out of sequence as the footer with A, B ... would be below the numbered. So you would have to then develop custom XSL to flip those areas.
And last, since you cannot dynamically size a footer area, it is unclear that even that would work out acceptably well especially it is such that the A, B type footnotes could be one line or six lines. You would only be able to do it if a fixed space was known to work.
answered Nov 16 at 20:55
Kevin Brown
6,82721128
Indeed, I gave up on using built-infootnotes(and I suspect this is a reason my colleagues frequently transform to TeX or LaTeX.) I decided to create a solution much like in an XSL output to HTML, by manually building two blocks of separate content at the end of my flow which I can control directly. It's overly complex but it functions. Unfortunately, the resulting hack is restricted to deployment at the end of a given 'section', not at the bottom of each page.
– jbrehr
Nov 17 at 9:31
Incidentally, it strikes me as a modest change that XEP could implement (along the lines of using attributes likexsl:numberuses and some sort of display mode attribute like inline vs newline). For other things like margin notes, etc. XEP handles it all really well for me.
– jbrehr
Nov 17 at 9:34
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I do not believe that the structure you show is possible at all, or at least with custom code to manipulate the resulting area tree (intermediate format also called XEPOUT).
1) The first set of "footnotes" you show as inline. I would assume these could run one, two maybe three lines. That alone I could not see how to build properly, without maybe some hack. Such a structure could be possibly accomplished by surrounding each footnote with a marker with fo:inline's and pull those to the footer. In other words, not make them footnotes.
Since they are separate in the document you would need something like make marker A, make marker B, as they occur on the page ... and a footer that would pull the universe of all markers but only on that page (first starting on page without carryover). Now if those markers did not exist, it would pull nothing. So that could be possible to do if you knew for instance that you would never have more than F markers, then pull A through F in the footer.
2) The second part is just footnotes
3) However, the two areas would be out of sequence as the footer with A, B ... would be below the numbered. So you would have to then develop custom XSL to flip those areas.
And last, since you cannot dynamically size a footer area, it is unclear that even that would work out acceptably well especially it is such that the A, B type footnotes could be one line or six lines. You would only be able to do it if a fixed space was known to work.
answered Nov 16 at 20:55
Kevin Brown
6,82721128
Indeed, I gave up on using built-infootnotes(and I suspect this is a reason my colleagues frequently transform to TeX or LaTeX.) I decided to create a solution much like in an XSL output to HTML, by manually building two blocks of separate content at the end of my flow which I can control directly. It's overly complex but it functions. Unfortunately, the resulting hack is restricted to deployment at the end of a given 'section', not at the bottom of each page.
– jbrehr
Nov 17 at 9:31
Incidentally, it strikes me as a modest change that XEP could implement (along the lines of using attributes likexsl:numberuses and some sort of display mode attribute like inline vs newline). For other things like margin notes, etc. XEP handles it all really well for me.
– jbrehr
Nov 17 at 9:34
add a comment |
up vote
1
down vote
accepted
I do not believe that the structure you show is possible at all, or at least with custom code to manipulate the resulting area tree (intermediate format also called XEPOUT).
1) The first set of "footnotes" you show as inline. I would assume these could run one, two maybe three lines. That alone I could not see how to build properly, without maybe some hack. Such a structure could be possibly accomplished by surrounding each footnote with a marker with fo:inline's and pull those to the footer. In other words, not make them footnotes.
Since they are separate in the document you would need something like make marker A, make marker B, as they occur on the page ... and a footer that would pull the universe of all markers but only on that page (first starting on page without carryover). Now if those markers did not exist, it would pull nothing. So that could be possible to do if you knew for instance that you would never have more than F markers, then pull A through F in the footer.
2) The second part is just footnotes
3) However, the two areas would be out of sequence as the footer with A, B ... would be below the numbered. So you would have to then develop custom XSL to flip those areas.
And last, since you cannot dynamically size a footer area, it is unclear that even that would work out acceptably well especially it is such that the A, B type footnotes could be one line or six lines. You would only be able to do it if a fixed space was known to work.
answered Nov 16 at 20:55
Kevin Brown
6,82721128
Indeed, I gave up on using built-infootnotes(and I suspect this is a reason my colleagues frequently transform to TeX or LaTeX.) I decided to create a solution much like in an XSL output to HTML, by manually building two blocks of separate content at the end of my flow which I can control directly. It's overly complex but it functions. Unfortunately, the resulting hack is restricted to deployment at the end of a given 'section', not at the bottom of each page.
– jbrehr
Nov 17 at 9:31
Incidentally, it strikes me as a modest change that XEP could implement (along the lines of using attributes likexsl:numberuses and some sort of display mode attribute like inline vs newline). For other things like margin notes, etc. XEP handles it all really well for me.
– jbrehr
Nov 17 at 9:34
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I do not believe that the structure you show is possible at all, or at least with custom code to manipulate the resulting area tree (intermediate format also called XEPOUT).
1) The first set of "footnotes" you show as inline. I would assume these could run one, two maybe three lines. That alone I could not see how to build properly, without maybe some hack. Such a structure could be possibly accomplished by surrounding each footnote with a marker with fo:inline's and pull those to the footer. In other words, not make them footnotes.
Since they are separate in the document you would need something like make marker A, make marker B, as they occur on the page ... and a footer that would pull the universe of all markers but only on that page (first starting on page without carryover). Now if those markers did not exist, it would pull nothing. So that could be possible to do if you knew for instance that you would never have more than F markers, then pull A through F in the footer.
2) The second part is just footnotes
3) However, the two areas would be out of sequence as the footer with A, B ... would be below the numbered. So you would have to then develop custom XSL to flip those areas.
And last, since you cannot dynamically size a footer area, it is unclear that even that would work out acceptably well especially it is such that the A, B type footnotes could be one line or six lines. You would only be able to do it if a fixed space was known to work.
answered Nov 16 at 20:55
Kevin Brown
6,82721128
I do not believe that the structure you show is possible at all, or at least with custom code to manipulate the resulting area tree (intermediate format also called XEPOUT).
1) The first set of "footnotes" you show as inline. I would assume these could run one, two maybe three lines. That alone I could not see how to build properly, without maybe some hack. Such a structure could be possibly accomplished by surrounding each footnote with a marker with fo:inline's and pull those to the footer. In other words, not make them footnotes.
Since they are separate in the document you would need something like make marker A, make marker B, as they occur on the page ... and a footer that would pull the universe of all markers but only on that page (first starting on page without carryover). Now if those markers did not exist, it would pull nothing. So that could be possible to do if you knew for instance that you would never have more than F markers, then pull A through F in the footer.
2) The second part is just footnotes
3) However, the two areas would be out of sequence as the footer with A, B ... would be below the numbered. So you would have to then develop custom XSL to flip those areas.
And last, since you cannot dynamically size a footer area, it is unclear that even that would work out acceptably well especially it is such that the A, B type footnotes could be one line or six lines. You would only be able to do it if a fixed space was known to work.
answered Nov 16 at 20:55
Kevin Brown
6,82721128
edited Nov 16 at 21:01
answered Nov 16 at 20:55
Kevin Brown
6,82721128
answered Nov 16 at 20:55
Kevin Brown
6,82721128
answered Nov 16 at 20:55
Kevin Brown
6,82721128
6,82721128
Indeed, I gave up on using built-infootnotes(and I suspect this is a reason my colleagues frequently transform to TeX or LaTeX.) I decided to create a solution much like in an XSL output to HTML, by manually building two blocks of separate content at the end of my flow which I can control directly. It's overly complex but it functions. Unfortunately, the resulting hack is restricted to deployment at the end of a given 'section', not at the bottom of each page.
– jbrehr
Nov 17 at 9:31
Incidentally, it strikes me as a modest change that XEP could implement (along the lines of using attributes likexsl:numberuses and some sort of display mode attribute like inline vs newline). For other things like margin notes, etc. XEP handles it all really well for me.
– jbrehr
Nov 17 at 9:34
add a comment |
Indeed, I gave up on using built-infootnotes(and I suspect this is a reason my colleagues frequently transform to TeX or LaTeX.) I decided to create a solution much like in an XSL output to HTML, by manually building two blocks of separate content at the end of my flow which I can control directly. It's overly complex but it functions. Unfortunately, the resulting hack is restricted to deployment at the end of a given 'section', not at the bottom of each page.
– jbrehr
Nov 17 at 9:31
Incidentally, it strikes me as a modest change that XEP could implement (along the lines of using attributes likexsl:numberuses and some sort of display mode attribute like inline vs newline). For other things like margin notes, etc. XEP handles it all really well for me.
– jbrehr
Nov 17 at 9:34
Indeed, I gave up on using built-in
footnotes (and I suspect this is a reason my colleagues frequently transform to TeX or LaTeX.) I decided to create a solution much like in an XSL output to HTML, by manually building two blocks of separate content at the end of my flow which I can control directly. It's overly complex but it functions. Unfortunately, the resulting hack is restricted to deployment at the end of a given 'section', not at the bottom of each page.– jbrehr
Nov 17 at 9:31
Indeed, I gave up on using built-in
footnotes (and I suspect this is a reason my colleagues frequently transform to TeX or LaTeX.) I decided to create a solution much like in an XSL output to HTML, by manually building two blocks of separate content at the end of my flow which I can control directly. It's overly complex but it functions. Unfortunately, the resulting hack is restricted to deployment at the end of a given 'section', not at the bottom of each page.– jbrehr
Nov 17 at 9:31
Incidentally, it strikes me as a modest change that XEP could implement (along the lines of using attributes like
xsl:number uses and some sort of display mode attribute like inline vs newline). For other things like margin notes, etc. XEP handles it all really well for me.– jbrehr
Nov 17 at 9:34
Incidentally, it strikes me as a modest change that XEP could implement (along the lines of using attributes like
xsl:number uses and some sort of display mode attribute like inline vs newline). For other things like margin notes, etc. XEP handles it all really well for me.– jbrehr
Nov 17 at 9:34
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53249781%2fxsl-fo-two-separate-footnote-blocks-xep%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Would it be too nonacademic to float the small notes to the side of the page as sidenotes and then use regular
fo:footnotefor the block footnotes?– Tony Graham
Nov 20 at 13:21
Yes, because there is a definite line between the 'text' and its possible marginal annotations (in particular when editing medieval manuscripts) and the critical apparatus. Any marginalia would be considered part of the original text.
– jbrehr
Nov 20 at 13:53