> On 2 Jun 2026, at 19:42, Hans Åberg <[email protected]> wrote: > > > >> On 2 Jun 2026, at 19:24, Hans Aikema <[email protected]> wrote: >> >>> On 2 Jun 2026, at 19:21, Hans Åberg <[email protected]> wrote: >>> >>> >>>> On 2 Jun 2026, at 18:53, Silvain Dupertuis <[email protected]> >>>> wrote: >>>> >>>> I tried this, no success.. >>> >>> The HTTP header says “content-encoding: gzip”. A net search suggests it >>> should be: >>> content-encoding: text/xml; charset=utf-8 >> >> No, content-encoding is yet another header, that shows how the >> bytes-on-the-line are encoded, which in this case are sent as a gzip >> compressed bytestream (HTTP transport compression) >> Content-type defines what the bytes on the wire represent > > The page below says one can use: > Accept-Charset: utf-8 > > https://en.wikipedia.org/wiki/List_of_HTTP_header_fields
Again… not a solution, the only solution is to fix up the HTTP Response headers that describe the data that is transferred back to the browser, which is the Content-Type What worked for me on a local test starting with the httpd Docker image: on httpd.conf override the default configuration for AllowOverride of FileInfo in .htaccess: DocumentRoot "/usr/local/apache2/htdocs" <Directory "/usr/local/apache2/htdocs"> …. AllowOverride FileInfo … </Directory> and then in .htaccess for a folder that servers .ly files: AddCharset UTF8 .ly AddType text/x-lilypond .ly Which also explains why Sylvain’s configuration is not working: the site that showed configuration used an improper directive, the right directive is AddCharset, not AddDefaultCharset (which is meant to indicate the default charset to specify for text/plain and text/html) https://httpd.apache.org/docs/current/mod/core.html#adddefaultcharset so in httpd.conf configuration it also works (also adding the extension frequently used for include files) if you add (typically inside the <IfModule mime_module> block): AddType text/x-lilypond .ly .ily AddCharset UTF8 .ly .ily
