Artifacts from Latex configuration showing in output
I've written some Latex in my doxygen comment that looks like this...
/*!
@note
@latexonly
documentclass{article}
usepackage{courier}
lstset{basicstyle=footnotesizettfamily}
begin{document}
fontsize{10pt}{12pt}selectfont
newpage
begin{verbatim}
CONTENT
end{verbatim}
end{document}
@endlatexonly
*/
Produces this after running 'pdflatex'
article courier
basicstyle=
(PageBreak: No text in PDF)
CONTENT
What am I doing wrong? I just wanted to set the text to a monospace font and have it output verbatim.
Note: I'm running MikTeX 2.9 on windows 7
Update:
I Took a look in the .tex file doxygen makes for the class with this comment and found this.
begin{DoxyNote}{Note}
//Everything above
end{DoxyNote}
Could that create the odd things I'm seeing?
Update 2:
I found this,
Starts a block of text that will be verbatim included in the generated
LaTeX documentation only.
So that tells me MiKTeX doesn't like those labels. When doxygen creates the .Tex files this bit shows up in the middle. Does LaTeX have rules about defining a preamble in the middle of a document? This is the first thing I've ever done in LaTeX so I'm not surprised that I'm having issues.
I did some testing and when I remove documentclass,begin{document} and end{document} it didn't get rid of the artifacts but it did fix some other problems I opened another question about funny enough. And then moved to here
pdf miktex output
edited 16 mins ago
albert
625414
asked Aug 13 '13 at 19:20
Dan
1216
add a comment |
I've written some Latex in my doxygen comment that looks like this...
/*!
@note
@latexonly
documentclass{article}
usepackage{courier}
lstset{basicstyle=footnotesizettfamily}
begin{document}
fontsize{10pt}{12pt}selectfont
newpage
begin{verbatim}
CONTENT
end{verbatim}
end{document}
@endlatexonly
*/
Produces this after running 'pdflatex'
article courier
basicstyle=
(PageBreak: No text in PDF)
CONTENT
What am I doing wrong? I just wanted to set the text to a monospace font and have it output verbatim.
Note: I'm running MikTeX 2.9 on windows 7
Update:
I Took a look in the .tex file doxygen makes for the class with this comment and found this.
begin{DoxyNote}{Note}
//Everything above
end{DoxyNote}
Could that create the odd things I'm seeing?
Update 2:
I found this,
Starts a block of text that will be verbatim included in the generated
LaTeX documentation only.
So that tells me MiKTeX doesn't like those labels. When doxygen creates the .Tex files this bit shows up in the middle. Does LaTeX have rules about defining a preamble in the middle of a document? This is the first thing I've ever done in LaTeX so I'm not surprised that I'm having issues.
I did some testing and when I remove documentclass,begin{document} and end{document} it didn't get rid of the artifacts but it did fix some other problems I opened another question about funny enough. And then moved to here
pdf miktex output
edited 16 mins ago
albert
625414
asked Aug 13 '13 at 19:20
Dan
1216
Can't help withDoxygen, but doesn't the commandlstsetrequire you to load something like thelistingspackage (i.e.,usepackage{listings})?
– jon
Aug 13 '13 at 21:41
I honestly couldn't tell you I adapted an example from here. I am usingusepackage{courier}right before that line. And from what the link mentioned that was sottfamilycould use it.
– Dan
Aug 13 '13 at 21:50
@jon oh you're right it's for setting listings to courier. Could you tell me how to set the content section to courier correctly then?
– Dan
Aug 13 '13 at 21:55
It (a normal LaTeX document) should work as long as you add the lineusepackage{listings}. The fontsize can more easily be set to 10pt by loading it as an option to your documentclass:documentclass[10pt]{article}. ... But how that all interacts/works withDoxygenis not something I can competently answer.
– jon
Aug 13 '13 at 22:08
@jon now I'm gettingarticle listings courier basicstyle=:p. I get the feeling this might be Doxygen but lets not count out my noob-ness either. Thanks for trying to help.
– Dan
Aug 13 '13 at 23:01
add a comment |
I've written some Latex in my doxygen comment that looks like this...
/*!
@note
@latexonly
documentclass{article}
usepackage{courier}
lstset{basicstyle=footnotesizettfamily}
begin{document}
fontsize{10pt}{12pt}selectfont
newpage
begin{verbatim}
CONTENT
end{verbatim}
end{document}
@endlatexonly
*/
Produces this after running 'pdflatex'
article courier
basicstyle=
(PageBreak: No text in PDF)
CONTENT
What am I doing wrong? I just wanted to set the text to a monospace font and have it output verbatim.
Note: I'm running MikTeX 2.9 on windows 7
Update:
I Took a look in the .tex file doxygen makes for the class with this comment and found this.
begin{DoxyNote}{Note}
//Everything above
end{DoxyNote}
Could that create the odd things I'm seeing?
Update 2:
I found this,
Starts a block of text that will be verbatim included in the generated
LaTeX documentation only.
So that tells me MiKTeX doesn't like those labels. When doxygen creates the .Tex files this bit shows up in the middle. Does LaTeX have rules about defining a preamble in the middle of a document? This is the first thing I've ever done in LaTeX so I'm not surprised that I'm having issues.
I did some testing and when I remove documentclass,begin{document} and end{document} it didn't get rid of the artifacts but it did fix some other problems I opened another question about funny enough. And then moved to here
pdf miktex output
edited 16 mins ago
albert
625414
asked Aug 13 '13 at 19:20
Dan
1216
I've written some Latex in my doxygen comment that looks like this...
/*!
@note
@latexonly
documentclass{article}
usepackage{courier}
lstset{basicstyle=footnotesizettfamily}
begin{document}
fontsize{10pt}{12pt}selectfont
newpage
begin{verbatim}
CONTENT
end{verbatim}
end{document}
@endlatexonly
*/
Produces this after running 'pdflatex'
article courier
basicstyle=
(PageBreak: No text in PDF)
CONTENT
What am I doing wrong? I just wanted to set the text to a monospace font and have it output verbatim.
Note: I'm running MikTeX 2.9 on windows 7
Update:
I Took a look in the .tex file doxygen makes for the class with this comment and found this.
begin{DoxyNote}{Note}
//Everything above
end{DoxyNote}
Could that create the odd things I'm seeing?
Update 2:
I found this,
Starts a block of text that will be verbatim included in the generated
LaTeX documentation only.
So that tells me MiKTeX doesn't like those labels. When doxygen creates the .Tex files this bit shows up in the middle. Does LaTeX have rules about defining a preamble in the middle of a document? This is the first thing I've ever done in LaTeX so I'm not surprised that I'm having issues.
I did some testing and when I remove documentclass,begin{document} and end{document} it didn't get rid of the artifacts but it did fix some other problems I opened another question about funny enough. And then moved to here
pdf miktex output
pdf miktex output
edited 16 mins ago
albert
625414
asked Aug 13 '13 at 19:20
Dan
1216
edited 16 mins ago
albert
625414
asked Aug 13 '13 at 19:20
Dan
1216
edited 16 mins ago
albert
625414
edited 16 mins ago
albert
625414
edited 16 mins ago
albert
625414
625414
asked Aug 13 '13 at 19:20
Dan
1216
asked Aug 13 '13 at 19:20
Dan
1216
asked Aug 13 '13 at 19:20
Dan
1216
1216
Can't help withDoxygen, but doesn't the commandlstsetrequire you to load something like thelistingspackage (i.e.,usepackage{listings})?
– jon
Aug 13 '13 at 21:41
I honestly couldn't tell you I adapted an example from here. I am usingusepackage{courier}right before that line. And from what the link mentioned that was sottfamilycould use it.
– Dan
Aug 13 '13 at 21:50
@jon oh you're right it's for setting listings to courier. Could you tell me how to set the content section to courier correctly then?
– Dan
Aug 13 '13 at 21:55
It (a normal LaTeX document) should work as long as you add the lineusepackage{listings}. The fontsize can more easily be set to 10pt by loading it as an option to your documentclass:documentclass[10pt]{article}. ... But how that all interacts/works withDoxygenis not something I can competently answer.
– jon
Aug 13 '13 at 22:08
@jon now I'm gettingarticle listings courier basicstyle=:p. I get the feeling this might be Doxygen but lets not count out my noob-ness either. Thanks for trying to help.
– Dan
Aug 13 '13 at 23:01
add a comment |
Can't help withDoxygen, but doesn't the commandlstsetrequire you to load something like thelistingspackage (i.e.,usepackage{listings})?
– jon
Aug 13 '13 at 21:41
I honestly couldn't tell you I adapted an example from here. I am usingusepackage{courier}right before that line. And from what the link mentioned that was sottfamilycould use it.
– Dan
Aug 13 '13 at 21:50
@jon oh you're right it's for setting listings to courier. Could you tell me how to set the content section to courier correctly then?
– Dan
Aug 13 '13 at 21:55
It (a normal LaTeX document) should work as long as you add the lineusepackage{listings}. The fontsize can more easily be set to 10pt by loading it as an option to your documentclass:documentclass[10pt]{article}. ... But how that all interacts/works withDoxygenis not something I can competently answer.
– jon
Aug 13 '13 at 22:08
@jon now I'm gettingarticle listings courier basicstyle=:p. I get the feeling this might be Doxygen but lets not count out my noob-ness either. Thanks for trying to help.
– Dan
Aug 13 '13 at 23:01
Can't help with
Doxygen, but doesn't the command lstset require you to load something like the listings package (i.e., usepackage{listings})?– jon
Aug 13 '13 at 21:41
Can't help with
Doxygen, but doesn't the command lstset require you to load something like the listings package (i.e., usepackage{listings})?– jon
Aug 13 '13 at 21:41
I honestly couldn't tell you I adapted an example from here. I am using
usepackage{courier} right before that line. And from what the link mentioned that was so ttfamily could use it.– Dan
Aug 13 '13 at 21:50
I honestly couldn't tell you I adapted an example from here. I am using
usepackage{courier} right before that line. And from what the link mentioned that was so ttfamily could use it.– Dan
Aug 13 '13 at 21:50
@jon oh you're right it's for setting listings to courier. Could you tell me how to set the content section to courier correctly then?
– Dan
Aug 13 '13 at 21:55
@jon oh you're right it's for setting listings to courier. Could you tell me how to set the content section to courier correctly then?
– Dan
Aug 13 '13 at 21:55
It (a normal LaTeX document) should work as long as you add the line
usepackage{listings}. The fontsize can more easily be set to 10pt by loading it as an option to your documentclass: documentclass[10pt]{article}. ... But how that all interacts/works with Doxygen is not something I can competently answer.– jon
Aug 13 '13 at 22:08
It (a normal LaTeX document) should work as long as you add the line
usepackage{listings}. The fontsize can more easily be set to 10pt by loading it as an option to your documentclass: documentclass[10pt]{article}. ... But how that all interacts/works with Doxygen is not something I can competently answer.– jon
Aug 13 '13 at 22:08
@jon now I'm getting
article listings courier basicstyle= :p. I get the feeling this might be Doxygen but lets not count out my noob-ness either. Thanks for trying to help.– Dan
Aug 13 '13 at 23:01
@jon now I'm getting
article listings courier basicstyle= :p. I get the feeling this might be Doxygen but lets not count out my noob-ness either. Thanks for trying to help.– Dan
Aug 13 '13 at 23:01
add a comment |
1 Answer
1
active
oldest
votes
EUREKA!
The labels you add in Doxygen comments are inside a begin{document} or something like it. So preamble (I think that's what definitions like usepackage are called) aren't valid syntax there.
So what was happening was the COMMANDS would be absorbed, deemed invalid there and the arguments would come through as plain text.
So the answer was to this is...
/*!
@note
@latexonly
newpage
fontsize{10pt}{12pt}selectfont
ttfamily
begin{verbatim}
CONTENT
end{verbatim}
@endlatexonly
*/
Strictly speaking all ttfamily guarantees is a monospaced font but that's all I wanted.
:)
answered Aug 14 '13 at 0:42
Dan
1216
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%2f128084%2fartifacts-from-latex-configuration-showing-in-output%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
EUREKA!
The labels you add in Doxygen comments are inside a begin{document} or something like it. So preamble (I think that's what definitions like usepackage are called) aren't valid syntax there.
So what was happening was the COMMANDS would be absorbed, deemed invalid there and the arguments would come through as plain text.
So the answer was to this is...
/*!
@note
@latexonly
newpage
fontsize{10pt}{12pt}selectfont
ttfamily
begin{verbatim}
CONTENT
end{verbatim}
@endlatexonly
*/
Strictly speaking all ttfamily guarantees is a monospaced font but that's all I wanted.
:)
answered Aug 14 '13 at 0:42
Dan
1216
add a comment |
EUREKA!
The labels you add in Doxygen comments are inside a begin{document} or something like it. So preamble (I think that's what definitions like usepackage are called) aren't valid syntax there.
So what was happening was the COMMANDS would be absorbed, deemed invalid there and the arguments would come through as plain text.
So the answer was to this is...
/*!
@note
@latexonly
newpage
fontsize{10pt}{12pt}selectfont
ttfamily
begin{verbatim}
CONTENT
end{verbatim}
@endlatexonly
*/
Strictly speaking all ttfamily guarantees is a monospaced font but that's all I wanted.
:)
answered Aug 14 '13 at 0:42
Dan
1216
add a comment |
EUREKA!
The labels you add in Doxygen comments are inside a begin{document} or something like it. So preamble (I think that's what definitions like usepackage are called) aren't valid syntax there.
So what was happening was the COMMANDS would be absorbed, deemed invalid there and the arguments would come through as plain text.
So the answer was to this is...
/*!
@note
@latexonly
newpage
fontsize{10pt}{12pt}selectfont
ttfamily
begin{verbatim}
CONTENT
end{verbatim}
@endlatexonly
*/
Strictly speaking all ttfamily guarantees is a monospaced font but that's all I wanted.
:)
answered Aug 14 '13 at 0:42
Dan
1216
EUREKA!
The labels you add in Doxygen comments are inside a begin{document} or something like it. So preamble (I think that's what definitions like usepackage are called) aren't valid syntax there.
So what was happening was the COMMANDS would be absorbed, deemed invalid there and the arguments would come through as plain text.
So the answer was to this is...
/*!
@note
@latexonly
newpage
fontsize{10pt}{12pt}selectfont
ttfamily
begin{verbatim}
CONTENT
end{verbatim}
@endlatexonly
*/
Strictly speaking all ttfamily guarantees is a monospaced font but that's all I wanted.
:)
answered Aug 14 '13 at 0:42
Dan
1216
answered Aug 14 '13 at 0:42
Dan
1216
answered Aug 14 '13 at 0:42
Dan
1216
answered Aug 14 '13 at 0:42
Dan
1216
1216
add a comment |
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%2f128084%2fartifacts-from-latex-configuration-showing-in-output%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't help with
Doxygen, but doesn't the commandlstsetrequire you to load something like thelistingspackage (i.e.,usepackage{listings})?– jon
Aug 13 '13 at 21:41
I honestly couldn't tell you I adapted an example from here. I am using
usepackage{courier}right before that line. And from what the link mentioned that was sottfamilycould use it.– Dan
Aug 13 '13 at 21:50
@jon oh you're right it's for setting listings to courier. Could you tell me how to set the content section to courier correctly then?
– Dan
Aug 13 '13 at 21:55
It (a normal LaTeX document) should work as long as you add the line
usepackage{listings}. The fontsize can more easily be set to 10pt by loading it as an option to your documentclass:documentclass[10pt]{article}. ... But how that all interacts/works withDoxygenis not something I can competently answer.– jon
Aug 13 '13 at 22:08
@jon now I'm getting
article listings courier basicstyle=:p. I get the feeling this might be Doxygen but lets not count out my noob-ness either. Thanks for trying to help.– Dan
Aug 13 '13 at 23:01