<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 18, 2018, 7:31 PM Chris Johns <<a href="mailto:chrisj@rtems.org">chrisj@rtems.org</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 19/12/2018 11:49, Joel Sherrill wrote:<br>
> On Tue, Dec 18, 2018 at 5:33 PM Chris Johns <<a href="mailto:chrisj@rtems.org" target="_blank" rel="noreferrer">chrisj@rtems.org</a><br>
> <mailto:<a href="mailto:chrisj@rtems.org" target="_blank" rel="noreferrer">chrisj@rtems.org</a>>> wrote:<br>
> On 19/12/2018 06:12, Christian Mauderer wrote:<br>
> > I updated waf in rtems-tools with a reference to the ticket. I'm still a<br>
> > little unsure about our tickets: Should I create separate tickets for<br>
> > that problem in rtems-docs, rtems-libbsd (both have the same problem)<br>
> > and examples-v2 (I haven't tested that yet but I would expect the<br>
> > problem there too).<br>
> <br>
> No, the same ticket should be fine. Maybe update the ticket's details to<br>
> highlight this is happening. Separate tickets are needed for separate branches<br>
> because the timeline cannot be shared.<br>
> <br>
> > Note that rtems-docs needs an extra patch to build with python 3. There<br>
> > is an indentation error (mix of space and tab).<br>
> <br>
> Yes I have tripped over this but I have not had time to push a fix. Building PDF<br>
> is broken for me with the latest Sphinx. I am on a fully updated FreeBSD 11.2-p5<br>
> and all packages are updated plus the latest Sphinx in a virtualend. The issue<br>
> seems to be deep in Latex and relates to unicode characters in bib entries with<br>
> hyperef and the other package and things being confused. I do not know if it is<br>
> a bug in Sphinx or our configuration.<br>
> <br>
> <br>
> FWIW I am building html fine with Python 2 and Sphinx 1.6, 1.7, and 1.8.2 on three<br>
> different CentOS computers. But PDF doesn't work on any of those platforms. <br>
<br>
The build on <a href="http://sync.rtems.org" rel="noreferrer noreferrer" target="_blank">sync.rtems.org</a> for the online manuals is failing with unicode errors:<br>
<br>
$ file `find . -name \*.rst` | grep Unicode<br>
./eng/users-manuals.rst: UTF-8 Unicode text<br>
./eng/test-plan.rst: UTF-8 Unicode text<br>
./eng/vc-users.rst: UTF-8 Unicode text<br>
./eng/appendix-a.rst: UTF-8 Unicode text<br>
./eng/vc-authors.rst: UTF-8 Unicode text<br>
./eng/license-requirements.rst: UTF-8 Unicode text<br>
./eng/prequalification.rst: UTF-8 Unicode text<br>
./user/tracing/examples.rst: UTF-8 Unicode text<br>
./user/tracing/introduction.rst: UTF-8 Unicode text<br>
./bsp-howto/i2c.rst: UTF-8 Unicode text<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I can't try this tonight but Google reminded me that I did this on another project with the iconv utility. </div><div dir="auto"><br></div><div dir="auto">This happens when you copy from a website or MS-Word to text. </div><div dir="auto"><br></div><div dir="auto">I can fix it tomorrow if you can't find the command.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This raises 2 issues, we need the docs to build so the listed files need to be<br>
cleaned and the second issue is being able to support unicode. That is a<br>
separate development effort that will need to be worked on.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I should be able to fix those if you can't.</div><div dir="auto"><br></div><div dir="auto">How about a git check for Unicode. :)</div><div dir="auto"><br></div><div dir="auto">Agreed that long term we may want support but we don't need it now.</div><div dir="auto"><br></div><div dir="auto">--joel</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Chris<br>
</blockquote></div></div></div>