It overrides to make sure that a good encoding is used. It will not override utf8 in the next release. Regarding line ending i don't override. So there must be some other cause.
---- Original message ---- From: Valentin Villenave <v.villen...@gmail.com> Sent: 2 Jan 2009 10:37 -08:00 To: Bertalan Fodor <lilypondt...@organum.hu> Cc: Stan Sanderson <physinfo...@ameritech.net>, lilypond-user Mailinglist <lilypond-user@gnu.org> Subject: Re: LilyPondTool-2.12-r1 for download >> On Dec 31, 2008, at 7:59 AM, Valentin Villenave wrote: >> >>> By the way, I noticed that too: whilst I always save all my files in >>> UTF-8, LPT tries to override that and specifies UTF-8Y instead. When I >>> relaunch jEdit afterwards, it says : "I/O error: the file could not be >>> loaded correctly (some data might be lost) with encoding UTF-8Y. >>> (java.nio.charset.MalformedInputException: input length = 0)" 2008/12/31 Bertalan Fodor <lilypondt...@organum.hu>: > Yes, it's my fault. I don't know why LPT overrides user-defined encoding settings; besides, I've just noticed that it also saves every file with \r\n EOLs, whereas I need to use \n endings. About the memory problem: I'll do some benchmarking when I have more time. Cheers, Valentin _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
