SWI Prolog documentation generator tags environment: tag not allowedEnumerate 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
Typing CO_2 easily
What should be the ideal length of sentences in a blog post for ease of reading?
How to make a list of partial sums using forEach
Is there anyway, I can have two passwords for my wi-fi
Would a primitive species be able to learn English from reading books alone?
Pre-Employment Background Check With Consent For Future Checks
What happens if I try to grapple mirror image?
Overlapping circles covering polygon
Air travel with refrigerated insulin
How do I tell my boss that I'm quitting in 15 days (a colleague left this week)
Do I have to know the General Relativity theory to understand the concept of inertial frame?
Animation: customize bounce interpolation
Has the laser at Magurele, Romania reached a tenth of the Sun's power?
Why does the Persian emissary display a string of crowned skulls?
Why is the principal energy of an electron lower for excited electrons in a higher energy state?
Telemetry for feature health
Make a Bowl of Alphabet Soup
I'm just a whisper. Who am I?
Is there a distance limit for minecart tracks?
Storage of electrolytic capacitors - how long?
Can I say "fingers" when referring to toes?
Alignment of six matrices
Is there a reason to prefer HFS+ over APFS for disk images in High Sierra and/or Mojave?
Possible Eco thriller, man invents a device to remove rain from glass
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
:
newcommandtag[1]%
item[#1]
...
% begintags ... endtags
newenvironmenttags%
beginquotebegindescription%
setlengthitemsep0pt%
footnotesize%
enddescriptionendquote
This is used in the generated TeX file as follows:
subsectionautomata.pl: High-level predicates for dealing with regular expressions
labelsec:automata
begintags
tagSee also
urlhttps://github.com/wvxvw/intro-to-automata-theory
tagTo be done
Add predrefmatch_suffix_regex3, predrefmatch_all_regex3, predreffind_regex3
endtags
Which I insert into a larger document as follows:
documentclass[11pt]article
...
usepackageamsmath
...
usepackagepldoc
...
begindocument
...
sectionAppendix A
labelsec:orgheadline18
inputautomata-doc
enddocument
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
|
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
:
newcommandtag[1]%
item[#1]
...
% begintags ... endtags
newenvironmenttags%
beginquotebegindescription%
setlengthitemsep0pt%
footnotesize%
enddescriptionendquote
This is used in the generated TeX file as follows:
subsectionautomata.pl: High-level predicates for dealing with regular expressions
labelsec:automata
begintags
tagSee also
urlhttps://github.com/wvxvw/intro-to-automata-theory
tagTo be done
Add predrefmatch_suffix_regex3, predrefmatch_all_regex3, predreffind_regex3
endtags
Which I insert into a larger document as follows:
documentclass[11pt]article
...
usepackageamsmath
...
usepackagepldoc
...
begindocument
...
sectionAppendix A
labelsec:orgheadline18
inputautomata-doc
enddocument
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
1
tag
is an important command inamsmath
-- the definition in your.sty
file clashes here. Since I've no access topldoc.sty
I can't test, but I suggest to copy thetag
definition frompldoc.sty
and rename itpltag
, as well replacing anytag...
in your real document withpltag...
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
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
Note that LaTeX must have given earlier errors. It will have told you thattag
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
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
:
newcommandtag[1]%
item[#1]
...
% begintags ... endtags
newenvironmenttags%
beginquotebegindescription%
setlengthitemsep0pt%
footnotesize%
enddescriptionendquote
This is used in the generated TeX file as follows:
subsectionautomata.pl: High-level predicates for dealing with regular expressions
labelsec:automata
begintags
tagSee also
urlhttps://github.com/wvxvw/intro-to-automata-theory
tagTo be done
Add predrefmatch_suffix_regex3, predrefmatch_all_regex3, predreffind_regex3
endtags
Which I insert into a larger document as follows:
documentclass[11pt]article
...
usepackageamsmath
...
usepackagepldoc
...
begindocument
...
sectionAppendix A
labelsec:orgheadline18
inputautomata-doc
enddocument
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
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
:
newcommandtag[1]%
item[#1]
...
% begintags ... endtags
newenvironmenttags%
beginquotebegindescription%
setlengthitemsep0pt%
footnotesize%
enddescriptionendquote
This is used in the generated TeX file as follows:
subsectionautomata.pl: High-level predicates for dealing with regular expressions
labelsec:automata
begintags
tagSee also
urlhttps://github.com/wvxvw/intro-to-automata-theory
tagTo be done
Add predrefmatch_suffix_regex3, predrefmatch_all_regex3, predreffind_regex3
endtags
Which I insert into a larger document as follows:
documentclass[11pt]article
...
usepackageamsmath
...
usepackagepldoc
...
begindocument
...
sectionAppendix A
labelsec:orgheadline18
inputautomata-doc
enddocument
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
edited Sep 20 '15 at 21:25
user31729
asked Sep 20 '15 at 21:15
wvxvwwvxvw
3791412
3791412
1
tag
is an important command inamsmath
-- the definition in your.sty
file clashes here. Since I've no access topldoc.sty
I can't test, but I suggest to copy thetag
definition frompldoc.sty
and rename itpltag
, as well replacing anytag...
in your real document withpltag...
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
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
Note that LaTeX must have given earlier errors. It will have told you thattag
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
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
tag
is an important command inamsmath
-- the definition in your.sty
file clashes here. Since I've no access topldoc.sty
I can't test, but I suggest to copy thetag
definition frompldoc.sty
and rename itpltag
, as well replacing anytag...
in your real document withpltag...
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
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
Note that LaTeX must have given earlier errors. It will have told you thattag
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
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
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
New contributor
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
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
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
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
1
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
New contributor
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
New contributor
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
New contributor
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
New contributor
New contributor
answered 14 mins ago
Franco MorandoFranco Morando
1
1
New contributor
New contributor
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
tag
is an important command inamsmath
-- the definition in your.sty
file clashes here. Since I've no access topldoc.sty
I can't test, but I suggest to copy thetag
definition frompldoc.sty
and rename itpltag
, as well replacing anytag...
in your real document withpltag...
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
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
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
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