Originally created by: colingh...@gmail.com
Originally owned by: v.villenave
Reported by Samuel Da Mota on Lilypond user here:
http://lists.gnu.org/archive/html/lilypond-user/2012-07/msg00105.html
Hi,
I'm a pretty much new user of lilypond and I have an idea for a almost
dummy new feature: automatically attach lilypond code in pdf.
With pdf files it is possible to attach a file into it. I think it
would be nice to have a lilypond option that attaches the .ly files
into the pdf.
This way when someone creates a partition and upload it to a website,
the code will be uploaded too, thus making it much more easier for any
user to possibly modify it.
Moreover it will help spreading the use of lilypond.
In linux it is easy to do it using pdftk (the command is "pdftk
input_file.pdf attach_files source_file.ly output output_file.pdf").
It may be interesting to automatically call this command just after
the pdf generation. Pdftk seems to be also available under windows and
mac os.
Moreover, if this feature is accepted, it may be interesting to modify
the default tagline which says "engraved by lilypond version x.y.z" to
"engraved by lilypond version x.y.z with source file attached" to
increase its visibility.
Of course, for musicians who doesn't want to share their lilypond
code, this feature should be kept as an option (maybe turned on by
default).
Best Regards,
--
Samuel DA MOTA
Originally posted by: pkx1...@gmail.com
Still keeping on review until I hear different from David K - as he asked for time in comment #23 and I don't see anyone clamouring for this patch to be pushed
Originally posted by: pkx1...@gmail.com
Still keeping on review until I hear different from David K - as he asked for time in comment #23 and I don't see anyone clamouring for this patch to be pushed
Originally posted by: pkx1...@gmail.com
Still keeping on review until I hear different from David K - as he asked for time in comment #23 and I don't see anyone clamouring for this patch to be pushed
Originally posted by: pkx1...@gmail.com
Do I still keep on review or move to 'waiting'? Although I forget why people wanted me to keep the 'waiting' patches listed - but that's not important.
Originally posted by: dak@gnu.org
Currently "waiting". I've started taking a look but, uh, it is quite more tricky than I tried selling to Valentin.
And we don't want to expose absolute paths in the attachments while they might be required for actually getting the files.
Labels: -Patch-review Patch-waiting
Originally posted by: dak@gnu.org
Valentin?
The parser can now be retrieved in Scheme as (*parser*) and in C++ as
scm_fluid_ref (ly_lily_module_constant ("%parser"))
at the point of use (don't try storing it somewhere).
This involved several issues, most notably issue 4422. Hopefully this is the missing piece of the puzzle.
Related
Issues:
#4422Originally posted by: v.villenave
Yep; this should make things easier indeed. I’ll have a look, thanks for the ping!
Diff:
This issue seems to be moribund as there has been no action for over 6 months. Reverting status to Accepted.
Access source files only through LilyPond.
http://codereview.appspot.com/225040043
Passes make, make check and a full make doc.
Diff:
Patch on countdown for March 1st.
Make parser arg optional
http://codereview.appspot.com/225040043
passes make, make check and a full make doc.
Patch on countdown for March 4th
Remove source file heading
http://codereview.appspot.com/225040043
Passes make, make check and a full make doc
Patch on countdown for March 7th.