first attempt at PreTeXt conversion #1
Conversation
|
I should have added: I can modify the conversion script to hard-code the numbers so that they |
|
Hi David, I finally had a chance to check this out. I am having trouble building the initial PreTeXt version, which most likely means that I am doing something stupid since I am completely inexperienced with PreTeXt. I am trying to build from the ptx directory using the guide here. In particular, I've cloned the mathbook project and I'm running
This generates Am I doing something wrong here or is there a problem with the PreTeXt such that it's not generating any actual content? |
|
I think I forgot to send you my email that says "be sure you can
build the sample article and sample book, before you try building
your own material."
The "/path/to" is not literal. If you do not know about Unix paths,
start googling.
Also, you should be in a new directory, and the "index.ptx" should
be "/path/to/index.ptx". Otherwise, the html files will be in the
same directory as the source, and you absolutely do not want that.
You also need the command to start with
xsltproc --xinclude ...
because the source involves multiple files. (The sample article is one
big file. The sample book is multiple files.)
Once you get this working, it would be great if you could contribute back
some improvements to the getting started instructions.
…On Thu, 5 Dec 2019, Dan Whitman wrote:
Hi David, I finally had a chance to check this out. I am having trouble building the initial PreTeXt version,
which most likely means that I am doing something stupid since I am completely inexperienced with PreTeXt.
I am trying to build from the ptx directory using the guide here. In particular, I've cloned the mathbook
project and I'm running
xsltproc /path/to/mathbook/xsl/mathbook-html.xsl index.ptx
This generates index.html and article-1.html and I do get a warning about not having any sections, worksheets,
or top-level paragraphs. However, when I open either of these in my browser (using Firefox if that's relevant)
all it shows is the document title but no real content at all. If I run xsltproc on any of the other .ptx files
in the same way it spits out a bunch of stuff and no files are generated. If I try building the LaTeX version of
index.ptx per the guide above the .tex file is generated but it will not compile using pdflatex.
Am I doing something wrong here or is there a problem with the PreTeXt such that it's not generating any actual
content?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, orunsubscribe.[AABTULB62GZZ4GUNXDHFJ63QXEYMVA5CNFSM4JU63XG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOOR
PWSZGOEGBNHTQ.gif]
|
|
Turns out the main issue was missing the I did run into some issues with the LaTeX output (I wanted to see what that looked like). Most of the issues were some LaTeX commands I defined in my original manual that didn't make it into the converted version, which I was able to fix myself temporarily to at least get the LaTeX to compile. I am already very impressed by the fidelity of this conversion and the PreTeXt output, both PDF and HTML. I did discover numerous issues with both output formats, but after seeing this I'm confident that PreTeXt will suite my needs for these solutions manuals, so I'm going to start investing time in learning PreTeXt so I can start resolving these issues. |
|
Glad to hear it. If there is something I can improve in the automated
conversion, please ask.
Otherwise, subscribe to the three Google groups and use them as
a resource for all things PreTeXt.
…On Thu, 5 Dec 2019, Dan Whitman wrote:
Turns out the main issue was missing the -xinclude option to xsltproc. I knew that
/path/to/mathbook/xsl/mathbook-html.xsl should be the actual path, I just left that in there because where I put
that isn't relevant. You have a good point though about generating the HTML output to it's own directory instead
of mixing it all up with the .ptx XML files.
I did run into some issues with the LaTeX output (I wanted to see what that looked like). Most of the issues
were some LaTeX commands I defined in my original manual that didn't make it into the converted version, which I
was able to fix myself temporarily to at least get the LaTeX to compile.
I am already very impressed by the fidelity of this conversion and the PreTeXt output, both PDF and HTML. I did
discover numerous issues with both output formats, but after seeing this I'm confident that PreTeXt will suite
my needs for these solutions manuals, so I'm going to start investing time in learning PreTeXt so I can start
resolving these issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, orunsubscribe.[AABTULCD55IDDGSNOZJ5NPLQXF2HNA5CNFSM4JU63XG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOOR
PWSZGOEGCJEYA.gif]
|
|
As I fix issues in the conversion (which won't' be for awhile because my time is currently pretty limited and I need to learn PreTeXt first!) I will make notes of the issues I found and feed these back to you to improve your conversion script as you will. |
|
The repository will move soon, but it is here now:
https://github.com/rbeezer/mathbook
…On Fri, 6 Dec 2019, Dan Whitman wrote:
As I fix issues in the conversion (which won't' be for awhile because my time is currently pretty limited and I
need to learn PreTeXt first!) I will make notes of the issues I found and feed these back to you to improve your
conversion script as you will.
Also, as you mentioned before, once I learn some PreTeXt I'm happy to contribute back a bit and add a note in
the Processing page in the guide about using the --xinclude option but I can't find the PreTeXt source for the
guide, which I am guessing is in a GitHub repository. Can you link me to the project?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, orunsubscribe.[AABTULHUVIQW3XEWQOK2VB3QXJXCNA5CNFSM4JU63XG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOOR
PWSZGOEGEPDRI.gif]
|
Initial PreTeXt version is in the "ptx" directory.
Try compiling the HTML and check for systematic errors.
Errors that appear repeatedly can probably be fixed by re-doing the conversion.
Errors that appear only a few times should be fixed by hand after the automated phase
of the conversion is complete.
You will probably find that the default settings for the HTML conversion are not
suitable for you. That is independent of the source markup.