Why does setmonofont change the justifying of normal text using the same font?












3














I usually use a different font for URLs e.g. email adresses. Today, I tried to change it in a letter to use the same font als the normal text and it cancelled the justification in the main body of the letter. A MWE is here:



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
% setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


Compiling this (with LuaLaTeX) yields fine justification. But after uncommenting the commented line, there is no more justification in the main body.



Is this a bug or am I misunderstanding some features of LuaLaTeX, KOMAscript, fontspec or url?










share|improve this question






















  • Strange, but are you looking for urlstyle{rm} instead?
    – Andrew Swann
    Dec 8 at 11:36
















3














I usually use a different font for URLs e.g. email adresses. Today, I tried to change it in a letter to use the same font als the normal text and it cancelled the justification in the main body of the letter. A MWE is here:



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
% setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


Compiling this (with LuaLaTeX) yields fine justification. But after uncommenting the commented line, there is no more justification in the main body.



Is this a bug or am I misunderstanding some features of LuaLaTeX, KOMAscript, fontspec or url?










share|improve this question






















  • Strange, but are you looking for urlstyle{rm} instead?
    – Andrew Swann
    Dec 8 at 11:36














3












3








3







I usually use a different font for URLs e.g. email adresses. Today, I tried to change it in a letter to use the same font als the normal text and it cancelled the justification in the main body of the letter. A MWE is here:



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
% setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


Compiling this (with LuaLaTeX) yields fine justification. But after uncommenting the commented line, there is no more justification in the main body.



Is this a bug or am I misunderstanding some features of LuaLaTeX, KOMAscript, fontspec or url?










share|improve this question













I usually use a different font for URLs e.g. email adresses. Today, I tried to change it in a letter to use the same font als the normal text and it cancelled the justification in the main body of the letter. A MWE is here:



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
% setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


Compiling this (with LuaLaTeX) yields fine justification. But after uncommenting the commented line, there is no more justification in the main body.



Is this a bug or am I misunderstanding some features of LuaLaTeX, KOMAscript, fontspec or url?







koma-script fontspec typewriter url justification






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 8 at 11:25









Toscho

3,7651118




3,7651118












  • Strange, but are you looking for urlstyle{rm} instead?
    – Andrew Swann
    Dec 8 at 11:36


















  • Strange, but are you looking for urlstyle{rm} instead?
    – Andrew Swann
    Dec 8 at 11:36
















Strange, but are you looking for urlstyle{rm} instead?
– Andrew Swann
Dec 8 at 11:36




Strange, but are you looking for urlstyle{rm} instead?
– Andrew Swann
Dec 8 at 11:36










1 Answer
1






active

oldest

votes


















4














The monospaced font is assigned rigid interword space, which of course makes justification essentially impossible.



For efficiency reasons, a font is loaded only once, so your declaration has the effect of setting rigid interword space also for the main font.



Switch the order of declarations, as the “monospaced” font having flexible interword space should not be a concern.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


enter image description here



On the other hand, using urlstyle{rm} seems much easier.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
urlstyle{rm}

usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}





share|improve this answer





















  • OK, understood. But it seems to be unnecessary means to increase effiency. If I declare a different font, it also has to be loaded. By happenstance it was the same font, but for a different goal. If I want to really only load one font, I could say something like 'letttdefaultrmdefault'. And it is also intransparent.
    – Toscho
    Dec 9 at 10:59










  • @Toscho Remember that when TeX was born memory was scarce, so loading twice a font could hinder loading others. XeTeX follows essentially the same model, just allowing different types of fonts to be loaded: a new font selector that points to the same external font as another font selector, the new one is made equivalent to the previous. You could load the font with a slightly different magnification (Scale=1.001 should do).
    – egreg
    Dec 9 at 11:12










  • When XeTeX and LuaTeX were born, memory was no relevant ressource any more. And I see no reasony to differentiate between loading a font with a different scaling and loading it with fixed/variable interword space.
    – Toscho
    Dec 10 at 8:11










  • @Toscho I don't know about LuaTeX, but XeTeX hooked in TeX without making changes where not necessary. That's a documented behavior.
    – egreg
    Dec 10 at 8:24











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%2f463798%2fwhy-does-setmonofont-change-the-justifying-of-normal-text-using-the-same-font%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














The monospaced font is assigned rigid interword space, which of course makes justification essentially impossible.



For efficiency reasons, a font is loaded only once, so your declaration has the effect of setting rigid interword space also for the main font.



Switch the order of declarations, as the “monospaced” font having flexible interword space should not be a concern.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


enter image description here



On the other hand, using urlstyle{rm} seems much easier.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
urlstyle{rm}

usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}





share|improve this answer





















  • OK, understood. But it seems to be unnecessary means to increase effiency. If I declare a different font, it also has to be loaded. By happenstance it was the same font, but for a different goal. If I want to really only load one font, I could say something like 'letttdefaultrmdefault'. And it is also intransparent.
    – Toscho
    Dec 9 at 10:59










  • @Toscho Remember that when TeX was born memory was scarce, so loading twice a font could hinder loading others. XeTeX follows essentially the same model, just allowing different types of fonts to be loaded: a new font selector that points to the same external font as another font selector, the new one is made equivalent to the previous. You could load the font with a slightly different magnification (Scale=1.001 should do).
    – egreg
    Dec 9 at 11:12










  • When XeTeX and LuaTeX were born, memory was no relevant ressource any more. And I see no reasony to differentiate between loading a font with a different scaling and loading it with fixed/variable interword space.
    – Toscho
    Dec 10 at 8:11










  • @Toscho I don't know about LuaTeX, but XeTeX hooked in TeX without making changes where not necessary. That's a documented behavior.
    – egreg
    Dec 10 at 8:24
















4














The monospaced font is assigned rigid interword space, which of course makes justification essentially impossible.



For efficiency reasons, a font is loaded only once, so your declaration has the effect of setting rigid interword space also for the main font.



Switch the order of declarations, as the “monospaced” font having flexible interword space should not be a concern.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


enter image description here



On the other hand, using urlstyle{rm} seems much easier.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
urlstyle{rm}

usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}





share|improve this answer





















  • OK, understood. But it seems to be unnecessary means to increase effiency. If I declare a different font, it also has to be loaded. By happenstance it was the same font, but for a different goal. If I want to really only load one font, I could say something like 'letttdefaultrmdefault'. And it is also intransparent.
    – Toscho
    Dec 9 at 10:59










  • @Toscho Remember that when TeX was born memory was scarce, so loading twice a font could hinder loading others. XeTeX follows essentially the same model, just allowing different types of fonts to be loaded: a new font selector that points to the same external font as another font selector, the new one is made equivalent to the previous. You could load the font with a slightly different magnification (Scale=1.001 should do).
    – egreg
    Dec 9 at 11:12










  • When XeTeX and LuaTeX were born, memory was no relevant ressource any more. And I see no reasony to differentiate between loading a font with a different scaling and loading it with fixed/variable interword space.
    – Toscho
    Dec 10 at 8:11










  • @Toscho I don't know about LuaTeX, but XeTeX hooked in TeX without making changes where not necessary. That's a documented behavior.
    – egreg
    Dec 10 at 8:24














4












4








4






The monospaced font is assigned rigid interword space, which of course makes justification essentially impossible.



For efficiency reasons, a font is loaded only once, so your declaration has the effect of setting rigid interword space also for the main font.



Switch the order of declarations, as the “monospaced” font having flexible interword space should not be a concern.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


enter image description here



On the other hand, using urlstyle{rm} seems much easier.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
urlstyle{rm}

usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}





share|improve this answer












The monospaced font is assigned rigid interword space, which of course makes justification essentially impossible.



For efficiency reasons, a font is loaded only once, so your declaration has the effect of setting rigid interword space also for the main font.



Switch the order of declarations, as the “monospaced” font having flexible interword space should not be a concern.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmonofont[Ligatures=TeX]{TeX Gyre Pagella}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}


enter image description here



On the other hand, using urlstyle{rm} seems much easier.



documentclass[fromemail=true]{scrlttr2}
usepackage{fontspec}
setmainfont[Ligatures=TeX]{TeX Gyre Pagella}
usepackage{url}
setkomavar{fromname}{John Doe}
setkomavar{fromaddress}{Some Place\Somewhere}
setkomavar{fromemail}{url{john.doe@example.com}}
urlstyle{rm}

usepackage{lipsum}
begin{document}

begin{letter}{irgendwas}
setkomavar{toname}{People, who understand LaTeX{} better than me}
setkomavar{toaddress}{Maybe on Stackexchange}
setkomavar{subject}{Is this a bug?}

opening{Dear,}

lipsum[1]

closing{Regards}
end{letter}
end{document}






share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 8 at 11:39









egreg

708k8618813162




708k8618813162












  • OK, understood. But it seems to be unnecessary means to increase effiency. If I declare a different font, it also has to be loaded. By happenstance it was the same font, but for a different goal. If I want to really only load one font, I could say something like 'letttdefaultrmdefault'. And it is also intransparent.
    – Toscho
    Dec 9 at 10:59










  • @Toscho Remember that when TeX was born memory was scarce, so loading twice a font could hinder loading others. XeTeX follows essentially the same model, just allowing different types of fonts to be loaded: a new font selector that points to the same external font as another font selector, the new one is made equivalent to the previous. You could load the font with a slightly different magnification (Scale=1.001 should do).
    – egreg
    Dec 9 at 11:12










  • When XeTeX and LuaTeX were born, memory was no relevant ressource any more. And I see no reasony to differentiate between loading a font with a different scaling and loading it with fixed/variable interword space.
    – Toscho
    Dec 10 at 8:11










  • @Toscho I don't know about LuaTeX, but XeTeX hooked in TeX without making changes where not necessary. That's a documented behavior.
    – egreg
    Dec 10 at 8:24


















  • OK, understood. But it seems to be unnecessary means to increase effiency. If I declare a different font, it also has to be loaded. By happenstance it was the same font, but for a different goal. If I want to really only load one font, I could say something like 'letttdefaultrmdefault'. And it is also intransparent.
    – Toscho
    Dec 9 at 10:59










  • @Toscho Remember that when TeX was born memory was scarce, so loading twice a font could hinder loading others. XeTeX follows essentially the same model, just allowing different types of fonts to be loaded: a new font selector that points to the same external font as another font selector, the new one is made equivalent to the previous. You could load the font with a slightly different magnification (Scale=1.001 should do).
    – egreg
    Dec 9 at 11:12










  • When XeTeX and LuaTeX were born, memory was no relevant ressource any more. And I see no reasony to differentiate between loading a font with a different scaling and loading it with fixed/variable interword space.
    – Toscho
    Dec 10 at 8:11










  • @Toscho I don't know about LuaTeX, but XeTeX hooked in TeX without making changes where not necessary. That's a documented behavior.
    – egreg
    Dec 10 at 8:24
















OK, understood. But it seems to be unnecessary means to increase effiency. If I declare a different font, it also has to be loaded. By happenstance it was the same font, but for a different goal. If I want to really only load one font, I could say something like 'letttdefaultrmdefault'. And it is also intransparent.
– Toscho
Dec 9 at 10:59




OK, understood. But it seems to be unnecessary means to increase effiency. If I declare a different font, it also has to be loaded. By happenstance it was the same font, but for a different goal. If I want to really only load one font, I could say something like 'letttdefaultrmdefault'. And it is also intransparent.
– Toscho
Dec 9 at 10:59












@Toscho Remember that when TeX was born memory was scarce, so loading twice a font could hinder loading others. XeTeX follows essentially the same model, just allowing different types of fonts to be loaded: a new font selector that points to the same external font as another font selector, the new one is made equivalent to the previous. You could load the font with a slightly different magnification (Scale=1.001 should do).
– egreg
Dec 9 at 11:12




@Toscho Remember that when TeX was born memory was scarce, so loading twice a font could hinder loading others. XeTeX follows essentially the same model, just allowing different types of fonts to be loaded: a new font selector that points to the same external font as another font selector, the new one is made equivalent to the previous. You could load the font with a slightly different magnification (Scale=1.001 should do).
– egreg
Dec 9 at 11:12












When XeTeX and LuaTeX were born, memory was no relevant ressource any more. And I see no reasony to differentiate between loading a font with a different scaling and loading it with fixed/variable interword space.
– Toscho
Dec 10 at 8:11




When XeTeX and LuaTeX were born, memory was no relevant ressource any more. And I see no reasony to differentiate between loading a font with a different scaling and loading it with fixed/variable interword space.
– Toscho
Dec 10 at 8:11












@Toscho I don't know about LuaTeX, but XeTeX hooked in TeX without making changes where not necessary. That's a documented behavior.
– egreg
Dec 10 at 8:24




@Toscho I don't know about LuaTeX, but XeTeX hooked in TeX without making changes where not necessary. That's a documented behavior.
– egreg
Dec 10 at 8:24


















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.





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%2f463798%2fwhy-does-setmonofont-change-the-justifying-of-normal-text-using-the-same-font%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

How to change which sound is reproduced for terminal bell?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

Can I use Tabulator js library in my java Spring + Thymeleaf project?