musipedia.org// ?
Deutsch  English  Français  中文 
 

Logging in is required for posting.

Special forum features: inserting music notation, posting audio recordings.

All Categories > Musipedia > Musipedia Features > Bug report: Do not auto-insert escape characters for Lilypond
Total Posts: 7 - Pages (1): [1]
see Author: mu913472
source Posted: Aug 23 2013 - 06:09 AM
follow Subject: re: Bug report: Do not auto-insert escape characters for Lilypond
This is still happening! If I wasn't a very technical user I would have simply walked away unable to contribute.

Here are the steps:
- load an entry such as the sandbox
- click "edit"
- make sure there's a quote in a note
- click "preview"

And you should get the error!

The URL of the popup is:

http://www.musipedia.org/preview.php?fnr=g%27&lily=c,4cg%27%27gaag2Mor-genk%C3%B6mmtderWeih-nachts-mannf4feed2cindieSchu-hub-laaa-d%C3%B6.&key2=\major&key1=c&time1=4&time2=4&pns=Y&minv=N&instr=N&upbeat=

Surely this is a server-side problem?
user picture Author: rt
Posted: Jul 28 2010 - 02:48 PM
click Subject: re: re: Bug report: Do not auto-insert escape characters for Lilypond
pianoman74 wrote:
Preview?
I think not. For if I use the simple interface, I'm unable to enter any melodies at all because of that bug!
As the other user said, yes I have to work around the bug by using an external editor. There is no other way - not currently.


I still can't reproduce it. It would really help if you could give me the concrete steps you take for a concrete example so I can see the problem too.

My concrete example for which it works is the "Sandbox" entry: http://musipedia.org/contour/Sandbox. I edited it, inserted an apostrophe to make the g and subsequent notes an octave higher, saved it, and there was no problem with escaping.

Cheers,

Rainer
Author: pianoman74
Posted: Jul 28 2010 - 03:12 AM
Subject: re: Bug report: Do not auto-insert escape characters for Lilypond
Preview?
I think not. For if I use the simple interface, I'm unable to enter any melodies at all because of that bug!
As the other user said, yes I have to work around the bug by using an external editor. There is no other way - not currently.
user picture Author: rt
Posted: Jul 25 2010 - 09:31 PM
Subject: re: re: Bug report: Do not auto-insert escape characters for Lilypond
btw, no, I don't think it has anything to do with MySQL... it's about passing the Lilypond code from JavaScript to a PHP script. Assuming, of course, that you are talking about the preview functionality.
user picture Author: rt
Posted: Jul 25 2010 - 09:27 PM
Subject: re: Bug report: Do not auto-insert escape characters for Lilypond
pianoman74 wrote:

It's definitely the \ character that must not be there.
I know mysql (which you apparently use ;)) does have huge problems with single quotes from its birth.
I guess that's why you auto-insert the \'s.

Error report:

Processing `blabla4711.ly'
Parsing...
blabla4711.ly:31:9: error: syntax error, unexpected \C[haracter]


Hi Pianoman74,

thanks for pointing this out. I am aware of a problem like this popping up once in a while, but only for the preview. I have fixed this back and forth a couple of times - apparently, JavaScript and PHP and various urlencode and urldecode functions don't always work the same way everywhere (in this case: the JavaScript in your browser urlencodes special characters in one way, and PHP on the server urldecodes them in some other way). To steer this discussion in the right direction, may I ask: Am I assuming correctly that you are talking about the preview functionality? That is, this problem never occurs when you save the record, but only when you hit the preview button?

Cheers,

Rainer
Author: firebat
Posted: Jul 25 2010 - 08:35 PM
Subject: re: Bug report: Do not auto-insert escape characters for Lilypond
I'm having the same problem with the escape character. Someone please fix this. Meanwhile, I guess you could copy & paste the Lilypond source into the text editor as a work around.
Author: pianoman74
Posted: Jul 14 2010 - 12:24 PM
Subject: Bug report: Do not auto-insert escape characters for Lilypond
Hi there,

funny, hardly arrived on here and my first post is a bug report :)
I'm on Firefox.

In the simplified Lilypond interface, I encountered a problem I'm unable to solve from my humble user's side:

Assuming, you're entering:

f8 gis'8

The ' is for one octave up, obviously.
Your parser will create:

...
\override Score.RehearsalMark #'break-visibility = #(vector #t #t #f)
f8 gis\'8

and break the whole caboodle!
It's definitely the \ character that must not be there.
I know mysql (which you apparently use ;)) does have huge problems with single quotes from its birth.
I guess that's why you auto-insert the \'s.

Error report:

Processing `blabla4711.ly'
Parsing...
blabla4711.ly:31:9: error: syntax error, unexpected \C[haracter]
Total Posts: 7 - Pages (1): [1]
You must login to post a message to this conference.

How to insert music:

Add a bit of sheet music, along with a MIDI file, simply by entering note names in Lilypond syntax between the [L] and [/L] tags.
For example, you can try what happens if you enter: [l]g'4 g'4 d''4 d''4 e''4 e''4 d''2[/l] (use the Preview function if you don't actually want to post this).
You can create these lists of note names by clicking on piano keys here.

How to post an audio recording:

If you just want to sing, whistle, or play a melody so that other forum visitors can hear it, follow these steps:

  1. Record your audio here.
  2. You should notice a 32-character hash code, something like: 2a40281c5001c5a7d8c9f57fcdeccfaf
  3. copy this hash code and paste it into a forum post, enclosed in the audio tags, for example: [audio]2a40281c5001c5a7d8c9f57fcdeccfaf[/audio]

How to mark a thread as solved:

If the original question in a thread is solved, please mark it as solved using the "solved" icon (or by just typing [solved] into your post). This makes life easier for people who are willing to identify melodies, since unsolved problems are easier to spot that way. If a problem turns out to not be solved after all, just write [/solved] in a new post, and the thread will be labeled accordingly.