Re: PATCH: Arrowed accidentals for microtone notation
On Tue, Dec 16, 2008 at 5:43 PM, Maximilian Albert < maximilian.alb...@googlemail.com> wrote: > 2008/12/14 Werner LEMBERG : > > > >> Can we please make sure to include at least one example of input > >> syntax in the newsfile? > > > > Well, it's Maximilian's turn... > > Yup, sorry. During the last couple of days I didn't have access to the > computer I presently work on (and won't have for another few days), > whence the delay in my response. Werner, thanks a lot for applying and > cleaning up the patches! I should have taken care of using the right > the coding style in the first place. > > As for the input syntax, that's a good point anyway. So far I only > used the arrowed accidentals by tweaking the maqam example and > defining separate names for all combinations of notes with all kinds > of arrowed accidentals (see the attached file micro1.ly). The drawback > is that the microtonal notes are associated with a certain pitch and > that one has to add a huge list of note name definitions at the > beginning of the file. One could also redefine the +/- 1/4 and +/- 3/4 > alterations to use the arrowed accidentals, as in the attached file > micro2.ly. The drawback ist that one cannot use the "regular" > quartertone accidentals any more since they are overridden by the new > definition (and microtones are still attached to a specific pitch). > > Do you think we should provide "standard" names for all the notes with > microtonal alterations? These would have to be localized, right? > (which I don't know how to do properly since I'm not familiar with the > naming conventions in other languages.) Or should we require the user > to make his own definitions each time (s)he wants to use these > accidentals? Which of these methods should be included in the news > file as an example for the recommended syntax? Hey Max, I can't speak to any other language besides English, but for English I might suggest the following (pasted out of one of my earlier mail): %%% ARROWED-ACCIDENTAL SUGGESTION FOR ENGLISH %%% OK, ideally I'd like something like this added to english.ly: cs'16 % normal C-sharp csu'16 % C-sharp with up-arrow csd'16 % C-sharp with down-arrow bf'16 % normal B-flat bfu'16 % B-flat with up-arrow bfd'16 % B-flat with down-arrow and also ... cqs'16 % normal (ie, exact) C-quartersharp cqsu'16 % C-quartersharp with up-arrow cqsd'16 % C-quatersharp with down-arrow etc. That's how I would, ideally, like to access the arrowed accidentals. Would be very slick, indeed. Just a -d (for 'down') or -u (for 'up') appended to the complete set of all existing accidental input names. %%% END %%% Of course, I'm also OK with defining my own commands for getting to the arrowed accidentals, as you and Werner are discussing, so long as there's an example of how to set up the definition. Very cool, btw! Trevor. -- Trevor Bača trevorb...@gmail.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Building LilyPond with GUB on a 64bit machine with 32bit OS
Am Dienstag, 16. Dezember 2008 schrieb Jan Nieuwenhuizen:
> > Should the LD_LIBRARY_PATH really be set during the execution of
> > lilypond's configure script???
>
> Good question, but is this what breaks your configure run?
>
> Every binary in tools should either have a wrapper, or
> be using rpath. It is being set in gub/target.py:
>
> 'LD_LIBRARY_PATH': '%(tools_prefix)s/lib'
> + misc.append_path (os.environ.get ('LD_LIBRARY_PATH', '')),
>
> it would be nice to have documented why we [think we] need this.
Actually, this IS what is breaking the configure check. By setting
LD_LIBRARY_PATH to the tools dir, you are telling the linker to use the
libraries from there (which are linked to glib 2.3). This fails in the guile
check, since some libraries are used from the system and some from the tools
dir.
If I uncomment all three
LD_LIBRARY_PATH': '%(tools_prefix)s/lib'
+ misc.append_path (os.environ.get ('LD_LIBRARY_PATH', '')),
settings in the gub/*.py files, then the configure check works fine and
lilypond
builds also fine.
It then only fails on the TODO file:
file from VC not distributed: lilypond-2.11.66/lily/TODO
rm -rf /tmp/tmpMdXowy
Traceback (most recent call last):
File "test-lily/dist-check.py", line 136, in
main ()
File "test-lily/dist-check.py", line 131, in main
check_files (tarball, repo)
File "test-lily/dist-check.py", line 116, in check_files
raise Exception ('dist error found')
Exception: dist error found
make[3]: *** [unlocked-dist-check] Fehler 1
make[3]: Verlasse Verzeichnis '/home/reinhold/lilypond/gub'
make[2]: *** [cached-dist-check] Fehler 2
make[2]: Verlasse Verzeichnis '/home/reinhold/lilypond/gub'
make[1]: *** [dist-check] Fehler 2
make[1]: Verlasse Verzeichnis '/home/reinhold/lilypond/gub'
Cheers,
Reinhold
--
--
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
* K Desktop Environment, http://www.kde.org, KOrganizer maintainer
* Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond binary
Hi John, could you create new po files for the binary and upload them to the Translation Project? Thanks Till -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Upgrade Howto
I have prepared a draft of an upgrade howto, Ubuntu only yet, other distribution's users could write down their own methods. http://lilypondwiki.tuxfamily.org/index.php?title=Upgrade_howto -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: PATCH: Arrowed accidentals for microtone notation
> Or should we require the user to make his own definitions each time > (s)he wants to use these accidentals? Which of these methods should > be included in the news file as an example for the recommended > syntax? I'm in favour of this solution, at least temporarily. Given that 2.12 is coming soon, arrowed accidentals should be documented somehow, together how a user can get them. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: why is Dutch the default language for note-entry?
> I installed unifont and that fixed it for GEdit, but in emacs it > even removed sharp and flat to display little boxes. > > Then I installed emacs-snapshot (with xft backend), sharp and flat > are back, but none from the music block starting at 0x1d12a shows. Hmm. I don't know either. Maybe a question for emacs-devel? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: why is Dutch the default language for note-entry?
2008/12/17 Bertalan Fodor : > Once a French conductor sang the melody "a a gis a g fis g" with the words > "la la sol la sol fa sol". It was very funny. Then you could die of laughing if you come to any of the orchestras, music schools or conservatoires in Spain... -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: why is Dutch the default language for note-entry?
Op dinsdag 16-12-2008 om 22:27 uur [tijdzone +0100], schreef Werner
LEMBERG:
> > although (with read-quoted-char-radix=16) C-Q 1d12a RET does not
> > give me a double sharp?
>
> What do you mean? A wrong code point or a missing glyph?
Actually I have no idea how emacs juggles fonts.
I installed unifont and that fixed it for GEdit, but in emacs it even
removed sharp and flat to display little boxes.
Then I installed emacs-snapshot (with xft backend), sharp
and flat are back, but none from the music block starting
at 0x1d12a shows.
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
\header {
texidoc = "
Unicode symbols for sharp and flat can be used in note names.
[WIP: for C only, only in nederlands.ly]
"
}
\version "2.11.51"
{
♭♭c c♭ c c♯ c♯♯
}
%{
double sharp: 𝄪
double flat: 𝄫
flat^: 𝄬
flatv: 𝄭
neutral^: 𝄮
neutralv: 𝄯
sharp^: 𝄰
sharpv: 𝄱
sharp4: 𝄲
flat4: 𝄳
'♭' (U+266D)
0xF0 0x9D 0x84 0xAB (f09d84ab)
%}
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
