Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify purpose of -e / --encoding option #1651

Closed
jeanas opened this issue Aug 1, 2023 · 2 comments
Closed

Clarify purpose of -e / --encoding option #1651

jeanas opened this issue Aug 1, 2023 · 2 comments

Comments

@jeanas
Copy link
Member

jeanas commented Aug 1, 2023

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.

@fedelibre
Copy link
Member

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?

@jeanas
Copy link
Member Author

jeanas commented Aug 1, 2023

Ah, yes, thank you, that explains it. (I agree though that in 2023, everything should just use UTF-8.)

@jeanas jeanas closed this as not planned Won't fix, can't repro, duplicate, stale Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants