You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frescobaldi command supports an -e / --encoding option to open files in an encoding other than UTF-8. I wonder why, since LilyPond supports UTF-8 encoded files exclusively, and no other encoding.
The text was updated successfully, but these errors were encountered:
Maybe because Frescobaldi can also open .html or .tex files (mixed with lilypond code) and these files may have a different encoding? See for example #38 (well, opened in 2012). I guess that today any file should use UTF-8?
The
frescobaldi
command supports an-e
/--encoding
option to open files in an encoding other than UTF-8. I wonder why, since LilyPond supports UTF-8 encoded files exclusively, and no other encoding.The text was updated successfully, but these errors were encountered: