James | 23 Apr 14:40 2014
Picon

PATCHES: Countdown for April 26th - 06:00 BST

Hello,

3904 Documentation Federico Bruni countdown robots.txt: disallow old stable and old development doc






3905 Enhancement Urs Liska review Patch: Doc: Clarify grace note synchronisation workaround






3239 Enhancement Janek Warchol waiting Patch: rewrite Self_alignment_interface May 2013
3186 Ugly Janek Warchol waiting Positioning of "8" under clef symbol in G_8 clef   Bounty Jan 26
3156 Enhancement Mike Solomon waiting Patch: Prevents vertical axis groups with empty skylines Feb 2013
3134 Enhancement Mike Solomon waiting Patch: Removes the translate_axis call from axis-group-interface outside-staff positioning. Aug 2013
2812 Documentation Keith Ohara waiting Renaming to distinguish keySignature from KeySignature Nov 11
2716 Enhancement David Kastrup waiting Patch: Implement music functions in Scheme rather than C++ Aug 2012
<!-- BODY,DIV,TABLE,THEAD,TBODY,TFOOT,TR,TH,TD,P { font-family:"Liberation Sans"; font-size:x-small } -->

James
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
lilyliska | 22 Apr 20:56 2014

Doc: Clarify grace note synchronisation workaround (issue 90270044)

Reviewers: ,

Description:
Doc: Clarify grace note synchronisation workaround

As pointed out in the thread
http://lists.gnu.org/archive/html/lilypond-user/2014-04/msg00540.html
it is necessary to use \grace for the old grace note sync issue.
This commit makes that explicit in the known issues section in the NR

Please review this at https://codereview.appspot.com/90270044/

Affected files (+6, -0 lines):
   M Documentation/notation/rhythms.itely

Index: Documentation/notation/rhythms.itely
diff --git a/Documentation/notation/rhythms.itely  
b/Documentation/notation/rhythms.itely
index  
9ca613ed753d4e025dac2bbfdcd9d3a4fb3ce5b1..51178310127983208de660bc91adee23d4a53e4e  
100644
--- a/Documentation/notation/rhythms.itely
+++ b/Documentation/notation/rhythms.itely
 <at>  <at>  -3511,6 +3511,12  <at>  <at>  durations in the other staves.  For the above example
  >>
   <at> end lilypond

+Please make sure that you use the  <at> cmd{\grace} command for the
+spacer part, even if the visual part uses  <at> cmd{\acciaccatura} or
+ <at> cmd{\appoggiatura} because otherwise an ugly slur fragment will
+be printed, connecting the invisible grace note with the following
+note.
+
  The use of grace notes within voice contexts confuses the way the voice
  is typeset. This can be overcome by inserting a rest or note between the
  voice command and the grace note.
tisimst | 21 Apr 19:19 2014
Picon

Question about customizing emmentaler font

I am developing a /relatively/ easy python script to allow a person to tweak
the default Emmentaler font as they desire without needing to mess with
metafont, but by simply modifying the .OTF files in FontForge. I feel like
I've gotten things /mostly/ under control, but I am running into two issues
that I just can't figure out.

The first has to do with the glyphs, which I tweaked a little, that come
from the feta-alphabet subfonts (i.e., the time-signature numerals and the
dynamics letters) which for some reason default to some other font for the
numbers and letters and don't use those in my font at all:

<http://lilypond.1069038.n5.nabble.com/file/n161702/timesignature-and-dynamics.png> 

The other issue appears with the arpeggio element and, I suspect, also with
the trill element (though I haven't tried it explicitly), neither of which
did I modify at all. As can be seen below, the glyph doesn't connect for a
continuous look:

<http://lilypond.1069038.n5.nabble.com/file/n161702/arpeggio-and-dynamics.png> 

I have combed through the source code, but I couldn't find anything remotely
obvious as to why this would be the case.  There also appears to be some
kerning information for these glyphs that I think I've figured out, but not
sure. Let's just say I am at a loss without some help from someone more
intimately involved in the data required to render these glyphs (Han-wen?
Werner?)

Now, why am I doing this? 

Well, Although creating a new music notation font is definitely fun, there's
another more important reason for this. I'm an engineer by trade with some
manufacturing experience. I also love singing and playing the piano and
computer programming, which makes using LilyPond quite enjoyable. As I have
looked at the notation glyphs from older (and IMHO more beautiful) scores
that are hand engraved and printed, there is an artistic aspect of the glyph
designs that is still missing from Emmentaler. I am, in NO WAY, saying that
Emmentaler is a poorly designed font. It is VERY NICE and I offer my highest
regards to those who developed it. I know it took a ton of work.

Here's what's missing, and I don't know how metafont can capture this. Much
of the focus of the design of Emmentaler font has been around the
*/engraving/* part, which is HUGELY important. However, one thing we are
forgetting (which may not be important to others, but I see as more
critical) is the design AND FABRICATION of the punches that were used. Let
me explain what I mean. 

In order to cut metal, I have to have a tool that is */sharp/*. How sharp?
Well, that's relative I suppose, but let's assume I have a tool with
knife-like edge that is hard enough to cut, say, the treble clef punch at a
particular size. Now, this knife edge is only so sharp and, when cutting
metal, isn't likely to be used like we would use a knife to carve wood. On
the contrary, it would be used more like a chisel and would be able to
create a /smallest/ feature size, like for an interior corner. This is the
most obvious kind of feature that most people don't think about when
creating a classical-looking font. Exterior corners can be made sharp--/no
problem!/--because I am not limited in size by the tool I'm using to create
it. On the other hand, the interior corners are /*NEVER EVER EVER* going to
be sharp/ because I simply do not have a strong enough tool with a sharp
enough edge to cut a perfectly sharp interior corner. Even nowadays with our
advanced manufacturing processes, this is a difficult and very expensive
challenge. 

What this means: in order to have a truly authentic, classically engraved
look, ALL interior corners should be rounded-ish, and the rounded-ness
should remain optically constant (i.e., for emmentaler-26, the internal
rounds would be optically the same size as those for emmentaler-11, but in
the font itself, the rounds would be /MUCH LARGER/ for emmentaler-11 than
emmentaler-26 because the intended print size is /MUCH SMALLER/). I realize
that using a traditional printing press with liquid ink will also contribute
to the final size of these rounds, so what this "minimum feature size"
should be is certainly debatable. I know that not everyone would agree with
the need to add this feature, or with any of the other changes I've made,
but take it for what it's worth. I think it would add a very nice touch to
Emmentaler.

(phew!)

Wow, I didn't mean for all that to come out right now, but I thought I'd
share some thoughts on this matter. I just LOVE LOVE LOVE LOVE the printed
look of hand-engraved scores, and the Emmentaler font does great for the
most part, but I don't feel like it quite captures some unmistakable
hand-engraved features of the whole engraving/printing process needed to
make computer-generated scores look more authentic and less
computer-generated. There are even more features that I love, but would be
most difficult to mimic, so I won't go there (yet).

So, back to my original reason for posting this. Can someone help me figure
out why the dynamic letters and time-signature numbers won't appear like
they should from my font and why the arpeggio elements won't line up? I know
there's kerning involved, but I don't suspect that is the issue. I know the
glyphs are there in the font, so that's also not the issue. Thanks for your
help and keep up the excellent work!

-Abraham

--
View this message in context: http://lilypond.1069038.n5.nabble.com/Question-about-customizing-emmentaler-font-tp161702.html
Sent from the Dev mailing list archive at Nabble.com.
MacUpdate Content Team | 21 Apr 12:57 2014

Your app listing has been updated on MacUpdate.com

Hi lilypond.org,

We have updated your application listing for LilyPond 2.19.5-1 on MacUpdate.com. Please take a moment to review your application's information to make sure that everything is correct.

You may view your updated listing by visiting:
https://www.macupdate.com/app/mac/19024/lilypond


Create a Developer Account today to reply to comments and view stats:
https://www.macupdate.com/developers/signup/


You may submit new updates, or changes to your app listing here:
https://www.macupdate.com/developers/update/


Questions? Contact our Content Update Team updates <at> macupdate.com.

Thank you for being part of the MacUpdate Software Community!:

-The MacUpdate Team



_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
fedelogy | 19 Apr 16:37 2014
Picon

issue 3904: disallow old stable and old dev doc in robots.txt (issue 89460044)

Reviewers: ,

Description:
issue 3904: disallow old stable and old dev doc in robots.txt

Please review this at https://codereview.appspot.com/89460044/

Affected files (+2, -0 lines):
   M Documentation/web/server/robots.txt

Index: Documentation/web/server/robots.txt
diff --git a/Documentation/web/server/robots.txt  
b/Documentation/web/server/robots.txt
index  
8213d0e215d5b6684347dd98dbb1279ae743402e..d1879c94ce0ebc7ec22ac1829484779d9f3eca2b  
100644
--- a/Documentation/web/server/robots.txt
+++ b/Documentation/web/server/robots.txt
 <at>  <at>  -21,5 +21,7  <at>  <at>  Disallow: /doc/v2.12/
  Disallow: /doc/v2.13/
  Disallow: /doc/v2.14/
  Disallow: /doc/v2.15/
+Disallow: /doc/v2.16/
+Disallow: /doc/v2.17/

  Disallow: /web/
James | 19 Apr 11:51 2014
Picon

PATCHES: Countdown for April 21st - 06:00 GMT

Hello,

3239 Enhancement Janek Warchol waiting Patch: rewrite Self_alignment_interface May 2013
3186 Ugly Janek Warchol waiting Positioning of "8" under clef symbol in G_8 clef   Bounty Jan 26
3156 Enhancement Mike Solomon waiting Patch: Prevents vertical axis groups with empty skylines Feb 2013
3134 Enhancement Mike Solomon waiting Patch: Removes the translate_axis call from axis-group-interface outside-staff positioning. Aug 2013
2812 Documentation Keith Ohara waiting Renaming to distinguish keySignature from KeySignature Nov 11
2716 Enhancement David Kastrup waiting Patch: Implement music functions in Scheme rather than C++ Aug 2012
<!-- BODY,DIV,TABLE,THEAD,TBODY,TFOOT,TR,TH,TD,P { font-family:"Liberation Sans"; font-size:x-small } -->


James
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
James | 15 Apr 08:47 2014
Picon

PATCHES: Countdown for April 18th - 06:00 GMT

Hello,

3239 Enhancement Janek Warchol waiting Patch: rewrite Self_alignment_interface May 2013
3186 Ugly Janek Warchol waiting Positioning of "8" under clef symbol in G_8 clef   Bounty Jan 26
3156 Enhancement Mike Solomon waiting Patch: Prevents vertical axis groups with empty skylines Feb 2013
3134 Enhancement Mike Solomon waiting Patch: Removes the translate_axis call from axis-group-interface outside-staff positioning. Aug 2013
2812 Documentation Keith Ohara waiting Renaming to distinguish keySignature from KeySignature Nov 11
2716 Enhancement David Kastrup waiting Patch: Implement music functions in Scheme rather than C++ Aug 2012
<!-- BODY,DIV,TABLE,THEAD,TBODY,TFOOT,TR,TH,TD,P { font-family:"Liberation Sans"; font-size:x-small } -->


James
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
James | 15 Apr 00:34 2014
Picon

Re: Patch for issue 3895

On 14/04/14 19:24, Devon Schudy wrote:
author Devon Schudy <dschudy <at> gmail.com>
  Sun, 30 Mar 2014 05:15:57 +0000 (01:15 -0400)
committer James Lowe <pkx166h <at> gmail.com>
  Mon, 14 Apr 2014 22:32:02 +0000 (23:32 +0100)
commit731c856348456b8286e1e40a2f6aa4118c304107

James
Pierre Perol-Schneider | 13 Apr 21:09 2014
Picon

Re: LSR updates

Hi Phil,
Hi Dev Team,

See Seb's message below.
Cheers,
Pierre


2014-04-13 20:29 GMT+02:00 Sebastiano Vigna <vigna <at> di.unimi.it>:


Uffa. There was a constant in the Java code that I forgot about. It should be OK now.

Ciao,

                                        seba


_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Phil Holmes | 13 Apr 12:18 2014
Picon

LSR updates

(I'm sending this to David and Pierre as well as the list.  As I mentioned 
before, mail I initiate and send to the list seems to be silently ignored. 
Please copy my text in any reply.)

I've just run an LSR import and makelsr.  I'm confused about the outcome of 
the makelsr run.  It appears that convert-ly is not doing its job properly. 
For example, with
Documentation/snippets/adding-an-extra-staff.ly I see the following diffs:

-\version "2.17.30"
+\version "2.14.2"

- \once \omit Staff.TimeSignature
+ \once \override Staff.TimeSignature.stencil = ##f

So it appears to be ignoring updated syntax and setting the version back to 
2.14.  Or simply not updating the syntax at all.  Anyone any thoughts why 
this might be?

--
Phil Holmes 
PNEU | 12 Apr 19:23 2014
Picon

Special characters: make text-replacements list longer

Dear LilyPond Community,

I would like to suggest a little enhancement to make special characters
easier to insert.

I was getting tired of using these methods (c \mark \markup {\concat {"B"
\char ##xd6 "u" \char ##x159 "r" \char ##xe9 "e"} &ndash;_&OE;&hellip }) to
insert special characters in my lyrics, titles etc.

So I changed my text-replacements.ly file to this (see below 1), changing
all characters to their equivalent in I-dont-know-what other encoding. It
works surprisingly well! You just have to enter the characters in plain text
in LilyPad and out they come in the PDF.

I did have an interference with the default tagline -- the dash would not
get printed -- so I changed my default tagline accordingly (in file
titling-init.ly), see below 2.

If it is not too risky you might really consider switching the default
text-replacement.ly file to this. Indeed it is currently really difficult
for French / German / Spanish etc users to insert special characters in
LilyPond.

Thanks a lot, good luck,
PNEU

##### \LilyPond 2.18.2\usr\share\lilypond\current\ly\text-replacements.ly #####

\version "2.16.0"

#(define (add-text-replacements! alist)
   (set! text-font-defaults
	 (assoc-set! text-font-defaults 'replacement-alist
		     (cdaar
		      (internal-add-text-replacements (list text-font-defaults) alist)))))

#(define (include-special-characters)
   (add-text-replacements!
     '(;; Punctuation
       ("&hellip;" . "…")
       ("&ndash;" . "–")
       ("&mdash;" . "—")
       ("&iexcl;" . "¡")
       ("&iquest;" . "¿")
       ("&solidus;" . "∕") ; this is not a slash,
                           ; contrary to what is said in Unicode.

       ;; French, German and English quotes open/close
       ("&flq;" . "‹")
       ("&frq;" . "›")
       ("&flqq;" . "«")
       ("&frqq;" . "»")
       ("&glq;" . "‚")
       ("&grq;" . "‘")
       ("&glqq;" . "„")
       ("&grqq;" . "“")
       ("&elq;" . "‘")
       ("&erq;" . "’")
       ("&elqq;" . "“")
       ("&erqq;" . "”")

       ;; Word dividers
       ("&ensp;" . " ")
       ("&emsp;" . " ")
       ("&thinsp;" . " ")
       ("&nbsp;" . " ")
       ("&nnbsp;" . " ") ; narrow non-breaking space
       ("&zwj;" . "‍")
       ("&zwnj;" . "‌")
       ("&middot;" . "·") ; interpunct

       ;; General typography
       ("&bull;" . "•")
       ("&copyright;" . "©")
       ("&registered;" . "®")
       ("&trademark;" . "â„¢")
       ("&dagger;" . "†")
       ("&Dagger;" . "‡")
       ("&numero;" . "â„–")
       ("&ordf;" . "ª")
       ("&ordm;" . "º")
       ("&para;" . "¶")
       ("&sect;" . "§")
       ("&deg;" . "°")
       ("&numero;" . "â„–")
       ("&permil;" . "‰")
       ("&brvbar;" . "¦")

       ;; Diacritics
       ("&acute;" . "´")
       ("&acutedbl;" . "˝")
       ("&grave;" . "`")
       ("&breve;" . "˘")
       ("&caron;" . "ˇ")
       ("&cedilla;" . "¸")
       ("&circumflex;" . "^")
       ("&diaeresis;" . "¨")
       ("&macron;" . "¯")

       ;; Non-ASCII Letters (Excluding Accented Letters)
       ("&aa;" . "Ã¥")
       ("&AA;" . "Ã…")
       ("&ae;" . "æ")
       ("&AE;" . "Æ")
       ("&dh;" . "ð")
       ("&DH;" . "Ð")
       ("&dj;" . "Ä‘")
       ("&DJ;" . "Đ")
       ("&l;" . "Å‚")
       ("&L;" . "Ł")
       ("&ng;" . "Å‹")
       ("&NG;" . "ÅŠ")
       ("&o;" . "ø")
       ("&O;" . "Ø")
       ("&oe;" . "Å“")
       ("&OE;" . "Å’")
       ("&s;" . "Å¿")
       ("&ss;" . "ß")
       ("&th;" . "þ")
       ("&TH;" . "Þ")

       ;; Mathematical symbols
       ("&plus;" . "+")
       ("&minus;" . "−")
       ("&times;" . "×")
       ("&div;" . "÷")
       ("&sup1;" . "¹")
       ("&sup2;" . "²")
       ("&sup3;" . "³")
       ("&sqrt;" . "√")
       ("&increment;" . "∆")
       ("&infty;" . "∞")
       ("&sum;" . "∑")
       ("&pm;" . "±")
       ("&bulletop;" . "∙")
       ("&partial;" . "∂")
       ("&neg;" . "¬")

       ;; Currency symbols
       ("&currency;" . "¤")
       ("&dollar;" . "$")
       ("&euro;" . "€")
       ("&pounds;" . "£")
       ("&yen;" . "Â¥")
       ("&cent;" . "¢")

	 

	;; My symbols, added
	("¡" . "Ž")
	("¢" . "¢")
	("£" . "£")
	("¥" . "Â¥")
	("¦" . "Ĭ")
	("§" . "§")
	("¨" . "Ŭ")
	("©" . "©")
	("ª" . "Ǧ")
	("«" . "«")
	("¬" . "ÅŠ")
	("­" . "­")
	("®" . "®")
	("¯" . "Ç‘")
	("°" . "°")
	("±" . "ž")
	("²" . "²")
	("³" . "³")
	("´" . "´")
	("µ" . "µ")
	("¶" . "Ä­")
	("·" . "·")
	("¸" . "Å­")
	("¹" . "¹")
	("º" . "ǧ")
	("»" . "»")
	("¼" . "Å‹")
	("½" . "½")
	("¾" . "Ÿ")
	("¿" . "Ç’")
	("À" . "À")
	("Á" . "Ã")
	("Â" . "Â")
	("Ã" . "Ã")
	("Ä" . "Ä")
	("Å" . "Ã…")
	("Æ" . "Æ")
	("Ç" . "Ç")
	("È" . "È")
	("É" . "É")
	("Ê" . "Ê")
	("Ë" . "Ë")
	("Ì" . "ÃŒ")
	("Í" . "Ã")
	("Î" . "ÃŽ")
	("Ï" . "Ã")
	("Ð" . "Äž")
	("Ñ" . "Ñ")
	("Ò" . "Ã’")
	("Ó" . "Ó")
	("Ô" . "Ô")
	("Õ" . "Õ")
	("Ö" . "Ö")
	("×" . "Ã")
	("Ø" . "ÆŸ")
	("Ù" . "Ù")
	("Ú" . "Ú")
	("Û" . "Û")
	("Ü" . "Ãœ")
	("Ý" . "Ä°")
	("Þ" . "Åž")
	("ß" . "ß")
	("à" . "à")
	("á" . "á")
	("â" . "â")
	("ã" . "ã")
	("ä" . "ä")
	("å" . "Ã¥")
	("æ" . "É™")
	("ç" . "ç")
	("è" . "è")
	("é" . "é")
	("ê" . "ê")
	("ë" . "ë")
	("ì" . "ì")
	("í" . "í")
	("î" . "î")
	("ï" . "ï")
	("ð" . "ÄŸ")
	("ñ" . "ñ")
	("ò" . "ò")
	("ó" . "ó")
	("ô" . "ô")
	("õ" . "õ")
	("ö" . "ö")
	("÷" . "ý")
	("ø" . "ɵ")
	("ù" . "ù")
	("ú" . "ú")
	("û" . "û")
	("ü" . "ü")
	("ý" . "ı")
	("þ" . "ÅŸ")
	("ÿ" . "ÿ")
	("Œ" . "ÂŒ")
	("œ" . "Âœ")
	("Š" . "Š")
	("š" . "š")
	("Ÿ" . "Ÿ")
	("ƒ" . "ƒ")
	;("–" . "–") 
	;("—" . "—")
	("‘" . "‘")
	("’" . "Â’")
	("‚" . "‚")
	("“" . "“")
	("”" . "”")
	("„" . "„")
	("†" . "†")
	("‡" . "‡")
	("•" . "•")
	("…" . "Â…")
	("‰" . "‰")
	("€" . "€")
	("™" . "™"))))

###### in file \LilyPond
2.18.2\usr\share\lilypond\current\ly\titling-init.ly ######

tagline = \markup {
  \pad-to-box #'(0 . 0) #'(0 . 3)
  {  \with-url

    #"http://lilypond.org/"
    \line {

      %% 2014 = em dash.

      #(format #f "Music engraving by LilyPond ~a -- www.lilypond.org"
         (lilypond-version)
         )
    }
  }
}

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Gmane