Problem with web not recognizing HTML tags

[rhutch...@gmail.com]

I updated my PreTeXt book this morning and here is how it now appears on web (from https://musictheory.pugetsound.edu/mt21c/RomanNumeralChordSymbols.html):

We will use Roman numerals to represent chords within a specified key. The Roman numeral “\(\left.\text{I}\right.\)” represents a triad built on \(\hat{1} \), or the 1st note of the scale. Uppercase Roman numerals represent major triads and lowercase Roman numerals (e.g., “\(\left.\text{i}\right.\)”) represent minor triads. Uppercase Roman numerals with a “\(\left.\text{}{+}\right.\)” are augmented (e.g., “\(\left.\text{III}{+}\right.\)”), and lowercase Roman numerals with a “\(\left.\text{}^{\circ}{}\right.\)” are diminished (e.g., “\(\left.\text{vii}^{\circ}{}\right.\)”). (There is also the Nashville Number System, which uses Arabic numbers for chords instead of Roman numerals.)

Here's the XML source: 

<p>We will use Roman numerals to represent chords within a specified key. The Roman numeral <q><chord root="I"/></q> represents a triad built on <scaledeg>1</scaledeg>, or the 1st note of the scale. Uppercase Roman numerals represent major triads and lowercase Roman numerals (e.g., <q><chord root="i"/></q>) represent minor triads. Uppercase Roman numerals with a <q><chord mode="augmented"/></q> are augmented (e.g., <q><chord root="III" mode="augmented"/></q>), and lowercase Roman numerals with a <q><chord mode="diminished"/></q> are diminished (e.g., <q><chord root="vii" mode="diminished"/></q>). (There is also the <url href="https://en.wikipedia.org/wiki/Nashville_number_system">Nashville Number System</url>, which uses Arabic numbers for chords instead of Roman numerals.)</p>

And here's the HTML:

<div class="para" id="RomanNumeralChordSymbols-3">We will use Roman numerals to represent chords within a specified key. The Roman numeral “<span class="process-math">\(\left.\text{I}\right.\)</span>” represents a triad built on <span class="process-math">\(\hat{1} \)</span>, or the 1st note of the scale. Uppercase Roman numerals represent major triads and lowercase Roman numerals (e.g., “<span class="process-math">\(\left.\text{i}\right.\)</span>”) represent minor triads. Uppercase Roman numerals with a “<span class="process-math">\(\left.\text{}{+}\right.\)</span>” are augmented (e.g., “<span class="process-math">\(\left.\text{III}{+}\right.\)</span>”), and lowercase Roman numerals with a “<span class="process-math">\(\left.\text{}^{\circ}{}\right.\)</span>” are diminished (e.g., “<span class="process-math">\(\left.\text{vii}^{\circ}{}\right.\)</span>”). (There is also the <a class="external" href="https://en.wikipedia.org/wiki/Nashville_number_system" target="_blank">Nashville Number System</a>, which uses Arabic numbers for chords instead of Roman numerals.)<div class="autopermalink" data-description="Paragraph"><a href="#RomanNumeralChordSymbols-3" title="Copy heading and permalink for Paragraph" aria-label="Copy heading and permalink for Paragraph"></a></div>

I did "pretext update" and "pretext upgrade" at various points during the process of updating the book and building it, in case that matters. I use FileZilla to move the html files onto the server.

This book is being actively used throughout the United States right now and I would like to fix this as soon as possible but am not sure where to start.

Rob Hutchinson

[Rob Beezer]

Those bits you don't like are technically bits of math, made to look like musical notation. So I don't think MathJax is processing those. I might be able to closer in a little bit.

On March 31, 2026 6:58:29 PM PDT, "rhutch...@gmail.com" <rhutch...@gmail.com> wrote:
>I updated my PreTeXt book this morning and here is how it now appears on
>web
>(from https://musictheory.pugetsound.edu/mt21c/RomanNumeralChordSymbols.html):
>
>We will use Roman numerals to represent chords within a specified key. The
>Roman numeral “\(\left.\text{I}\right.\)” represents a triad built on \(\hat{1}
>\), or the 1st note of the scale. Uppercase Roman numerals represent major
>triads and lowercase Roman numerals (e.g., “\(\left.\text{i}\right.\)”)
>represent minor triads. Uppercase Roman numerals with a “
>\(\left.\text{}{+}\right.\)” are augmented (e.g., “
>\(\left.\text{III}{+}\right.\)”), and lowercase Roman numerals with a “
>\(\left.\text{}^{\circ}{}\right.\)” are diminished (e.g., “
>\(\left.\text{vii}^{\circ}{}\right.\)”). (There is also the Nashville

>Number System <https://en.wikipedia.org/wiki/Nashville_number_system>,

[Rob Beezer]

When you upload your files via FileZilla, there will be a folder named
"_static". It needs to be uploaded along with everything else - it is not
present on your server. It is not new, but we have not always had it either.

That's the first obvious thing that is not right.

[Oscar Levin]

The console (using dev-tools in the browser; right-click select "inspect") is complaining about being unable to load a mathjax javascript file.  Maybe try syncing the _static folder to your web server again?

--
You received this message because you are subscribed to the Google Groups "PreTeXt support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/MTAwMDAwNC5iZWV6ZXI.1775010204%40pnsh.

[rhutch...@gmail.com]

That fixed it! Thanks!

Is this something I need to do (update the _static folder) every time I update the book?

[Sean Fitzpatrick]

Probably a good idea to update it every time.

When I'm building on Windows and moving files with FileZilla:

- I compress the whole output/web folder to a zip or tar file

- I move that one file into the server

- I unzip the file once on the server

That way nothing gets missed, and it's the same effort every time.

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/a837c3f7-95a6-4395-a789-ef5559cf6048n%40googlegroups.com.

[Rob Beezer]

The Python routines have an option to create the HTML files as zip file (or maybe tar.gz). That reduces the effort by one-third.

Don't know if the CLI exposes that option.

>> https://groups.google.com/d/msgid/pretext-support/a837c3f7-95a6-4395-a789-ef5559cf6048n%40googlegroups.com
>> <https://groups.google.com/d/msgid/pretext-support/a837c3f7-95a6-4395-a789-ef5559cf6048n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

[Rob Beezer]

On 3/31/26 20:36, rhutch...@gmail.com wrote:
> Is this something I need to do (update the _static folder) every time I update
> the book?

Yes, definitely. Despite the name, it will change over time. And you really
want to trash what is on the server before updating. For FCLA, I would

1. Upload the new build into a folder I would make fresh called fcla-new.

2. Rename fcla folder to fcla-old.

3. Rename fcla-new to fcla.

4. Delete fcla-old (which can take a while).

That way the world only sees an outage in the (short) transition from #2 to #3.
#1 and #4 have considerable delays but only affect you waiting around, not your
readers.

And you don't have a whole lot of stale stuff on the server.

The Other Rob