2013/2/24 David Kastrup <[email protected]>: > David Kastrup <[email protected]> writes: > >> So much for my theory that a mail attachment is a guarantee for a >> byte-for-byte faithful copy. On my side, the file was definitely >> UTF-8-encoded. >> >> I have to agree that what appears on Gmane (where I read this list) >> was Latin-1 encoded however. Let's see whether sending to the list >> server fares better. >> >> Attached again. > > The version on Gmane is Latin-1 encoded, the version in the GNU list > server archives (and most likely the version people subscribed directly > to the list rather than reading it via Gmane) is UTF-8 encoded. For > both mails. > > So it would seem that Gmane chooses to reencode attachments in Latin-1. > That's a rather serious blunder. > > -- > David Kastrup
Hi David, FWIW, I downloaded your file direct from the mail (reading your mail in gmail in my Firefoxbrowser) Opening it with Jedit returned: /home/harm/Desktop/xxx.ly: The file could not be loaded correctly (some data might be lost) with the encoding "UTF-8". (java.nio.charset.MalformedInputException: Input length = 1) Try selecting a different encoding. It can be selected with the menu File->Reload with Encoding. If you want it to be done automatically, add the candidates into "List of fallback encodings" in Encodings pane of Global Options. Looking in http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00147.html and opening the attached file http://lists.gnu.org/archive/html/bug-lilypond/2013-02/txtldXgXL7Yon.txt in firefox shows: ->attached png. (It's a screenshot, don't knowing which result others will see, following the links) -Harm
<<attachment: bug.png>>
_______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
