SWI Prolog documentation generator tags environment: tag not allowedEnumerate and itemize undefined +...
Why do Radio Buttons not fill the entire outer circle?
How to get directions in deep space?
Does Doodling or Improvising on the Piano Have Any Benefits?
Given this phrasing in the lease, when should I pay my rent?
Deciphering cause of death?
When and why was runway 07/25 at Kai Tak removed?
Should I warn a new PhD Student?
"Oh no!" in Latin
Check if object is null and return null
If the only attacker is removed from combat, is a creature still counted as having attacked this turn?
Do you waste sorcery points if you try to apply metamagic to a spell from a scroll but fail to cast it?
If Captain Marvel (MCU) were to have a child with a human male, would the child be human or Kree?
ContourPlot — How do I color by contour curvature?
Sigmoid with a slope but no asymptotes?
What is the meaning of "You've never met a graph you didn't like?"
Why is the principal energy of an electron lower for excited electrons in a higher energy state?
How do you justify more code being written by following clean code practices?
SOQL query causes internal Salesforce error
How would a solely written language work mechanically
What is this high flying aircraft over Pennsylvania?
Sound waves in different octaves
Is there anyway, I can have two passwords for my wi-fi
How do I prevent inappropriate ads from appearing in my game?
Are Captain Marvel's powers affected by Thanos breaking the Tesseract and claiming the stone?
SWI Prolog documentation generator tags environment: tag not allowed
Enumerate and itemize undefined + captions not workingLaTeX Error: File subfigure.sty not foundarray environment with tags/labels! Package amsmath Error: tag not allowed hereError message while compiling labeled equation in align in newenvironment. It says some other labels will be lostWhat does this input encoding error mean?Does amsmath treat double dollars and `[' `]' delimiters differently?Can't generate png with Error: Erroneous nesting of equation structuresEquations not properly centered when using tag in gather* environmentTrouble with displayquote and page numbers for citations
I'm trying to generate documentation using SWI Prolog PlDoc package, but I'm running into a problem with the environment defined in pldoc.sty:
newcommand{tag}[1]{%
item[#1]}
...
% begin{tags} ... end{tags}
newenvironment{tags}%
{begin{quote}begin{description}%
setlength{itemsep}{0pt}%
footnotesize}%
{end{description}end{quote}}
This is used in the generated TeX file as follows:
subsection{automata.pl: High-level predicates for dealing with regular expressions}
label{sec:automata}
begin{tags}
tag{See also}
url{https://github.com/wvxvw/intro-to-automata-theory}
tag{To be done}
Add predref{match_suffix_regex}{3}, predref{match_all_regex}{3}, predref{find_regex}{3}
end{tags}
Which I insert into a larger document as follows:
documentclass[11pt]{article}
...
usepackage{amsmath}
...
usepackage{pldoc}
...
begin{document}
...
section{Appendix A}
label{sec:orgheadline18}
input{automata-doc}
end{document}
When I try to generate PDF using latexmk with pdflatex I receive the following error:
! Package amsmath Error: tag not allowed here.
See the amsmath package documentation for explanation.
Type H <return> for immediate help.
...
l.253 tag
{See also}
However, when I generate standalone documentation (which does not use amsmath package), this error doesn't happen. My guess is that amsmath is messing things up, but I don't know how to prevent it from interfering.
errors amsmath
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
|
show 5 more comments
I'm trying to generate documentation using SWI Prolog PlDoc package, but I'm running into a problem with the environment defined in pldoc.sty:
newcommand{tag}[1]{%
item[#1]}
...
% begin{tags} ... end{tags}
newenvironment{tags}%
{begin{quote}begin{description}%
setlength{itemsep}{0pt}%
footnotesize}%
{end{description}end{quote}}
This is used in the generated TeX file as follows:
subsection{automata.pl: High-level predicates for dealing with regular expressions}
label{sec:automata}
begin{tags}
tag{See also}
url{https://github.com/wvxvw/intro-to-automata-theory}
tag{To be done}
Add predref{match_suffix_regex}{3}, predref{match_all_regex}{3}, predref{find_regex}{3}
end{tags}
Which I insert into a larger document as follows:
documentclass[11pt]{article}
...
usepackage{amsmath}
...
usepackage{pldoc}
...
begin{document}
...
section{Appendix A}
label{sec:orgheadline18}
input{automata-doc}
end{document}
When I try to generate PDF using latexmk with pdflatex I receive the following error:
! Package amsmath Error: tag not allowed here.
See the amsmath package documentation for explanation.
Type H <return> for immediate help.
...
l.253 tag
{See also}
However, when I generate standalone documentation (which does not use amsmath package), this error doesn't happen. My guess is that amsmath is messing things up, but I don't know how to prevent it from interfering.
errors amsmath
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
1
tagis an important command inamsmath-- the definition in your.styfile clashes here. Since I've no access topldoc.styI can't test, but I suggest to copy thetagdefinition frompldoc.styand rename itpltag, as well replacing anytag{...}in your real document withpltag{...}accordingly.
– user31729
Sep 20 '15 at 21:22
@ChristianHupfer technically, the.styisn't my. Should I write to the maintainer to alert them to the problem, or is this something that I can remedy locally (without having to modify the said.sty)?
– wvxvw
Sep 20 '15 at 21:23
1
You should not modify the.styat all. Writing to the maintainer is certainly a good idea
– user31729
Sep 20 '15 at 21:24
Note that LaTeX must have given earlier errors. It will have told you thattagwas not available to be created as a new command, for example. You ignore such errors at your peril!
– cfr
Sep 20 '15 at 23:27
1
Well, a publisher might if they don't want you using those package anyway. That way, you don't have to change the source much in order to produce the output they want. Same way different classes all definesection{}. That's not coincidence either! But since this package isn't part of TeX Live and I have no idea what it is for or where to find it, I can't say whether this has any relevance or not ;).
– cfr
Sep 21 '15 at 1:18
|
show 5 more comments
I'm trying to generate documentation using SWI Prolog PlDoc package, but I'm running into a problem with the environment defined in pldoc.sty:
newcommand{tag}[1]{%
item[#1]}
...
% begin{tags} ... end{tags}
newenvironment{tags}%
{begin{quote}begin{description}%
setlength{itemsep}{0pt}%
footnotesize}%
{end{description}end{quote}}
This is used in the generated TeX file as follows:
subsection{automata.pl: High-level predicates for dealing with regular expressions}
label{sec:automata}
begin{tags}
tag{See also}
url{https://github.com/wvxvw/intro-to-automata-theory}
tag{To be done}
Add predref{match_suffix_regex}{3}, predref{match_all_regex}{3}, predref{find_regex}{3}
end{tags}
Which I insert into a larger document as follows:
documentclass[11pt]{article}
...
usepackage{amsmath}
...
usepackage{pldoc}
...
begin{document}
...
section{Appendix A}
label{sec:orgheadline18}
input{automata-doc}
end{document}
When I try to generate PDF using latexmk with pdflatex I receive the following error:
! Package amsmath Error: tag not allowed here.
See the amsmath package documentation for explanation.
Type H <return> for immediate help.
...
l.253 tag
{See also}
However, when I generate standalone documentation (which does not use amsmath package), this error doesn't happen. My guess is that amsmath is messing things up, but I don't know how to prevent it from interfering.
errors amsmath
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
I'm trying to generate documentation using SWI Prolog PlDoc package, but I'm running into a problem with the environment defined in pldoc.sty:
newcommand{tag}[1]{%
item[#1]}
...
% begin{tags} ... end{tags}
newenvironment{tags}%
{begin{quote}begin{description}%
setlength{itemsep}{0pt}%
footnotesize}%
{end{description}end{quote}}
This is used in the generated TeX file as follows:
subsection{automata.pl: High-level predicates for dealing with regular expressions}
label{sec:automata}
begin{tags}
tag{See also}
url{https://github.com/wvxvw/intro-to-automata-theory}
tag{To be done}
Add predref{match_suffix_regex}{3}, predref{match_all_regex}{3}, predref{find_regex}{3}
end{tags}
Which I insert into a larger document as follows:
documentclass[11pt]{article}
...
usepackage{amsmath}
...
usepackage{pldoc}
...
begin{document}
...
section{Appendix A}
label{sec:orgheadline18}
input{automata-doc}
end{document}
When I try to generate PDF using latexmk with pdflatex I receive the following error:
! Package amsmath Error: tag not allowed here.
See the amsmath package documentation for explanation.
Type H <return> for immediate help.
...
l.253 tag
{See also}
However, when I generate standalone documentation (which does not use amsmath package), this error doesn't happen. My guess is that amsmath is messing things up, but I don't know how to prevent it from interfering.
errors amsmath
errors amsmath
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
edited Sep 20 '15 at 21:25
user31729
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
3791412
1
tagis an important command inamsmath-- the definition in your.styfile clashes here. Since I've no access topldoc.styI can't test, but I suggest to copy thetagdefinition frompldoc.styand rename itpltag, as well replacing anytag{...}in your real document withpltag{...}accordingly.
– user31729
Sep 20 '15 at 21:22
@ChristianHupfer technically, the.styisn't my. Should I write to the maintainer to alert them to the problem, or is this something that I can remedy locally (without having to modify the said.sty)?
– wvxvw
Sep 20 '15 at 21:23
1
You should not modify the.styat all. Writing to the maintainer is certainly a good idea
– user31729
Sep 20 '15 at 21:24
Note that LaTeX must have given earlier errors. It will have told you thattagwas not available to be created as a new command, for example. You ignore such errors at your peril!
– cfr
Sep 20 '15 at 23:27
1
Well, a publisher might if they don't want you using those package anyway. That way, you don't have to change the source much in order to produce the output they want. Same way different classes all definesection{}. That's not coincidence either! But since this package isn't part of TeX Live and I have no idea what it is for or where to find it, I can't say whether this has any relevance or not ;).
– cfr
Sep 21 '15 at 1:18
|
show 5 more comments
1
tagis an important command inamsmath-- the definition in your.styfile clashes here. Since I've no access topldoc.styI can't test, but I suggest to copy thetagdefinition frompldoc.styand rename itpltag, as well replacing anytag{...}in your real document withpltag{...}accordingly.
– user31729
Sep 20 '15 at 21:22
@ChristianHupfer technically, the.styisn't my. Should I write to the maintainer to alert them to the problem, or is this something that I can remedy locally (without having to modify the said.sty)?
– wvxvw
Sep 20 '15 at 21:23
1
You should not modify the.styat all. Writing to the maintainer is certainly a good idea
– user31729
Sep 20 '15 at 21:24
Note that LaTeX must have given earlier errors. It will have told you thattagwas not available to be created as a new command, for example. You ignore such errors at your peril!
– cfr
Sep 20 '15 at 23:27
1
Well, a publisher might if they don't want you using those package anyway. That way, you don't have to change the source much in order to produce the output they want. Same way different classes all definesection{}. That's not coincidence either! But since this package isn't part of TeX Live and I have no idea what it is for or where to find it, I can't say whether this has any relevance or not ;).
– cfr
Sep 21 '15 at 1:18
1
1
tag is an important command in amsmath -- the definition in your .sty file clashes here. Since I've no access to pldoc.sty I can't test, but I suggest to copy the tag definition from pldoc.sty and rename it pltag, as well replacing any tag{...} in your real document with pltag{...} accordingly.– user31729
Sep 20 '15 at 21:22
tag is an important command in amsmath -- the definition in your .sty file clashes here. Since I've no access to pldoc.sty I can't test, but I suggest to copy the tag definition from pldoc.sty and rename it pltag, as well replacing any tag{...} in your real document with pltag{...} accordingly.– user31729
Sep 20 '15 at 21:22
@ChristianHupfer technically, the
.sty isn't my. Should I write to the maintainer to alert them to the problem, or is this something that I can remedy locally (without having to modify the said .sty)?– wvxvw
Sep 20 '15 at 21:23
@ChristianHupfer technically, the
.sty isn't my. Should I write to the maintainer to alert them to the problem, or is this something that I can remedy locally (without having to modify the said .sty)?– wvxvw
Sep 20 '15 at 21:23
1
1
You should not modify the
.sty at all. Writing to the maintainer is certainly a good idea– user31729
Sep 20 '15 at 21:24
You should not modify the
.sty at all. Writing to the maintainer is certainly a good idea– user31729
Sep 20 '15 at 21:24
Note that LaTeX must have given earlier errors. It will have told you that
tag was not available to be created as a new command, for example. You ignore such errors at your peril!– cfr
Sep 20 '15 at 23:27
Note that LaTeX must have given earlier errors. It will have told you that
tag was not available to be created as a new command, for example. You ignore such errors at your peril!– cfr
Sep 20 '15 at 23:27
1
1
Well, a publisher might if they don't want you using those package anyway. That way, you don't have to change the source much in order to produce the output they want. Same way different classes all define
section{}. That's not coincidence either! But since this package isn't part of TeX Live and I have no idea what it is for or where to find it, I can't say whether this has any relevance or not ;).– cfr
Sep 21 '15 at 1:18
Well, a publisher might if they don't want you using those package anyway. That way, you don't have to change the source much in order to produce the output they want. Same way different classes all define
section{}. That's not coincidence either! But since this package isn't part of TeX Live and I have no idea what it is for or where to find it, I can't say whether this has any relevance or not ;).– cfr
Sep 21 '15 at 1:18
|
show 5 more comments
2 Answers
2
active
oldest
votes
It appears that the maintainer isn't willing to change the STY provided with the documentation generator: https://github.com/SWI-Prolog/packages-pldoc/issues/11
I lack the knowledge to try to patch this myself, so, the only way I found around the problem was to generate the code documentation and the rest of the article separately and then join the two resulting PDFs following these (or similar) instructions: https://askubuntu.com/a/18691/638782
edited Apr 13 '17 at 12:23
Community♦
1
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
add a comment |
I had the same problem and I modified the Prolog and LaTeX code to
get things right. You can find the modified files and some instructions on GitHub in the repository AltPldoc.
https://github.com/francomorando/AltPldoc
answered 12 mins ago
Franco MorandoFranco Morando
1
New contributor
Franco Morando 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 |
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%2f268597%2fswi-prolog-documentation-generator-tags-environment-tag-not-allowed%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
It appears that the maintainer isn't willing to change the STY provided with the documentation generator: https://github.com/SWI-Prolog/packages-pldoc/issues/11
I lack the knowledge to try to patch this myself, so, the only way I found around the problem was to generate the code documentation and the rest of the article separately and then join the two resulting PDFs following these (or similar) instructions: https://askubuntu.com/a/18691/638782
edited Apr 13 '17 at 12:23
Community♦
1
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
add a comment |
It appears that the maintainer isn't willing to change the STY provided with the documentation generator: https://github.com/SWI-Prolog/packages-pldoc/issues/11
I lack the knowledge to try to patch this myself, so, the only way I found around the problem was to generate the code documentation and the rest of the article separately and then join the two resulting PDFs following these (or similar) instructions: https://askubuntu.com/a/18691/638782
edited Apr 13 '17 at 12:23
Community♦
1
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
add a comment |
It appears that the maintainer isn't willing to change the STY provided with the documentation generator: https://github.com/SWI-Prolog/packages-pldoc/issues/11
I lack the knowledge to try to patch this myself, so, the only way I found around the problem was to generate the code documentation and the rest of the article separately and then join the two resulting PDFs following these (or similar) instructions: https://askubuntu.com/a/18691/638782
edited Apr 13 '17 at 12:23
Community♦
1
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
It appears that the maintainer isn't willing to change the STY provided with the documentation generator: https://github.com/SWI-Prolog/packages-pldoc/issues/11
I lack the knowledge to try to patch this myself, so, the only way I found around the problem was to generate the code documentation and the rest of the article separately and then join the two resulting PDFs following these (or similar) instructions: https://askubuntu.com/a/18691/638782
edited Apr 13 '17 at 12:23
Community♦
1
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
1
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
answered Feb 5 '17 at 16:27
wvxvwwvxvw
3791412
3791412
add a comment |
add a comment |
I had the same problem and I modified the Prolog and LaTeX code to
get things right. You can find the modified files and some instructions on GitHub in the repository AltPldoc.
https://github.com/francomorando/AltPldoc
answered 12 mins ago
Franco MorandoFranco Morando
1
New contributor
Franco Morando 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 |
I had the same problem and I modified the Prolog and LaTeX code to
get things right. You can find the modified files and some instructions on GitHub in the repository AltPldoc.
https://github.com/francomorando/AltPldoc
answered 12 mins ago
Franco MorandoFranco Morando
1
New contributor
Franco Morando 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 |
I had the same problem and I modified the Prolog and LaTeX code to
get things right. You can find the modified files and some instructions on GitHub in the repository AltPldoc.
https://github.com/francomorando/AltPldoc
answered 12 mins ago
Franco MorandoFranco Morando
1
New contributor
Franco Morando is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had the same problem and I modified the Prolog and LaTeX code to
get things right. You can find the modified files and some instructions on GitHub in the repository AltPldoc.
https://github.com/francomorando/AltPldoc
answered 12 mins ago
Franco MorandoFranco Morando
1
New contributor
Franco Morando is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 12 mins ago
Franco MorandoFranco Morando
1
New contributor
Franco Morando is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 12 mins ago
Franco MorandoFranco Morando
1
answered 12 mins ago
Franco MorandoFranco Morando
1
1
New contributor
Franco Morando is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Franco Morando is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Franco Morando 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 |
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%2f268597%2fswi-prolog-documentation-generator-tags-environment-tag-not-allowed%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
1
tagis an important command inamsmath-- the definition in your.styfile clashes here. Since I've no access topldoc.styI can't test, but I suggest to copy thetagdefinition frompldoc.styand rename itpltag, as well replacing anytag{...}in your real document withpltag{...}accordingly.– user31729
Sep 20 '15 at 21:22
@ChristianHupfer technically, the
.styisn't my. Should I write to the maintainer to alert them to the problem, or is this something that I can remedy locally (without having to modify the said.sty)?– wvxvw
Sep 20 '15 at 21:23
1
You should not modify the
.styat all. Writing to the maintainer is certainly a good idea– user31729
Sep 20 '15 at 21:24
Note that LaTeX must have given earlier errors. It will have told you that
tagwas not available to be created as a new command, for example. You ignore such errors at your peril!– cfr
Sep 20 '15 at 23:27
1
Well, a publisher might if they don't want you using those package anyway. That way, you don't have to change the source much in order to produce the output they want. Same way different classes all define
section{}. That's not coincidence either! But since this package isn't part of TeX Live and I have no idea what it is for or where to find it, I can't say whether this has any relevance or not ;).– cfr
Sep 21 '15 at 1:18