-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
~[Feature Request] Literature sorting improvement~ Literature in v54.01 DFG template #31
Comments
Neat, I also agree that's a good feature to have to clearly distinguish between own and other literature in the text. I'll also check the PR. |
hey @gituser789 -- unfortunately the DFG changed the literature section in the newest v54 template -.- Now there is only Section 3 left, see the descriptions here
For now, to fulfill the request here: #28, I will remove the complicated "own" literature section 1.2 and keep section 3 bc/ this is the new DFG template. Then all literature is listed here. Then, it should be relatively easy to implement a way to make up to 10 selected citations bold. However, another way would be also to use your nice implementation adding a prefix "O" ("Own") or "E" ("Eigene", in the german version). But then we would need smt like the following I guess
What do you think? I will merge a PR w/ the updates for the DFG template v54.01 in the next minutes so this code base can be used as an basis. |
Summary
Is there a way to include literature sorting with different labels directly into the template?
e.g. own literature labeled as [E1], [E2], ...
others literature labeld as [1], [2], ...
Describing the Problem
There are mainly two different literature sections
The general order is
The result is a unsorted mixture of literature in the text. Lets assume [1]-[10] are own literature, and [11-30] others.
In Chapter 1 in the text, there is a mixture of the literature, e.g.
Possible Solution
is there a way to label own literature with additonal sign directly into the template?
The text was updated successfully, but these errors were encountered: