hi-res kievan notation images

I meant to upload some images of kievan notation today, but our electricity went out for most of the day. Before that happened, I was discovering that our internet connection is not good enough to upload whole pages of Russian chant books in 1200 dpi. Would it be better to sent smaller snippets

Re: copyright symbol?

Before spending lots of time compiling your own version, you should really make sure that the file is saved in UTF-8 and nothing else. For example, you can use the command "file": >file myfile.ly myfile.ly: UTF-8 Unicode text By the way, the compilation error you got is probably due to the Guile

Re: copyright symbol?

On Friday 01 December 2006 15:26, Ian Stirling wrote: > I'll install all the missing 'no' and compile from source > to see if the problem still exists. 'make failed at building the documentation thus: lilypond-2.11.0/out/bin/../share/lilypond/2.11.0/ly/music-functions-init.ly:181:1: error: GUIL

Re: copyright symbol?

On Friday 01 December 2006 15:15, Ian Stirling wrote: > I get the following messages with 2.11.0 when I run lilypond > on the latest updated kubuntu - and the resulting pdf doesn't > contain the copyright symbol. [snip] I fetched the source tarball. './configure' shows a lot missing and ends w

Re: copyright symbol?

On Friday 01 December 2006 13:56, you wrote: > Last time I checked, UTF-8 was text. Seriously, if you think that ASCII is > adequate for text, then you are one of those poor souls never having met > anything but English literature. Heck, you cannot even encode the _name_ > of the composer of th

Re: urgent: layout of first page

> > Isn't this the same what I propose? > > I thought you were proposing to scrap B altogether. Well, I have proposed this ^ ^ | B| header | v A| | v which can be directly transformed into your proposal.

Re: copyright symbol?

Hi, On Fri, 1 Dec 2006, Ian Stirling wrote: > On Thursday 30 November 2006 02:38, you wrote: > > > and then save the file in UTF-8 encoding. > > Does this mean that lilypond output is no longer > controlled by an ascii file? > I thought the beauty of Lilypond was music output > is based on a

Re: convert-ly, musicxml2ly, etc. problems

Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Jan, > > do you know how Python 2.4/mingw found out where to locate its modules? The path is set through argv0 relocation, but I had to patch calculate_path in Modules/getpath.c, see below. I haven't checked if this is the new patch bomb, or what c

Re: copyright symbol?

On Thursday 30 November 2006 02:38, you wrote: > and then save the file in UTF-8 encoding. Does this mean that lilypond output is no longer controlled by an ascii file? I thought the beauty of Lilypond was music output is based on a text file input. Ian -- ___

NEWS.pdf

Hi all, Am I dreaming, or in NEWS.pdf, is the sample graphic for the skyline algorithm going vertically? I'm looking at the one linked from the NEWS.html page on the website: http://lilypond.org/doc/v2.11/Documentation/topdocs/NEWS.pdf --Phil Kirlin _

Re: skyline vertical spacing

Joe Neeman escreveu: > Sounds like a good idea. There's one thing I'm not comfortable with > (and I was bitten by this doing the separation item stuff), but I'm > not sure it could be a problem in this case. > > It is possible to ask for the X,Y extent of an axis group which is X >

Re: skyline vertical spacing

On 12/1/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Joe Neeman escreveu: > On 11/28/06, *Han-Wen Nienhuys* <[EMAIL PROTECTED] > > wrote: > > Joe Neeman escreveu: > > On 11/28/06, *Werner LEMBERG* <[EMAIL PROTECTED] >

Re: convert-ly, musicxml2ly, etc. problems

Bertalan Fodor escreveu: > Well, that doesn't work in 2.10.0-2, and (according to Rick) in 2.11.x > > Because with that you get the message: > > C:\Program Files\LilyPond\usr\bin>python -v convert-ly -h > # installing zipimport hook > import zipimport # builtin > # installed zipimport hook > 'imp

Re: skyline vertical spacing

Han-Wen Nienhuys escreveu: > Sounds like a good idea. There's one thing I'm not comfortable with > (and I was bitten by this doing the separation item stuff), but I'm > not sure it could be a problem in this case. > > It is possible to ask for the X,Y extent of an axis group which is X > but not Y

Re: skyline vertical spacing

Joe Neeman escreveu: > On 11/28/06, *Han-Wen Nienhuys* <[EMAIL PROTECTED] > > wrote: > > Joe Neeman escreveu: > > On 11/28/06, *Werner LEMBERG* <[EMAIL PROTECTED] PROTECTED]> > >> wrote: >

Re: skyline vertical spacing

On 11/28/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Joe Neeman escreveu: > On 11/28/06, *Werner LEMBERG* <[EMAIL PROTECTED] > wrote: > > > Joe, > > > here's a quite important problem regarding skyline positioning and > outside-staff-priority. Hopefull

Re: There no ligatures in Kievan notation

Monk Panteleimon escreveu: > I can send hardcopies of printed books to whoever will be doing the glyph > designing, or I can scan at the highest resolution available to me and put a > few images up for download. Which is better? I'd think a hardcopy would be > since, it leaves less possibility

Re: There no ligatures in Kievan notation

> I second Han-Wen: Metafont should be used for that. However, it > doesn't prevent that you use a tracing program to get some coordinates > which can be then imported to Metafont for a first draft. On the > other hand, it is probably faster to design a shape from scratch, > based on high-resolut

Re: There no ligatures in Kievan notation

> I am not sure what is the latest state of incorporating new glyphs > into lily; so far, we used to have to design glyphs by manually > writing Metafont code, which may result in high-quality glyphs, but > is also an extremely time-consuming process. But nowadays, lily > supports a couple of font

Re: There no ligatures in Kievan notation (was Re: Kievan "hatchet" notes for lilypond?)

Juergen Reuter escreveu: > I am not sure what is the latest state of incorporating new glyphs into > lily; so far, we used to have to design glyphs by manually writing > Metafont code, which may result in high-quality glyphs, but is also an > extremely time-consuming process. But nowadays, lily s

Re: There no ligatures in Kievan notation (was Re: Kievan "hatchet" notes for lilypond?)

Juergen Reuter escreveu: > I am not sure what is the latest state of incorporating new glyphs into > lily; so far, we used to have to design glyphs by manually writing > Metafont code, which may result in high-quality glyphs, but is also an > extremely time-consuming process. But nowadays, lily s

Re: There no ligatures in Kievan notation (was Re: Kievan "hatchet" notes for lilypond?)

On Thu, 30 Nov 2006, Monk Panteleimon wrote: On Thursday 30 November 2006 06:01, you wrote: Hello, Panteleimon! Hello, thank you for your response I fear the task of fully implementing kievan chant notation is more than just a question of adding thirteen glyphs. recognize at least pes ligat

Re: skyline vertical spacing

On 11/26/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: - on a random sample (mozart horn concerto), the skyline stuff looks working. However, should we increase the default padding/skyline-padding to improve appearance (see mozart concerto, page 1, bar 68, forte and beam being close)?

Re: urgent: layout of first page

Werner LEMBERG escreveu: >> The effective distance would be the lowest of both. > > Isn't this the same what I propose? I thought you were proposing to scrap B altogether. > > > > ^ header^ ^ no header >

Re: request for combined accent

You can easily define markup commands for all these combinations yourself, for example \version "2.10.0" dnormlegato = \markup{\override #'(baseline-skip . 0.9) \center-align {\musicglyph #"scripts.tenuto" \musicglyph #"scripts.sforzato" } } unormlegato = \markup{\override #'(baseline-skip . 0.9

Re: urgent: layout of first page

> >>> Regarding head-separation I wonder whether the current approach > >>> of lilypond to handle headers and footers is the right one. > >>> Wouldn't it be better to define a zone of a given height within > >>> the header (or footer) is rendered, instead of defining a > >>> distance from the heade