On Thu, Dec 20, 2018, 5:02 PM Chris Johns On 21/12/2018 09:38, Chris Johns wrote:
> >
> > 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 [4]:
> >
>
> I should have checked before
On 21/12/2018 09:38, Chris Johns wrote:
>
> 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
> [4]:
>
I should have checked before posting. The master online docs are being built
ag
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 re
On 20/12/2018 14:19, Joel Sherrill wrote:
I don't disagree but there was a suspicion it was related to building
PDF. 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
I don't disagree but there was a suspicion it was related to building PDF.
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 corr
Hello Joel,
I don't think we should remove ALL the UTF-8 characters. I would like to
be able to properly mention authors in the bibliography. I worked well
for example for the RTEMS BSP and Driver Guide so far:
https://docs.rtems.org/branches/master/bsp-howto.pdf
I use UTF-8 for all my Latex
