Software Documentation Dot-Operator/Period Hyphenation
I'm still new-ish to latex, and I'm trying to document some software using the tool. I'm referencing local terms that are long and contain periods/dot-operators. I know how/why Latex doesn't like to hyphenate words with periods from this question:
Babel fails to hyphenate when the word contains periods
I found the post to not be so helpful. All these double quotes shortcuts don't make sense with the number of times I'm using these terms.
My understanding so far with Latex leads me to believe that this should be easily accomplished with some soft of function in the header (or editing hyphenation source) where if there is no space after a period make that word "hyphenable" after said period.
ORR... it would be even more awesome if there was a package that did this that i just haven't heard about yet.
Any help on this matter would be appreciated.
packages hyphenation package-writing
asked Dec 12 '18 at 16:30
CharlieBrown
82
add a comment |
I'm still new-ish to latex, and I'm trying to document some software using the tool. I'm referencing local terms that are long and contain periods/dot-operators. I know how/why Latex doesn't like to hyphenate words with periods from this question:
Babel fails to hyphenate when the word contains periods
I found the post to not be so helpful. All these double quotes shortcuts don't make sense with the number of times I'm using these terms.
My understanding so far with Latex leads me to believe that this should be easily accomplished with some soft of function in the header (or editing hyphenation source) where if there is no space after a period make that word "hyphenable" after said period.
ORR... it would be even more awesome if there was a package that did this that i just haven't heard about yet.
Any help on this matter would be appreciated.
packages hyphenation package-writing
asked Dec 12 '18 at 16:30
CharlieBrown
82
Can you give an example of something you'd like to hyphenate?
– samcarter
Dec 12 '18 at 16:41
@samcarter a suitable example may be IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature They are quite long, but very precise. Which what was asked of me.
– CharlieBrown
Dec 12 '18 at 17:03
add a comment |
I'm still new-ish to latex, and I'm trying to document some software using the tool. I'm referencing local terms that are long and contain periods/dot-operators. I know how/why Latex doesn't like to hyphenate words with periods from this question:
Babel fails to hyphenate when the word contains periods
I found the post to not be so helpful. All these double quotes shortcuts don't make sense with the number of times I'm using these terms.
My understanding so far with Latex leads me to believe that this should be easily accomplished with some soft of function in the header (or editing hyphenation source) where if there is no space after a period make that word "hyphenable" after said period.
ORR... it would be even more awesome if there was a package that did this that i just haven't heard about yet.
Any help on this matter would be appreciated.
packages hyphenation package-writing
asked Dec 12 '18 at 16:30
CharlieBrown
82
I'm still new-ish to latex, and I'm trying to document some software using the tool. I'm referencing local terms that are long and contain periods/dot-operators. I know how/why Latex doesn't like to hyphenate words with periods from this question:
Babel fails to hyphenate when the word contains periods
I found the post to not be so helpful. All these double quotes shortcuts don't make sense with the number of times I'm using these terms.
My understanding so far with Latex leads me to believe that this should be easily accomplished with some soft of function in the header (or editing hyphenation source) where if there is no space after a period make that word "hyphenable" after said period.
ORR... it would be even more awesome if there was a package that did this that i just haven't heard about yet.
Any help on this matter would be appreciated.
packages hyphenation package-writing
packages hyphenation package-writing
asked Dec 12 '18 at 16:30
CharlieBrown
82
asked Dec 12 '18 at 16:30
CharlieBrown
82
asked Dec 12 '18 at 16:30
CharlieBrown
82
asked Dec 12 '18 at 16:30
CharlieBrown
82
asked Dec 12 '18 at 16:30
CharlieBrown
82
82
Can you give an example of something you'd like to hyphenate?
– samcarter
Dec 12 '18 at 16:41
@samcarter a suitable example may be IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature They are quite long, but very precise. Which what was asked of me.
– CharlieBrown
Dec 12 '18 at 17:03
add a comment |
Can you give an example of something you'd like to hyphenate?
– samcarter
Dec 12 '18 at 16:41
@samcarter a suitable example may be IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature They are quite long, but very precise. Which what was asked of me.
– CharlieBrown
Dec 12 '18 at 17:03
Can you give an example of something you'd like to hyphenate?
– samcarter
Dec 12 '18 at 16:41
Can you give an example of something you'd like to hyphenate?
– samcarter
Dec 12 '18 at 16:41
@samcarter a suitable example may be IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature They are quite long, but very precise. Which what was asked of me.
– CharlieBrown
Dec 12 '18 at 17:03
@samcarter a suitable example may be IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature They are quite long, but very precise. Which what was asked of me.
– CharlieBrown
Dec 12 '18 at 17:03
add a comment |
1 Answer
1
active
oldest
votes
I would suggest to treat such terms as verbatim material. You can allow linebreaks e.g. with the listings package and lstinline[breaklines=true]
documentclass{article}
usepackage{listings}
begin{document}
test test test test test test test test test test test test lstinline[breaklines=true]|IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature|
end{document}
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
This seems to work pretty awesome. It's a little impractical to keep writing this out in the text considering how many times these items are referenced. But, I decided to add it in a variable definition at the start of the document. This ended up helping on multiple fronts. Now, i have a variable with a shorter name that I can write by reference. Also, because it's by reference if the signal name ever changes I only need to edit the definition... something I should have been doing before anyway with the # of occurrences I'm dealing with and potential volatility in its name. You rock! Thanks!
– CharlieBrown
Dec 12 '18 at 19:30
@CharlieBrown You're welcome!
– samcarter
Dec 12 '18 at 20:53
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%2f464552%2fsoftware-documentation-dot-operator-period-hyphenation%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
I would suggest to treat such terms as verbatim material. You can allow linebreaks e.g. with the listings package and lstinline[breaklines=true]
documentclass{article}
usepackage{listings}
begin{document}
test test test test test test test test test test test test lstinline[breaklines=true]|IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature|
end{document}
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
This seems to work pretty awesome. It's a little impractical to keep writing this out in the text considering how many times these items are referenced. But, I decided to add it in a variable definition at the start of the document. This ended up helping on multiple fronts. Now, i have a variable with a shorter name that I can write by reference. Also, because it's by reference if the signal name ever changes I only need to edit the definition... something I should have been doing before anyway with the # of occurrences I'm dealing with and potential volatility in its name. You rock! Thanks!
– CharlieBrown
Dec 12 '18 at 19:30
@CharlieBrown You're welcome!
– samcarter
Dec 12 '18 at 20:53
add a comment |
I would suggest to treat such terms as verbatim material. You can allow linebreaks e.g. with the listings package and lstinline[breaklines=true]
documentclass{article}
usepackage{listings}
begin{document}
test test test test test test test test test test test test lstinline[breaklines=true]|IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature|
end{document}
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
This seems to work pretty awesome. It's a little impractical to keep writing this out in the text considering how many times these items are referenced. But, I decided to add it in a variable definition at the start of the document. This ended up helping on multiple fronts. Now, i have a variable with a shorter name that I can write by reference. Also, because it's by reference if the signal name ever changes I only need to edit the definition... something I should have been doing before anyway with the # of occurrences I'm dealing with and potential volatility in its name. You rock! Thanks!
– CharlieBrown
Dec 12 '18 at 19:30
@CharlieBrown You're welcome!
– samcarter
Dec 12 '18 at 20:53
add a comment |
I would suggest to treat such terms as verbatim material. You can allow linebreaks e.g. with the listings package and lstinline[breaklines=true]
documentclass{article}
usepackage{listings}
begin{document}
test test test test test test test test test test test test lstinline[breaklines=true]|IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature|
end{document}
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
I would suggest to treat such terms as verbatim material. You can allow linebreaks e.g. with the listings package and lstinline[breaklines=true]
documentclass{article}
usepackage{listings}
begin{document}
test test test test test test test test test test test test lstinline[breaklines=true]|IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature|
end{document}
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
answered Dec 12 '18 at 17:09
samcarter
85.8k794275
85.8k794275
This seems to work pretty awesome. It's a little impractical to keep writing this out in the text considering how many times these items are referenced. But, I decided to add it in a variable definition at the start of the document. This ended up helping on multiple fronts. Now, i have a variable with a shorter name that I can write by reference. Also, because it's by reference if the signal name ever changes I only need to edit the definition... something I should have been doing before anyway with the # of occurrences I'm dealing with and potential volatility in its name. You rock! Thanks!
– CharlieBrown
Dec 12 '18 at 19:30
@CharlieBrown You're welcome!
– samcarter
Dec 12 '18 at 20:53
add a comment |
This seems to work pretty awesome. It's a little impractical to keep writing this out in the text considering how many times these items are referenced. But, I decided to add it in a variable definition at the start of the document. This ended up helping on multiple fronts. Now, i have a variable with a shorter name that I can write by reference. Also, because it's by reference if the signal name ever changes I only need to edit the definition... something I should have been doing before anyway with the # of occurrences I'm dealing with and potential volatility in its name. You rock! Thanks!
– CharlieBrown
Dec 12 '18 at 19:30
@CharlieBrown You're welcome!
– samcarter
Dec 12 '18 at 20:53
This seems to work pretty awesome. It's a little impractical to keep writing this out in the text considering how many times these items are referenced. But, I decided to add it in a variable definition at the start of the document. This ended up helping on multiple fronts. Now, i have a variable with a shorter name that I can write by reference. Also, because it's by reference if the signal name ever changes I only need to edit the definition... something I should have been doing before anyway with the # of occurrences I'm dealing with and potential volatility in its name. You rock! Thanks!
– CharlieBrown
Dec 12 '18 at 19:30
This seems to work pretty awesome. It's a little impractical to keep writing this out in the text considering how many times these items are referenced. But, I decided to add it in a variable definition at the start of the document. This ended up helping on multiple fronts. Now, i have a variable with a shorter name that I can write by reference. Also, because it's by reference if the signal name ever changes I only need to edit the definition... something I should have been doing before anyway with the # of occurrences I'm dealing with and potential volatility in its name. You rock! Thanks!
– CharlieBrown
Dec 12 '18 at 19:30
@CharlieBrown You're welcome!
– samcarter
Dec 12 '18 at 20:53
@CharlieBrown You're welcome!
– samcarter
Dec 12 '18 at 20:53
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.
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.
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%2f464552%2fsoftware-documentation-dot-operator-period-hyphenation%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
Can you give an example of something you'd like to hyphenate?
– samcarter
Dec 12 '18 at 16:41
@samcarter a suitable example may be IN_CAN0.SA0xGG.TeamProprietaryMsg.FeatureStatus_SubFeature They are quite long, but very precise. Which what was asked of me.
– CharlieBrown
Dec 12 '18 at 17:03