After some testing, it seems that using the Text Object is the best way to go in terms of storing the generation of the lilypond syntax either to compile together for use with your object/script, or as a "dictionary" of sorts to translate midi->lilypond. It seems to not have "programming" traits like coll and sprintf, and treats backslash and comma normally. You can also send it commands for carriage returns and have it spit out specific lines, and write to file with a .ly extension, eliminating the need to pass the str into Ruby at all, just call the file from the script. I will let you know how further tests go.
PS sorry for the back-to-back comments... just thought I would pass along that tidbit, because it makes this whole approach feasible again.
Quick Update
After some testing, it seems that using the Text Object is the best way to go in terms of storing the generation of the lilypond syntax either to compile together for use with your object/script, or as a "dictionary" of sorts to translate midi->lilypond. It seems to not have "programming" traits like coll and sprintf, and treats backslash and comma normally. You can also send it commands for carriage returns and have it spit out specific lines, and write to file with a .ly extension, eliminating the need to pass the str into Ruby at all, just call the file from the script. I will let you know how further tests go.
PS sorry for the back-to-back comments... just thought I would pass along that tidbit, because it makes this whole approach feasible again.