Re: Pre-review questions about image(s) and translations

2014-01-15 Thread Carl Peterson
On Wed, Jan 15, 2014 at 10:15 AM, Urs Liska wrote: > Am 15.01.2014 16:13, schrieb Paul Morris: > > Urs Liska wrote >> >>> a) in what form should I provide such an image that it can be translated >>> and modified in the future? >>> >> >> Since your image is simply boxes with text and arrows conne

Re: Pre-review questions about image(s) and translations

2014-01-15 Thread Carl Peterson
On Tue, Jan 14, 2014 at 11:51 AM, Urs Liska wrote: > > > As you can see I have created a flowchart to visualize the relation > between the different parts of the editing cycle. > > If it were simple the two PNG files I knew that I would have to add them > to lilypond-extra and open a pull request

Re: PATCHES: Countdown for January 15th - 06:00 GMT

2014-01-12 Thread Carl Peterson
%3APatch-new%20OR%20label%3APatch-push&sort=patch&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified> > Enhancement > Carl Peterson push Patch: Cleanup of ugly MI and SOL shaped noteheads > > > > > Patch attached, if someone can pus

Re: 3.0?

2014-01-11 Thread Carl Peterson
On Sat, Jan 11, 2014 at 11:50 PM, Paul Morris wrote: > Carl Sorensen-3 wrote > > I can't speak for Carl P's work. For me, effective LP input files > require > > structure (variables, contexts) that MusicXML knows nothing of. And it's > > generally easier to create them than to fix them on import

Re: 3.0?

2014-01-10 Thread Carl Peterson
On Fri, Jan 10, 2014 at 4:25 PM, Urs Liska wrote: > > Well, > compiling a few measures of a single staff feels nearly instantaneous, and > when you're editing an orchestral score this makes a huge difference. > > Generally I'd think it would be a good idea to have such an interface in > Frescobal

Re: 3.0?

2014-01-10 Thread Carl Peterson
On Fri, Jan 10, 2014 at 12:46 AM, Paul Morris wrote: > Carl Peterson wrote > > I use MuseScore, > > Scorio, and Finale Notepad (depending on where I am and how I feel) > > for compositional work because they provide ease of note entry in the > > composing process and

Re: 3.0?

2014-01-09 Thread Carl Peterson
On Thu, Jan 9, 2014 at 6:20 AM, David Kastrup wrote: > Another problem is that LilyPond has a usage philosophy and workflow > that strongly penalizes manual tweaks. Graphically/manually oriented > workflows detract from the importance of getting good default > typesetting. I don't know that I ag

Re: Web:Introduction: Rename "Our Goal" box (issue 48430043)

2014-01-07 Thread Carl Peterson
On Tue, Jan 7, 2014 at 9:16 AM, Phil Holmes wrote: > - Original Message - From: "Urs Liska" > > >>> I believe I had suggested "purpose." I realize that's not much better >>> than goal/mission, but it's less corporate than "mission," and is more >>> focused on why we exist than what we thi

Re: Web:Introduction: Rename "Our Goal" box (issue 48430043)

2014-01-07 Thread Carl Peterson
On Tue, Jan 7, 2014 at 8:34 AM, Urs Liska wrote: > Am 07.01.2014 14:32, schrieb Carl Sorensen: > >> >> On Jan 7, 2014, at 3:56 AM, "Phil Holmes" wrote: >> >>> - Original Message - From: >>> To: >>> Cc: ; >>> Sent: Tuesday, January 07, 2014 10:45 AM >>> Subject: Re: Web:Introduction: Re

Re: License of files in Documentation/pictures and ability to distribute them unclear

2014-01-04 Thread Carl Peterson
On Sat, Jan 4, 2014 at 10:51 PM, Graham Percival wrote: > On Fri, Jan 03, 2014 at 03:28:22PM -0800, Don Armstrong wrote: >> It's great that a lot of them have the source which they were built from >> present, but there are some which are still missing the source. [For >> example, logo-debian.png c

Re: LILY-GIT PITA

2014-01-02 Thread Carl Peterson
On Wed, Jan 1, 2014 at 10:12 AM, James wrote: > On 07/12/13 18:33, Carl Sorensen wrote: >> I've thought of some possible fixes: >> >> 1) Add an "expert mode" button that then would open up a listbox that >> would allow you to choose your branch. >> >> 2) Create a special, branch-unaware version of

Re: Content of "Introduction"->"Our Goal"

2014-01-01 Thread Carl Peterson
On Wed, Jan 1, 2014 at 5:16 PM, Urs Liska wrote: > Am 01.01.2014 18:34, schrieb Phil Holmes: > >> - Original Message - From: "Urs Liska" >> To: "LilyPond Development Team" >> Sent: Wednesday, January 01, 2014 5:03 PM >> Subject: Content of "Introduction"->"Our Goal" >> >> [snip] >> >> I

Re: Cleanup of ugly MI and SOL shaped noteheads (issue 45160043)

2013-12-31 Thread Carl Peterson
On Tue, Dec 31, 2013 at 12:29 PM, wrote: > On 2013/12/24 23:22:00, Carl P. wrote: > >> This may well need to happen. As I said, I've tried a few times over > > the >> >> last 8 or 9 months to inquire about the mi head particulary, with no >> response. > > > If you're the only person on the lists

Re: Cleanup of ugly MI and SOL shaped noteheads (issue 45160043)

2013-12-24 Thread Carl Peterson
On Dec 24, 2013 5:57 PM, wrote: > > The extra width on the "ugly" mi notes was a specific design decision > that was made in conjunction with the shape note community at the time > (see https://code.google.com/p/lilypond/issues/detail?id=1060). > I've wondered this, but I had been unable to determ

Re: Problems with git cl

2013-12-24 Thread Carl Peterson
On Tue, Dec 24, 2013 at 7:31 AM, James wrote: > Hello, > Is 'git-cl upload master' (which works for me) the same as 'git-cl upload > origin/master'? > I received the same error either way. > This error sounds familiar to me anyway :) > > Are you using Lily-git.tcl? > I have been, intermixed with

Problems with git cl

2013-12-24 Thread Carl Peterson
Trying to upload a follow-up patch for my notehead change. When I try to run "git cl upload origin/master," I get fatal: ref HEAD is not a symbolic ref Command "git symbolic-ref HEAD" failed What am I doing wrong? Carl P. ___ lilypond-devel mailing li

Re: Fwd: Issue 3714 in lilypond: website: use colors to distinguish each manual and stable vs. development

2013-12-21 Thread Carl Peterson
On Sat, Dec 21, 2013 at 5:51 AM, David Kastrup wrote: >> Pushed them to staging. Can you try word wrapping the lines of the >> commit messages next time? I noticed this only after pushing. > If > you actually fix previous aspects of the _same_ patch series, you should > likely reorganize the se

Fwd: Issue 3714 in lilypond: website: use colors to distinguish each manual and stable vs. development

2013-12-20 Thread Carl Peterson
r and someone can push it for you. Patches attached. Can someone push? Thanks, Carl P. From a3c461efca539350e3da4f25423895bbf6f78519 Mon Sep 17 00:00:00 2001 From: Carl Peterson Date: Sun, 8 Dec 2013 11:44:08 -0500 Subject: [PATCH 1/5] Add classes to tag of documentation files To facilitate request

Re: Simplified version of Trevor Daniels' SATB framework. (issue 38720045)

2013-12-18 Thread Carl Peterson
On Wed, Dec 18, 2013 at 5:34 PM, wrote: > I'm not sure about using the default paper > margins. The printed output goes very close > to the left margin and the bottom of the bass > staff is cut off on some pages. Either LP's > defaults should be changed or we include the > values I suggested or

Re: Web: Download: Add introductory text (issue 40510046)

2013-12-18 Thread Carl Peterson
On Wed, Dec 18, 2013 at 5:30 AM, Graham Percival wrote: > On Mon, Dec 16, 2013 at 01:50:53PM -0500, Carl Peterson wrote: >> (2) utilizing back-end scripting (PHP, etc.) to custom-serve the >> content based on the http header. > > We're using a donated web-server,

Re: Web: Download: Add introductory text (issue 40510046)

2013-12-16 Thread Carl Peterson
On Mon, Dec 16, 2013 at 4:25 AM, David Kastrup wrote: > Carl Peterson writes: >> Just thinking out loud here...would it be worth looking into tweaking the >> .htaccess file to do OS-based redirection on the download page, like many >> sites do? That way, if someone request

Re: Web: Download: Add introductory text (issue 40510046)

2013-12-15 Thread Carl Peterson
On Dec 16, 2013 12:16 AM, "Graham Percival" wrote: > > On Sun, Dec 15, 2013 at 01:23:51PM +0100, Urs Liska wrote: > > It was consensus that new users should actively be encouraged to > > download one of the complete environments, namely Frescobaldi or > > Denemo, which would then take care of inst

Re: Issue 3720: Built-in templates for SATB vocal scores (issue 41990043)

2013-12-15 Thread Carl Peterson
On Sun, Dec 15, 2013 at 2:40 PM, wrote: > Good point. The SA-TB template pair puts SA on one > staff and TB on another, but in this revision it has > only verses between. There is no reason why it should > not also have soprano lyrics above, bass lyrics below > and alto and tenor lyrics in-betw

Re: Issue 3720: Built-in templates for SATB vocal scores (issue 41990043)

2013-12-15 Thread Carl Peterson
On Sun, Dec 15, 2013 at 4:51 AM, wrote: > > On 2013/12/14 23:17:55, Keith wrote: >> >> On 2013/12/14 22:32:06, Devon Schudy wrote: >> > This interface is unlike any other in Lilypond, > > >> This was intended not as an interface to a built-in bulletproof > > engine, but >> >> rather a template tha

Re: Enable manual-specific styling of documentation; issue 3714 (issue 36480048)

2013-12-14 Thread Carl Peterson
On Sat, Dec 14, 2013 at 1:50 AM, James wrote: > On 14/12/13 05:57, Carl Peterson wrote: >> I have updated the patch in Rietvald > > > But not the tracker. So the patch will not get tested. > > Please remember to either use git-cl or change the tracker to patch-new > wh

Re: Enable manual-specific styling of documentation; issue 3714 (issue 36480048)

2013-12-13 Thread Carl Peterson
On Fri, Dec 13, 2013 at 10:41 PM, Graham Percival wrote: > On Fri, Dec 13, 2013 at 10:02:23AM -0500, Carl Peterson wrote: >> On Thu, Dec 12, 2013 at 7:36 PM, wrote: >> > I think that the index sidebar colors are too dark. They dominate the >> > page, in my opinon.

Re: Enable manual-specific styling of documentation; issue 3714 (issue 36480048)

2013-12-13 Thread Carl Peterson
On Thu, Dec 12, 2013 at 7:36 PM, wrote: > I think that the index sidebar colors are too dark. They dominate the > page, in my opinon. In the current design, the sidebar color and the > highlight box fill color are the same. Why not keep it that way? Attaching another option, to address your c

Re: Enable manual-specific styling of documentation; issue 3714(issue 36480048)

2013-12-13 Thread Carl Peterson
On Fri, Dec 13, 2013 at 8:31 AM, James wrote: > On 13/12/13 13:04, Phil Holmes wrote: > > Thanks for what you're doing, but please don't put a lot of images on the > Google Issue tracker. For bizarre reasons only known to themselves, the > storage available for attachments is _very_ limited. By

Re: Enable manual-specific styling of documentation; issue 3714 (issue 36480048)

2013-12-12 Thread Carl Peterson
On Thu, Dec 12, 2013 at 1:06 AM, wrote: > > Message: > Patch for initial solution to issue 3714, regarding color-coding of > manuals. > > Please review this at https://codereview.appspot.com/36480048/ I have submitted follow-up patches to Rietveld to address comments regarding the duplicate CSS

Re: Enable manual-specific styling of documentation; issue 3714 (issue 36480048)

2013-12-12 Thread Carl Peterson
On Thu, Dec 12, 2013 at 4:10 AM, wrote: > LGTM, although it is difficult to visualise > the effect of the various colours without seeing > them. > > https://codereview.appspot.com/36480048/ > I'll see what I can do about getting representative screenshots. ___

Re: Enable manual-specific styling of documentation; issue 3714 (issue 36480048)

2013-12-12 Thread Carl Peterson
On Thu, Dec 12, 2013 at 7:49 AM, Carl Peterson wrote: > On Thu, Dec 12, 2013 at 2:21 AM, wrote: > >> LGTM, with one small nit. >> >> >> https://codereview.appspot.com/36480048/diff/1/ >> Documentation/css/lilypond-manuals.css >> File Documentation/css

Re: Enable manual-specific styling of documentation; issue 3714 (issue 36480048)

2013-12-12 Thread Carl Peterson
On Thu, Dec 12, 2013 at 2:21 AM, wrote: > LGTM, with one small nit. > > > https://codereview.appspot.com/36480048/diff/1/Documentation/css/lilypond- > manuals.css > File Documentation/css/lilypond-manuals.css (right): > > https://codereview.appspot.com/36480048/diff/1/Documentation/css/lilypond-

Re: contributing instructions are misleading!

2013-12-11 Thread Carl Peterson
On Wed, Dec 11, 2013 at 11:56 PM, Graham Percival wrote: > On Wed, Dec 11, 2013 at 11:26:55PM -0500, Carl Peterson wrote: > >In my searching, I didn't find a page that really did this. Section > 1.2 of > >the current CG should theoretically do this (based

Re: contributing instructions are misleading!

2013-12-11 Thread Carl Peterson
On Wed, Dec 11, 2013 at 10:35 PM, Graham Percival wrote > > Fixing this doesn't require a reorganization. It requires > deleting the two incorrect bits, dumping a @ref{Submitting a > patch} or whatever the @node is called. On a similar note, > there's at least 2 "checklists before submitting a pa

Re: contributing instructions are misleading!

2013-12-11 Thread Carl Peterson
On Wed, Dec 11, 2013 at 9:54 PM, Graham Percival wrote: > On Wed, Dec 11, 2013 at 01:48:54PM +0100, Janek Warchoł wrote: > > PS ccing to Graham because he might be interested to know that > > Someone(TM) is doing Something(TM) to help new contributors! > > Sorry, this awoke Grumpy Graham. > > Reor

Re: branching

2013-12-10 Thread Carl Peterson
On Tue, Dec 10, 2013 at 3:21 PM, Mike Solomon wrote: > > The only hassle for me, which I did not run up against when I started with > the project, is David’s way of communicating. I’m not claiming this is all > on him, but I’m also pretty sure that I’m not the only one who has peaced > out becau