> Turn out it was the file name that cause the problem.As suggest by > David, 1.. I rename the .ly file not using any utf-8 code and it > complies fine.2.. I change the first utf-8 character "禱" to another "主" > and the file complies fine as well3.. the file name with utf-8 "禱" when > comply generate the strange error -- no version statement found. > Question: can be be resolved? Or nothing we can do?
FWIW I can compile all 3 files you attached to your last email on my Linux system using the current stable frescobaldi and LP 2.19.30 Kind regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
