denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] Final version, with pdf defect?


From: Richard Shann
Subject: Re: [Denemo-devel] Final version, with pdf defect?
Date: Sun, 06 Nov 2011 19:13:15 +0000

On Sun, 2011-11-06 at 08:07 -0600, Jeremiah Benham wrote:
> The gtk3 branch does not yet compile. One thing I am stuck in now is the 
> gtksourceview stuff (specifically the string searching stuff). 
That is search and replace in the scheme window - well, certainly low
priority then :)

> 
> If you like I can give you ssh access to a system that you can use to build.
If it doesn't involve too much effort I could give it a try...

Richard

> 
> Jeremiah
> 
> Sent from my Samsung smartphone on AT&T
> 
> Richard Shann <address@hidden> wrote:
> 
> >On Sat, 2011-11-05 at 19:27 +0000, Richard Shann wrote:
> >> On Thu, 2011-11-03 at 15:55 -0500, Jeremiah Benham wrote:
> >> > We can release. The gtk3 stuff is not ready yet
> >
> >aargh! I was forgetting, this means that the evince stuff will not work
> >on any reasonably modern distro. Is there anything in problematic still
> >about the gtk3 port? Can I help?
> >Also, I should bump the version number of the .denemo file format (well
> >I need to check, but I think there are incompatibilities)
> >
> >Richard
> >
> >
> >
> >
> >> . We can put it into the release after this one perhaps. So when shall I 
> >> create branch 0.9.4? Tarball release this sunday?
> >> Well, I'll try and update the docs this week and then we should
> >>       * copy the new features to the change log
> >>       * create the branch
> >>       * upload the candidate tarball to denemo.org
> >>       * download and test that it is ok
> >>       * final upload to ftp.gnu.org 
> >> We could aim for Sunday 13th November if you prefer a weekend, otherwise
> >> midweek is generally better for announcements.
> >> 
> >> Richard
> >> 
> >> 
> >> > 
> >> > Jeremiah
> >> > 
> >> > Sent from my Samsung smartphone on AT&T
> >> > 
> >> > Richard Shann <address@hidden> wrote:
> >> > 
> >> > >I have run the same LilyPond version under windows and generated the pdf
> >> > >http://www.denemo.org/dl31 which displays correctly in evince under
> >> > >linux and acrord32 under windows. It is also smaller because I have
> >> > >taken out all the point-and-click links.
> >> > >I think this is ready to go to press. However, until we make a release,
> >> > >very few people will be able to make use of the source file :(
> >> > >
> >> > >Any enthusiasm for a release?
> >> > >
> >> > >Richard
> >> > >
> >> > >
> >> > >
> >> > >On Thu, 2011-11-03 at 18:20 +0000, Richard Shann wrote:
> >> > >> On Thu, 2011-11-03 at 11:30 -0500, Jeremiah Benham wrote:
> >> > >> > On 11/03/2011 08:08 AM, Richard Shann wrote:
> >> > >> > > I have uploaded a final version of the Keyboard Polyphony 
> >> > >> > > example. The
> >> > >> > > pdf is
> >> > >> > > http://www.denemo.org/dl29
> >> > >> > >
> >> > >> > > and the source file is
> >> > >> > >
> >> > >> > > http://www.denemo.org/dl30
> >> > >> > >
> >> > >> > > this source has an include file, so you may need to run the 
> >> > >> > > Dynamic
> >> > >> > > Directive Refresh command before it will print (it is for the book
> >> > >> > > titles - re-doing the titles will also work, and nothing is 
> >> > >> > > needed if
> >> > >> > > you have installed to /usr/local).
> >> > >> > >
> >> > >> > > My PDF reader displays the treble clef wrongly, if you also see 
> >> > >> > > this and
> >> > >> > > have a recent version of LilyPond can you try re-printing it to 
> >> > >> > > see if
> >> > >> > > this is a bug that has been fixed. It does not show this problem 
> >> > >> > > in 20pt
> >> > >> > > font size, only 18 pt.
> >> > >> > 
> >> > >> > The treble cleff's did look fine for me at 18pt using lilypond 
> >> > >> > 2.12.3.
> >> > >> Which viewer program did you use? I downloaded dl29 onto a windows
> >> > >> laptop and viewed it in Adobe reader. The treble clef was only 
> >> > >> slightly
> >> > >> broken on the right side of the top loop. The same file viewed with
> >> > >> evince and xpdf (which I think use the same underlying library) filled
> >> > >> in the top loop of the treble clef in black.
> >> > >> 
> >> > >> >  
> >> > >> > The pdf that you sent had distorted treble cleff's. What version of 
> >> > >> > lilypond do you have?
> >> > >> lilypond --version
> >> > >> GNU LilyPond 2.12.3
> >> > >> 
> >> > >> So that is quite strange - you get Denemo to generate a pdf via from
> >> > >> dl30 and it looks different to dl29, and yet we have the same 
> >> > >> installed
> >> > >> LilyPond... Hmm.
> >> > >> I'll try the LilyPond that is installed on my windows laptop.
> >> > >> Thanks for the feedback
> >> > >> Richard
> >> > >> 
> >> > >> 
> >> > >> > 
> >> > >> > Jeremiah
> >> > >> > 
> >> > >> > 
> >> > >> > > I have included a better epilog in this version, and fixed the 
> >> > >> > > final
> >> > >> > > chords to conform with the traditional appearance. The entire 
> >> > >> > > file is
> >> > >> > > created without inserting any special purpose LilyPond text, that 
> >> > >> > > is
> >> > >> > > just (now-standard) Denemo commands.
> >> > >> > >
> >> > >> > > Richard
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > _______________________________________________
> >> > >> > > Denemo-devel mailing list
> >> > >> > > address@hidden
> >> > >> > > https://lists.gnu.org/mailman/listinfo/denemo-devel
> >> > >> > 
> >> > >> > 
> >> > >> > _______________________________________________
> >> > >> > Denemo-devel mailing list
> >> > >> > address@hidden
> >> > >> > https://lists.gnu.org/mailman/listinfo/denemo-devel
> >> > >> 
> >> > >> 
> >> > >> 
> >> > >> _______________________________________________
> >> > >> Denemo-devel mailing list
> >> > >> address@hidden
> >> > >> https://lists.gnu.org/mailman/listinfo/denemo-devel
> >> > >
> >> > >
> >> 
> >> 
> >> 
> >> _______________________________________________
> >> Denemo-devel mailing list
> >> address@hidden
> >> https://lists.gnu.org/mailman/listinfo/denemo-devel
> >
> >





reply via email to

[Prev in Thread] Current Thread [Next in Thread]