BibLaTeX long URL extending into border despite using biburllcpenalty












6














MWE:



test.tex:



% !TeX program = xelatex

documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}

usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{7000}

setcounter{biburlucpenalty}{9999}

addbibresource{resources.bib}

begin{document}

cite{Test.2018}

printbibliography

end{document}


resources.bib:



@misc{Test.2018,

    author = {{testauthor test author testauthor}},

    year= {2018},

    title = {{testfile test file testfile}},

    url = {http://abcdefghijklmnopqrstuvwxy.com/phrrFK5dS1ztTjiaCmveRARXpGBtV01U%20B93FcrxkOVhj2CceIguNuUPpwDaUD4GjTTWh9cL30D6rLgWxapYlhegDXQGFlE0hao7B2YS227ca%20keoWHWNmQVKVcNOUFxfsCp0SwCElfTVtpMv6DKqiSwhWgO2zrHvstd4UNBo99UQBSCTkzL7lD2UyRLTRy6xXdJ}

}


Here the URL does not break properly due to the fontspec package changing the parindent. How can I fix this?



begingroup

sloppy

printbibliography

endgroup


This makes the URL look extremely ugly with the first line not even justified. It is just this one weird character extending into the border. I do not want to use any weird workarounds like using the url package and changing the bibliography when BibLaTeX supports URLs natively with Biber.






biblatex xetex line-breaking koma-script







share|improve this question









New contributor




Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Young Un Thank you for helping keep things into the QA structure in the other question. It definitely works better this way. If I may, I have another suggestion. How about you use in your question the actual URL that's giving you trouble? If you provide us with an arbitrarily long made up URL, the only general solution may be to use something of the kind of sloppy. But usually real URL are less badly behaved (even if nasty enough!), so the real case might get you a better solution.
    – gusbrs
    Dec 16 at 18:29












  • You could also use setcounter{biburlnumpenalty}{9900} (or some other value), to also allow breakpoints after numbers.
    – Skillmon
    Dec 16 at 18:33










  • Thanks for staying with me! Actually the real url is of a similar length and also composed of a similar length of random characters (or base64 strings) after the tld. This is what confuses me. The url is literally a string of random characters and latex decides not to break at one random point that is at the end of the regular line but instead after the next character. I tried setting biburlnumpenalty, it did not have an impact either.
    – Young Un
    Dec 16 at 18:36












  • Mmh, In this case, let's see what folks have to say.
    – gusbrs
    Dec 16 at 18:39






  • 2




    As to your comment "I do not want to use any weird workarounds like using the url package and changing the bibliography when biblatex supports urls natively with biber." Actually biblatex loads the url package and it is url that provides biblatex's support for urls. So, you might as well use its options, if they do get things better.
    – gusbrs
    Dec 16 at 18:47


















6














MWE:



test.tex:



% !TeX program = xelatex

documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}

usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{7000}

setcounter{biburlucpenalty}{9999}

addbibresource{resources.bib}

begin{document}

cite{Test.2018}

printbibliography

end{document}


resources.bib:



@misc{Test.2018,

    author = {{testauthor test author testauthor}},

    year= {2018},

    title = {{testfile test file testfile}},

    url = {http://abcdefghijklmnopqrstuvwxy.com/phrrFK5dS1ztTjiaCmveRARXpGBtV01U%20B93FcrxkOVhj2CceIguNuUPpwDaUD4GjTTWh9cL30D6rLgWxapYlhegDXQGFlE0hao7B2YS227ca%20keoWHWNmQVKVcNOUFxfsCp0SwCElfTVtpMv6DKqiSwhWgO2zrHvstd4UNBo99UQBSCTkzL7lD2UyRLTRy6xXdJ}

}


Here the URL does not break properly due to the fontspec package changing the parindent. How can I fix this?



begingroup

sloppy

printbibliography

endgroup


This makes the URL look extremely ugly with the first line not even justified. It is just this one weird character extending into the border. I do not want to use any weird workarounds like using the url package and changing the bibliography when BibLaTeX supports URLs natively with Biber.






biblatex xetex line-breaking koma-script







share|improve this question









New contributor




Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Young Un Thank you for helping keep things into the QA structure in the other question. It definitely works better this way. If I may, I have another suggestion. How about you use in your question the actual URL that's giving you trouble? If you provide us with an arbitrarily long made up URL, the only general solution may be to use something of the kind of sloppy. But usually real URL are less badly behaved (even if nasty enough!), so the real case might get you a better solution.
    – gusbrs
    Dec 16 at 18:29












  • You could also use setcounter{biburlnumpenalty}{9900} (or some other value), to also allow breakpoints after numbers.
    – Skillmon
    Dec 16 at 18:33










  • Thanks for staying with me! Actually the real url is of a similar length and also composed of a similar length of random characters (or base64 strings) after the tld. This is what confuses me. The url is literally a string of random characters and latex decides not to break at one random point that is at the end of the regular line but instead after the next character. I tried setting biburlnumpenalty, it did not have an impact either.
    – Young Un
    Dec 16 at 18:36












  • Mmh, In this case, let's see what folks have to say.
    – gusbrs
    Dec 16 at 18:39






  • 2




    As to your comment "I do not want to use any weird workarounds like using the url package and changing the bibliography when biblatex supports urls natively with biber." Actually biblatex loads the url package and it is url that provides biblatex's support for urls. So, you might as well use its options, if they do get things better.
    – gusbrs
    Dec 16 at 18:47
















6












6








6


0





MWE:



test.tex:



% !TeX program = xelatex

documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}

usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{7000}

setcounter{biburlucpenalty}{9999}

addbibresource{resources.bib}

begin{document}

cite{Test.2018}

printbibliography

end{document}


resources.bib:



@misc{Test.2018,

    author = {{testauthor test author testauthor}},

    year= {2018},

    title = {{testfile test file testfile}},

    url = {http://abcdefghijklmnopqrstuvwxy.com/phrrFK5dS1ztTjiaCmveRARXpGBtV01U%20B93FcrxkOVhj2CceIguNuUPpwDaUD4GjTTWh9cL30D6rLgWxapYlhegDXQGFlE0hao7B2YS227ca%20keoWHWNmQVKVcNOUFxfsCp0SwCElfTVtpMv6DKqiSwhWgO2zrHvstd4UNBo99UQBSCTkzL7lD2UyRLTRy6xXdJ}

}


Here the URL does not break properly due to the fontspec package changing the parindent. How can I fix this?



begingroup

sloppy

printbibliography

endgroup


This makes the URL look extremely ugly with the first line not even justified. It is just this one weird character extending into the border. I do not want to use any weird workarounds like using the url package and changing the bibliography when BibLaTeX supports URLs natively with Biber.






biblatex xetex line-breaking koma-script







share|improve this question









New contributor




Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











MWE:



test.tex:



% !TeX program = xelatex

documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}

usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{7000}

setcounter{biburlucpenalty}{9999}

addbibresource{resources.bib}

begin{document}

cite{Test.2018}

printbibliography

end{document}


resources.bib:



@misc{Test.2018,

    author = {{testauthor test author testauthor}},

    year= {2018},

    title = {{testfile test file testfile}},

    url = {http://abcdefghijklmnopqrstuvwxy.com/phrrFK5dS1ztTjiaCmveRARXpGBtV01U%20B93FcrxkOVhj2CceIguNuUPpwDaUD4GjTTWh9cL30D6rLgWxapYlhegDXQGFlE0hao7B2YS227ca%20keoWHWNmQVKVcNOUFxfsCp0SwCElfTVtpMv6DKqiSwhWgO2zrHvstd4UNBo99UQBSCTkzL7lD2UyRLTRy6xXdJ}

}


Here the URL does not break properly due to the fontspec package changing the parindent. How can I fix this?



begingroup

sloppy

printbibliography

endgroup


This makes the URL look extremely ugly with the first line not even justified. It is just this one weird character extending into the border. I do not want to use any weird workarounds like using the url package and changing the bibliography when BibLaTeX supports URLs natively with Biber.






biblatex xetex line-breaking koma-script




biblatex xetex line-breaking koma-script






share|improve this question









New contributor




Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited Dec 17 at 7:31









Peter Mortensen

53536




53536






New contributor




Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Dec 16 at 18:17









Young Un

905




905




New contributor




Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Young Un is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1




    Young Un Thank you for helping keep things into the QA structure in the other question. It definitely works better this way. If I may, I have another suggestion. How about you use in your question the actual URL that's giving you trouble? If you provide us with an arbitrarily long made up URL, the only general solution may be to use something of the kind of sloppy. But usually real URL are less badly behaved (even if nasty enough!), so the real case might get you a better solution.
    – gusbrs
    Dec 16 at 18:29












  • You could also use setcounter{biburlnumpenalty}{9900} (or some other value), to also allow breakpoints after numbers.
    – Skillmon
    Dec 16 at 18:33










  • Thanks for staying with me! Actually the real url is of a similar length and also composed of a similar length of random characters (or base64 strings) after the tld. This is what confuses me. The url is literally a string of random characters and latex decides not to break at one random point that is at the end of the regular line but instead after the next character. I tried setting biburlnumpenalty, it did not have an impact either.
    – Young Un
    Dec 16 at 18:36












  • Mmh, In this case, let's see what folks have to say.
    – gusbrs
    Dec 16 at 18:39






  • 2




    As to your comment "I do not want to use any weird workarounds like using the url package and changing the bibliography when biblatex supports urls natively with biber." Actually biblatex loads the url package and it is url that provides biblatex's support for urls. So, you might as well use its options, if they do get things better.
    – gusbrs
    Dec 16 at 18:47
















  • 1




    Young Un Thank you for helping keep things into the QA structure in the other question. It definitely works better this way. If I may, I have another suggestion. How about you use in your question the actual URL that's giving you trouble? If you provide us with an arbitrarily long made up URL, the only general solution may be to use something of the kind of sloppy. But usually real URL are less badly behaved (even if nasty enough!), so the real case might get you a better solution.
    – gusbrs
    Dec 16 at 18:29












  • You could also use setcounter{biburlnumpenalty}{9900} (or some other value), to also allow breakpoints after numbers.
    – Skillmon
    Dec 16 at 18:33










  • Thanks for staying with me! Actually the real url is of a similar length and also composed of a similar length of random characters (or base64 strings) after the tld. This is what confuses me. The url is literally a string of random characters and latex decides not to break at one random point that is at the end of the regular line but instead after the next character. I tried setting biburlnumpenalty, it did not have an impact either.
    – Young Un
    Dec 16 at 18:36












  • Mmh, In this case, let's see what folks have to say.
    – gusbrs
    Dec 16 at 18:39






  • 2




    As to your comment "I do not want to use any weird workarounds like using the url package and changing the bibliography when biblatex supports urls natively with biber." Actually biblatex loads the url package and it is url that provides biblatex's support for urls. So, you might as well use its options, if they do get things better.
    – gusbrs
    Dec 16 at 18:47










1




1




Young Un Thank you for helping keep things into the QA structure in the other question. It definitely works better this way. If I may, I have another suggestion. How about you use in your question the actual URL that's giving you trouble? If you provide us with an arbitrarily long made up URL, the only general solution may be to use something of the kind of sloppy. But usually real URL are less badly behaved (even if nasty enough!), so the real case might get you a better solution.
– gusbrs
Dec 16 at 18:29






Young Un Thank you for helping keep things into the QA structure in the other question. It definitely works better this way. If I may, I have another suggestion. How about you use in your question the actual URL that's giving you trouble? If you provide us with an arbitrarily long made up URL, the only general solution may be to use something of the kind of sloppy. But usually real URL are less badly behaved (even if nasty enough!), so the real case might get you a better solution.
– gusbrs
Dec 16 at 18:29














You could also use setcounter{biburlnumpenalty}{9900} (or some other value), to also allow breakpoints after numbers.
– Skillmon
Dec 16 at 18:33




You could also use setcounter{biburlnumpenalty}{9900} (or some other value), to also allow breakpoints after numbers.
– Skillmon
Dec 16 at 18:33












Thanks for staying with me! Actually the real url is of a similar length and also composed of a similar length of random characters (or base64 strings) after the tld. This is what confuses me. The url is literally a string of random characters and latex decides not to break at one random point that is at the end of the regular line but instead after the next character. I tried setting biburlnumpenalty, it did not have an impact either.
– Young Un
Dec 16 at 18:36






Thanks for staying with me! Actually the real url is of a similar length and also composed of a similar length of random characters (or base64 strings) after the tld. This is what confuses me. The url is literally a string of random characters and latex decides not to break at one random point that is at the end of the regular line but instead after the next character. I tried setting biburlnumpenalty, it did not have an impact either.
– Young Un
Dec 16 at 18:36














Mmh, In this case, let's see what folks have to say.
– gusbrs
Dec 16 at 18:39




Mmh, In this case, let's see what folks have to say.
– gusbrs
Dec 16 at 18:39




2




2




As to your comment "I do not want to use any weird workarounds like using the url package and changing the bibliography when biblatex supports urls natively with biber." Actually biblatex loads the url package and it is url that provides biblatex's support for urls. So, you might as well use its options, if they do get things better.
– gusbrs
Dec 16 at 18:47






As to your comment "I do not want to use any weird workarounds like using the url package and changing the bibliography when biblatex supports urls natively with biber." Actually biblatex loads the url package and it is url that provides biblatex's support for urls. So, you might as well use its options, if they do get things better.
– gusbrs
Dec 16 at 18:47












2 Answers
2






active

oldest

votes


















7














You could insert a bit stretchable space:



documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}



usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{100}

setcounter{biburlucpenalty}{100}

setcounter{biburlnumpenalty}{100}

addbibresource{resource.bib}



renewcommand*{biburlsetup}{%

  Urlmuskip=0mu plus 3murelax

  mathchardefUrlBigBreakPenalty=100relax

  mathchardefUrlBreakPenalty=200relax

  defUrlBigBreaks{do:do-}%

  defUrlBreaks{%

    do.do@do/do\do!do_do|do;do>do]do)do}%

    do,do?do'do+do=do#do$do&do*do^do"}%

  ifnumgreater{value{biburlnumpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlnumpenalty}}}}%

     do1do2do3do4do5do6do7do8do9do}

    {}%

  ifnumgreater{value{biburlucpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlucpenalty}}}}%

     doAdoBdoCdoDdoEdoFdoGdoHdoIdoJ

     doKdoLdoMdoNdoOdoPdoQdoRdoSdoT

     doUdoVdoWdoXdoYdoZ}

    {}%

  ifnumgreater{value{biburllcpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburllcpenalty}}}}%

     doadobdocdoddoedofdogdohdoidoj

     dokdoldomdondoodopdoqdordosdot

     doudovdowdoxdoydoz}

    {}%

  letdo=noexpand}



begin{document}





cite{Test.2018}

printbibliography

end{document}


enter image description here






share|improve this answer





















  • +1 I played with this definition quite a lot, to no avail. But why does placing the glue inside UrlSpecials differs from setting a larger glue in Urlmuskip?
    – gusbrs
    Dec 16 at 20:36






  • 1




    Urlmuskip has an effect only at the dot and the slash. It doesn't affect the problematic line.
    – Ulrike Fischer
    Dec 16 at 20:39










  • Ah! so that's why I had to go up to 10mu just to get a lousy result...
    – gusbrs
    Dec 16 at 20:41



















3














try



usepackage[style=authoryear,citestyle=authoryear]{biblatex}

usepackage{xurl}


enter image description here






share|improve this answer























  • Tried, did not work at all. The url now overshoots the page by about 10 cm.
    – Young Un
    Dec 16 at 19:25










  • see edited answer
    – Herbert
    Dec 16 at 19:51










  • Is using a whole different mono font the only way to fix one single linebreak?
    – Young Un
    Dec 16 at 19:52










  • this font is only an example!
    – Herbert
    Dec 16 at 19:54






  • 1




    I'm sorry, I can not follow. Your example literally changes the font and my problem is about an url not breaking the way I want it to.
    – Young Un
    Dec 16 at 21:42











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
});


}
});






Young Un is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f466114%2fbiblatex-long-url-extending-into-border-despite-using-biburllcpenalty%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









7














You could insert a bit stretchable space:



documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}



usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{100}

setcounter{biburlucpenalty}{100}

setcounter{biburlnumpenalty}{100}

addbibresource{resource.bib}



renewcommand*{biburlsetup}{%

  Urlmuskip=0mu plus 3murelax

  mathchardefUrlBigBreakPenalty=100relax

  mathchardefUrlBreakPenalty=200relax

  defUrlBigBreaks{do:do-}%

  defUrlBreaks{%

    do.do@do/do\do!do_do|do;do>do]do)do}%

    do,do?do'do+do=do#do$do&do*do^do"}%

  ifnumgreater{value{biburlnumpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlnumpenalty}}}}%

     do1do2do3do4do5do6do7do8do9do}

    {}%

  ifnumgreater{value{biburlucpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlucpenalty}}}}%

     doAdoBdoCdoDdoEdoFdoGdoHdoIdoJ

     doKdoLdoMdoNdoOdoPdoQdoRdoSdoT

     doUdoVdoWdoXdoYdoZ}

    {}%

  ifnumgreater{value{biburllcpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburllcpenalty}}}}%

     doadobdocdoddoedofdogdohdoidoj

     dokdoldomdondoodopdoqdordosdot

     doudovdowdoxdoydoz}

    {}%

  letdo=noexpand}



begin{document}





cite{Test.2018}

printbibliography

end{document}


enter image description here






share|improve this answer





















  • +1 I played with this definition quite a lot, to no avail. But why does placing the glue inside UrlSpecials differs from setting a larger glue in Urlmuskip?
    – gusbrs
    Dec 16 at 20:36






  • 1




    Urlmuskip has an effect only at the dot and the slash. It doesn't affect the problematic line.
    – Ulrike Fischer
    Dec 16 at 20:39










  • Ah! so that's why I had to go up to 10mu just to get a lousy result...
    – gusbrs
    Dec 16 at 20:41
















7














You could insert a bit stretchable space:



documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}



usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{100}

setcounter{biburlucpenalty}{100}

setcounter{biburlnumpenalty}{100}

addbibresource{resource.bib}



renewcommand*{biburlsetup}{%

  Urlmuskip=0mu plus 3murelax

  mathchardefUrlBigBreakPenalty=100relax

  mathchardefUrlBreakPenalty=200relax

  defUrlBigBreaks{do:do-}%

  defUrlBreaks{%

    do.do@do/do\do!do_do|do;do>do]do)do}%

    do,do?do'do+do=do#do$do&do*do^do"}%

  ifnumgreater{value{biburlnumpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlnumpenalty}}}}%

     do1do2do3do4do5do6do7do8do9do}

    {}%

  ifnumgreater{value{biburlucpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlucpenalty}}}}%

     doAdoBdoCdoDdoEdoFdoGdoHdoIdoJ

     doKdoLdoMdoNdoOdoPdoQdoRdoSdoT

     doUdoVdoWdoXdoYdoZ}

    {}%

  ifnumgreater{value{biburllcpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburllcpenalty}}}}%

     doadobdocdoddoedofdogdohdoidoj

     dokdoldomdondoodopdoqdordosdot

     doudovdowdoxdoydoz}

    {}%

  letdo=noexpand}



begin{document}





cite{Test.2018}

printbibliography

end{document}


enter image description here






share|improve this answer





















  • +1 I played with this definition quite a lot, to no avail. But why does placing the glue inside UrlSpecials differs from setting a larger glue in Urlmuskip?
    – gusbrs
    Dec 16 at 20:36






  • 1




    Urlmuskip has an effect only at the dot and the slash. It doesn't affect the problematic line.
    – Ulrike Fischer
    Dec 16 at 20:39










  • Ah! so that's why I had to go up to 10mu just to get a lousy result...
    – gusbrs
    Dec 16 at 20:41














7












7








7






You could insert a bit stretchable space:



documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}



usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{100}

setcounter{biburlucpenalty}{100}

setcounter{biburlnumpenalty}{100}

addbibresource{resource.bib}



renewcommand*{biburlsetup}{%

  Urlmuskip=0mu plus 3murelax

  mathchardefUrlBigBreakPenalty=100relax

  mathchardefUrlBreakPenalty=200relax

  defUrlBigBreaks{do:do-}%

  defUrlBreaks{%

    do.do@do/do\do!do_do|do;do>do]do)do}%

    do,do?do'do+do=do#do$do&do*do^do"}%

  ifnumgreater{value{biburlnumpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlnumpenalty}}}}%

     do1do2do3do4do5do6do7do8do9do}

    {}%

  ifnumgreater{value{biburlucpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlucpenalty}}}}%

     doAdoBdoCdoDdoEdoFdoGdoHdoIdoJ

     doKdoLdoMdoNdoOdoPdoQdoRdoSdoT

     doUdoVdoWdoXdoYdoZ}

    {}%

  ifnumgreater{value{biburllcpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburllcpenalty}}}}%

     doadobdocdoddoedofdogdohdoidoj

     dokdoldomdondoodopdoqdordosdot

     doudovdowdoxdoydoz}

    {}%

  letdo=noexpand}



begin{document}





cite{Test.2018}

printbibliography

end{document}


enter image description here






share|improve this answer












You could insert a bit stretchable space:



documentclass[paper=A4,fontsize=12pt]{scrartcl}

usepackage[left=3cm, right=3cm, bottom=3cm, top=3cm]{geometry}

usepackage{fontspec}



usepackage[backend=biber,style=authoryear,citestyle=authoryear]{biblatex}

DeclareNameAlias{sortname}{last-first}

DeclareNameAlias{default}{last-first}

setcounter{biburllcpenalty}{100}

setcounter{biburlucpenalty}{100}

setcounter{biburlnumpenalty}{100}

addbibresource{resource.bib}



renewcommand*{biburlsetup}{%

  Urlmuskip=0mu plus 3murelax

  mathchardefUrlBigBreakPenalty=100relax

  mathchardefUrlBreakPenalty=200relax

  defUrlBigBreaks{do:do-}%

  defUrlBreaks{%

    do.do@do/do\do!do_do|do;do>do]do)do}%

    do,do?do'do+do=do#do$do&do*do^do"}%

  ifnumgreater{value{biburlnumpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlnumpenalty}}}}%

     do1do2do3do4do5do6do7do8do9do}

    {}%

  ifnumgreater{value{biburlucpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburlucpenalty}}}}%

     doAdoBdoCdoDdoEdoFdoGdoHdoIdoJ

     doKdoLdoMdoNdoOdoPdoQdoRdoSdoT

     doUdoVdoWdoXdoYdoZ}

    {}%

  ifnumgreater{value{biburllcpenalty}}{0}

    {defdo##1{apptoUrlSpecials{do##1{mathchar`##1 mskip 0mu plus 1mupenaltyvalue{biburllcpenalty}}}}%

     doadobdocdoddoedofdogdohdoidoj

     dokdoldomdondoodopdoqdordosdot

     doudovdowdoxdoydoz}

    {}%

  letdo=noexpand}



begin{document}





cite{Test.2018}

printbibliography

end{document}


enter image description here







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 16 at 20:32









Ulrike Fischer

185k7289666




185k7289666












  • +1 I played with this definition quite a lot, to no avail. But why does placing the glue inside UrlSpecials differs from setting a larger glue in Urlmuskip?
    – gusbrs
    Dec 16 at 20:36






  • 1




    Urlmuskip has an effect only at the dot and the slash. It doesn't affect the problematic line.
    – Ulrike Fischer
    Dec 16 at 20:39










  • Ah! so that's why I had to go up to 10mu just to get a lousy result...
    – gusbrs
    Dec 16 at 20:41


















  • +1 I played with this definition quite a lot, to no avail. But why does placing the glue inside UrlSpecials differs from setting a larger glue in Urlmuskip?
    – gusbrs
    Dec 16 at 20:36






  • 1




    Urlmuskip has an effect only at the dot and the slash. It doesn't affect the problematic line.
    – Ulrike Fischer
    Dec 16 at 20:39










  • Ah! so that's why I had to go up to 10mu just to get a lousy result...
    – gusbrs
    Dec 16 at 20:41
















+1 I played with this definition quite a lot, to no avail. But why does placing the glue inside UrlSpecials differs from setting a larger glue in Urlmuskip?
– gusbrs
Dec 16 at 20:36




+1 I played with this definition quite a lot, to no avail. But why does placing the glue inside UrlSpecials differs from setting a larger glue in Urlmuskip?
– gusbrs
Dec 16 at 20:36




1




1




Urlmuskip has an effect only at the dot and the slash. It doesn't affect the problematic line.
– Ulrike Fischer
Dec 16 at 20:39




Urlmuskip has an effect only at the dot and the slash. It doesn't affect the problematic line.
– Ulrike Fischer
Dec 16 at 20:39












Ah! so that's why I had to go up to 10mu just to get a lousy result...
– gusbrs
Dec 16 at 20:41




Ah! so that's why I had to go up to 10mu just to get a lousy result...
– gusbrs
Dec 16 at 20:41











3














try



usepackage[style=authoryear,citestyle=authoryear]{biblatex}

usepackage{xurl}


enter image description here






share|improve this answer























  • Tried, did not work at all. The url now overshoots the page by about 10 cm.
    – Young Un
    Dec 16 at 19:25










  • see edited answer
    – Herbert
    Dec 16 at 19:51










  • Is using a whole different mono font the only way to fix one single linebreak?
    – Young Un
    Dec 16 at 19:52










  • this font is only an example!
    – Herbert
    Dec 16 at 19:54






  • 1




    I'm sorry, I can not follow. Your example literally changes the font and my problem is about an url not breaking the way I want it to.
    – Young Un
    Dec 16 at 21:42
















3














try



usepackage[style=authoryear,citestyle=authoryear]{biblatex}

usepackage{xurl}


enter image description here






share|improve this answer























  • Tried, did not work at all. The url now overshoots the page by about 10 cm.
    – Young Un
    Dec 16 at 19:25










  • see edited answer
    – Herbert
    Dec 16 at 19:51










  • Is using a whole different mono font the only way to fix one single linebreak?
    – Young Un
    Dec 16 at 19:52










  • this font is only an example!
    – Herbert
    Dec 16 at 19:54






  • 1




    I'm sorry, I can not follow. Your example literally changes the font and my problem is about an url not breaking the way I want it to.
    – Young Un
    Dec 16 at 21:42














3












3








3






try



usepackage[style=authoryear,citestyle=authoryear]{biblatex}

usepackage{xurl}


enter image description here






share|improve this answer














try



usepackage[style=authoryear,citestyle=authoryear]{biblatex}

usepackage{xurl}


enter image description here







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 17 at 6:18

























answered Dec 16 at 18:51









Herbert

268k24407716




268k24407716












  • Tried, did not work at all. The url now overshoots the page by about 10 cm.
    – Young Un
    Dec 16 at 19:25










  • see edited answer
    – Herbert
    Dec 16 at 19:51










  • Is using a whole different mono font the only way to fix one single linebreak?
    – Young Un
    Dec 16 at 19:52










  • this font is only an example!
    – Herbert
    Dec 16 at 19:54






  • 1




    I'm sorry, I can not follow. Your example literally changes the font and my problem is about an url not breaking the way I want it to.
    – Young Un
    Dec 16 at 21:42


















  • Tried, did not work at all. The url now overshoots the page by about 10 cm.
    – Young Un
    Dec 16 at 19:25










  • see edited answer
    – Herbert
    Dec 16 at 19:51










  • Is using a whole different mono font the only way to fix one single linebreak?
    – Young Un
    Dec 16 at 19:52










  • this font is only an example!
    – Herbert
    Dec 16 at 19:54






  • 1




    I'm sorry, I can not follow. Your example literally changes the font and my problem is about an url not breaking the way I want it to.
    – Young Un
    Dec 16 at 21:42
















Tried, did not work at all. The url now overshoots the page by about 10 cm.
– Young Un
Dec 16 at 19:25




Tried, did not work at all. The url now overshoots the page by about 10 cm.
– Young Un
Dec 16 at 19:25












see edited answer
– Herbert
Dec 16 at 19:51




see edited answer
– Herbert
Dec 16 at 19:51












Is using a whole different mono font the only way to fix one single linebreak?
– Young Un
Dec 16 at 19:52




Is using a whole different mono font the only way to fix one single linebreak?
– Young Un
Dec 16 at 19:52












this font is only an example!
– Herbert
Dec 16 at 19:54




this font is only an example!
– Herbert
Dec 16 at 19:54




1




1




I'm sorry, I can not follow. Your example literally changes the font and my problem is about an url not breaking the way I want it to.
– Young Un
Dec 16 at 21:42




I'm sorry, I can not follow. Your example literally changes the font and my problem is about an url not breaking the way I want it to.
– Young Un
Dec 16 at 21:42










Young Un is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Young Un is a new contributor. Be nice, and check out our Code of Conduct.













Young Un is a new contributor. Be nice, and check out our Code of Conduct.












Young Un is a new contributor. Be nice, and check out our Code of Conduct.
















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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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%2f466114%2fbiblatex-long-url-extending-into-border-despite-using-biburllcpenalty%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

數位音樂下載

Image
數位音樂下載 為非以「實體」方式來販賣音樂的相關產品，而使用數位格式如mp3、AAC等文件格式來進行銷售販賣的一种音乐产业形式。著名的數位音樂下載服務商有iTunes Store、RecoChoku、Google Play音乐和微软Zune等。数字音乐下载在二十一世纪初一度风靡全球， [1] [2] 使得传统唱片产业走向衰落，但其自身也在2010年代流媒体音乐服务如Apple Music、Spotify等的挤压下迅速失去市场份额。 [3] [4] 数字音乐下载有便于携带、传播迅速、制作简单成本低等优点，与流媒体音乐相比也能更好保障音乐人权益； [5] 但它同时很可能带来侵犯版权和滥用的情形， [6] 也给音乐产业带来了诸多不利影响。数字音乐下载为音乐人和乐迷提供了更加便捷直接的交流渠道，也一定程度上推动了网络音乐人的出现和独立音乐的迅速发展。 [7] 目录 1 历史 1.1 技术积淀（1987-2000） 1.2 出现与兴起（2000-2004） 1.3 唱片市场的颠覆者（2004-2007） 1.4 巅峰和衰落（2005-2013） 1.5 摇摇欲坠的现状与不可预知的明天（2014至今） 2 主要文件格式 2.1 PCM编码格式 2.1.1 WAV 2.1.2 APE 2.1.3 FLAC 2.2 苹果推出的无损文件格式 2.2.1 AIFF 2.2.2 ALAC 2.3 有损压缩格式 2.3.1 MP3 2.3.2 AAC 3 主要市场 3.1 iTunes Store 3.2 Google Play音乐商店 3.3 亚马逊音乐商店 3.4 部分其他音乐商店 4 影响与评价 4.1 对音乐产业的影响 4.2 对科技行业的影响 4.3 正面评价 4.4 负面评价 4.4.1 侵权问题 4.4.2 经营模式不明晰 4.4.3 不适应移动时代 4.5 文化现象 5 延伸阅读 6 参考资料 历史 苹果iTunes+iPod的软硬件搭配让数字音...
Read more

When can things happen in Etherscan, such as the picture below?

Image
2 I don't know why balance of the address is 0. when can this situation? etherscan balances share | improve this question asked yesterday Ru Hi Ru Hi 11 1 New contributor Ru Hi is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  ...
Read more

格利澤436b

Image
格利泽436b 太陽系外行星 太陽系外行星列表 艺术家笔下的格利泽436b 母恆星 母恆星 Gliese 436 星座 獅子座 赤經 ( α ) 11 h  42 m  11.0941 s [1] 赤緯 ( δ ) +26° 42′ 23.652″ [1] 距離 33.4 ly (10.2 pc) 光譜類型 M2.5 V [1] 軌道參數 半长轴 ( a ) 0.0291±0.0004 [2] AU 軌道離心率 ( e ) 0.150±0.012 [2] 公轉週期 ( P ) 2.643904±0.000005 [3] d (0.00723849 y) 軌道傾角 ( i ) 85.8 +0.21 −0.25 [3] ° 角距 ( θ ) 2.794 mas 近星點時間 ( T 0 ) 2,451,551.716 ±0.01 JD 半振幅 ( K ) 18.68±0.8 m/s 物理性质 质量 ( m ) 22.2±1.0 [2] M ⊕ 半徑 ( r ) 4.327±0.183 [2] [4] R ⊕ 密度 ( ρ ) 1.51 g cm -3 表面重力 ( g ) 1.18 g 溫度 ( T ) 712±36 [2] K 發現 發現時間 2004 發現者 巴特勒、沃格特、 馬西 et al. 發現方法 徑向速度、凌日法 發現地點 美國加利福尼亞州 發表論文 出版 其他名稱 Ross 905 b, GJ 436 b, [5] LTT 13213 b, GCTP 2704.10 b, LHS 310, AC+27:28217 b, Vyssotsky 616 b, HIP 57087 b, GEN# +9.80120068 b, LP 319-75 b, G 121-7 b, LSPM J1142+2642 b, 1RXS J114211.9+264328 b, ASCC 683818 b, G 147-68 b, UCAC2 41198281 b, BP...
Read more