You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- This looks interesting. Does it work with \nocite{*} or does it depend on explicit citation of each item in the bibliography? Can it be generalised to multiple criteria/keywords (eg type=report AND keyword=MyProject AND notkeyword=ProgressReport)? Thanks.user8786– user87862012-08-12 21:06:26 +00:00Commented Aug 12, 2012 at 21:06
- oh, it's a better way ! no problem of time for running. It's working with nocite. And you can make a lot of test : for exemple :\ifkeyword{toto}{\ifkeyword{titi}{}{\stepcounter{toto}}}{}. You should read the manual of biblatex : theres is a lot of test.Maïeul– Maïeul2012-08-12 21:30:54 +00:00Commented Aug 12, 2012 at 21:30
- but the manual say Note that, if there are any refsection environments in the document and an entry is cited in more than one of them, the ⟨code⟩ may be executed multiple times for an entry. I don't know in your case. But why not.Maïeul– Maïeul2012-08-12 21:35:20 +00:00Commented Aug 12, 2012 at 21:35
- @Audrey yes, that is why it could be a problem, in some context. But I think you suggestion is better than mine, for time processing.Maïeul– Maïeul2012-08-12 22:18:40 +00:00Commented Aug 12, 2012 at 22:18
- This works well, and is fast. However I prefer Maieul's method since it uses the same selection criteria as \printbibligraphy. This allows me to set say \myprojectreports to "keyword=myproject,type=report" once and refer to it when counting and when generating the bibliography. Some of my selection criteria are quite complicated, so keeping a single copy is much easier. Thanks though - I'm sure this will come in useful someday.user8786– user87862012-08-13 12:11:10 +00:00Commented Aug 13, 2012 at 12:11
| Show 2 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. tikz-pgf), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-tex