On 5/6/21 10:27 AM, Mauro Carvalho Chehab wrote:

Em Thu, 6 May 2021 19:04:44 +0200
Markus Heiser [off-list ref] escreveu:

quoted

Am 06.05.21 um 18:46 schrieb Mauro Carvalho Chehab:

quoted

Em Thu, 6 May 2021 17:57:15 +0200
Markus Heiser [off-list ref] escreveu:
  

quoted

Am 06.05.21 um 12:39 schrieb Michal Suchánek:  

quoted

When building HTML documentation I get this output:  

...  

quoted

[  412s] UnicodeEncodeError: 'latin-1' codec can't encode characters in position 18-20: ordinal not in range(256)  

...  

quoted

It does not say which input file contains the offending character so I can't tell which file is broken.

Any idea how to debug?  

I guess the build host is a very simple container, what does

    echo $LC_ALL
    echo $LANG

prompt?  If it is latin, change it to something using utf-8 (I recommend
'en_US.utf8').

A UnicodeEncodeError can occour everywhere where characters are
encoded from (internal) unicode to the encoding of the stream.

By example:

A print or log statement which streams to stdout needs to encode
from unicode to stdout's encoding.  If there is one unicode symbol
which can not encoded to stream's encoding a UnicodeEncodeError
is raised.  

Hi Markus,

It shouldn't matter the builder's locale when building the Kernel
documentation (or any other documents built from other git trees
on other open source projects), as the Kernel's *.rpm document charset
won't change, no matter on what part of the globe it was built.

I vaguely remember about a change we made a couple of years ago
in order to address this issue.  

Hi Mauro :)

sure? .. what if the logger wants to log some symbols from the
chines translated parts to stdout and the encoding of stdout is
latin?

In python the logger will raise a UnicodeEncodeError, this is
what I know .. but I'm often wrong ;)

Yeah, Python (and almost all python apps) has a mad behavior when
it finds an unexpected character: instead of ignoring it, it
just crashes. On Sphinx, this is is even worse, as it blames
the parallel building, instead of pinpointing the real culprit.

And for error messages such as this problem, it should include
file name and line number along with the position.  Is position
in this case offset from the beginning of file or beginning of line?
What a bad error message.

[ah, I see that Michal has found where the error happens.]


I have been going thru some of the Documentation/ files...

Why do several of the files begin with
(hex) ef bb bf    followed by "=================="
for a heading, instead of just "===================".
See e.g. Documentation/timers/no_hz.rst.

thanks.
-- 
~Randy [resending due to smtp error]