> On Aug 27, 2023, at 11:55 PM, Werner LEMBERG wrote:
>
>
I do not think that my Times New Roman font is corrupted.
>>
>> Actually, I think it is: Most likely the font's 'post' table is
>> broken (i.e., it has a wrong PostScript name for glyph 'N').
>> Normally, you won't see the problem at
> On 28 Aug 2023, at 08:49, Jean Abou Samra wrote:
>
>
>
>> Le 28 août 2023 à 08:45, Jean Abou Samra a écrit :
>>
>>
>>
>>> You might try to copy the affected font from macOS 14 to macOS 13 and
>>> check whether it works.
>>
>>
>> This bug has already been fixed in Homebrew. Please ju
> Le 28 août 2023 à 08:45, Jean Abou Samra a écrit :
>
>
>
>> You might try to copy the affected font from macOS 14 to macOS 13 and
>> check whether it works.
>
>
> This bug has already been fixed in Homebrew. Please just uninstall and
> reinstall LilyPond and it should go away.
Whoops,
> You might try to copy the affected font from macOS 14 to macOS 13 and
> check whether it works.
This bug has already been fixed in Homebrew. Please just uninstall and
reinstall LilyPond and it should go away.
Jean
> Jean did the analysis then, he can tell more.
D'oh, *I* did the analysis then :-)
https://gitlab.com/lilypond/lilypond/-/issues/6508
Werner
>>> I do not think that my Times New Roman font is corrupted.
>
> Actually, I think it is: Most likely the font's 'post' table is
> broken (i.e., it has a wrong PostScript name for glyph 'N').
> Normally, you won't see the problem at all because most applications
> access a font's 'cmap' table (
>> I am experiencing a very weird problem with Lilypond on macOS 13
>> Ventura. When using the Times New Roman font, the capital letter N
>> is mis-printed.
Have a look at the thread starting at
https://lists.gnu.org/archive/html/lilypond-user/2022-12/msg00349.html
which discusses a very s
Hi.
> On 28 Aug 2023, at 11:36, David F. wrote:
>
> I am experiencing a very weird problem with Lilypond on macOS 13 Ventura.
> When using the Times New Roman font, the capital letter N is mis-printed.
>
I can confirm and replicate this under 13.4.1
> I do not think that my Times New Roman
Hi!
Maybe you can try installing de development version (2.19.*).
El 16/11/2016 8:51 p. m., "Thiago Censi" escribió:
> Hello.
>
> I am new to Lilypond. I am on Xubuntu 16.04 and installed the packages via
> the default repositories. I am having a problem with the fonts used in the
> score. I do
Hi Thiago,
> Michael, the actual sheet music (don't know the precise word in English,
> sorry) looks ok. But if I put any text, even change the time to a 3/4, it
> screws up. I tried changing the font size of the title. It doesn't work
> when I use #1 or fractions:
>
> piece = \markup { \fontsize
Thiago Censi wrote
> Hello.
>
> I am new to Lilypond. I am on Xubuntu 16.04 and installed the packages via
> the default repositories. I am having a problem with the fonts used in the
> score. I don't know if it is a Lilypond problem or a package missint or
> something else. I tried looking in the
Hi, Mark.
I knew there was nothing wrong with the code itself, I wanted some
directions with the font problem. I sownloaded the liilypond file here:
http://eugenecormier.com/?p=157
And this is what it looks like after compiling on my system:
http://i.imgur.com/uZMzfZw.png
Michael, the actual she
Hi Thiago,
> I am new to Lilypond. I am on Xubuntu 16.04 and installed the packages via
> the default repositories. I am having a problem with the fonts used in the
> score. I don't know if it is a Lilypond problem or a package missint or
> something else. I tried looking in the manual, Google and
Thiago,
I removed the “%” and everything looked correct.
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Thiago Censi
Sent: Wednesday, November 16, 2016 6:50 PM
To: lilypond-user@gnu.org
Subject: Font problem
Hello.
I am new to Lil
Am 2011-08-15 um 12:38 schrieb Jean-Alexis Montignies:
I don't see why pango or fontconfig would use this font as I doubt
it has the char I'm looking for, may be I can try to remove the X11
folder from the font search path. I'll dig into pango and fontconfig.
Henning, would you try compiling
>> To be more precise: LilyPond only handles outline fonts. A proper
>> filter to ensure that is still missing. Reason is that the
>> FontConfig interface doesn't provide a means to implement it.
>> IIRC, there is already a bug tracker issue which covers this.
>
> I don't see why pango or fontc
On 14 août 2011, at 23:47, Werner LEMBERG wrote:
>
>>> Here are the messages I get in the console:
>>>
>>> warning: no PostScript font name for font
>>> `/usr/X11R6/lib/X11/fonts/misc/10x20.pcf.gz'
>>
>> It's improbable that you want to use an X11 font with LilyPond.
>
> To be more precise: L
>> Here are the messages I get in the console:
>>
>> warning: no PostScript font name for font
>> `/usr/X11R6/lib/X11/fonts/misc/10x20.pcf.gz'
>
> It's improbable that you want to use an X11 font with LilyPond.
To be more precise: LilyPond only handles outline fonts. A proper
filter to ensure t
Am 2011-08-14 um 14:22 schrieb Jean-Alexis Montignies:
I've been compiling lilypond with fink (MacOS X 10.6) for two
years. Since a update about one year ago I didn't track down, I have
some trouble with some unicode characters (in that case 0x266D which
is a flat sign).
The binary versio
I'm not sure I understand exactly what you tried. If I understand you
correctly, the problems you reported first with missing font symbols
for text fonts, was when you tried the Cygwin installation. Right?
Then, you tried the non-cygwin version and got the error message
you included below, right?
Maxime Brugidou a écrit :
I wrote :
>>Hello
>>i installed lilypond with cygwin on my winXP and are now able to use
lilypond
but ok, i'm trying to use it the non-cygwin package, but i got an error :
"Pange-ERROR **: file
/var/fred/cvs/savannah/lilypond/installers/windows/mingw/src/pango-1.8.1
Mats Bengtsson a écrit :
You didn't say earlier that you used the Cygwin installation.
I would recommend the non-Cygwin "native" Windows package
available at lilypond.org/web/install/, unless you have any specific
reason to work in Cygwin.
/Mats
I wrote :
>>Hello
>>i installed lilypond with
You didn't say earlier that you used the Cygwin installation.
I would recommend the non-Cygwin "native" Windows package
available at lilypond.org/web/install/, unless you have any specific
reason to work in Cygwin.
/Mats
Maxime Brugidou wrote:
Han-Wen Nienhuys a écrit :
Maxime Brugidou wro
Han-Wen Nienhuys a écrit :
Maxime Brugidou wrote:
my version is 2.6.4 i send an example from the lilypond.org website
http://membres.lycos.fr/cocatpe/Schubert.ly
http://membres.lycos.fr/cocatpe/Schubert.pdf
can you check whether 2.6.3 does work for you?
http://lilypond.org/download/binar
Maxime Brugidou wrote:
my version is 2.6.4 i send an example from the lilypond.org website
http://membres.lycos.fr/cocatpe/Schubert.ly
http://membres.lycos.fr/cocatpe/Schubert.pdf
can you check whether 2.6.3 does work for you?
http://lilypond.org/download/binaries/mingw/lilypond-2.6.3-1.exe
Once you get your basic font setup working, don't forget to save
your .ly file using UTF-8 encoding instead of Latin 1 (ISO 8859-1).
However, this doesn't explain the problems you show in your example.
/Mats
Maxime Brugidou wrote:
Mats Bengtsson a écrit :
Very strange, I haven't seen that
Mats Bengtsson a écrit :
Very strange, I haven't seen that problem reported earlier.
Lyrics certainly work well for me in WinXP.
Exactly which version of LilyPond did you install?
/Mats
Maxime Brugidou wrote:
Hello
i installed lilypond with cygwin on my winXP and are now able to use
lily
Very strange, I haven't seen that problem reported earlier.
Lyrics certainly work well for me in WinXP.
Exactly which version of LilyPond did you install?
/Mats
Maxime Brugidou wrote:
Hello
i installed lilypond with cygwin on my winXP and are now able to use
lilypond
i can do really good
Mats Bengtsson <[EMAIL PROTECTED]> writes:
> OK, what happens if you do
> ps2pdf testfont.ps
> and view the resulting PDF file?
I can see the ugly treble clef again.
> If the PS file looks OK, then I would definitely suspect
> your Ghostscript (which is the program doing the job in
> ps2pdf).
S
OK, what happens if you do
ps2pdf testfont.ps
and view the resulting PDF file?
If the PS file looks OK, then I would definitely suspect your
Ghostscript (which is the program doing the job in ps2pdf).
Do you get the same problem both when viewing the PDF on screen
and when you print it on paper? Co
Mats Bengtsson <[EMAIL PROTECTED]> writes:
> Did you build the ec-fonts-mftraced yourself? I would guess so,
> since you have problems both with the feta fonts in LilyPond and
> the ec-font used for the title.
You guessed wrong. ec-fonts-mftraced is from the Lilypond
download site.
> If you wan
Did you build the ec-fonts-mftraced yourself? I would guess so,
since you have problems both with the feta fonts in LilyPond and
the ec-font used for the title.
In that case, it must be something wrong with your mftrace (or
some of the programs it uses).
If you want to verify that a certain font fi
Ferenc Wagner <[EMAIL PROTECTED]> writes:
http://article.gmane.org/gmane.comp.gnu.lilypond.general/14591/
> Notice the ugly clef and the title.
>
> I used the 1.0.12 version of ec-fonts-mftraced. Living on
> Debian Woody has its quirks concerning updmap, but I did
> my best. Any hints where the
In message <[EMAIL PROTECTED]>, Jan Nieuwenhuizen
<[EMAIL PROTECTED]> writes
Anthony W. Youngman writes:
This is *linux*. "rpm -U" fails, "rpm --install" fails ... and why
should I expect it to make any difference?
TeX may have been updated, and there's a postinstall script.
Unfortunately, mktexls
Anthony W. Youngman writes:
> This is *linux*. "rpm -U" fails, "rpm --install" fails ... and why
> should I expect it to make any difference?
TeX may have been updated, and there's a postinstall script.
> Unfortunately, mktexlsr doesn't make any difference either.
The check that configure does
In message <[EMAIL PROTECTED]>, Jan Nieuwenhuizen
<[EMAIL PROTECTED]> writes
Anthony W. Youngman writes:
"ec-fonts-mftraced is not installed" - except "rpm -U" fails with
"already installed".
Try to reinstall ec-fonts-mftraced or run mktexlsr by hand.
This is *linux*. "rpm -U" fails, "rpm --instal
Anthony W. Youngman writes:
> "ec-fonts-mftraced is not installed" - except "rpm -U" fails with
> "already installed".
Try to reinstall ec-fonts-mftraced or run mktexlsr by hand.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien
In message <[EMAIL PROTECTED]>, Jan Nieuwenhuizen
<[EMAIL PROTECTED]> writes
Anthony W. Youngman writes:
There is a problem with the ec-fonts-mftraced package, it is not
tetex-3.0 compatible. Bertalan made manual fixes for cygwin,
but there is no autodetection yet.
Any more news?
Yes, ec-fonts-mf
Anthony W. Youngman writes:
>>There is a problem with the ec-fonts-mftraced package, it is not
>>tetex-3.0 compatible. Bertalan made manual fixes for cygwin,
>>but there is no autodetection yet.
>>
> Any more news?
Yes, ec-fonts-mftraced v1.0.12 is tetex-3.0 compatible.
> I'm trying to install
Anthony W. Youngman wrote:
> In message <[EMAIL PROTECTED]>, Jan Nieuwenhuizen
> <[EMAIL PROTECTED]> writes
>
>> Doug Asherman writes:
>>
>>> I compiled 2.4.5 from the tarball -- I'm trying to use it with tetex-3.0
>>
<<< Stuff deleted -- >>>
>>
> Any more news?
>
> I'm trying to install 2.4.5 on S
In message <[EMAIL PROTECTED]>, Jan Nieuwenhuizen
<[EMAIL PROTECTED]> writes
Doug Asherman writes:
I compiled 2.4.5 from the tarball -- I'm trying to use it with tetex-3.0
The problem I'm seeing is that the generated .ps and .pdf files have no
fonts except for the notes and associated stuff like
Doug Asherman writes:
> I compiled 2.4.5 from the tarball -- I'm trying to use it with tetex-3.0
> The problem I'm seeing is that the generated .ps and .pdf files have no
> fonts except for the notes and associated stuff like time signatures,
> etc. But I'm not seeing title, composer, rehearsal m
On Tue, Mar 08, 2005 at 09:51:50AM -0800, Doug Asherman wrote:
> I compiled 2.4.5 from the tarball -- I'm trying to use it with tetex-3.0
> under Linux. I've read the compilation instructions, and aside from a
> small problem with espgs, everything seemed to go well.
For the OpenBSD port (to be an
Le 9 déc. 04, à 21:41, Graham Percival a écrit :
On 9-Dec-04, at 6:40 AM, Paul Crabbe wrote:
I installed lilypond 2.3.13 on Mac OSX
Please upgrade to stable lilypond in fink (it's 2.4.2, IIRC)
Cheers,
- Graham
&
> BTW, you may have to do a fink selfupdate. I missed that step...
that was it! I did
BTW, you may have to do a fink selfupdate. I missed that step and kept
wondering why the Fink distribution was so far behind the current
version. :)
On Dec 9, 2004, at 12:41 PM, Graham Percival wrote:
On 9-Dec-04, at 6:40 AM, Paul Crabbe wrote:
I installed lilypond 2.3.13 on Mac OSX
Please upgra
On 9-Dec-04, at 6:40 AM, Paul Crabbe wrote:
I installed lilypond 2.3.13 on Mac OSX
Please upgrade to stable lilypond in fink (it's 2.4.2, IIRC)
Cheers,
- Graham
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypo
Hello list, hello Pedro,
You wrote:
> Roland Goretzki <[EMAIL PROTECTED]> writes:
>
> >> http://www.pedrokroeger.net/lilypond/lilypond-snapshot-doc_2.4.0-2_all.deb
>
> I actually meant:
>
> http://www.pedrokroeger.net/lilypond/lilypond-snapshot_2.4.0-2_i386.deb
Well, I installed them both,
li
Roland Goretzki <[EMAIL PROTECTED]> writes:
>> http://www.pedrokroeger.net/lilypond/lilypond-snapshot-doc_2.4.0-2_all.deb
I actually meant:
http://www.pedrokroeger.net/lilypond/lilypond-snapshot_2.4.0-2_i386.deb
> Now there is another error message:
>
> ERROR: In procedure primitive-load-path:
Hello list, hello Pedro,
You wrote:
> could you, please, try the new and corrected version I upload recently?
> it's here:
>
> http://www.pedrokroeger.net/lilypond/lilypond-snapshot-doc_2.4.0-2_all.deb
>
> Please, let me know if it works for you (or not).
Now there is another error message:
E
Roland Goretzki <[EMAIL PROTECTED]> writes:
> Hi at all,
>
> after installing lilypond-snapshot 2.4.0 from Pedro Kroegers site
> on a never-online-host with dpkg as follows:
>
> dpkg -i ec-fonts-mftraced_1.0.7-1_all.deb
> dpkg -i lilypond-snapshot_2.4.0_i386.deb
>
> and both worked success
> Hi All,
>
> When compiling lilypond 2.3.9 or 2.3.10 from source, everything
> compiles fine, but when I run the program, I get the following error:
>
> Parsing...
> Interpreting music... error: can't find `feta20.afm'
> Music font has not been installed properly. Aborting
>
> The font was trace
Did you read about the file lilypond-profile (or lilypond-login if
you use tcsh) in INSTALL.txt?
/Mats
J. Scott Amort wrote:
Hi All,
When compiling lilypond 2.3.9 or 2.3.10 from source, everything compiles
fine, but when I run the program, I get the following error:
Parsing...
Interpreting music
On Mon, 2003-08-18 at 17:50, Stefaan Himpe wrote:
> Hi,
>
> Your .pdf looks bad on my Debian SID system
> as well. Upon regenerating the .pdf from the source
> using lilypond, it looks perfectly normal on my system.
>
> In addition your .pdf is about 25% larger than the
> one my system generates.
Hi,
Your .pdf looks bad on my Debian SID system
as well. Upon regenerating the .pdf from the source
using lilypond, it looks perfectly normal on my system.
In addition your .pdf is about 25% larger than the
one my system generates. How did you generate the .pdf?
Best regards,
Stefaan
___
Tyler Eaves writes:
> Hi gang - Just reinstall debian on my system (I was flirting with FBSD
> 5.1). Lilypond 1.8.0 (apt-geted from unstable) works great, except that
> pdfs have font weirdness in the heading. Compare the attached dvi and
> pdf. I've attached the ly source as well.
Both look fin
[EMAIL PROTECTED] writes:
> > > Lilypond is version 1.4.10-87
> > >
> > > When I process my files I get C clefs appearing instead of the
> > > tails of quavers. Any suggestions?
> >
> > Can you send us the output of ly2dvi or lilypond --verbose?
> > Lilypond should detect this problem (which alre
> On Wednesday 31 July 2002 00:23, Han-Wen wrote:
> > [EMAIL PROTECTED] writes:
> > > I'm running lilypond on SuSE Linux 8.0.
> > >
> > > Lilypond is version 1.4.10-87
> > >
> > > When I process my files I get C clefs appearing instead of the
> > > tails of quavers. Any suggestions?
> >
> > Can y
On Wednesday 31 July 2002 00:23, Han-Wen wrote:
> [EMAIL PROTECTED] writes:
> > I'm running lilypond on SuSE Linux 8.0.
> >
> > Lilypond is version 1.4.10-87
> >
> > When I process my files I get C clefs appearing instead of the
> > tails of quavers. Any suggestions?
>
> Can you send us the outpu
> I'm running lilypond on SuSE Linux 8.0.
>
> Lilypond is version 1.4.10-87
>
> When I process my files I get C clefs appearing instead of the tails
> of quavers. Any suggestions?
You have probably used a different Lilypond version before.
Please read what the README or INSTALL file for Lilyp
this sounds like a font-path problem.
source the file lilypond-profile in $LILYSRC/buildscripts/ or add those
contents of lilypond-profile permanently to your .bash_profile.
(i think -- at least that works for me)
hope this helps. greetings from the alps,
simon.
On Tue, 2002-07-30 at 00:42, A
Amelie Zapf wrote:
>
Amelie,
if you are using a distribution that includes tetex, then
the following suggestion might help you:
1. get the latest xdvi-22.48
ftp://ftp.math.berkeley.edu/pub/Software/TeX/
2. ./configure --with-tetex (or --with-tetex=PATHLIST) (a
> Hi Jan and all,
>
> now I typeset a couple LaTeX documents with dvips -Ppdf, and now I can't make
> any more Lilypond pdfs (if I do, I get no noteheads). I get the following
> messages:
>
> amelie@amy:~/music/gospelchor > dvips -Ppdf charleston_alley.dvi
> This is dvips(k) 5.86 Copyright 199
62 matches
Mail list logo
