protect hyphenated word from breaking
Consider this example:
documentclass{report}
begin{document}
bbbb bbbb bbbb ddf hdfhdf hdfhfd hdfhdf ddfgdfg dgdfg ert we Cabibbo-Kobayashi-Maskawa matrix is equal to 1
end{document}
The output is
Breaking the word
Cabibbo-Kobayashi-Maskawa
is not a good idea. Does hyphenation play a role in breaking and how can I protect this word from breaking?
line-breaking hyphenation
add a comment |
Consider this example:
documentclass{report}
begin{document}
bbbb bbbb bbbb ddf hdfhdf hdfhfd hdfhdf ddfgdfg dgdfg ert we Cabibbo-Kobayashi-Maskawa matrix is equal to 1
end{document}
The output is
Breaking the word
Cabibbo-Kobayashi-Maskawa
is not a good idea. Does hyphenation play a role in breaking and how can I protect this word from breaking?
line-breaking hyphenation
4
hyphens are normally break points, you can protect them, e.g. with mbox or with babel commands, but if you remove break points from such a large word, latex will have a hard time to break the line without creating an overfull box.
– Ulrike Fischer
7 hours ago
3
Why shouldn't it be a good idea?
– egreg
7 hours ago
@egreg, not appealing to a gourmet's exquisite taste
– Viesturs
7 hours ago
1
Would you prefer humongous spaces between words?
– egreg
7 hours ago
@egreg, for the sake of having a solution, yes
– Viesturs
7 hours ago
add a comment |
Consider this example:
documentclass{report}
begin{document}
bbbb bbbb bbbb ddf hdfhdf hdfhfd hdfhdf ddfgdfg dgdfg ert we Cabibbo-Kobayashi-Maskawa matrix is equal to 1
end{document}
The output is
Breaking the word
Cabibbo-Kobayashi-Maskawa
is not a good idea. Does hyphenation play a role in breaking and how can I protect this word from breaking?
line-breaking hyphenation
Consider this example:
documentclass{report}
begin{document}
bbbb bbbb bbbb ddf hdfhdf hdfhfd hdfhdf ddfgdfg dgdfg ert we Cabibbo-Kobayashi-Maskawa matrix is equal to 1
end{document}
The output is
Breaking the word
Cabibbo-Kobayashi-Maskawa
is not a good idea. Does hyphenation play a role in breaking and how can I protect this word from breaking?
line-breaking hyphenation
line-breaking hyphenation
edited 7 hours ago
Viesturs
asked 7 hours ago
ViestursViesturs
1,96841327
1,96841327
4
hyphens are normally break points, you can protect them, e.g. with mbox or with babel commands, but if you remove break points from such a large word, latex will have a hard time to break the line without creating an overfull box.
– Ulrike Fischer
7 hours ago
3
Why shouldn't it be a good idea?
– egreg
7 hours ago
@egreg, not appealing to a gourmet's exquisite taste
– Viesturs
7 hours ago
1
Would you prefer humongous spaces between words?
– egreg
7 hours ago
@egreg, for the sake of having a solution, yes
– Viesturs
7 hours ago
add a comment |
4
hyphens are normally break points, you can protect them, e.g. with mbox or with babel commands, but if you remove break points from such a large word, latex will have a hard time to break the line without creating an overfull box.
– Ulrike Fischer
7 hours ago
3
Why shouldn't it be a good idea?
– egreg
7 hours ago
@egreg, not appealing to a gourmet's exquisite taste
– Viesturs
7 hours ago
1
Would you prefer humongous spaces between words?
– egreg
7 hours ago
@egreg, for the sake of having a solution, yes
– Viesturs
7 hours ago
4
4
hyphens are normally break points, you can protect them, e.g. with mbox or with babel commands, but if you remove break points from such a large word, latex will have a hard time to break the line without creating an overfull box.
– Ulrike Fischer
7 hours ago
hyphens are normally break points, you can protect them, e.g. with mbox or with babel commands, but if you remove break points from such a large word, latex will have a hard time to break the line without creating an overfull box.
– Ulrike Fischer
7 hours ago
3
3
Why shouldn't it be a good idea?
– egreg
7 hours ago
Why shouldn't it be a good idea?
– egreg
7 hours ago
@egreg, not appealing to a gourmet's exquisite taste
– Viesturs
7 hours ago
@egreg, not appealing to a gourmet's exquisite taste
– Viesturs
7 hours ago
1
1
Would you prefer humongous spaces between words?
– egreg
7 hours ago
Would you prefer humongous spaces between words?
– egreg
7 hours ago
@egreg, for the sake of having a solution, yes
– Viesturs
7 hours ago
@egreg, for the sake of having a solution, yes
– Viesturs
7 hours ago
add a comment |
1 Answer
1
active
oldest
votes
If you really don't want to break a long hyphenated word, this is something to do in the final edits, because the naive solution (mbox{Cabbibo-Kobayashi-Maskawa}
) is likely to cause more aesthetic trouble than it saves. At this point you'll have to decide whether to reword the sentence (or even an earlier part of the paragraph) for reasons purely of appearance. That tweaking of the wording may be sufficient to fix the line breaking, or it may need to be combined with mbox{...}
.
I have used the mbox
approach without having to edit on much shorter phrases (mbox{$c$-axis}
). In this case it works well. In your case the compound word is over 1/3 of a line; in a two-column document you'd really struggle to get the breaking reasonable with it mbox
ed together.
The longest example in my thesis was mbox{x-positions}
; in papers I've only had to do this for even shorter strings (chemical formulae in physics papers set using normal text). It's probably best to reserve such tuning for situations where the comprehension of the text depends on it.
1
You can use$c$nobreakdash-axis
if you loadamsmath
.
– egreg
7 hours ago
1
@egreg, yes, and I did loadamsmath
but I find thembox
approach easier to read in the source. I should probably have written a macro for the "-axis" example as I discussed several, mention the c-axis quite a few times -- but this only came up in the final proofreading stage so I just fixed it the way I knew.
– Chris H
7 hours ago
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483922%2fprotect-hyphenated-word-from-breaking%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
If you really don't want to break a long hyphenated word, this is something to do in the final edits, because the naive solution (mbox{Cabbibo-Kobayashi-Maskawa}
) is likely to cause more aesthetic trouble than it saves. At this point you'll have to decide whether to reword the sentence (or even an earlier part of the paragraph) for reasons purely of appearance. That tweaking of the wording may be sufficient to fix the line breaking, or it may need to be combined with mbox{...}
.
I have used the mbox
approach without having to edit on much shorter phrases (mbox{$c$-axis}
). In this case it works well. In your case the compound word is over 1/3 of a line; in a two-column document you'd really struggle to get the breaking reasonable with it mbox
ed together.
The longest example in my thesis was mbox{x-positions}
; in papers I've only had to do this for even shorter strings (chemical formulae in physics papers set using normal text). It's probably best to reserve such tuning for situations where the comprehension of the text depends on it.
1
You can use$c$nobreakdash-axis
if you loadamsmath
.
– egreg
7 hours ago
1
@egreg, yes, and I did loadamsmath
but I find thembox
approach easier to read in the source. I should probably have written a macro for the "-axis" example as I discussed several, mention the c-axis quite a few times -- but this only came up in the final proofreading stage so I just fixed it the way I knew.
– Chris H
7 hours ago
add a comment |
If you really don't want to break a long hyphenated word, this is something to do in the final edits, because the naive solution (mbox{Cabbibo-Kobayashi-Maskawa}
) is likely to cause more aesthetic trouble than it saves. At this point you'll have to decide whether to reword the sentence (or even an earlier part of the paragraph) for reasons purely of appearance. That tweaking of the wording may be sufficient to fix the line breaking, or it may need to be combined with mbox{...}
.
I have used the mbox
approach without having to edit on much shorter phrases (mbox{$c$-axis}
). In this case it works well. In your case the compound word is over 1/3 of a line; in a two-column document you'd really struggle to get the breaking reasonable with it mbox
ed together.
The longest example in my thesis was mbox{x-positions}
; in papers I've only had to do this for even shorter strings (chemical formulae in physics papers set using normal text). It's probably best to reserve such tuning for situations where the comprehension of the text depends on it.
1
You can use$c$nobreakdash-axis
if you loadamsmath
.
– egreg
7 hours ago
1
@egreg, yes, and I did loadamsmath
but I find thembox
approach easier to read in the source. I should probably have written a macro for the "-axis" example as I discussed several, mention the c-axis quite a few times -- but this only came up in the final proofreading stage so I just fixed it the way I knew.
– Chris H
7 hours ago
add a comment |
If you really don't want to break a long hyphenated word, this is something to do in the final edits, because the naive solution (mbox{Cabbibo-Kobayashi-Maskawa}
) is likely to cause more aesthetic trouble than it saves. At this point you'll have to decide whether to reword the sentence (or even an earlier part of the paragraph) for reasons purely of appearance. That tweaking of the wording may be sufficient to fix the line breaking, or it may need to be combined with mbox{...}
.
I have used the mbox
approach without having to edit on much shorter phrases (mbox{$c$-axis}
). In this case it works well. In your case the compound word is over 1/3 of a line; in a two-column document you'd really struggle to get the breaking reasonable with it mbox
ed together.
The longest example in my thesis was mbox{x-positions}
; in papers I've only had to do this for even shorter strings (chemical formulae in physics papers set using normal text). It's probably best to reserve such tuning for situations where the comprehension of the text depends on it.
If you really don't want to break a long hyphenated word, this is something to do in the final edits, because the naive solution (mbox{Cabbibo-Kobayashi-Maskawa}
) is likely to cause more aesthetic trouble than it saves. At this point you'll have to decide whether to reword the sentence (or even an earlier part of the paragraph) for reasons purely of appearance. That tweaking of the wording may be sufficient to fix the line breaking, or it may need to be combined with mbox{...}
.
I have used the mbox
approach without having to edit on much shorter phrases (mbox{$c$-axis}
). In this case it works well. In your case the compound word is over 1/3 of a line; in a two-column document you'd really struggle to get the breaking reasonable with it mbox
ed together.
The longest example in my thesis was mbox{x-positions}
; in papers I've only had to do this for even shorter strings (chemical formulae in physics papers set using normal text). It's probably best to reserve such tuning for situations where the comprehension of the text depends on it.
edited 7 hours ago
answered 7 hours ago
Chris HChris H
6,48622157
6,48622157
1
You can use$c$nobreakdash-axis
if you loadamsmath
.
– egreg
7 hours ago
1
@egreg, yes, and I did loadamsmath
but I find thembox
approach easier to read in the source. I should probably have written a macro for the "-axis" example as I discussed several, mention the c-axis quite a few times -- but this only came up in the final proofreading stage so I just fixed it the way I knew.
– Chris H
7 hours ago
add a comment |
1
You can use$c$nobreakdash-axis
if you loadamsmath
.
– egreg
7 hours ago
1
@egreg, yes, and I did loadamsmath
but I find thembox
approach easier to read in the source. I should probably have written a macro for the "-axis" example as I discussed several, mention the c-axis quite a few times -- but this only came up in the final proofreading stage so I just fixed it the way I knew.
– Chris H
7 hours ago
1
1
You can use
$c$nobreakdash-axis
if you load amsmath
.– egreg
7 hours ago
You can use
$c$nobreakdash-axis
if you load amsmath
.– egreg
7 hours ago
1
1
@egreg, yes, and I did load
amsmath
but I find the mbox
approach easier to read in the source. I should probably have written a macro for the "-axis" example as I discussed several, mention the c-axis quite a few times -- but this only came up in the final proofreading stage so I just fixed it the way I knew.– Chris H
7 hours ago
@egreg, yes, and I did load
amsmath
but I find the mbox
approach easier to read in the source. I should probably have written a macro for the "-axis" example as I discussed several, mention the c-axis quite a few times -- but this only came up in the final proofreading stage so I just fixed it the way I knew.– Chris H
7 hours ago
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483922%2fprotect-hyphenated-word-from-breaking%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
4
hyphens are normally break points, you can protect them, e.g. with mbox or with babel commands, but if you remove break points from such a large word, latex will have a hard time to break the line without creating an overfull box.
– Ulrike Fischer
7 hours ago
3
Why shouldn't it be a good idea?
– egreg
7 hours ago
@egreg, not appealing to a gourmet's exquisite taste
– Viesturs
7 hours ago
1
Would you prefer humongous spaces between words?
– egreg
7 hours ago
@egreg, for the sake of having a solution, yes
– Viesturs
7 hours ago