Re: Encoding Issue for .ly Files on CPDL

Silvain Dupertuis <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.general
Message-ID <[email protected]>
Hello everyone.
There is an explanation of this page 
<https://ubiq.co/tech-blog/how-to-set-default-charset-to-utf-8-encoding-in-apache-using-htaccess/>
I tried this locally... with no success so far.

Le 02.06.26 à 17:24, Gabriel Ellsworth a écrit :
>
> Thank you, Sven.
>
>
> On Tue, 2 Jun 2026, Sven Axelsson wrote:
>
>     All the files linked from that forum post are served as images as can be seen from
>     the url (https://www1.cpdl.org/wiki/images/e/eb/Alma-2026-02.ly)
>     That probably means that they are interpreted as raw binary instead of utf-8.
>
>
> Here is my current understanding of the problem and potential solution.
>
>
> The problem:
>
>
> CPDL’s server currently interprets .ly files as raw binary instead of UTF-8 and delivers 
> the files to browsers as generic binary uploads.
>
>
> … and the solution would be:
>
>
> Adjust CPDL’s web server or MediaWiki configuration so that .ly files are delivered to 
> browsers as text/plain; charset=UTF-8.
>
>
> Do I have that right? (I asked AI for help, so it very well could be wrong!)
>
>
> At Help:Special characters - MediaWiki 
> <https://www.mediawiki.org/wiki/Help:Special_characters>, I read that “MediaWiki uses 
> Unicode (UTF-8) for character encoding,” so my hope is that this would be an easy fix 
> for CPDL.
>
>
> By the way, would anyone reading this message be willing to forward this thread to 
> Nancho Álvarez? I tried an email address that I found on his website, but my message 
> could not be delivered. I would like to ask him how he makes his website work well in 
> this regard.
>

-- 
Silvain Dupertuis
Route de Lausanne 335
1293 Bellevue (Switzerland)
tél. +41-(0)22-774.20.67
portable +41-(0)79-604.87.52
web: silvain-dupertuis.org <https://perso.silvain-dupertuis.org>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.