Updates:
Status: Fixed
Labels: fixed_2_13_17
Comment #6 on issue 993 by percival.music.ca: translation infrastructure
for new website
http://code.google.com/p/lilypond/issues/detail?id=993
Fixed the general infrastructure. Translators might want to take a look at
things.
Comment #1 on issue 1050 by percival.music.ca: website translations should
use gettext
http://code.google.com/p/lilypond/issues/detail?id=1050
Oh wait: before blithely adding gettext, check what would be required to
make it work
with "make website". Running make -C po/ might require ./con
Status: Accepted
Owner:
Labels: Type-Build Priority-Medium Maintainability website
New issue 1050 by percival.music.ca: website translations should use gettext
http://code.google.com/p/lilypond/issues/detail?id=1050
Currently, the website translation requires editing
scripts/build/website_p
dynamic_cast? (or maybe my mind is corrupted by 15 years
> of Smalltalk, and this is a standard C quirk?)
Oops, keyboard failure, obviously meant "C quirk"!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailma
Replace constrained-breaking.cc:461 by
>
> Interval begin_extent = sys->begin_of_line_extent (start, end);
> Interval rest_extent = sys->rest_of_line_extent (start, end);
Ok, experimenting with this, I am inclined to *add* instead of
*replacing*. The extent_ member of Line_details is touche
On Mon, 2010-03-29 at 21:25 -0400, Boris Shingarov wrote:
> Hi Joe,
>
> > Replace constrained-breaking.cc:461 by
> >
> > Interval begin_extent = sys->begin_of_line_extent (start, end);
> > Interval rest_extent = sys->rest_of_line_extent (start, end);
> >
> > and replace constrained-break
On Mon, 2010-03-29 at 20:49 -0400, Boris Shingarov wrote:
> > I'd rather discuss this point now, because I don't like the extension of
> > Interval (and I'd rather you didn't spend a whole lot of time getting it
> > to work if there is a nicer way)
>
> No kidding, neither do I like diluting I
Hi Joe,
Replace constrained-breaking.cc:461 by
>
> Interval begin_extent = sys->begin_of_line_extent (start, end);
> Interval rest_extent = sys->rest_of_line_extent (start, end);
>
> and replace constrained-breaking.cc:485 by something analogous.
Btw, it's not clear to me what the invers
I'd rather discuss this point now, because I don't like the extension of
> Interval (and I'd rather you didn't spend a whole lot of time getting it
> to work if there is a nicer way)
No kidding, neither do I like diluting Interval. One, it is an extremely
hacky way to do things. Two, it *do
On Mon, 2010-03-29 at 17:04 -0400, Boris Shingarov wrote:
> > Do we really need this to be included in every Interval? I'd have
> > thought that the only data structure that needs to change is
> > Line_details.
>
> Right, but how do you get the actual value in there?
Replace constrained-brea
On Mon, 29 Mar 2010 12:04:42 -0700, Joe Neeman wrote:
but I think you don't need to store an
> extra version of rod-height. Just define rod-height to measure the
> bottom of the last staff (whether that bottom comes from
> begin_of_line_extent or rest_of_line_extent). Each time you add a sta
Do we really need this to be included in every Interval? I'd have
> thought that the only data structure that needs to change is
> Line_details.
Right, but how do you get the actual value in there?
It's filled from calling the Y-extent Scheme function, which can be
anything, and in most cases
On Mon, 2010-03-29 at 15:53 -0400, Boris Shingarov wrote:
> On Mon, 29 Mar 2010 08:48:35 -0700, Joe Neeman wrote:
>
> > Keep in mind that a lyric line is the same as a staff to the
> > page-breaker. Don't your one-staffers have lyrics? If so, they are
> > really two-staffers and so the probl
On Mon, 29 Mar 2010 08:48:35 -0700, Joe Neeman wrote:
Keep in mind that a lyric line is the same as a staff to the
> page-breaker. Don't your one-staffers have lyrics? If so, they are
> really two-staffers and so the problem could still be in the
> within-system estimation.
My one-staffe
On Wed, 2010-03-24 at 22:01 -0400, Boris Shingarov wrote:
> First of all, thank you Joe for all the explanations -- now that it
> has dawned on me what the source of confusion was, it all
> makes sense. Thanks!!
>
> > I am now thinking about how to implement this TODO best.
> > One idea that
On Wed, 2010-03-24 at 19:42 -0400, Boris Shingarov wrote:
> On Wed, 24 Mar 2010 18:15:45 -0400, Boris Shingarov wrote:
> > Hmm, let me understand this better.
> > Does it mean that Constrained_breaking::fill_line_details() gets
> > called before the line breaks are calculated, and then again
Status: Accepted
Owner:
Labels: Type-Build Priority-Low Maintainability
New issue 1049 by percival.music.ca: GUB should push git tags
http://code.google.com/p/lilypond/issues/detail?id=1049
GUB automatically adds a tag for each release, but those tags should also
be uploaded (pushed).
--
17 matches
Mail list logo
