Re: Encoding Issue for .ly Files on CPDL

Hans Aikema, direct vanuit de iCloud

> Op 3 jun 2026 om 14:03 heeft Gabriel Ellsworth <[email protected]> het volgende geschreven:
> 
> 
> Thanks very much for your help, Silvain, Hans, and Hans.
> 
> IIUC, what CPDL should do is to edit/adjust the HTTP response headers that CPDL’s server sends/returns to browsers.
> 
> Those HTTP response headers should include:
> Content-Type: text/xml; charset=utf-8
> 
> Is all of the above correct?
> 
> And just to confirm, should it be text/xml and not text/plain?

Lilypond is not xml, so the value should either be

 text/plain;charset=utf-8

or (using the pattern of private unregistered extension-types) a proprietary extensionsubtype for text specific for lilypond e.g.:

text/x-lilypond;charset=utf-8

both assuming that the lilypond files on cpdl are always encoded in utf-8 (not sure whether they can guarantee that with their infrastructure)

if they can be in any encoding there is essentially nothing that CPDL can do as they also wouldn't know whether the author encoded the text with utf-8, iso-8859-1, iso-8859-15 or even other encodings common in non-latin-alphabet regions