Closed dwp-forge closed 9 years ago
I'm not sure what you mean by "overrides." For each note you are supposed to have a
single entry in the notes block regardless of the number of references to that note.
The page range specified with "page" or "pages" field is rendered as part of the reference
(if you choose Harvard style for references).
Can you attach a snapshot that shows the problem?
Original issue reported on code.google.com by dwp-forge
on 2013-07-19 11:45:31
Firstly thanks for your quick reply ;)
im a fraid a snapshot wouldn't help much, maybe i try to describe the problem more
precicely:
my goal is something like this:
article-section:
source:
texttext[(:lit:horn3>>page:10)] texttext[(:lit:horn3>>pages:11-15)]
rendered as
texttext[1] texttext [2]
source-section:
[1] Horn, 2005, a Booktitle p. 10
[2] Horn, 2005, a Booktitle pp. 11-15
yet what im getting with the above is as follows:
article-section renders as:
texttext[1] texttext [2]
the tooltip-text for both [1] & [2] is "Horn, 2005, a Booktitle pp. 11-15"
source-section:
[2] Horn, 2005, a Booktitle, pp. 11-15
(only the last specified "page" will appear in the notes section. thats what i meant
with "the last notes will override all previous notes" )
I hope this helps to see my problem.
Thanx again for your help.
Original issue reported on code.google.com by dennis.kueppers
on 2013-07-19 12:27:10
i missed some thing:
source-section atm will render as::
[1] a,b Horn, 2005, a Booktitle, pp. 11-15
Original issue reported on code.google.com by dennis.kueppers
on 2013-07-19 12:36:51
Getting warmer. Are you sure it's rendered as
texttext[1] texttext [2]
I so far managed to reproduce only
texttext[1] texttext [1]
Original issue reported on code.google.com by dwp-forge
on 2013-07-19 20:15:36
Okay, I finally got the combination of styles that results in situation that you observe.
Bad news -- it works as expected.
Your problem is that you are trying to get two notes using single note id (:lit:horn3).
This is not going to work. With current design each note is rendered only once.
As a workaround you could create separate notes for each reference (e.g. :lit:horn3-10,
:lit:horn3-11-15), but that will result in lots of copy-pasting and generally doesn't
look too good.
Alternatively, you could switch to Harvard-style references. Actually, the ">> page:10"
syntax was designed with this use case in mind. There you will have something like:
texttext(Horn, 2005, p.10) texttext (Horn, 2005, pp.11-15)
And in the note block:
1. a,b Horn, 2005, a Booktitle
Original issue reported on code.google.com by dwp-forge
on 2013-07-20 16:13:36
Ok, i was kinda expecting something like this.
Unfortunately i am already using harvard style.
Another workaround i had in mind:
Would it work to use the 'direct' note rendering mode in the text
such as ... text text (Horn 2005 page 10) text text (Horn 2005 page 11-15)
and to have it show up in the notes section without any specific page at all?
rather: is there a way to 'style' the way harvard style is rendered?
thanx for your time!
Original issue reported on code.google.com by dennis.kueppers
on 2013-07-20 17:51:40
Why unfortunately? Doesn't it work, or you just don't like the formatting?
If by 'direct' you mean 'inline,' then no. Inline notes are not rendered in the notes
block.
Styling of Harvard references and notes is rather limited. It depends on what you want
to achieve. You can still play with formatting options but the contents (the text)
of both references and notes is hard-coded. I thought of having a way to create custom
patterns to generate the contents from individual fields, but it gets way to complicated
and I don't think that many people would find it useful.
Original issue reported on code.google.com by dwp-forge
on 2013-07-20 18:22:14
Yea im afraid this problem is very specific to what i want to do.
i will try to find a proper solution to get it working for me.
again thank you for your help :) if i end up with some groundbreaking solutions i'll
gladly share it on here ;)
Greetings from Germany ;)
Original issue reported on code.google.com by dennis.kueppers
on 2013-07-21 10:16:28
Original issue reported on code.google.com by
dennis.kueppers
on 2013-07-18 13:53:43