Italic text in corporate authorpackage acro does not work with biblatex anymoreProblem with latest BibLaTeX...

How is this property called for mod?

A fantasy book with seven white haired women on the cover

Broad Strokes - missing letter riddle

Potential client has a problematic employee I can't work with

What is the wife of a henpecked husband called?

Is there a way to not have to poll the UART of an AVR?

Does an Eldritch Knight's Weapon Bond protect him from losing his weapon to a Telekinesis spell?

A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?

Website seeing my Facebook data?

What makes papers publishable in top-tier journals?

Does the ditching switch allow an A320 to float indefinitely?

Coworker asking me to not bring cakes due to self control issue. What should I do?

Are History of Worldbuilding questions on topic?

What is a good reason for every spaceship to carry a weapon on board?

I have trouble understanding this fallacy: "If A, then B. Therefore if not-B, then not-A."

2019 Stack Overflow Moderator Election Q&A - Question Collection

The No-Straight Maze

Possible issue with my W4 and tax return

Can a player sacrifice a creature after declaring that creature as blocker while taking lethal damage?

Cat is tipping over bed-side lamps during the night

What's the oldest plausible frozen specimen for a Jurassic Park style story-line?

Time-efficient matrix elements grouping and summing

Can you determine if focus is sharp without diopter adjustment if your sight is imperfect?

Will rerolling initiative each round stop meta-gaming about initiative?



Italic text in corporate author


package acro does not work with biblatex anymoreProblem with latest BibLaTeX release?Error using command in .bib file since update (“Extra }”)Biblatex 3.11: author = {{textsc{…}}, breaks compilationBibTeX: Abbreviate first name (aka given name) to 2 or 3 letters (not 1)! Paragraph ended before name was completeTwo or three letter initials in bibliography with Biblatex (again)How to identify Illustrator in bibtex?Two or three letter initials in bibliography with Biblatexbiblatex: textcite author formatting vs. bibliography author formattingNon-italic emph, italic biblatex titlesHow the author name could be made italic in citation using biblatex?Biblatex multiple author in-text initials missingBiblatex: omit authorcitations (author /year)“Author (in prep.)” instead of “Author (year)”Biblatex: Citing “full author” after short author was citedOlder biblatex version automatically used after MikTeX package upgradeBiblatex journal name non-italic













6















How to use italic text within a corporate author in biblatex v3.11?



The following MWE with italic text within a corporate author used to work with biblatex 3.10 from texlive2017:



documentclass{book}

usepackage{filecontents}
begin{filecontents*}{jobname.bib}
@online{cicerone,
author = {{textit{italic text} normal text}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}
end{filecontents*}

usepackage{biblatex}
addbibresource{jobname.bib}

begin{document}

cite{cicerone}
printbibliography

end{document}


With the following package versions:



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2017/12/19 v3.10 programmable bibliographies (PK/JW/AB)
pdftexcmds.sty 2018/01/21 v0.26 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def
biblatex-dm.cfg
blx-compat.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
biblatex.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
standard.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.cbx 2017/12/19 v3.10 biblatex citation style (PK/JW/AB)
biblatex.cfg
english.lbx 2017/12/19 v3.10 biblatex localization (PK/JW/AB)


With biblatex v3.11 from texlive2018(pretest) and the following packages



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2018/03/04 v3.11 programmable bibliographies (PK/MW)
pdftexcmds.sty 2018/01/30 v0.27 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def 2018/03/04 v3.11 biblatex localization (PK/MW)
blx-compat.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
biblatex.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
standard.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.cbx 2018/03/04 v3.11 biblatex citation style (PK/MW)
biblatex.cfg
english.lbx 2018/03/04 v3.11 biblatex localization (PK/MW)


It fails with the following error message



! Extra }, or forgotten endgroup.
l.27 }

?









share|improve this question























  • Wait for biblatex 3.12: github.com/plk/biber/issues/216 (see also github.com/plk/biber/issues/215, github.com/plk/biblatex/issues/727). This was due to the changes introduced in github.com/plk/biber/issues/210. Duplicate question tex.stackexchange.com/q/420043/35864

    – moewe
    Apr 11 '18 at 11:06













  • @moewe Thanks, that is indeed the same problem. Would you like to write a short answer (to the other question) which says that this will be fixed in 3.12? Otherwise I cannot close this one as dupe

    – samcarter
    Apr 11 '18 at 11:08













  • Oh sorry. I got confused an wrote an answer to this one and closed the other. Hope you don't mind. The outcome should be roughly the same...

    – moewe
    Apr 11 '18 at 11:16













  • @moewe I don't mind at all. Thank you very much! (Have to wait another 3 minutes before I am allowed to accept...)

    – samcarter
    Apr 11 '18 at 11:16


















6















How to use italic text within a corporate author in biblatex v3.11?



The following MWE with italic text within a corporate author used to work with biblatex 3.10 from texlive2017:



documentclass{book}

usepackage{filecontents}
begin{filecontents*}{jobname.bib}
@online{cicerone,
author = {{textit{italic text} normal text}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}
end{filecontents*}

usepackage{biblatex}
addbibresource{jobname.bib}

begin{document}

cite{cicerone}
printbibliography

end{document}


With the following package versions:



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2017/12/19 v3.10 programmable bibliographies (PK/JW/AB)
pdftexcmds.sty 2018/01/21 v0.26 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def
biblatex-dm.cfg
blx-compat.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
biblatex.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
standard.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.cbx 2017/12/19 v3.10 biblatex citation style (PK/JW/AB)
biblatex.cfg
english.lbx 2017/12/19 v3.10 biblatex localization (PK/JW/AB)


With biblatex v3.11 from texlive2018(pretest) and the following packages



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2018/03/04 v3.11 programmable bibliographies (PK/MW)
pdftexcmds.sty 2018/01/30 v0.27 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def 2018/03/04 v3.11 biblatex localization (PK/MW)
blx-compat.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
biblatex.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
standard.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.cbx 2018/03/04 v3.11 biblatex citation style (PK/MW)
biblatex.cfg
english.lbx 2018/03/04 v3.11 biblatex localization (PK/MW)


It fails with the following error message



! Extra }, or forgotten endgroup.
l.27 }

?









share|improve this question























  • Wait for biblatex 3.12: github.com/plk/biber/issues/216 (see also github.com/plk/biber/issues/215, github.com/plk/biblatex/issues/727). This was due to the changes introduced in github.com/plk/biber/issues/210. Duplicate question tex.stackexchange.com/q/420043/35864

    – moewe
    Apr 11 '18 at 11:06













  • @moewe Thanks, that is indeed the same problem. Would you like to write a short answer (to the other question) which says that this will be fixed in 3.12? Otherwise I cannot close this one as dupe

    – samcarter
    Apr 11 '18 at 11:08













  • Oh sorry. I got confused an wrote an answer to this one and closed the other. Hope you don't mind. The outcome should be roughly the same...

    – moewe
    Apr 11 '18 at 11:16













  • @moewe I don't mind at all. Thank you very much! (Have to wait another 3 minutes before I am allowed to accept...)

    – samcarter
    Apr 11 '18 at 11:16
















6












6








6








How to use italic text within a corporate author in biblatex v3.11?



The following MWE with italic text within a corporate author used to work with biblatex 3.10 from texlive2017:



documentclass{book}

usepackage{filecontents}
begin{filecontents*}{jobname.bib}
@online{cicerone,
author = {{textit{italic text} normal text}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}
end{filecontents*}

usepackage{biblatex}
addbibresource{jobname.bib}

begin{document}

cite{cicerone}
printbibliography

end{document}


With the following package versions:



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2017/12/19 v3.10 programmable bibliographies (PK/JW/AB)
pdftexcmds.sty 2018/01/21 v0.26 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def
biblatex-dm.cfg
blx-compat.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
biblatex.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
standard.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.cbx 2017/12/19 v3.10 biblatex citation style (PK/JW/AB)
biblatex.cfg
english.lbx 2017/12/19 v3.10 biblatex localization (PK/JW/AB)


With biblatex v3.11 from texlive2018(pretest) and the following packages



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2018/03/04 v3.11 programmable bibliographies (PK/MW)
pdftexcmds.sty 2018/01/30 v0.27 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def 2018/03/04 v3.11 biblatex localization (PK/MW)
blx-compat.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
biblatex.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
standard.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.cbx 2018/03/04 v3.11 biblatex citation style (PK/MW)
biblatex.cfg
english.lbx 2018/03/04 v3.11 biblatex localization (PK/MW)


It fails with the following error message



! Extra }, or forgotten endgroup.
l.27 }

?









share|improve this question














How to use italic text within a corporate author in biblatex v3.11?



The following MWE with italic text within a corporate author used to work with biblatex 3.10 from texlive2017:



documentclass{book}

usepackage{filecontents}
begin{filecontents*}{jobname.bib}
@online{cicerone,
author = {{textit{italic text} normal text}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}
end{filecontents*}

usepackage{biblatex}
addbibresource{jobname.bib}

begin{document}

cite{cicerone}
printbibliography

end{document}


With the following package versions:



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2017/12/19 v3.10 programmable bibliographies (PK/JW/AB)
pdftexcmds.sty 2018/01/21 v0.26 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def
biblatex-dm.cfg
blx-compat.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
biblatex.def 2017/12/19 v3.10 biblatex compatibility (PK/JW/AB)
standard.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.bbx 2017/12/19 v3.10 biblatex bibliography style (PK/JW/AB)
numeric.cbx 2017/12/19 v3.10 biblatex citation style (PK/JW/AB)
biblatex.cfg
english.lbx 2017/12/19 v3.10 biblatex localization (PK/JW/AB)


With biblatex v3.11 from texlive2018(pretest) and the following packages



 *File List*
book.cls 2014/09/29 v1.4h Standard LaTeX document class
bk10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
filecontents.sty 2011/10/08 v1.3 Create an external file from within a LaTeX
document
biblatex.sty 2018/03/04 v3.11 programmable bibliographies (PK/MW)
pdftexcmds.sty 2018/01/30 v0.27 Utility functions of pdfTeX for LuaTeX (HO)
infwarerr.sty 2016/05/16 v1.4 Providing info/warning/error messages (HO)
ifluatex.sty 2016/05/16 v1.4 Provides the ifluatex switch (HO)
ltxcmds.sty 2016/05/16 v1.23 LaTeX kernel commands for general use (HO)
ifpdf.sty 2017/03/15 v3.2 Provides the ifpdf switch
etoolbox.sty 2018/02/11 v2.5e e-TeX tools for LaTeX (JAW)
keyval.sty 2014/10/28 v1.15 key=value parser (DPC)
kvoptions.sty 2016/05/16 v3.12 Key value format for package options (HO)
kvsetkeys.sty 2016/05/16 v1.17 Key value parser (HO)
etexcmds.sty 2016/05/16 v1.6 Avoid name clashes with e-TeX commands (HO)
logreq.sty 2010/08/04 v1.0 xml request logger
logreq.def 2010/08/04 v1.0 logreq spec v1.0
ifthen.sty 2014/09/29 v1.1c Standard LaTeX ifthen package (DPC)
url.sty 2013/09/16 ver 3.4 Verb mode for urls, etc.
xstring.sty 2013/10/13 v1.7c String manipulations (C Tellechea)
blx-dm.def 2018/03/04 v3.11 biblatex localization (PK/MW)
blx-compat.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
biblatex.def 2018/03/04 v3.11 biblatex compatibility (PK/MW)
standard.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.bbx 2018/03/04 v3.11 biblatex bibliography style (PK/MW)
numeric.cbx 2018/03/04 v3.11 biblatex citation style (PK/MW)
biblatex.cfg
english.lbx 2018/03/04 v3.11 biblatex localization (PK/MW)


It fails with the following error message



! Extra }, or forgotten endgroup.
l.27 }

?






biblatex






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 11 '18 at 11:05









samcartersamcarter

1




1













  • Wait for biblatex 3.12: github.com/plk/biber/issues/216 (see also github.com/plk/biber/issues/215, github.com/plk/biblatex/issues/727). This was due to the changes introduced in github.com/plk/biber/issues/210. Duplicate question tex.stackexchange.com/q/420043/35864

    – moewe
    Apr 11 '18 at 11:06













  • @moewe Thanks, that is indeed the same problem. Would you like to write a short answer (to the other question) which says that this will be fixed in 3.12? Otherwise I cannot close this one as dupe

    – samcarter
    Apr 11 '18 at 11:08













  • Oh sorry. I got confused an wrote an answer to this one and closed the other. Hope you don't mind. The outcome should be roughly the same...

    – moewe
    Apr 11 '18 at 11:16













  • @moewe I don't mind at all. Thank you very much! (Have to wait another 3 minutes before I am allowed to accept...)

    – samcarter
    Apr 11 '18 at 11:16





















  • Wait for biblatex 3.12: github.com/plk/biber/issues/216 (see also github.com/plk/biber/issues/215, github.com/plk/biblatex/issues/727). This was due to the changes introduced in github.com/plk/biber/issues/210. Duplicate question tex.stackexchange.com/q/420043/35864

    – moewe
    Apr 11 '18 at 11:06













  • @moewe Thanks, that is indeed the same problem. Would you like to write a short answer (to the other question) which says that this will be fixed in 3.12? Otherwise I cannot close this one as dupe

    – samcarter
    Apr 11 '18 at 11:08













  • Oh sorry. I got confused an wrote an answer to this one and closed the other. Hope you don't mind. The outcome should be roughly the same...

    – moewe
    Apr 11 '18 at 11:16













  • @moewe I don't mind at all. Thank you very much! (Have to wait another 3 minutes before I am allowed to accept...)

    – samcarter
    Apr 11 '18 at 11:16



















Wait for biblatex 3.12: github.com/plk/biber/issues/216 (see also github.com/plk/biber/issues/215, github.com/plk/biblatex/issues/727). This was due to the changes introduced in github.com/plk/biber/issues/210. Duplicate question tex.stackexchange.com/q/420043/35864

– moewe
Apr 11 '18 at 11:06







Wait for biblatex 3.12: github.com/plk/biber/issues/216 (see also github.com/plk/biber/issues/215, github.com/plk/biblatex/issues/727). This was due to the changes introduced in github.com/plk/biber/issues/210. Duplicate question tex.stackexchange.com/q/420043/35864

– moewe
Apr 11 '18 at 11:06















@moewe Thanks, that is indeed the same problem. Would you like to write a short answer (to the other question) which says that this will be fixed in 3.12? Otherwise I cannot close this one as dupe

– samcarter
Apr 11 '18 at 11:08







@moewe Thanks, that is indeed the same problem. Would you like to write a short answer (to the other question) which says that this will be fixed in 3.12? Otherwise I cannot close this one as dupe

– samcarter
Apr 11 '18 at 11:08















Oh sorry. I got confused an wrote an answer to this one and closed the other. Hope you don't mind. The outcome should be roughly the same...

– moewe
Apr 11 '18 at 11:16







Oh sorry. I got confused an wrote an answer to this one and closed the other. Hope you don't mind. The outcome should be roughly the same...

– moewe
Apr 11 '18 at 11:16















@moewe I don't mind at all. Thank you very much! (Have to wait another 3 minutes before I am allowed to accept...)

– samcarter
Apr 11 '18 at 11:16







@moewe I don't mind at all. Thank you very much! (Have to wait another 3 minutes before I am allowed to accept...)

– samcarter
Apr 11 '18 at 11:16












1 Answer
1






active

oldest

votes


















4














This was a bug in Biber 2.11 that was fixed in 2.12. See https://github.com/plk/biber/issues/216 (and to a lesser extent https://github.com/plk/biber/issues/215 and https://github.com/plk/biblatex/issues/727). It came about because of a fix to support unnecessary braces around last names: https://github.com/plk/biber/issues/210 and ! Paragraph ended before name was complete.



The fix in 2.12 does not re-establish functionality for certain other constructions that used to work. In particular Two or three letter initials in bibliography with Biblatex, BibTeX: Abbreviate first name (aka given name) to 2 or 3 letters (not 1) will still not work - a different solution has to be found: Two or three letter initials in bibliography with Biblatex (again).



If at all possible, macros should be avoided in name fields because arbitrary macros can interfere with conversion of ASCII-macros to Unicode characters as well as the brace protection for casing. Macros can also seriously inhibit Biber's ability to extract name initials from fields. Biber is written in Perl and extensively uses RegEx to parse data: Braces and braced groups present a challenge there.






This workaround is only retained for historic interest. It should not be necessary in a current version of Biber.




If you must absolutely have these macros in your author field, a work-around using the extended name format is possible. With the extended name format you give each part of the name explicitly and do not rely on the btparse library to parse the name as usual. The particular error occurs because the name initial routine gets thrown off by toon many braces, if you provide the problematic initial yourself, the error is avoided. So the example in the question would compile fine as



@online{cicerone,
author = {family={textit{italic text} normal text}, family-i={textit{i}}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}





share|improve this answer


























  • Thanks again for you answer! You should get extra points for the record breaking speed!

    – samcarter
    Apr 11 '18 at 11:22











  • Out of curiosity: Do you know if there is some list of all the available key words of the extended name format? I had a look at the biber documentation "3.8. Extended Name Format" but only found examples.

    – samcarter
    May 20 '18 at 19:52











  • @samcarter Because the name format is extensible there is no definitive list. By default the name parts family, given, prefix and suffix are defined. So these four and their 'initial parts' family-i, given-i, prefix-i and suffix-i are normally accepted. If you define new name parts, they and their initial form also become valid. Additionally per-name and per-namelist options (as listed in Appendix E) are valid.

    – moewe
    May 20 '18 at 19:58













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%2f425947%2fitalic-text-in-corporate-author%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









4














This was a bug in Biber 2.11 that was fixed in 2.12. See https://github.com/plk/biber/issues/216 (and to a lesser extent https://github.com/plk/biber/issues/215 and https://github.com/plk/biblatex/issues/727). It came about because of a fix to support unnecessary braces around last names: https://github.com/plk/biber/issues/210 and ! Paragraph ended before name was complete.



The fix in 2.12 does not re-establish functionality for certain other constructions that used to work. In particular Two or three letter initials in bibliography with Biblatex, BibTeX: Abbreviate first name (aka given name) to 2 or 3 letters (not 1) will still not work - a different solution has to be found: Two or three letter initials in bibliography with Biblatex (again).



If at all possible, macros should be avoided in name fields because arbitrary macros can interfere with conversion of ASCII-macros to Unicode characters as well as the brace protection for casing. Macros can also seriously inhibit Biber's ability to extract name initials from fields. Biber is written in Perl and extensively uses RegEx to parse data: Braces and braced groups present a challenge there.






This workaround is only retained for historic interest. It should not be necessary in a current version of Biber.




If you must absolutely have these macros in your author field, a work-around using the extended name format is possible. With the extended name format you give each part of the name explicitly and do not rely on the btparse library to parse the name as usual. The particular error occurs because the name initial routine gets thrown off by toon many braces, if you provide the problematic initial yourself, the error is avoided. So the example in the question would compile fine as



@online{cicerone,
author = {family={textit{italic text} normal text}, family-i={textit{i}}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}





share|improve this answer


























  • Thanks again for you answer! You should get extra points for the record breaking speed!

    – samcarter
    Apr 11 '18 at 11:22











  • Out of curiosity: Do you know if there is some list of all the available key words of the extended name format? I had a look at the biber documentation "3.8. Extended Name Format" but only found examples.

    – samcarter
    May 20 '18 at 19:52











  • @samcarter Because the name format is extensible there is no definitive list. By default the name parts family, given, prefix and suffix are defined. So these four and their 'initial parts' family-i, given-i, prefix-i and suffix-i are normally accepted. If you define new name parts, they and their initial form also become valid. Additionally per-name and per-namelist options (as listed in Appendix E) are valid.

    – moewe
    May 20 '18 at 19:58


















4














This was a bug in Biber 2.11 that was fixed in 2.12. See https://github.com/plk/biber/issues/216 (and to a lesser extent https://github.com/plk/biber/issues/215 and https://github.com/plk/biblatex/issues/727). It came about because of a fix to support unnecessary braces around last names: https://github.com/plk/biber/issues/210 and ! Paragraph ended before name was complete.



The fix in 2.12 does not re-establish functionality for certain other constructions that used to work. In particular Two or three letter initials in bibliography with Biblatex, BibTeX: Abbreviate first name (aka given name) to 2 or 3 letters (not 1) will still not work - a different solution has to be found: Two or three letter initials in bibliography with Biblatex (again).



If at all possible, macros should be avoided in name fields because arbitrary macros can interfere with conversion of ASCII-macros to Unicode characters as well as the brace protection for casing. Macros can also seriously inhibit Biber's ability to extract name initials from fields. Biber is written in Perl and extensively uses RegEx to parse data: Braces and braced groups present a challenge there.






This workaround is only retained for historic interest. It should not be necessary in a current version of Biber.




If you must absolutely have these macros in your author field, a work-around using the extended name format is possible. With the extended name format you give each part of the name explicitly and do not rely on the btparse library to parse the name as usual. The particular error occurs because the name initial routine gets thrown off by toon many braces, if you provide the problematic initial yourself, the error is avoided. So the example in the question would compile fine as



@online{cicerone,
author = {family={textit{italic text} normal text}, family-i={textit{i}}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}





share|improve this answer


























  • Thanks again for you answer! You should get extra points for the record breaking speed!

    – samcarter
    Apr 11 '18 at 11:22











  • Out of curiosity: Do you know if there is some list of all the available key words of the extended name format? I had a look at the biber documentation "3.8. Extended Name Format" but only found examples.

    – samcarter
    May 20 '18 at 19:52











  • @samcarter Because the name format is extensible there is no definitive list. By default the name parts family, given, prefix and suffix are defined. So these four and their 'initial parts' family-i, given-i, prefix-i and suffix-i are normally accepted. If you define new name parts, they and their initial form also become valid. Additionally per-name and per-namelist options (as listed in Appendix E) are valid.

    – moewe
    May 20 '18 at 19:58
















4












4








4







This was a bug in Biber 2.11 that was fixed in 2.12. See https://github.com/plk/biber/issues/216 (and to a lesser extent https://github.com/plk/biber/issues/215 and https://github.com/plk/biblatex/issues/727). It came about because of a fix to support unnecessary braces around last names: https://github.com/plk/biber/issues/210 and ! Paragraph ended before name was complete.



The fix in 2.12 does not re-establish functionality for certain other constructions that used to work. In particular Two or three letter initials in bibliography with Biblatex, BibTeX: Abbreviate first name (aka given name) to 2 or 3 letters (not 1) will still not work - a different solution has to be found: Two or three letter initials in bibliography with Biblatex (again).



If at all possible, macros should be avoided in name fields because arbitrary macros can interfere with conversion of ASCII-macros to Unicode characters as well as the brace protection for casing. Macros can also seriously inhibit Biber's ability to extract name initials from fields. Biber is written in Perl and extensively uses RegEx to parse data: Braces and braced groups present a challenge there.






This workaround is only retained for historic interest. It should not be necessary in a current version of Biber.




If you must absolutely have these macros in your author field, a work-around using the extended name format is possible. With the extended name format you give each part of the name explicitly and do not rely on the btparse library to parse the name as usual. The particular error occurs because the name initial routine gets thrown off by toon many braces, if you provide the problematic initial yourself, the error is avoided. So the example in the question would compile fine as



@online{cicerone,
author = {family={textit{italic text} normal text}, family-i={textit{i}}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}





share|improve this answer















This was a bug in Biber 2.11 that was fixed in 2.12. See https://github.com/plk/biber/issues/216 (and to a lesser extent https://github.com/plk/biber/issues/215 and https://github.com/plk/biblatex/issues/727). It came about because of a fix to support unnecessary braces around last names: https://github.com/plk/biber/issues/210 and ! Paragraph ended before name was complete.



The fix in 2.12 does not re-establish functionality for certain other constructions that used to work. In particular Two or three letter initials in bibliography with Biblatex, BibTeX: Abbreviate first name (aka given name) to 2 or 3 letters (not 1) will still not work - a different solution has to be found: Two or three letter initials in bibliography with Biblatex (again).



If at all possible, macros should be avoided in name fields because arbitrary macros can interfere with conversion of ASCII-macros to Unicode characters as well as the brace protection for casing. Macros can also seriously inhibit Biber's ability to extract name initials from fields. Biber is written in Perl and extensively uses RegEx to parse data: Braces and braced groups present a challenge there.






This workaround is only retained for historic interest. It should not be necessary in a current version of Biber.




If you must absolutely have these macros in your author field, a work-around using the extended name format is possible. With the extended name format you give each part of the name explicitly and do not rely on the btparse library to parse the name as usual. The particular error occurs because the name initial routine gets thrown off by toon many braces, if you provide the problematic initial yourself, the error is avoided. So the example in the question would compile fine as



@online{cicerone,
author = {family={textit{italic text} normal text}, family-i={textit{i}}},
title = {title},
url = {www.example.com},
urldate = {2016-05-12}
}






share|improve this answer














share|improve this answer



share|improve this answer








edited 2 hours ago

























answered Apr 11 '18 at 11:13









moewemoewe

92k10115347




92k10115347













  • Thanks again for you answer! You should get extra points for the record breaking speed!

    – samcarter
    Apr 11 '18 at 11:22











  • Out of curiosity: Do you know if there is some list of all the available key words of the extended name format? I had a look at the biber documentation "3.8. Extended Name Format" but only found examples.

    – samcarter
    May 20 '18 at 19:52











  • @samcarter Because the name format is extensible there is no definitive list. By default the name parts family, given, prefix and suffix are defined. So these four and their 'initial parts' family-i, given-i, prefix-i and suffix-i are normally accepted. If you define new name parts, they and their initial form also become valid. Additionally per-name and per-namelist options (as listed in Appendix E) are valid.

    – moewe
    May 20 '18 at 19:58





















  • Thanks again for you answer! You should get extra points for the record breaking speed!

    – samcarter
    Apr 11 '18 at 11:22











  • Out of curiosity: Do you know if there is some list of all the available key words of the extended name format? I had a look at the biber documentation "3.8. Extended Name Format" but only found examples.

    – samcarter
    May 20 '18 at 19:52











  • @samcarter Because the name format is extensible there is no definitive list. By default the name parts family, given, prefix and suffix are defined. So these four and their 'initial parts' family-i, given-i, prefix-i and suffix-i are normally accepted. If you define new name parts, they and their initial form also become valid. Additionally per-name and per-namelist options (as listed in Appendix E) are valid.

    – moewe
    May 20 '18 at 19:58



















Thanks again for you answer! You should get extra points for the record breaking speed!

– samcarter
Apr 11 '18 at 11:22





Thanks again for you answer! You should get extra points for the record breaking speed!

– samcarter
Apr 11 '18 at 11:22













Out of curiosity: Do you know if there is some list of all the available key words of the extended name format? I had a look at the biber documentation "3.8. Extended Name Format" but only found examples.

– samcarter
May 20 '18 at 19:52





Out of curiosity: Do you know if there is some list of all the available key words of the extended name format? I had a look at the biber documentation "3.8. Extended Name Format" but only found examples.

– samcarter
May 20 '18 at 19:52













@samcarter Because the name format is extensible there is no definitive list. By default the name parts family, given, prefix and suffix are defined. So these four and their 'initial parts' family-i, given-i, prefix-i and suffix-i are normally accepted. If you define new name parts, they and their initial form also become valid. Additionally per-name and per-namelist options (as listed in Appendix E) are valid.

– moewe
May 20 '18 at 19:58







@samcarter Because the name format is extensible there is no definitive list. By default the name parts family, given, prefix and suffix are defined. So these four and their 'initial parts' family-i, given-i, prefix-i and suffix-i are normally accepted. If you define new name parts, they and their initial form also become valid. Additionally per-name and per-namelist options (as listed in Appendix E) are valid.

– moewe
May 20 '18 at 19:58




















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%2f425947%2fitalic-text-in-corporate-author%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 |...