Fix dashed line errors (issue 320320043 by david.nales...@gmail.com)

2017-03-06 Thread david . nalesnik
Reviewers: , Message: Please review. Thanks! Description: Fix dashed line errors There are two errors in lily/line-interface.cc which cause dashed lines to be drawn inaccurately. (1) Line-thickness is improperly subtracted from the "off" value in Line_interface::make_dashed_line. This was

Re: GSoC 2017

2017-03-06 Thread Urs Liska
Am 06.03.2017 um 23:46 schrieb tisimst: > On Mon, Mar 6, 2017 at 3:34 PM, Urs Liska [via Lilypond] < > ml-node+s1069038n200802...@n5.nabble.com> wrote: > >> Of course it is good to have optical sizes - even if the vast majority >> of LilyPond users may not even be aware of it. And it's not

Re: Website upload

2017-03-06 Thread Urs Liska
Am 06.03.2017 um 23:43 schrieb Phil Holmes: > Simple answer - I run the GUB uploader. > > Slightly more useful one: there are two aspects to the "website": the > one that is created with "make website". This is a fairly simple > step, and any change to any file that is part of "website" is >

Re: GSoC 2017

2017-03-06 Thread tisimst
On Mon, Mar 6, 2017 at 3:34 PM, Urs Liska [via Lilypond] < ml-node+s1069038n200802...@n5.nabble.com> wrote: > Of course it is good to have optical sizes - even if the vast majority > of LilyPond users may not even be aware of it. And it's not depending on > the number of different sizes in a

Re: Website upload (was: Obsolete GSoC page)

2017-03-06 Thread Phil Holmes
Simple answer - I run the GUB uploader. Slightly more useful one: there are two aspects to the "website": the one that is created with "make website". This is a fairly simple step, and any change to any file that is part of "website" is automatically picked up by the website - it has a pair

Re: [requesting guidance] GSoC LilyPond

2017-03-06 Thread Urs Liska
Hello Adeel, I hope you are by now subscribed to this list. [forwarding from summer-of-c...@gnu.org] Am 06.03.2017 um 15:47 schrieb Urs Liska: > > Hello Adeel, > > > thanks for your interest in LilyPond and GSoC. > > > This message is for you as well as for the other recipients of this post. >

Re: GSoC 2017

2017-03-06 Thread Urs Liska
Am 06.03.2017 um 17:32 schrieb tisimst: > On Mon, Mar 6, 2017 at 1:42 AM, ul [via Lilypond] < > ml-node+s1069038n200762...@n5.nabble.com> wrote: > >> >> Am 06.03.2017 um 07:44 schrieb Werner LEMBERG: > Not yet :-) I can only second what Urs said. I think we (i.e. Abraham and you)

Re: GSoC 2017

2017-03-06 Thread Werner LEMBERG
> 3. IIUC, this was just a set of overrides and callback functions >picking up the correct symbols from a smufl font, doing the >mapping by glyph name. I think this helps already a lot – such a mapping has to be implemented anyway, at least in `convert-ly'. Werner

Re: GSoC 2017

2017-03-06 Thread Urs Liska
Am 06.03.2017 um 23:16 schrieb tisimst: > On Mon, Mar 6, 2017 at 2:34 PM, Noeck [via Lilypond] < > ml-node+s1069038n200797...@n5.nabble.com> wrote: > >> 3. IIUC, this was just a set of overrides and callback functions picking >> up the correct symbols from a smufl font, doing the mapping by

Re: GSoC 2017

2017-03-06 Thread tisimst
On Mon, Mar 6, 2017 at 2:34 PM, Noeck [via Lilypond] < ml-node+s1069038n200797...@n5.nabble.com> wrote: > 1. Nathan was coding this, I just included this into oll and wrote the > post. Correct. > 2. I guess it still works. > Yep. Mostly without problems, but it does have its limitations. >

Website upload (was: Obsolete GSoC page)

2017-03-06 Thread Urs Liska
Phil, could you tell us how you (you do that, isn't it?) how you upload the website? Urs Am 06.03.2017 um 11:59 schrieb Urs Liska: > > Am 6. März 2017 11:41:54 MEZ schrieb Federico Bruni : >> Il giorno lun 6 mar 2017 alle 11:27, Federico Bruni >> ha

Re: GSoC 2017

2017-03-06 Thread Noeck
Hi, Am 06.03.2017 um 09:41 schrieb Urs Liska: >> http://lilypondblog.org/2014/01/smufl-fonts-in-lilypond/ >> >> I don't know whether this is still up to date. > Oh, me neither. > Joram? 1. Nathan was coding this, I just included this into oll and wrote the post. 2. I guess it still works. 3.

Create Bracket class (issue 314610043 by david.nales...@gmail.com)

2017-03-06 Thread david . nalesnik
Reviewers: , Message: Please review. Thanks! Description: Create Bracket class Code involving brackets suffers from two confusing organizational issues: (1) Tuplet_bracket::make_bracket is used to create brackets for a number of grobs: BassFigureBracket, HorizontalBracket, OttavaBracket,

Re: can't upload a patch

2017-03-06 Thread David Nalesnik
On Mon, Mar 6, 2017 at 8:56 AM, David Kastrup wrote: > David Nalesnik writes: > >> On Mon, Mar 6, 2017 at 8:29 AM, Federico Bruni wrote: >>> >>> >>> Il giorno lun 6 mar 2017 alle 14:50, David Nalesnik >>> ha

Re: GSoC 2017

2017-03-06 Thread tisimst
On Mon, Mar 6, 2017 at 1:42 AM, ul [via Lilypond] < ml-node+s1069038n200762...@n5.nabble.com> wrote: > > > Am 06.03.2017 um 07:44 schrieb Werner LEMBERG: > >>> Not yet :-) I can only second what Urs said. > >> I think we (i.e. Abraham and you) should give Matthew some more > >> concrete pointers

Add making web.$(ISOLANG).pdf (issue 319450043 by truer...@gmail.com)

2017-03-06 Thread lemzwerg
LGTM https://codereview.appspot.com/319450043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: can't upload a patch

2017-03-06 Thread David Kastrup
David Nalesnik writes: > On Mon, Mar 6, 2017 at 8:29 AM, Federico Bruni wrote: >> >> >> Il giorno lun 6 mar 2017 alle 14:50, David Nalesnik >> ha scritto: >>> >>> Hi Federico, >>> >>> On Mon, Mar 6, 2017 at 1:15 AM,

Re: can't upload a patch

2017-03-06 Thread Federico Bruni
Il giorno lun 6 mar 2017 alle 15:38, David Nalesnik ha scritto: On Mon, Mar 6, 2017 at 8:29 AM, Federico Bruni wrote: Il giorno lun 6 mar 2017 alle 14:50, David Nalesnik ha scritto: Hi Federico, On Mon, Mar

Re: can't upload a patch

2017-03-06 Thread David Nalesnik
On Mon, Mar 6, 2017 at 8:29 AM, Federico Bruni wrote: > > > Il giorno lun 6 mar 2017 alle 14:50, David Nalesnik > ha scritto: >> >> Hi Federico, >> >> On Mon, Mar 6, 2017 at 1:15 AM, Federico Bruni wrote: >>> >>> Do you have

Re: can't upload a patch

2017-03-06 Thread Federico Bruni
Il giorno lun 6 mar 2017 alle 14:50, David Nalesnik ha scritto: Hi Federico, On Mon, Mar 6, 2017 at 1:15 AM, Federico Bruni wrote: Do you have ca-certificates installed? Yes, the newest version: ca-certificates/now 20141019+deb8u1 all

Re: can't upload a patch

2017-03-06 Thread David Nalesnik
Hi Federico, On Mon, Mar 6, 2017 at 1:15 AM, Federico Bruni wrote: > Do you have ca-certificates installed? Yes, the newest version: ca-certificates/now 20141019+deb8u1 all [installed,local] > > Il 6 marzo 2017 01:23:26 CET, David Nalesnik ha >

Re: Add capability to build Japanese PDF documents (issue 316340043 by truer...@gmail.com)

2017-03-06 Thread trueroad
Thank you for your reviewing. On 2017/03/06 12:40:30, davide.liessi wrote: 2017-03-06 13:32 GMT+01:00 : > https://codereview.appspot.com/316340043/diff/1/Documentation/ja/GNUmakefile#newcode24 > Documentation/ja/GNUmakefile:24: # (This package is for

Re: Add capability to build Japanese PDF documents (issue 316340043 by truer...@gmail.com)

2017-03-06 Thread trueroad
Thank you for your reviewing. https://codereview.appspot.com/316340043/diff/1/Documentation/ja/GNUmakefile File Documentation/ja/GNUmakefile (right): https://codereview.appspot.com/316340043/diff/1/Documentation/ja/GNUmakefile#newcode7 Documentation/ja/GNUmakefile:7: # By default, Japanese PDF

Re: Add capability to build Japanese PDF documents (issue 316340043 by truer...@gmail.com)

2017-03-06 Thread Davide Liessi
2017-03-06 13:32 GMT+01:00 : > https://codereview.appspot.com/316340043/diff/1/Documentation/ja/GNUmakefile#newcode24 > Documentation/ja/GNUmakefile:24: # (This package is for Chinese, but > can also used in Japanese.) > s/in/for/ Also s/can also used/can also be

Add capability to build Japanese PDF documents (issue 316340043 by truer...@gmail.com)

2017-03-06 Thread lemzwerg
LGTm https://codereview.appspot.com/316340043/diff/1/Documentation/ja/GNUmakefile File Documentation/ja/GNUmakefile (right): https://codereview.appspot.com/316340043/diff/1/Documentation/ja/GNUmakefile#newcode7 Documentation/ja/GNUmakefile:7: # By default, Japanese PDF documents are not

Re: Obsolete GSoC page

2017-03-06 Thread Urs Liska
Am 6. März 2017 11:41:54 MEZ schrieb Federico Bruni : >Il giorno lun 6 mar 2017 alle 11:27, Federico Bruni > ha scritto: >> gsoc-2012.html is generated by an existing node: "@node GSoC 2012", >> as shown by the grep above. > >Sorry, you are right: the

Re: Obsolete GSoC page

2017-03-06 Thread Federico Bruni
Il giorno lun 6 mar 2017 alle 11:27, Federico Bruni ha scritto: gsoc-2012.html is generated by an existing node: "@node GSoC 2012", as shown by the grep above. Sorry, you are right: the english file shouldn't be there (only catalan and chinese files).

Re: Obsolete GSoC page

2017-03-06 Thread Federico Bruni
Il giorno lun 6 mar 2017 alle 10:56, Urs Liska ha scritto: IIRC there's a page for every @node, so: $ git grep -i "@node gsoc" Documentation/ca/web/community.itexi:@node GSoC 2012 Documentation/zh/web/community.itexi:@node GSoC 2012 seems to confirm your hypothesis that

Re: Obsolete GSoC page

2017-03-06 Thread Urs Liska
Am 06.03.2017 um 10:16 schrieb Federico Bruni: > > > Il giorno lun 6 mar 2017 alle 7:20, Urs Liska ha > scritto: >> Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: >> >> PS: If I do a google search for `lilypond gsoc', the first hit is >> the old

Re: Obsolete GSoC page (was: GSoC 2017)

2017-03-06 Thread Federico Bruni
Il giorno lun 6 mar 2017 alle 7:20, Urs Liska ha scritto: Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: PS: If I do a google search for `lilypond gsoc', the first hit is the old http://lilypond.org/gsoc.html and only the second hit is the

Re: GSoC 2017

2017-03-06 Thread Urs Liska
Am 06.03.2017 um 07:44 schrieb Werner LEMBERG: >>> Not yet :-) I can only second what Urs said. >> I think we (i.e. Abraham and you) should give Matthew some more >> concrete pointers on where to start investigating. > Can you send him our e-mail conversation regarding this topic? > Currently,