Nocite like command in biblatex? Unicorn Meta Zoo #1: Why another podcast? ...

How can I make a line end at the edge of an irregular shape?

Protagonist's race is hidden - should I reveal it?

How to keep bees out of canned beverages?

What is it called when you ride around on your front wheel?

Where did Arya get these scars?

c++ diamond problem - How to call base method only once

Is it OK if I do not take the receipt in Germany?

How can I wire a 9-position switch so that each position turns on one more LED than the one before?

Justification for leaving new position after a short time

Co-worker works way more than he should

Check if a string is entirely made of the same substring

Is Electric Central Heating worth it if using Solar Panels?

A Paper Record is What I Hamper

Seek and ye shall find

What is the ongoing value of the Kanban board to the developers as opposed to management

Do I need to protect SFP ports and optics from dust/contaminants? If so, how?

What's parked in Mil Moscow helicopter plant?

What was Apollo 13's "Little Jolt" after MECO?

What's the difference between using dependency injection with a container and using a service locator?

Raising a bilingual kid. When should we introduce the majority language?

Can I criticise the more senior developers around me for not writing clean code?

My bank got bought out, am I now going to have to start filing tax returns in a different state?

A strange hotel

Would reducing the reference voltage of an ADC have any effect on accuracy?



Nocite like command in biblatex?



Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraSoftware-generated bibliographic entries: common errors and other mistakes to check before useInput encoding error after upgrading from Biber 1.9 to Biber 2.1Unicode -(U+301) error in biblatex, but not in main text: {'{i}}Biblatex and custom bibtex entries - is it possible?Adapting an existing biblatex style in order to imitate Springer's author-year reference list rules for authorsbiblatex messing up citation entry with lots of authorsBibliography in LaTeX with Biblatex and Biber as backendAbbreviate only middle names in biblatexCiting (author, journalabbr., year) neededOne cite crash allBiblatex: Change date/year output for one literature-type onlyOverload Biblatex thesis style and defineModifying bibliography with biblatex/biber (apa-style) location+publisher+doi












0















I'm trying to have all my references printed on the PDF, the thing is that I only cite 1 of all the entries in the .bib file. And looking at the documentation on biblatex it says I have to use the following command:



defbibentryset{hkeyi}{hkey1,key2,key3, …i}


But I do not understand the principal <key>, because from what I get all the rest hkey1, and so on, are the entries of the .bib file. Right?



I'm so used to using the nocite{*} command in the traditional bibliography style and now I'm trying to move to biblatex. Is there any other possibility? Like it seems quite troublesome to dead with this package, do you think is worthy?



My preamble looks like this:



documentclass{article}
usepackage{comment}


usepackage[]{biblatex}
addbibresource{Ex.bib}

begin{document}
Some text


printbibliography
defbibentryset{*}{*}

end{document}


And the .bib file is the following



@book{Brezis,
title={Functional analysis, Sobolev spaces and partial differential
equations},
author={Brezis, Haim},
year={2010},
publisher={Springer Science & Business Media}
}


@inbook{sob1,
publisher = {Wiley-Blackwell},
author={Wiley-Blackwell},
isbn = {9781118032725},
title = {Sobolev Spaces of Functions of One Variable},
booktitle = {Applied Functional Analysis},
chapter = {7},
pages = {145-166},
doi = {10.1002/9781118032725.ch7},
url =
{https://onlinelibrary.wiley.com/doi/abs/10.1002/9781118032725.ch7},
eprint =
{https://onlinelibrary.wiley.com/doi/pdf/10.1002/9781118032725.ch7},
year = {2011},
keywords = {Sobolev spaces, functions, distributions, trace theorems,
Hilbert space}
}

@book{Kub,
title={Essentials of measure theory},
author={Kubrusly, Carlos S},
year={2015},
publisher={Springer}
}

@book{grabinsky,
title={Teor{'i}a de la medida/por Guillermo Grabinsky.},
author={Grabinsky, Guillermo},
publisher={La prensas ciencias, UNAM},
year={2011}
}









share|improve this question




















  • 3





    You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful. biblatex knows nocite and so nocite{*} should do more or less the same thing as in BibTeX. Did you try it? What did not work as expected?

    – moewe
    1 hour ago











  • Yep I've tried before having the nocite{*} before and after printbibliography and it says that the command is undefined.

    – Lilian Hernández
    36 mins ago













  • What exactly is supposed to be undefined? And who says that? If you get an error message from TeX can you post it here in full, please? nocite{*} definitely is not undefined. But there is a potential issue in the entry grabinsky: biblatex/Biber does not like {'i}, you should try {'i} or even better í instead. See also tex.stackexchange.com/q/251261/35864

    – moewe
    32 mins ago











  • It says : Package inputenc: Unicode char' (U+301). Although it does the job, prints all the bibliography.

    – Lilian Hernández
    30 mins ago











  • Note also that author={Wiley-Blackwell}, in looks sob1 odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1. The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.

    – moewe
    30 mins ago
















0















I'm trying to have all my references printed on the PDF, the thing is that I only cite 1 of all the entries in the .bib file. And looking at the documentation on biblatex it says I have to use the following command:



defbibentryset{hkeyi}{hkey1,key2,key3, …i}


But I do not understand the principal <key>, because from what I get all the rest hkey1, and so on, are the entries of the .bib file. Right?



I'm so used to using the nocite{*} command in the traditional bibliography style and now I'm trying to move to biblatex. Is there any other possibility? Like it seems quite troublesome to dead with this package, do you think is worthy?



My preamble looks like this:



documentclass{article}
usepackage{comment}


usepackage[]{biblatex}
addbibresource{Ex.bib}

begin{document}
Some text


printbibliography
defbibentryset{*}{*}

end{document}


And the .bib file is the following



@book{Brezis,
title={Functional analysis, Sobolev spaces and partial differential
equations},
author={Brezis, Haim},
year={2010},
publisher={Springer Science & Business Media}
}


@inbook{sob1,
publisher = {Wiley-Blackwell},
author={Wiley-Blackwell},
isbn = {9781118032725},
title = {Sobolev Spaces of Functions of One Variable},
booktitle = {Applied Functional Analysis},
chapter = {7},
pages = {145-166},
doi = {10.1002/9781118032725.ch7},
url =
{https://onlinelibrary.wiley.com/doi/abs/10.1002/9781118032725.ch7},
eprint =
{https://onlinelibrary.wiley.com/doi/pdf/10.1002/9781118032725.ch7},
year = {2011},
keywords = {Sobolev spaces, functions, distributions, trace theorems,
Hilbert space}
}

@book{Kub,
title={Essentials of measure theory},
author={Kubrusly, Carlos S},
year={2015},
publisher={Springer}
}

@book{grabinsky,
title={Teor{'i}a de la medida/por Guillermo Grabinsky.},
author={Grabinsky, Guillermo},
publisher={La prensas ciencias, UNAM},
year={2011}
}









share|improve this question




















  • 3





    You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful. biblatex knows nocite and so nocite{*} should do more or less the same thing as in BibTeX. Did you try it? What did not work as expected?

    – moewe
    1 hour ago











  • Yep I've tried before having the nocite{*} before and after printbibliography and it says that the command is undefined.

    – Lilian Hernández
    36 mins ago













  • What exactly is supposed to be undefined? And who says that? If you get an error message from TeX can you post it here in full, please? nocite{*} definitely is not undefined. But there is a potential issue in the entry grabinsky: biblatex/Biber does not like {'i}, you should try {'i} or even better í instead. See also tex.stackexchange.com/q/251261/35864

    – moewe
    32 mins ago











  • It says : Package inputenc: Unicode char' (U+301). Although it does the job, prints all the bibliography.

    – Lilian Hernández
    30 mins ago











  • Note also that author={Wiley-Blackwell}, in looks sob1 odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1. The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.

    – moewe
    30 mins ago














0












0








0








I'm trying to have all my references printed on the PDF, the thing is that I only cite 1 of all the entries in the .bib file. And looking at the documentation on biblatex it says I have to use the following command:



defbibentryset{hkeyi}{hkey1,key2,key3, …i}


But I do not understand the principal <key>, because from what I get all the rest hkey1, and so on, are the entries of the .bib file. Right?



I'm so used to using the nocite{*} command in the traditional bibliography style and now I'm trying to move to biblatex. Is there any other possibility? Like it seems quite troublesome to dead with this package, do you think is worthy?



My preamble looks like this:



documentclass{article}
usepackage{comment}


usepackage[]{biblatex}
addbibresource{Ex.bib}

begin{document}
Some text


printbibliography
defbibentryset{*}{*}

end{document}


And the .bib file is the following



@book{Brezis,
title={Functional analysis, Sobolev spaces and partial differential
equations},
author={Brezis, Haim},
year={2010},
publisher={Springer Science & Business Media}
}


@inbook{sob1,
publisher = {Wiley-Blackwell},
author={Wiley-Blackwell},
isbn = {9781118032725},
title = {Sobolev Spaces of Functions of One Variable},
booktitle = {Applied Functional Analysis},
chapter = {7},
pages = {145-166},
doi = {10.1002/9781118032725.ch7},
url =
{https://onlinelibrary.wiley.com/doi/abs/10.1002/9781118032725.ch7},
eprint =
{https://onlinelibrary.wiley.com/doi/pdf/10.1002/9781118032725.ch7},
year = {2011},
keywords = {Sobolev spaces, functions, distributions, trace theorems,
Hilbert space}
}

@book{Kub,
title={Essentials of measure theory},
author={Kubrusly, Carlos S},
year={2015},
publisher={Springer}
}

@book{grabinsky,
title={Teor{'i}a de la medida/por Guillermo Grabinsky.},
author={Grabinsky, Guillermo},
publisher={La prensas ciencias, UNAM},
year={2011}
}









share|improve this question
















I'm trying to have all my references printed on the PDF, the thing is that I only cite 1 of all the entries in the .bib file. And looking at the documentation on biblatex it says I have to use the following command:



defbibentryset{hkeyi}{hkey1,key2,key3, …i}


But I do not understand the principal <key>, because from what I get all the rest hkey1, and so on, are the entries of the .bib file. Right?



I'm so used to using the nocite{*} command in the traditional bibliography style and now I'm trying to move to biblatex. Is there any other possibility? Like it seems quite troublesome to dead with this package, do you think is worthy?



My preamble looks like this:



documentclass{article}
usepackage{comment}


usepackage[]{biblatex}
addbibresource{Ex.bib}

begin{document}
Some text


printbibliography
defbibentryset{*}{*}

end{document}


And the .bib file is the following



@book{Brezis,
title={Functional analysis, Sobolev spaces and partial differential
equations},
author={Brezis, Haim},
year={2010},
publisher={Springer Science & Business Media}
}


@inbook{sob1,
publisher = {Wiley-Blackwell},
author={Wiley-Blackwell},
isbn = {9781118032725},
title = {Sobolev Spaces of Functions of One Variable},
booktitle = {Applied Functional Analysis},
chapter = {7},
pages = {145-166},
doi = {10.1002/9781118032725.ch7},
url =
{https://onlinelibrary.wiley.com/doi/abs/10.1002/9781118032725.ch7},
eprint =
{https://onlinelibrary.wiley.com/doi/pdf/10.1002/9781118032725.ch7},
year = {2011},
keywords = {Sobolev spaces, functions, distributions, trace theorems,
Hilbert space}
}

@book{Kub,
title={Essentials of measure theory},
author={Kubrusly, Carlos S},
year={2015},
publisher={Springer}
}

@book{grabinsky,
title={Teor{'i}a de la medida/por Guillermo Grabinsky.},
author={Grabinsky, Guillermo},
publisher={La prensas ciencias, UNAM},
year={2011}
}






biblatex






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 11 mins ago









moewe

97.4k10118364




97.4k10118364










asked 1 hour ago









Lilian Hernández Lilian Hernández

133




133








  • 3





    You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful. biblatex knows nocite and so nocite{*} should do more or less the same thing as in BibTeX. Did you try it? What did not work as expected?

    – moewe
    1 hour ago











  • Yep I've tried before having the nocite{*} before and after printbibliography and it says that the command is undefined.

    – Lilian Hernández
    36 mins ago













  • What exactly is supposed to be undefined? And who says that? If you get an error message from TeX can you post it here in full, please? nocite{*} definitely is not undefined. But there is a potential issue in the entry grabinsky: biblatex/Biber does not like {'i}, you should try {'i} or even better í instead. See also tex.stackexchange.com/q/251261/35864

    – moewe
    32 mins ago











  • It says : Package inputenc: Unicode char' (U+301). Although it does the job, prints all the bibliography.

    – Lilian Hernández
    30 mins ago











  • Note also that author={Wiley-Blackwell}, in looks sob1 odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1. The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.

    – moewe
    30 mins ago














  • 3





    You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful. biblatex knows nocite and so nocite{*} should do more or less the same thing as in BibTeX. Did you try it? What did not work as expected?

    – moewe
    1 hour ago











  • Yep I've tried before having the nocite{*} before and after printbibliography and it says that the command is undefined.

    – Lilian Hernández
    36 mins ago













  • What exactly is supposed to be undefined? And who says that? If you get an error message from TeX can you post it here in full, please? nocite{*} definitely is not undefined. But there is a potential issue in the entry grabinsky: biblatex/Biber does not like {'i}, you should try {'i} or even better í instead. See also tex.stackexchange.com/q/251261/35864

    – moewe
    32 mins ago











  • It says : Package inputenc: Unicode char' (U+301). Although it does the job, prints all the bibliography.

    – Lilian Hernández
    30 mins ago











  • Note also that author={Wiley-Blackwell}, in looks sob1 odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1. The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.

    – moewe
    30 mins ago








3




3





You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful. biblatex knows nocite and so nocite{*} should do more or less the same thing as in BibTeX. Did you try it? What did not work as expected?

– moewe
1 hour ago





You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful. biblatex knows nocite and so nocite{*} should do more or less the same thing as in BibTeX. Did you try it? What did not work as expected?

– moewe
1 hour ago













Yep I've tried before having the nocite{*} before and after printbibliography and it says that the command is undefined.

– Lilian Hernández
36 mins ago







Yep I've tried before having the nocite{*} before and after printbibliography and it says that the command is undefined.

– Lilian Hernández
36 mins ago















What exactly is supposed to be undefined? And who says that? If you get an error message from TeX can you post it here in full, please? nocite{*} definitely is not undefined. But there is a potential issue in the entry grabinsky: biblatex/Biber does not like {'i}, you should try {'i} or even better í instead. See also tex.stackexchange.com/q/251261/35864

– moewe
32 mins ago





What exactly is supposed to be undefined? And who says that? If you get an error message from TeX can you post it here in full, please? nocite{*} definitely is not undefined. But there is a potential issue in the entry grabinsky: biblatex/Biber does not like {'i}, you should try {'i} or even better í instead. See also tex.stackexchange.com/q/251261/35864

– moewe
32 mins ago













It says : Package inputenc: Unicode char' (U+301). Although it does the job, prints all the bibliography.

– Lilian Hernández
30 mins ago





It says : Package inputenc: Unicode char' (U+301). Although it does the job, prints all the bibliography.

– Lilian Hernández
30 mins ago













Note also that author={Wiley-Blackwell}, in looks sob1 odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1. The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.

– moewe
30 mins ago





Note also that author={Wiley-Blackwell}, in looks sob1 odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1. The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.

– moewe
30 mins ago










1 Answer
1






active

oldest

votes


















0














biblatex knows nocite and it works pretty much like its BibTeX counterpart. (The only difference that I'm aware of is that biblatex's nocite may also be used in the preamble. BibTeX normally wants it in the document body.)



You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful.





The real problem as confirmed in the comments here is the {'i} in grabinsky's Teor{'i}a. See for example Input encoding error after upgrading from Biber 1.9 to Biber 2.1, Unicode -(U+301) error in biblatex, but not in main text: {'{i}}. I suggest you use proper Unicode input and write



@book{grabinsky,
title = {Teoría de la medida},
author = {Grabinsky, Guillermo},
publisher = {La prensas ciencias, UNAM},
year = {2011},
}


In general Biber accepts all valid Unicode input. Whether you can get a reasonable output from that depends on your TeX engine. pdfLaTeX only supports a limited subset of Unicode and may throw errors in certain cases. The Unicode engines XeLaTeX and LuaLaTeX shouldn't have those problems, but their willingness to print characters as expected depends on the support for those characters by the used fonts.



Biber also understands many of the ASCII-macro replacements for Unicode characters (e.g. "a or o), but for reasons explained in the linked post 'i or rather all constructions with i are problematic. At the moment the i exceptions are the only problematic constructions I am aware of, but there might well be a few more.



Since you mention Springer-generated .bib entries I suggest you have a look at Software-generated bibliographic entries: common errors and other mistakes to check before use. Often those entries give subpar results.





Note also that author={Wiley-Blackwell}, in sob1 looks odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1.



The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.






share|improve this answer


























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "85"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f487485%2fnocite-like-command-in-biblatex%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    biblatex knows nocite and it works pretty much like its BibTeX counterpart. (The only difference that I'm aware of is that biblatex's nocite may also be used in the preamble. BibTeX normally wants it in the document body.)



    You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful.





    The real problem as confirmed in the comments here is the {'i} in grabinsky's Teor{'i}a. See for example Input encoding error after upgrading from Biber 1.9 to Biber 2.1, Unicode -(U+301) error in biblatex, but not in main text: {'{i}}. I suggest you use proper Unicode input and write



    @book{grabinsky,
    title = {Teoría de la medida},
    author = {Grabinsky, Guillermo},
    publisher = {La prensas ciencias, UNAM},
    year = {2011},
    }


    In general Biber accepts all valid Unicode input. Whether you can get a reasonable output from that depends on your TeX engine. pdfLaTeX only supports a limited subset of Unicode and may throw errors in certain cases. The Unicode engines XeLaTeX and LuaLaTeX shouldn't have those problems, but their willingness to print characters as expected depends on the support for those characters by the used fonts.



    Biber also understands many of the ASCII-macro replacements for Unicode characters (e.g. "a or o), but for reasons explained in the linked post 'i or rather all constructions with i are problematic. At the moment the i exceptions are the only problematic constructions I am aware of, but there might well be a few more.



    Since you mention Springer-generated .bib entries I suggest you have a look at Software-generated bibliographic entries: common errors and other mistakes to check before use. Often those entries give subpar results.





    Note also that author={Wiley-Blackwell}, in sob1 looks odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1.



    The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.






    share|improve this answer






























      0














      biblatex knows nocite and it works pretty much like its BibTeX counterpart. (The only difference that I'm aware of is that biblatex's nocite may also be used in the preamble. BibTeX normally wants it in the document body.)



      You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful.





      The real problem as confirmed in the comments here is the {'i} in grabinsky's Teor{'i}a. See for example Input encoding error after upgrading from Biber 1.9 to Biber 2.1, Unicode -(U+301) error in biblatex, but not in main text: {'{i}}. I suggest you use proper Unicode input and write



      @book{grabinsky,
      title = {Teoría de la medida},
      author = {Grabinsky, Guillermo},
      publisher = {La prensas ciencias, UNAM},
      year = {2011},
      }


      In general Biber accepts all valid Unicode input. Whether you can get a reasonable output from that depends on your TeX engine. pdfLaTeX only supports a limited subset of Unicode and may throw errors in certain cases. The Unicode engines XeLaTeX and LuaLaTeX shouldn't have those problems, but their willingness to print characters as expected depends on the support for those characters by the used fonts.



      Biber also understands many of the ASCII-macro replacements for Unicode characters (e.g. "a or o), but for reasons explained in the linked post 'i or rather all constructions with i are problematic. At the moment the i exceptions are the only problematic constructions I am aware of, but there might well be a few more.



      Since you mention Springer-generated .bib entries I suggest you have a look at Software-generated bibliographic entries: common errors and other mistakes to check before use. Often those entries give subpar results.





      Note also that author={Wiley-Blackwell}, in sob1 looks odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1.



      The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.






      share|improve this answer




























        0












        0








        0







        biblatex knows nocite and it works pretty much like its BibTeX counterpart. (The only difference that I'm aware of is that biblatex's nocite may also be used in the preamble. BibTeX normally wants it in the document body.)



        You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful.





        The real problem as confirmed in the comments here is the {'i} in grabinsky's Teor{'i}a. See for example Input encoding error after upgrading from Biber 1.9 to Biber 2.1, Unicode -(U+301) error in biblatex, but not in main text: {'{i}}. I suggest you use proper Unicode input and write



        @book{grabinsky,
        title = {Teoría de la medida},
        author = {Grabinsky, Guillermo},
        publisher = {La prensas ciencias, UNAM},
        year = {2011},
        }


        In general Biber accepts all valid Unicode input. Whether you can get a reasonable output from that depends on your TeX engine. pdfLaTeX only supports a limited subset of Unicode and may throw errors in certain cases. The Unicode engines XeLaTeX and LuaLaTeX shouldn't have those problems, but their willingness to print characters as expected depends on the support for those characters by the used fonts.



        Biber also understands many of the ASCII-macro replacements for Unicode characters (e.g. "a or o), but for reasons explained in the linked post 'i or rather all constructions with i are problematic. At the moment the i exceptions are the only problematic constructions I am aware of, but there might well be a few more.



        Since you mention Springer-generated .bib entries I suggest you have a look at Software-generated bibliographic entries: common errors and other mistakes to check before use. Often those entries give subpar results.





        Note also that author={Wiley-Blackwell}, in sob1 looks odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1.



        The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.






        share|improve this answer















        biblatex knows nocite and it works pretty much like its BibTeX counterpart. (The only difference that I'm aware of is that biblatex's nocite may also be used in the preamble. BibTeX normally wants it in the document body.)



        You shouldn't be needing defbibentryset if you don't want to define entry sets. In any case defbibentryset{*}{*} should not do anything useful.





        The real problem as confirmed in the comments here is the {'i} in grabinsky's Teor{'i}a. See for example Input encoding error after upgrading from Biber 1.9 to Biber 2.1, Unicode -(U+301) error in biblatex, but not in main text: {'{i}}. I suggest you use proper Unicode input and write



        @book{grabinsky,
        title = {Teoría de la medida},
        author = {Grabinsky, Guillermo},
        publisher = {La prensas ciencias, UNAM},
        year = {2011},
        }


        In general Biber accepts all valid Unicode input. Whether you can get a reasonable output from that depends on your TeX engine. pdfLaTeX only supports a limited subset of Unicode and may throw errors in certain cases. The Unicode engines XeLaTeX and LuaLaTeX shouldn't have those problems, but their willingness to print characters as expected depends on the support for those characters by the used fonts.



        Biber also understands many of the ASCII-macro replacements for Unicode characters (e.g. "a or o), but for reasons explained in the linked post 'i or rather all constructions with i are problematic. At the moment the i exceptions are the only problematic constructions I am aware of, but there might well be a few more.



        Since you mention Springer-generated .bib entries I suggest you have a look at Software-generated bibliographic entries: common errors and other mistakes to check before use. Often those entries give subpar results.





        Note also that author={Wiley-Blackwell}, in sob1 looks odd. There is also little point in giving a full URL in the eprint field. Especially if it is the same URL as the one from the url field. I suggest you drop the eprint field in sob1.



        The author in Kub should probably be author={Kubrusly, Carlos S.}, with a . after the S.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 15 mins ago

























        answered 24 mins ago









        moewemoewe

        97.4k10118364




        97.4k10118364






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


            • 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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f487485%2fnocite-like-command-in-biblatex%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            Can't compile dgruyter and caption packagesLaTeX templates/packages for writing a patent specificationLatex...

            Schneeberg (Smreczany) Bibliografia | Menu...

            Hans Bellmer Spis treści Życiorys | Upamiętnienie | Przypisy | Bibliografia | Linki zewnętrzne |...