<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Karl,</p>
<p>Thank you very much for you reply. The answer you gave me is
perfectly appropriate for me<br>
I will warn my readers about pdftex knowing that LuaTeX and XeTeX
are working fine with UTF-8. If I have time I will try to play
with the table of chars but for the moment my skills are not
enough evolved to do that.</p>
<p>Best regards<br>
</p>
<div class="moz-cite-prefix">On 01/12/2021 22:48, Karl Berry wrote:<br>
</div>
<blockquote type="cite"
cite="mid:202112012148.1B1LmslG021831@freefriends.org">
<pre class="moz-quote-pre" wrap="">Vincent - I'm not sure if you saw Thierry's answer
(<a class="moz-txt-link-freetext" href="https://tug.org/pipermail/pdftex/2021-December/009244.html">https://tug.org/pipermail/pdftex/2021-December/009244.html</a>).
(Thierry - please cc the original poster on replies to all tug mailing
lists.) It seems sensible to me, except E9 is the Unicode code point for
e-acute.
pdftex simply reads bytes, having been written long before UTF-8 became
pervasive. LaTeX will read UTF-8 input by default these days and map it
to the font slots as needed (defined). Plain TeX is not going to do
that; it's up to you to define it to output to the correct location.
In genera, you can't play around with Unicode code points in pdftex as
if they were characters (\lccode, \lowercase). LuaTeX and XeTeX read
UTF-8 natively so behave differently.
Good luck,
Karl
</pre>
</blockquote>
<div class="moz-signature">-- <br>
<p>Vincent Breton</p>
<p>Concepteur et développeur de solutions techniques innovantes.</p>
<blockquote style="font-style: italic;">L'obsolescence programmée
et la perte des savoir-faire commence par une pauvreté ou une
absence de documentation technique ou professionnelle - <a
href="https://www.presentiel.com">www.presentiel.com</a></blockquote>
</div>
</body>
</html>