-
Notifications
You must be signed in to change notification settings - Fork 8
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
UTF_8 issues for "roman-numeral" package #52
Comments
I have no experience with Frescobaldi, but you'll need to set it to wherever lyp's lilypond wrapper script resides, depending on how lyp was installed. To find it, run: $ which lilypond And put the result in Frescobaldi settings. Let me know if this helps. |
I did set it to where the lilypond wrapper script resides
(/usr/local/bin/), and this is the lilypond log I've received when
compiling with frescobaldi.
Starting lilypond 2.18.2 [trashme.ly]...
invalid byte sequence in US-ASCII
Completed successfully in 0.3".
By the way, using the command line in the terminal has no problem.
On Fri, Mar 17, 2017 at 3:37 AM Sharon Rosner <[email protected]> wrote:
I have no experience with Frescobaldi, but you'll need to set it to
wherever lyp's lilypond wrapper script resides, depending on lyp was
installed. To find it,run:
$ which lilypond
And put the result in Frescobaldi settings.
Let me know if this helps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIEdn5a40ZkPWDT7P7tTK7YjrkJ_UwBqks5rmkZdgaJpZM4MgNqW>
.
|
I just installed Frescobaldi 2.2 and successfully compiled a simple file including a \require "assert"
#(assert #t)
{ c d e f } |
Assert works on my machine too (although I don't know what it does). I
guess the problem is not on the wrapper.
The package I was using is roman-numerals
Here is the example code I was trying to compile:
\require "roman-numerals"
bassline = \relative c' {
\clef bass
\key g \major
\time 3/4
g4 fis f
e es es
d2 dis4
e2.
\bar "||"
}
analysis = \lyricmode {
\override LyricText.self-alignment-X = #-0.6
\offset StanzaNumber.X-offset #-3
\set stanza = #"G:"
% For bare Roman numerals, \rN simply outputs the string.
%\markup \rN { I }
I
\markup \rN { V 6 5 }
\markup \rN { vii o 4 3 / IV }
\markup \rN { IV 6 }
\markup \rN { ii h 4 3 }
\markup \rN { Fr +6 }
\markup \rN { I 6 4 }
\markup \rN { vii o 7 / vi }
vi
}
\score {
\new Staff <<
\new Voice = "bass" { \bassline }
\new Lyrics \with {
% to control distance of analysis from staff
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing =
#'((basic-distance . 6.5))
} \lyricsto "bass" { \analysis }
>
\layout {
\context {
\Score
% to control horizontal spacing
\override SpacingSpanner.shortest-duration-space = #6
}
\context {
\Lyrics
% to control global size
%\override LyricText.font-size = #-1
}
}
}
…On Fri, Mar 17, 2017 at 4:30 AM, Sharon Rosner ***@***.***> wrote:
I just installed Frescobaldi 2.2 and successfully compiled a simple file
including a \require command without any problem. Please try compiling
this on your machine:
\require "assert"
#(assert #t)
{ c d e f }
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIEdn27C0-L8X06TxI-CO8YOE7Kpqfb_ks5rmlLSgaJpZM4MgNqW>
.
|
It took a while to get to the bottom of this. The problem is that Frescobaldi does not set or pass the If you're on MacOS, run setenv LC_CTYPE=en_US.UTF-8 And you should be good to go (I don't know how this is done on Linux.) |
Still no luck. |
Please give me some info on your installation:
|
OSX 10.11.6
ruby 2.4.0p0
lyp 1.3.5
…On Sat, Mar 18, 2017 at 1:53 AM, Sharon Rosner ***@***.***> wrote:
Please give me some info on your installation:
- OS
- ruby version
- lyp version
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIEdn3UzKaQTWaJmaTca0UFQjA03NHDHks5rm39MgaJpZM4MgNqW>
.
|
Did you restart Frescobaldi after editing |
Yes I did.
…On Sat, Mar 18, 2017 at 3:32 AM Sharon Rosner ***@***.***> wrote:
Did you restart Frescobaldi after editing /etc/launchd.conf?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIEdn6QIRdm8YksVDk28dbjjQzuq9Q3cks5rm5aEgaJpZM4MgNqW>
.
|
OK, let's try to patch your lilypond gem wrapper script., Add the following line to Encoding.default_external = Encoding::UTF_8 Put this line just after the first ("shebang") line in the script. Let me know if this solves the problem. |
It works.
And it's also safe to delete my /etc/launchd.conf which did not exist in
the first place.
Thanks
Allen
…On Sat, Mar 18, 2017 at 8:05 AM Sharon Rosner ***@***.***> wrote:
OK, let's try to patch your lilypond gem wrapper script., Add the
following line to /usr/local/bin/lilypond (you'll probably need to open
it with sudo to edit it):
Encoding.default_external = Encoding::UTF_8
Put this line just after the first ("shebang") line in the script. Let me
know if this solves the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIEdnxC0BK3QXCu0a2lniNxGvvYSOEkEks5rm9algaJpZM4MgNqW>
.
|
OK. I'll try to find a way to detect this automatically without causing problems for users who use encodings other than UTF-8. |
After installing lilypond with lyp:
When I made /usr/local/bin/lilypond to be the default lilypond version in Frescobaldi, it does not generate any file even after the lilypond log replied compile successful.
When I made ~/.lyp/lilyponds/2.18.2/bin/lilypond as default version, the compiler does not recognize \require command.
Is there a way to make Frescobaldi to compile with lyp version of lilypond?
The text was updated successfully, but these errors were encountered: