Re: 3.0 -- gnome backend
Nicolas Sceaux <[EMAIL PROTECTED]> writes: > My mistake. > pango 1.4.1 was the debian's one. I have 1.5.0 from (old) CVS. This is the > one that was used to compile LilyPond with --enable-gui. > I am upgrading to pango 1.5.2. > > What does BLOEDIGE_RAND mean? bleeding edge? > Should I use pango, g-wrap, etc, from CVS/arch or the tar.gz packages? > Now, I have rebuilt and installed pango, g-wrap, guile-gnome: nicolas:~> pkg-config --modversion pango 1.5.2 nicolas:~> pkg-config --modversion g-wrap-2.0-guile 1.9.1 nicolas:~> pkg-config --modversion guile-gnome-glib 2.5.993 and then built again LilyPond from CVS. but still the same result. Note: this may have nothing to do with gnome and pango, but I can select LilyPond-feta in OOo Writer, and insert F-clef, dacoda signs, etc. nicolas <>___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes: > Nicolas Sceaux writes: > >>> That's quite strange. I tested on a fresh machine. What versions of >>> fontconfig/gnome/pango do you use? >> >> fontconfig is version 2.2.3 >> gnome is 2.6.1 >> pango is 1.4.1 >> >> ohoh, maybe I should look at guile-gnome.sh again, and get a more >> recent pango. I'm doing this. > > Yes. Does lily build with pango and show the gnome canvas? I'm > amazed, it needs pango 1.5.2 or newer. My mistake. pango 1.4.1 was the debian's one. I have 1.5.0 from (old) CVS. This is the one that was used to compile LilyPond with --enable-gui. I am upgrading to pango 1.5.2. What does BLOEDIGE_RAND mean? bleeding edge? Should I use pango, g-wrap, etc, from CVS/arch or the tar.gz packages? nicolas ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Nicolas Sceaux writes: >> That's quite strange. I tested on a fresh machine. What versions of >> fontconfig/gnome/pango do you use? > > fontconfig is version 2.2.3 > gnome is 2.6.1 > pango is 1.4.1 > > ohoh, maybe I should look at guile-gnome.sh again, and get a more > recent pango. I'm doing this. Yes. Does lily build with pango and show the gnome canvas? I'm amazed, it needs pango 1.5.2 or newer. > LilyPond fonts do appear in the font selection dialog. Ok. This is the same mechanism, also gnome/pango, so the fonts are there. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> That's quite strange. I tested on a fresh machine. What versions of
> fontconfig/gnome/pango do you use?
fontconfig is version 2.2.3
gnome is 2.6.1
pango is 1.4.1
ohoh, maybe I should look at guile-gnome.sh again, and get a more
recent pango. I'm doing this.
> PS: you may try compiling this, to see if LilyPond fonts show up in
> the dialogue.
>
> /*
> gfs.c
> gcc -o gfs gfs.c $(pkg-config --cflags --libs gtk+-2.0)
> */
> #include
>
> int main(int argc, char* argv[]) {
> GtkWidget *dlg;
>
> gtk_init(&argc, &argv);
> dlg = gtk_font_selection_dialog_new("Select font");
> if (gtk_dialog_run(GTK_DIALOG(dlg)) == GTK_RESPONSE_OK) {
> g_print("Selected: %s.\n",
> gtk_font_selection_dialog_get_font_name(
> GTK_FONT_SELECTION_DIALOG(dlg)));
> }
> return 0;
> }
LilyPond fonts do appear in the font selection dialog.
nicolas
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Nicolas Sceaux writes:
> (without the closing tag)
Of coures, sorry.
fc-list |grep -i lily
Fontconfig error: "~/.fonts.conf", line 3: mismatched tag
> LilyPond\-feta:style=Regular
Ok.
> but still no feta glyphs displayed when invoking lilypond -fgnome.
That's quite strange. I tested on a fresh machine. What versions of
fontconfig/gnome/pango do you use?
> I'll try with defoma.
I don't think that defoma has anything to do with it, but I would like
to see this working for others than Han-Wen (I just learned last week
that it had only worked for me, when I wondered about the lack of
enthousiasm) and me.
Jan.
PS: you may try compiling this, to see if LilyPond fonts show up in
the dialogue.
/*
gfs.c
gcc -o gfs gfs.c $(pkg-config --cflags --libs gtk+-2.0)
*/
#include
int main(int argc, char* argv[]) {
GtkWidget *dlg;
gtk_init(&argc, &argv);
dlg = gtk_font_selection_dialog_new("Select font");
if (gtk_dialog_run(GTK_DIALOG(dlg)) == GTK_RESPONSE_OK) {
g_print("Selected: %s.\n",
gtk_font_selection_dialog_get_font_name(
GTK_FONT_SELECTION_DIALOG(dlg)));
}
return 0;
}
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes: > Han-Wen Nienhuys writes: > >> I recall that it wasn't so long ago that not all distributions shipped >> with fontconfig, which is instrumental in getting fonts from >> ~/.fonts/ configured correctly. > > That's it! xset/xlsfonts has nothing todo with gnome/pango fonts. It > seems gnome-font-install doesn't either. > > It's the fontconfig package; lilypond fonts should show up in fc-list. > > My fontconfig documentation says it looks in /usr/share/fonts and > ~/.fonts. To have fontconfig look in other directories, make a > > ~/.fonts.conf: > > > > ~/cvs/savannah/lilypond/lilypond/mf/out > > (without the closing tag) $ cat ~/.fonts.conf ~/cvs/lilypond/mf/out $ fc-cache -f $ fc-list | grep -i lilypond LilyPond\-feta\-din:style=Regular LilyPond\-feta\-braces\-a:style=Regular LilyPond\-feta\-braces\-c:style=Regular LilyPond\-feta\-braces\-b:style=Regular LilyPond\-feta\-braces\-e:style=Regular LilyPond\-feta\-braces\-d:style=Regular LilyPond\-feta\-braces\-g:style=Regular LilyPond\-feta\-braces\-f:style=Regular LilyPond\-feta\-braces\-i:style=Regular LilyPond\-feta\-braces\-h:style=Regular LilyPond\-feta\-nummer:style=Regular LilyPond\-parmesan:style=Regular LilyPond\-feta:style=Regular but still no feta glyphs displayed when invoking lilypond -fgnome. I'll try with defoma. nicolas ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Han-Wen Nienhuys writes: > I recall that it wasn't so long ago that not all distributions shipped > with fontconfig, which is instrumental in getting fonts from > ~/.fonts/ configured correctly. That's it! xset/xlsfonts has nothing todo with gnome/pango fonts. It seems gnome-font-install doesn't either. It's the fontconfig package; lilypond fonts should show up in fc-list. My fontconfig documentation says it looks in /usr/share/fonts and ~/.fonts. To have fontconfig look in other directories, make a ~/.fonts.conf: ~/cvs/savannah/lilypond/lilypond/mf/out Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
[EMAIL PROTECTED] writes: > Han-Wen Nienhuys writes: > > >> > $ ln -s ~/cvs/lilypond/mf/out ~/.fonts > >> > $ mkfontdir ~/.fonts > >> > $ xset +fp ~/.fonts > >> > >> Something went wrong here. Does xlsfonts report the feta fonts? > > > > Could it be that this is system/distribution specific? > > Until we know what's wrong, it could be the cat. I recall that it wasn't so long ago that not all distributions shipped with fontconfig, which is instrumental in getting fonts from ~/.fonts/ configured correctly. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Han-Wen Nienhuys writes: >> > $ ln -s ~/cvs/lilypond/mf/out ~/.fonts >> > $ mkfontdir ~/.fonts >> > $ xset +fp ~/.fonts >> >> Something went wrong here. Does xlsfonts report the feta fonts? > > Could it be that this is system/distribution specific? Until we know what's wrong, it could be the cat. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
[EMAIL PROTECTED] writes: > Nicolas Sceaux writes: > > > I have some troubles with it: feta fonts seem not to be found when > > the gnome output is displayed, although I have done: > > $ ln -s ~/cvs/lilypond/mf/out ~/.fonts > > $ mkfontdir ~/.fonts > > $ xset +fp ~/.fonts > > Something went wrong here. Does xlsfonts report the feta fonts? Could it be that this is system/distribution specific? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes: > Nicolas Sceaux writes: > >> I have some troubles with it: feta fonts seem not to be found when >> the gnome output is displayed, although I have done: >> $ ln -s ~/cvs/lilypond/mf/out ~/.fonts >> $ mkfontdir ~/.fonts >> $ xset +fp ~/.fonts > > Something went wrong here. Does xlsfonts report the feta fonts? Yes. nicolas:~/lilypond/cesare/ly/0-1> xlsfonts | grep feta -gnu-lilypond-feta braces a-r-normal-15-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces a-r-normal-15-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces a-r-normal-15-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces a-r-normal-15-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces b-r-normal-30-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces b-r-normal-30-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces b-r-normal-30-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces b-r-normal-30-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces c-r-normal-45-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces c-r-normal-45-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces c-r-normal-45-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces c-r-normal-45-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces d-r-normal-60-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces d-r-normal-60-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces d-r-normal-60-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces d-r-normal-60-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces e-r-normal-75-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces e-r-normal-75-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces e-r-normal-75-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces e-r-normal-75-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces f-r-normal-90-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces f-r-normal-90-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces f-r-normal-90-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces f-r-normal-90-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces g-r-normal-105-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces g-r-normal-105-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces g-r-normal-105-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces g-r-normal-105-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces h-r-normal-120-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces h-r-normal-120-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces h-r-normal-120-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces h-r-normal-120-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces i-r-normal-135-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces i-r-normal-135-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces i-r-normal-135-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta braces i-r-normal-135-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-14-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-14-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-14-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-14-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-17-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-17-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-17-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-17-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-5.5-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-5.5-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-5.5-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-5.5-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-8-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-8-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-8-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta din-r-normal-8-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-10-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu-lilypond-feta nummer-r-normal-12-0-0-0-0-p-0-gnu-fontspecific -gnu
Re: 3.0 -- gnome backend
Nicolas Sceaux writes: > I have some troubles with it: feta fonts seem not to be found when > the gnome output is displayed, although I have done: > $ ln -s ~/cvs/lilypond/mf/out ~/.fonts > $ mkfontdir ~/.fonts > $ xset +fp ~/.fonts Something went wrong here. Does xlsfonts report the feta fonts? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0 -- gnome backend
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> There is also some other good news: some of the dependencies for the
>> LilyPond GNOME backend have been released or are almost ready to be
>> released. This means that in a short while we will have "native"
>> point-and-click, without requiring TeX or DVI.
I have some troubles with it: feta fonts seem not to be found when
the gnome output is displayed, although I have done:
$ ln -s ~/cvs/lilypond/mf/out ~/.fonts
$ mkfontdir ~/.fonts
$ xset +fp ~/.fonts
(It used to work some months ago)
Does someone think about an extra thing to do?
Besides that, point-and-click works fine.
when it's time to add a 2Gnome command in emacs LilyPond-mode, here is
a patch:
Index: elisp/lilypond-init.el
===
RCS file: /cvsroot/lilypond/lilypond/elisp/lilypond-init.el,v
retrieving revision 1.2
diff -u -r1.2 lilypond-init.el
--- elisp/lilypond-init.el 22 Mar 2004 22:21:54 - 1.2
+++ elisp/lilypond-init.el 19 Sep 2004 08:52:35 -
@@ -15,6 +15,6 @@
;(setq load-path (append (list (expand-file-name "~/site-lisp")) load-path))
(autoload 'LilyPond-mode "lilypond-mode" "LilyPond Editing Mode" t)
-(add-to-list 'auto-mode-alist '("\\.ly$" . LilyPond-mode))
+(add-to-list 'auto-mode-alist '("\\.ly\\(inc\\)?$" . LilyPond-mode))
(add-hook 'LilyPond-mode-hook (lambda () (turn-on-font-lock)))
Index: elisp/lilypond-mode.el
===
RCS file: /cvsroot/lilypond/lilypond/elisp/lilypond-mode.el,v
retrieving revision 1.11
diff -u -r1.11 lilypond-mode.el
--- elisp/lilypond-mode.el 10 Aug 2004 22:42:35 - 1.11
+++ elisp/lilypond-mode.el 19 Sep 2004 08:52:36 -
@@ -416,6 +416,7 @@
("2Dvi" . ("lilypond -f tex %s" "%s" "%d" "LaTeX"))
("2PS" . ("lilypond -f ps %s" "%s" "%p" "ViewPS"))
+("2Gnome" . ("lilypond -fgnome %s"))
("2Midi" . ("lilypond -m %s" "%s" "%m" "Midi"))
("Book" . ("lilypond-book %x" "%x" "%l" "LaTeX"))
@@ -557,6 +558,11 @@
(LilyPond-command (LilyPond-command-menu "2PS") 'LilyPond-get-master-file)
)
+(defun LilyPond-command-formatgnome ()
+ "Format the Gnome output of the current document."
+ (interactive)
+ (LilyPond-command (LilyPond-command-menu "2Gnome") 'LilyPond-get-master-file))
+
(defun LilyPond-command-formatmidi ()
"Format the midi output of the current document."
(interactive)
@@ -683,7 +689,7 @@
(while (LilyPond-running)
(message "Starts playing midi once it is built.")
(sit-for 0 100))
- (if (member name (list "LilyPond" "TeX" "2Midi" "2PS" "2Dvi"
+ (if (member name (list "LilyPond" "TeX" "2Midi" "2PS" "2Dvi" "2Gnome"
"Book" "LaTeX"))
(if (setq jobs (LilyPond-running))
(progn
@@ -743,6 +749,7 @@
(define-key LilyPond-mode-map "\C-cm" 'LilyPond-command-formatmidi)
(define-key LilyPond-mode-map "\C-c\C-d" 'LilyPond-command-formatdvi)
(define-key LilyPond-mode-map "\C-c\C-f" 'LilyPond-command-formatps)
+ (define-key LilyPond-mode-map "\C-c\C-g" 'LilyPond-command-formatgnome)
(define-key LilyPond-mode-map "\C-c\C-s" 'LilyPond-command-smartview)
(define-key LilyPond-mode-map "\C-c\C-v" 'LilyPond-command-view)
(define-key LilyPond-mode-map "\C-c\C-p" 'LilyPond-command-viewps)
@@ -963,6 +970,7 @@
'([ "TeX" (LilyPond-command (LilyPond-command-menu "TeX") 'LilyPond-get-master-file) ])
'([ "2Dvi" LilyPond-command-formatdvi t])
'([ "2PS" LilyPond-command-formatps t])
+ '([ "2Gnome" LilyPond-command-formatgnome t])
'([ "2Midi" LilyPond-command-formatmidi t])
'([ "Book" (LilyPond-command (LilyPond-command-menu "Book") 'LilyPond-get-master-file) ])
'([ "LaTeX" (LilyPond-command (LilyPond-command-menu "LaTeX") 'LilyPond-get-master-file) ])
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
