[PATCH] rtems-docs: Eliminate UTF-8 characters, PDF still broken
chrisj at rtems.org
Thu Dec 20 22:38:58 UTC 2018
On 21/12/2018 00:23, Sebastian Huber wrote:
> On 20/12/2018 14:19, Joel Sherrill wrote:
>> I don't disagree but there was a suspicion it was related to building PDF.
I also would like to have complete support however we seem to not have this on
all types of hosts and we have an issue we need to resolve. Something needs to
give at this point in time so we can build and publish the docs and make a release.
>> Until PDF is building again, let's keep them out.
>> Once PDFs are coming out again, feel free to revert or figure out how to do a
>> superscript for the i2c. For names, utf8 should be ok if we can produce PDFs
>> reliably and correctly across the various hosts.
> I am able to build the PDFs after my fix:
I cannot build the PDF on a FreeBSD 11.2-p5 with the latest Latex-alive and
sphinx via virtualenv and then pip. I have issues in the indexes/glossary/bib
generation for the user.pdf where the hyperref links for things like the 'waf'
reference  seems to get confused. I am not sure if this is a hyperref and
xinidy issue , a sphinx issue , something we are doing in our
configuration, or related to me using the latest release of sphinx.
This is not about restricting access to only non-unicode language, we want to
find the simplest fix we can.
The base need for a release is being able to build on sync.rtems.org as this is
the place the releases are created. I have a virtualenv environment which has :
chrisj at sync# pwd
chrisj at sync# . ./docs_builder/bin/activate
(docs_builder) chrisj at sync# sphinx-build --version
Sphinx (sphinx-build) 1.6.3
The Latex-alive version on sync.rtems.org is old and will have to remain that way.
You assistance in resolving this issue is most welcome. I can ask Amar to
provide you with a login to sync.rtems.org.
More information about the devel