<div dir="auto">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.<div dir="auto"><br></div><div dir="auto">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.</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Dec 20, 2018, 1:24 AM Sebastian Huber <<a href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-brains.de</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Joel,<br>
<br>
I don't think we should remove ALL the UTF-8 characters. I would like to <br>
be able to properly mention authors in the bibliography. I worked well <br>
for example for the RTEMS BSP and Driver Guide so far:<br>
<br>
<a href="https://docs.rtems.org/branches/master/bsp-howto.pdf" rel="noreferrer noreferrer" target="_blank">https://docs.rtems.org/branches/master/bsp-howto.pdf</a><br>
<br>
I use UTF-8 for all my Latex document sources. Not everything is English <br>
text in the world.<br>
<br>
The problem in the new manual was the Unicode character (U+200B) which <br>
your command line hasn't found:<br>
<br>
<a href="https://git.rtems.org/rtems-docs/commit/?id=e24c5e9682ee4d85474cbd326d25e99f0207731c" rel="noreferrer noreferrer" target="_blank">https://git.rtems.org/rtems-docs/commit/?id=e24c5e9682ee4d85474cbd326d25e99f0207731c</a><br>
<br>
The special " and ' characters should be fixed, but the I²C is fine from <br>
my point of view.<br>
<br>
find . -name "*.rst" | xargs -e file | grep Unicode | cut -d':' -f1 <br>
| xargs -e grep --color='auto' -P -n '[^\x00-\x7F]'<br>
./bsp-howto/i2c.rst:9:The Inter-Integrated Circuit (I2C, I²C, IIC) bus <br>
drivers should use the<br>
./eng/test-plan.rst:24:“fully tested.” A fully tested requirement is one <br>
which is implemented<br>
./eng/vc-users.rst:387:of the two branches, stores each commit of the <br>
branch you’re on to temporary<br>
./eng/license-requirements.rst:12:for documentation and “Two Paragraph <br>
BSD” for source code.<br>
./eng/appendix-a.rst:12:by a mission as a baselined starting point for <br>
“pre-qualification”<br>
./eng/appendix-a.rst:129: | Usability | Software User’s | <br>
The Software User Manual |<br>
./eng/appendix-a.rst:136:that encompasses the artifacts’ intents. The <br>
idea is that this living<br>
./eng/vc-authors.rst:28:account on <a href="http://dispatch.rtems.org" rel="noreferrer noreferrer" target="_blank">dispatch.rtems.org</a> one should be <br>
requested on the devel@… list.<br>
./eng/vc-authors.rst:45:master repository generate email to the vc@… <br>
list and development type commits<br>
./eng/prequalification.rst:17:change process, coding style, testing <br>
requirements, and a user’s<br>
./eng/prequalification.rst:18:manual. During system test, these <br>
standards call for a review – usually<br>
./eng/prequalification.rst:19:by an independent entity – that the <br>
standard has been adhered too. These<br>
./eng/prequalification.rst:23:term “qualification” independent of the <br>
standard.<br>
./eng/prequalification.rst:39:“pre-qualification”. True qualification <br>
must be performed on the<br>
./eng/prequalification.rst:40:project’s target hardware in a system <br>
context. The FAA has provided<br>
./eng/prequalification.rst:56:term “resources” is often used by open <br>
source projects to refer to<br>
./eng/prequalification.rst:77:qualification standards. It will maintain <br>
“scorecards” which<br>
./eng/users-manuals.rst:12:Reference the RTEMS C User’s Manual<br>
./user/tracing/introduction.rst:43:Step 2: The RTEMS Trace Linker reads <br>
the user’s configuration file and that<br>
./user/tracing/introduction.rst:47:wraps the functions defined in the <br>
user’s configuration with code that captures<br>
./user/tracing/introduction.rst:56:Step 4: RTEMS shell provides the <br>
“rtrace” command to display and save trace<br>
./user/tracing/examples.rst:59:fileio’s executable and object files in <br>
the last line of the command according<br>
<br>
-- <br>
Sebastian Huber, embedded brains GmbH<br>
<br>
Address : Dornierstr. 4, D-82178 Puchheim, Germany<br>
Phone : +49 89 189 47 41-16<br>
Fax : +49 89 189 47 41-09<br>
E-Mail : <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank" rel="noreferrer">sebastian.huber@embedded-brains.de</a><br>
PGP : Public key available on request.<br>
<br>
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
<br>
</blockquote></div>