Hi
On Fri, Dec 21, 2018 at 3:04 PM Sarah Conway Schnurr
<xenophenes42@gmail.com> wrote:
>
>
>>
>> Is your Sphinx an RPM installation? If so, they may have split that
>> theme out into a different package. We always install using PIP, which
>> works fine in every case I know of.
>
>
> No, it's installed through pip as well. Might it be version specific? I'm on the latest version supported by pip,
Sphinxv1.1.3.
Hmm, odd. Well if it helps any, all our CI/CD systems (Windows, Mac,
Linux, Docker) all rebuild the virtual environment on every test run
and build, based on just a plain old 'pip install sphinx' (as well as
the other requirements in requirements.txt).
>> > sed -i "/html_theme = 'classic'/d" docs/en_US/conf.py
>> >
>> > The PDF errors as mentioned previously in detail are additionally reproducible in the community packages from Git
for3.2, 3.6, and HEAD.
>> >
>> > ! Use of \@icentercr doesn't match its definition.
>>
>> Yeah, I see that as well. There's something in the doc source that is
>> getting converted into invalid TEX I think. I have no idea what
>> though, as I haven't really used TEX directly in 20+ years. It seems
>> like a Sphinx bug, in that it's quite happy with the input for other
>> formats, but barfs on anything that uses TEX.
>>
>> Do you know anyone that is familiar with TEX that might be able to
>> help? Maybe Joe?
>
>
> I'll do some research and see if I can determine what syntax it might be unhappy about; if able to figure it out,
willfollow up here with the fix.
Awesome - thanks!
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
