Am 06.05.21 um 18:46 schrieb Mauro Carvalho Chehab:

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 ;)

I remember we had some patches to the chinese translation
these days, may be there is an issue the logger wants to report.

    Anyway I would always recommend to use utf-8.

@Michal would you give it a try?

   -- Markus --