Reviewers: ,
Message:
Please review.
Description:
Add blurb about Kievan notation to changes
Adds a blurb and minimal example to changes.tely indicating support of
Kievan notation.
Please review this at http://codereview.appspot.com/6326056/
Affected files:
M Documentation/changes.tely
In
On Sun, Jul 1, 2012 at 6:29 PM, Graham Percival
wrote:
> I'm not certain where we stand. Over the weekend, some patches
> were pushed (by accident?) to master. One (or more?) of those
> commits broke compiling, and were reverted. This fix was (or will
I was just able to make doc from scratch w
This is definitely not an elegant approach to the problem at all (and it
does not solve the issue of the warning being given out at stem.cc line
128), but it's the best I can figure out after hacking at the code for a
while.
Perhaps reviewers more familiar with LilyPond internals can provide some
On 2012/08/07 18:19:14, dak wrote:
http://codereview.appspot.com/6305080/diff/4001/lily/beam.cc#newcode636
lily/beam.cc:636: extract_grob_set (stems[0], "note-heads", heads);
This looks like the wrong place to do this calculation. You overwrite
what has
been put into quantized-positions here.
On 2012/08/13 19:17:28, lemzwerg wrote:
It would be nice if a Russian speaking person could fix the Cyrillic
index
entries. However, since we don't have Cyrillic characters in the
index, this is
not an urgent issue (and maybe we never need this).
Could you explain what you mean by "fix the
Please review.
http://codereview.appspot.com/6305080/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: ,
Message:
Please review.
Description:
Fix vertical position of Kievan dots
Dots in Kievan notation should be placed at the same Y_AXIS position as
the note, even if they occur on a line.
Issue 2857.
Please review this at http://codereview.appspot.com/6570047/
Affected files:
M
http://codereview.appspot.com/6584045/diff/2001/ly/engraver-init.ly
File ly/engraver-init.ly (right):
http://codereview.appspot.com/6584045/diff/2001/ly/engraver-init.ly#newcode1150
ly/engraver-init.ly:1150: \override Beam #'positions =
#beam::get-kievan-positions
The only issue with putting thi
On 2012/10/01 23:34:39, MikeSol wrote:
I think a user should be able to use Kievan notation and normal
stems/flags/beams if she so chooses. I'll define something like
[snip]
and then use it in the documentation.
I still see some issues with this. As written now in stem.cc, when the
style
On 2012/10/02 07:28:10, J_lowe wrote:
If you are talking about the Documentation in the Notation Reference,
the
Ancient Notation doesn't follow (mostly) the standard Policies at all
- indeed
there is a while tracker to tidy this section up, I started but I
don't have any
knowlegde of Ancien
On 2012/10/02 14:56:28, mike7 wrote:
On 2 oct. 2012, at 16:42, mailto:aleksandr.andr...@gmail.com wrote:
> What I mean is that if something like
>
> {
> \override NoteHead #'style = #'kievan
> c'8
> }
>
> produces a quarter note in the output, the user is likely to be
> thoroughly confused.
Reviewers: ,
Message:
Please review.
Description:
Fix extra spacing in Kievan notation
In Kievan notation, notes should be spaced as tightly as possible within
melismas.
This patch fixes extra spacing caused by long syllables.
Issue 2631.
Please review this at http://codereview.appspot.com/6
On 2012/10/15 20:00:28, benko.pal wrote:
I don't like that: the patch manipulates a staff based on note head.
it also
increments a hack.
have you tried something like
\override SpacingSpanner #'shortest-duration-space = #0
\override SpacingSpanner #'spacing-increment = #0
?
The presence of
On 2012/10/16 08:14:17, benko.pal wrote:
> The presence of a long syllable in the lyrics makes the
left_col->extent
> larger than spring.min_distance(). Manipulating the SpacingSpanner
> properties has no effect -- the extraneous space is still there.
long syllables are a general problem, se
http://codereview.appspot.com/6584045/diff/13014/input/regression/kievan-notation.ly
File input/regression/kievan-notation.ly (right):
http://codereview.appspot.com/6584045/diff/13014/input/regression/kievan-notation.ly#newcode12
input/regression/kievan-notation.ly:12: c4 c4 c8 [ d8 ] c4 c2 b,\l
On 2012/11/03 18:21:09, mike7 wrote:
On 3 nov. 2012, at 12:26, mailto:d...@gnu.org wrote:
>
http://codereview.appspot.com/6584045/diff/1/scm/output-lib.scm#newcode85
> scm/output-lib.scm:85: (left-height (if (= direction DOWN)
> Is direction sure to be non-null?
>
Thanks again for the rev
http://codereview.appspot.com/6584045/diff/13014/input/regression/kievan-notation.ly
File input/regression/kievan-notation.ly (right):
http://codereview.appspot.com/6584045/diff/13014/input/regression/kievan-notation.ly#newcode13
input/regression/kievan-notation.ly:13: \bar "kievan"
Sorry, I mis
http://codereview.appspot.com/6584045/diff/13015/input/regression/kievan-notation.ly
File input/regression/kievan-notation.ly (right):
http://codereview.appspot.com/6584045/diff/13015/input/regression/kievan-notation.ly#newcode13
input/regression/kievan-notation.ly:13: \bar "kievan"
This needs t
On 2012/11/07 07:52:33, mike7 wrote:
On 7 nov. 2012, at 09:50, mailto:d...@gnu.org wrote:
> On 2012/11/07 05:32:40, mike7 wrote:
>> On 7 nov. 2012, at 00:50, mailto:d...@gnu.org wrote:
>
>> >
>> >
>
>
http://codereview.appspot.com/6584045/diff/13014/input/regression/note-head-style.ly#newcod
Hello list,
I am getting the following message when I try to run git cl upload
origin/master:
Traceback (most recent call last):
File "/usr/bin/git-cl", line 888, in
sys.exit(main(sys.argv))
File "/usr/bin/git-cl", line 882, in main
return func(argv[2:])
File "/usr/bin/git-cl", lin
Please review.
https://codereview.appspot.com/6865049/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I went into my git-cl directory and did a git pull -r
Works fine for me now.
Aleksandr
On Sun, Dec 2, 2012 at 6:08 PM, Thomas Morley
wrote:
> 2012/12/2 Phil Holmes :
>> - Original Message - From: "Graham Percival"
>>
>> To: "Phil Holmes"
>> Cc: ; "David Kastrup"
>> Sent: Sunday, Dece
On Fri, Dec 21, 2012 at 7:01 AM, Kieren MacMillan
wrote:
> The big ones for me are:
>
> 1. The completion of Janek's GSoC work on Lyrics.
+1!!
Aleksandr
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lily
Reviewers: ,
Message:
Please review.
Description:
Add Kievan ligature engraver
Creates support for melismas ("ligatures") in Kievan notation via the
use of a ligature engraver.
Please review this at https://codereview.appspot.com/7301097/
Affected files:
M lily/coherent-ligature-engraver.c
Reviewers: ,
Message:
Please review.
Description:
Document Kievan ligature engraver
Adds subsection about Kievan ligatures to ancient notation section of
notation manual.
Please review this at https://codereview.appspot.com/7382060/
Affected files:
M Documentation/notation/ancient.itely
I
On 2013/02/26 16:07:33, Trevor Daniels wrote:
One suggested change; otherwise LGTM.
Trevor
https://codereview.appspot.com/7382060/diff/1/Documentation/notation/ancient.itely
File Documentation/notation/ancient.itely (right):
https://codereview.appspot.com/7382060/diff/1/Documentation/no
On 2013/02/27 09:24:07, Trevor Daniels wrote:
On 2013/02/27 03:26:11, aleksandr.andreev wrote:
> Looking at the sections on Mensural and Gregorian notations, it
looks like the
> \transpose c c' syntax is used quite often there. On the other hand,
the
> \relative syntax is used in the "scenari
Reviewers: ,
Message:
Please review
Description:
Change \transpose to \relative in ancient.itely
Change \transpose c c' syntax to \relative c' syntax in examples in the
ancient notation chapter of notation manual.
Please review this at https://codereview.appspot.com/7538043/
Affected files:
https://codereview.appspot.com/7538043/diff/5001/Documentation/notation/ancient.itely
File Documentation/notation/ancient.itely (right):
https://codereview.appspot.com/7538043/diff/5001/Documentation/notation/ancient.itely#newcode952
Documentation/notation/ancient.itely:952: @c @end example
On 2
On 2013/03/16 09:09:29, dak wrote:
So many pitches are wrong in this patch that I think we should revert
it and
have it redone carefully.
I do not have push access, so I cannot do much at this point. Can you
revert it then?
Possibly using some automatism (like Frescobaldi's absolute/relati
Hello list members,
My current teaching schedule unfortunately means that I am not going
to have time to work on LilyPond development in the near future.
However, I am still interested in seeing outstanding issues with
Kievan notation resolved, as I plan to use LilyPond in some upcoming
projects.
I am offering a bounty of $100 for issue 1388, in particularly for an
interface that allows one to access stylistic sets in OpenType fonts.
http://code.google.com/p/lilypond/issues/detail?id=1388
Aleks
___
lilypond-devel mailing list
lilypond-devel@gnu
As per comments by Neil, I removed the reg test file. Also made the
necessary changes to Documentation/included/font-table.ly
Also merged with Parmesan patch by Bertrand and resolved conflict.
http://codereview.appspot.com/4951062/
___
lilypond-devel
Fixed alignment issue based on comments by lemzwerg.
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Unfortunately, I cannot get my documentation to build. As was
suggested earlier, I nuked my build folder and redid everything from
the beginning (configure.sh, make all, touch, make doc). However, make
doc errors out with the following message:
Calculating line breaks... Segmentation fault
command
>> What's in the above file? It'll probably contain 5-10 other
filename
Yes. All the different snippets seem to have something to do with percussion.
Aleks
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/l
Updated Documentation/notation/notation-appendices.itely to show new
glyphs, reflecting comments by Neil.
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-deve
Yet another rm -fdr build/ and re-run of make, etc., eliminated my
original problem with snippets.
Now, my make doc command crashes with the same error message that
Janek is getting.
Looks like there's a missing file web.texi.
Aleks
___
lilypond-devel
Hi Phil,
> Janek, Aleksandr - could you confirm what system you're getting make doc
> failing on?
Yes, I'm running Ubuntu Natty (not Lilydev).
More specifically, Linux sasha-desktop 2.6.38-11-generic #48-Ubuntu
x86_64 GNU/Linux
Aleks
___
lilypond-de
FWIW, I updated my kernel by installing the latest Ubuntu updates. I
also did a git rebase. I still get the same problem.
A
2011/9/22 Janek Warchoł :
> 2011/9/22 Peekay Ex :
>> Janek
>>
>> 2011/9/22 Janek Warchoł :
>>>
>>> I use Lilydev - probably not the newest version, how can i check it?
>>
>>
make doc problem solved on my system. I can confirm that make and make
doc run successfully with this patch.
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-d
> What did you do to get make doc going?
I nuked my entire lilypond-git directory, reinstalled the source and
ran make and make doc.
Then, I ran the Kievan patch and recompiled.
A
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gn
> This is a great work, but it doesn't fit correctly into LilyPond:
OK, I will merge with Parmesan and work on the Scheme stuff.
> I also agree with Werner, there's also a lot of cleanup to do inside
> your MetaFont stuff.
I'm new to MetaFont, so right now I'm using it like a GUI-less
outline f
Per comments by Bertrand, I have moved the Kievan glyphs to Parmesan. I
have also changed the names of the glyphs as he suggested.
I've begun working on improving the MetaFont code. Please take a look at
the code for the final note, the recitative, and the whole note and let
me know if I'm on the
I've uploaded changes to output-lib.scm. The problem I have is that
output-lib does not allow access to noteheads of log-duration greater
than 2.
I've temporarily changed a few lines of the file. However, I'm not sure
this is the best way of doing this. Please let me know what the right
approach
I've taken care of the issues Bertrand points out in #46. There are
still some issues outstanding. The code in output-lib.scm is probably
not the best way of doing this. Also, the Kievan bar line does not
appear correctly.
http://codereview.appspot.com/4951062/
__
I'm trying to implement beams, but I get this message:
"must have Item for spanner bound of Beam"
What does this refer to?
A
On Fri, Oct 7, 2011 at 6:29 AM, wrote:
> Here's the second part of my review. I saw that kievan notation has
> beams, contrary to what I thought. If you're intrepid,
Fixed the issues addressed by Bertrand.
What still remains:
1. Implementing beams
2. Changing the spacing so that notes in a phrasing slur are closer
together.
3. Remove extra space after final note.
Comments much appreciated.
http://codereview.appspot.com/4951062/
__
That is done, but before updating I wanted to resolve a few other
issues. However, I cannot figure out how to control the amount of
spacing between notes (I need the notes in a phrasing slur to be closer
together). Also, I can't get the beams to show properly.
http://codereview.appspot.com/495106
Hello folks,
I've downloaded the latest Lilypond source from git onto a different
computer than I was using before. This computer is running Ubuntu
11.04.
I was trying to test out some things for the Kievan notation project,
and to do that I wanted to build everything (including the
documentation
Here's the contents of the relevant log file:
GNU LilyPond 2.15.24
Killed
ing ./snippet-map--1615808177
Processing 94/lily-32d78681
Processing 8d/lily-d2e2b327
Processing 29/lily-e0ac5d9b
Processing 89/lily-1efebec4
Processing 56/lily-44b4b5eb
Processing de/lily-7583ff9a
Processing a1/lily-2532f52
Aha. Some Googling reveals that:
Exit code 137: The job was killed because it exceeded the time limit.
Any ideas how to up the time limit?
On Thu, Dec 29, 2011 at 10:54 AM, Phil Holmes wrote:
> - Original Message - From: "Aleksandr Andreev"
>
> To: "Phil Holme
Phil,
I ran it again this morning on the latest source from git pull, and I
get the same message. There is no notice in the relevant log file of
any failed files, so it doesn't appear to be a syntax error.
In fact, it looks like the relevant command runs, but for some reason
make test still crash
Merged Kievan patch with existing source code and fixed an issue in
output-lib.scm
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
something like stems, which should be hidden, stick from notes.
The problem here is that we're not using KievanVoice in
note-head-style.ly.
I've posted a potential solution to get rid of the "stems", but it's not
very elegant because it breaks the pattern.
Perhaps someone else has a better ide
On 2012/01/11 21:37:36, Neil Puttock wrote:
Add a check for kievan style in Stem::is_normal_stem ().
Unfortunately, that doesn't seem to do anything. Unless I'm not
accessing the property correctly ... see the latest patch.
Aleks
http://codereview.appspot.com/4951062/
__
On 2012/01/12 16:24:13, Neil Puttock wrote:
You're trying to access style from the Stem instead of the NoteHead.
Got it. Thanks, Neil.
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gn
Regarding comments by Jan:
I guess it should be 2.5 staff_space or something
I changed the depth and height parameters as you suggested. However, I
do not see any difference, in the reg tests or in my test files. Are we
sure that the entire glyph has to fit within the char_box, including the
"
When I go to make the regression tests, I get the following error
message:
texi2html --I=/home/sasha/lilypond-git/input/regression/lilypond-book
--I=./out-test -I /home/sasha/lilypond-git/Documentation
--I=/home/sasha/lilypond-git/build/./out-test/xref-maps
--init-file=/home/sasha/lilypond-git/Do
There is a difference, compare the position of "kievan" markups in
pdfs
Ah, OK, I see it now.
You've forgotten about one char_box, see below.
I fixed this one as well as the char_box for the clef.
I've run make and regtests from scratch on a freshly-updated source.
I'm getting the error
Reviewers: ,
Message:
Addressing the issue here:
http://code.google.com/p/lilypond/issues/detail?id=2318
Description:
Remove Time-signature from Kievan Staff
Time_signature_engraver is removed from Kievan Staff as per Google Code
issue 2318
http://code.google.com/p/lilypond/issues/detail?id=231
On 2012/02/16 11:32:18, janek wrote:
Looks Good To Me
I think this can be pushed.
http://codereview.appspot.com/5672063/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
> Oops, i see now that the tracker issue
> (http://code.google.com/p/lilypond/issues/detail?id=2318) doesn't have a
> "Patch" label, and therefore isn't included in our regular patch
> maintenance (i suppose it's because you didn't use our dedicated git-cl,
> see section "reviews" here
> http://lil
Reviewers: ,
Message:
Changing the char_box of the Kievan bar line to eliminate the problem
with the bar line being cut off.
However, this brings back the problem of staff lines appearing under the
bar line.
Description:
Fixing height of Kievan bar line
Kievan bar line is cut off when running
Hello list,
I'm back to trying to work on this issue after a bit of a hiatus.
The problem is how to get the staff lines to stop printing before the
Kievan bar line appears:
http://code.google.com/p/lilypond/issues/detail?id=2344
I've been hacking around the code a bit and here's my question. Is
> Wouldn't it be easier to draw a white box underneath the kievan glyph?
Can that be done with the same Stencil object?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
> Have a look at lily/grob.cc where the whiteout handling is defined.
Thanks. That seems to be a good approach. I've uploaded
a new patch. The results are here:
http://code.google.com/p/lilypond/issues/detail?id=2344#c12
There still appears to be a gray line at the bottom. Is that just a
feature
On Thu, Apr 5, 2012 at 2:51 PM, Marc Hohl wrote:
> I don't know whether the
> kievan bar line makes sense with span bars
It doesn't make sense with span bars.
> but I managed to get this better IMHO
I've attempted to modify your code to use stencil-whiteout to remove
the staff lines behind the
> Thanks. That seems to be a good approach. I've uploaded
> a new patch. The results are here:
> http://code.google.com/p/lilypond/issues/detail?id=2344#c12
>
Looks like the trick with stencil-whiteout does not work in all cases.
Here are two examples.
1.
\new KievanStaff {
\new KievanVoice
Resolved issue with the gray line appearing. I also added layer support,
thanks to a comment by Trevor Daniels. Looks like the Kievan bar line is
properly supported now.
http://codereview.appspot.com/5727051/
___
lilypond-devel mailing list
lilypond-de
Hello folks,
I've been experimenting with what is supported so far for Kievan
notation, and I've run in to some problems generating MIDI output. I
get the following messages at compile time if I add a \midi block:
warning: cannot find or create new `KievanStaff'
warning: cannot find or create new
> He plans to tackle 2451, 2452, and 2453 first via a parsing of pango strings
> to find word prefixes and suffixes and do alignment from where these lie.
Quick question: will languages that do not use Latin characters be
considered? For example, 2452 is also a problem when working with
Slavic lan
Upon further investigation, I believe this is related to this issue:
http://code.google.com/p/lilypond/issues/detail?id=2004
Aleksandr
On Wed, May 2, 2012 at 1:39 PM, Aleksandr Andreev
wrote:
> Hello folks,
>
> I've been experimenting with what is supported so far for Kievan
&
Reviewers: ,
Message:
Here is a patch that attempts to fix issues with MIDI playback of Kievan
notation.
Description:
Fix MIDI output for Kievan
Adding KievanStaff and KievanVoice for MIDI output of Kievan notation.
Please review this at http://codereview.appspot.com/6193043/
Affected files:
For whatever reason, \alias Staff and \alias Voice do not bring in the
performers. If I comment out the line \consists "Note_performer", I get
no notes in the MIDI file, only the appropriate number of rests.
I think this is also why Vaticana does not appear to work properly with
MIDI. Try this ex
On 2012/05/04 15:34:17, dak wrote:
Aliases are only relevant for properties, I think. The initial values
get
inherited, and any use of context property setting commands in the
music or
context mods will accept changes for Voice into this context.
But translators are independent.
Sorry,
On 2012/05/04 19:33:06, benko.pal wrote:
would you fix Vaticana and Mensural too?
I've uploaded a patch that gets at Vaticana and Mensural as well. It
seems that "Beam_performer" would not be necessary for the two, but I
don't know about "Tie_performer" and "Slur_performer". It would probably
On 2012/05/05 16:58:22, benko.pal wrote:
thank you very much! please add Beam_performer too to ensure
consistency with
Voice (may be needed when doing ancient and modern edition from a
common
source).
Added Beam_performer for Vaticana and Mensural based on this comment.
http://codereview.
Hello list,
After a hiatus related to the end of the semester here, I figured I'd
take a stab at solving this issue:
http://code.google.com/p/lilypond/issues/detail?id=2492
The problem is that a different note head needs to appear for the
Kievan eighth note if the note is beamed. (In Kievan notat
Reviewers: ,
Message:
A first attempt at fixing issue 2492.
This fixes the note heads for beamed kievan notes, also getting rid of
the warning messages.
Description:
Fix for beaming in Kievan notation
Implementing correct beaming functionality in Kievan notation
Fix for Issue 2492
Please rev
On 2012/06/11 00:49:42, Keith wrote:
looks good to me.
The question I have now is how to affect the position of the beam. It
needs to attach toward the bottom of the "stem" and not at center of the
staff.
http://codereview.appspot.com/6305080/
___
l
Reviewers: ,
Message:
Please review.
Description:
Documentation of Kievan notation
Adds a subsection to the Ancient notation section of the Notation
reference documenting support of Kievan square notation.
Issue 2317.
Please review this at http://codereview.appspot.com/6303095/
Affected file
Updated patch based on comments by Janek and Trevor.
http://codereview.appspot.com/6303095/diff/1/Documentation/music-glossary.tely
File Documentation/music-glossary.tely (right):
http://codereview.appspot.com/6303095/diff/1/Documentation/music-glossary.tely#newcode4539
Documentation/music-glos
http://codereview.appspot.com/6303095/diff/4/Documentation/notation/ancient.itely
File Documentation/notation/ancient.itely (right):
http://codereview.appspot.com/6303095/diff/4/Documentation/notation/ancient.itely#newcode2530
Documentation/notation/ancient.itely:2530:
@lilypond[quote,fragment,r
Per comments by Graham and Trevor, I have removed 'fragment' throughout
ancient.itely where 'relative' is also used.
http://codereview.appspot.com/6303095/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/li
On 2012/06/23 05:37:05, janek wrote:
pushed as a10311ff02578de9f979dc6ad83ba9535f8e4e4c.
Aleksandr, please close this Rietveld issue.
thanks!
Janek,
I was going to have the removal of 'fragment' reviewed in this issue,
per Trevor's recommendation. Or shall I open a separate issue for that?
Reviewers: ,
Message:
Please review.
Description:
Removing 'fragment' from ancient.itely
Issue 2619.
Please review this at http://codereview.appspot.com/6335049/
Affected files:
M Documentation/notation/ancient.itely
Index: Documentation/notation/ancient.itely
diff --git a/Documentat
>> Replacing the feta font is doable, but not trivial.
Is there anywhere I can read about how the Feta font is set up? The
font I have is part of our proposal to encode the Kievan glyphs in
Unicode, so it would need to be converted to the format that Feta
uses. Is there a detailed description of t
James wrote:
> It's crude (but effective), you either sym link the font dirs to point to the
> Gonville stuff (which is supplied via a zip/tgz file that you extract in
> situ) or as in the case of windows and mac you rename the old font dir and
> move the goneville one in its place.
>
This sou
s the amount of space
between lines?
Would it be appropriate to define a basis unit u in terms of
stafflinethickness and then specify the points in terms of u?
Where is the origin?
Thanks for the assistance,
Aleks
----
Aleksandr Andreev
Ponomar Project
_
Hi Jan,
Thanks for your comments.
> In case of noteheads, i suppose that everything would be best defined in
> staff_space. For stems (as i understand there are special characters for
> stems) stafflinethickness will be more appropriate.
Right now, I've got the notehead and stem being drawn a
ect a socket (Connection timed out)
What should I do?
Aleks
-
Aleksandr Andreev :: Founder / Sole Proprietor
Ponomar Technologies, Inc.
"Putting Modern Technology to Work for the Ancient Church"
http://www.ponomar.net/ * sa
step in supporting kievan square notation.
Add generic metafont file, driver files and
file containing code (one glyph currently).
Modified scripts used in font generation
to include kievan glyphs.
Signed-off-by: Aleksandr Andreev
Please review this at http://codereview.appspot.com/4951062
Hi Janek,
>
> Please report is these worked for you. If so, i will update
Just a thought: if you're editing the documentation, it would be
useful to indicate that git-cl pulls up an interface of vim and that
to get out of it, you use the standard vim commands. It's not obvious
when you're doing
Cleaned up code style based on comments from janek.
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi folks,
So now that we've got the Metafont code for the Kievan glyphs, what
shall I do next?
Basically, I would like to have an interface for Kievan Notation that
achieves the following:
1. Automatically uses the Kievan tsefaut clef.
2. Suppresses Time Signature and Key Signature.
3. Uses the K
> I think it should be done similarly to ancient music support: add a
> new kind of context, for example KievanVoice.
> See how mensural notation works now - an example:
OK, so IIUC, I have to add code to engraver-init.ly, and I can use the
MensuralVoice context as an example. That seems to be fa
Changed code style and glyph names based on the comments of Carl and
lemzwerg.
Carl, is it OK that the group name is kievan, so now we have glyphs like
kievan.s1kievan? Is this how it should be?
Re: "you can see that all coordinates rely on meta-parameters which
control the appearance"
I'm new
On 2011/09/10 12:47:18, J_lowe wrote:
I created
https://code.google.com/p/lilypond/issues/detail?id=1873
and called it
'Added glyphs for Kievan Notation'
so when this issue is changed can we use the same title?
I changed the name of the issue.
http://codereview.appspot.com/4951062/
On 2011/09/10 10:20:45, lemzwerg wrote:
Simply have a look how other note heads are implemented, and watch how
the shape
changes for different design sizes.
OK. What is noteheight# equal to and how is that determined?
http://codereview.appspot.com/4951062/
__
1 - 100 of 103 matches
Mail list logo
