Hi,
On Thu, Oct 26, 2023 at 09:36:24PM +0200, Jean Abou Samra wrote:
> > https://lilypond.org/doc/v2.25/Documentation/notation/font-families
> >
> > still claims that LilyPond still includes URW fonts, which it doesn't
> > since 2.24.
>
> It does — ot
Le jeudi 26 octobre 2023 à 21:26 +0200, Matthias Kilian a écrit :
> https://lilypond.org/doc/v2.25/Documentation/notation/font-families
>
> still claims that LilyPond still includes URW fonts, which it doesn't
> since 2.24.
It does — otherwise, they could not be set as the d
Hi,
https://lilypond.org/doc/v2.25/Documentation/notation/font-families
still claims that LilyPond still includes URW fonts, which it doesn't
since 2.24.
I'm not sure wether it's ok to just remove the 'distributed with
LilyPond' in the corresponding paragraph or wether this would let people
>> So yes, please open an issue.
>
> https://gitlab.com/lilypond/lilypond/-/issues/6613
Thanks!
Werner
Le mardi 23 mai 2023 à 20:13 +, Werner LEMBERG a écrit :
> So yes, please open an issue.
https://gitlab.com/lilypond/lilypond/-/issues/6613
signature.asc
Description: This is a digitally signed message part
> On master, compiling the code
>
> ```
> \version "2.25.6"
>
> \paper {
> property-defaults.fonts.serif = "Noto Serif"
> }
>
> \markup \bold "abc"
> ```
>
> I get
>
> ```
> warning: font index 393
On master, compiling the code
```
\version "2.25.6"
\paper {
property-defaults.fonts.serif = "Noto Serif"
}
\markup \bold "abc"
```
I get
```
warning: font index 393216 too large for font
`/usr/share/fonts/google-noto-vf/NotoSerif[wght].ttf', using
Sorry Walter one more thing: you would then point configure to those font
install locations explicitly
../configure \
--prefix=$HOME/usr \
--with-texgyre-dir=/texmf-dist/fonts/opentype/public/tex-gyre/ \
--with-urwotf-dir=/urw-core35-fonts/
replace '' with appropriate paths
Hi Walter,
here's a couple more direct pointers for you:
The TeX fonts (Gyre) will be in a place like
.../texmf-dist/opentype/public/tex-gyre/texgyreschola-regular.otf
the '...' is because the stem of the path changes system to system (I'm
assuming TexLive here).
If you find texmf-dist
> Le 26 juil. 2022 à 23:36, Dan Eble a écrit :
>
> On Jul 26, 2022, at 09:11, Walter Garcia-Fontes
> wrote:
>>
>> I checked, and the following packages are installed in my system:
>>
>> tex-gyre
>> texlive-fonts-extra
>> fonts-texgyre
>&
On Jul 26, 2022, at 09:11, Walter Garcia-Fontes wrote:
>
> I checked, and the following packages are installed in my system:
>
> tex-gyre
> texlive-fonts-extra
> fonts-texgyre
>
> How can I get these missing fonts?
Walter,
I'm using
https://github.com/fedelibre/Li
I'm trying to build Lilypond locally. My system is Ubuntu 22.04.
When I run "./configure" in my build diretory, at the end I get the
following message:
WARNING: Please consider installing optional programs or files: URW++ OTF
fonts (these files are missing: C059-BdIta.otf C059-Bol
>>> Stupid question: how do I find the path to TeXLive in the build
>>> system?
>>
>> All TeXLive binaries are expected to be in PATH. Why do you need
>> the path?
>
> Sorry, I meant the part of TEXINPUTS in your previous
> email.
Ah, ok. I think a good solution is to let `kpsewhich`
;
> For pygments with LM, the following additional tests would be
> necessary.
>
> * A check that the `pltotf` binary is present (it is part of the
> 'fontware' TeXLive package).
>
> * Checks for `fontinst.sty` (in the 'fontinst' package) and the LM
> fonts (in the '
fontinst.sty` (in the 'fontinst' package) and the LM
fonts (in the 'lm' package). Something like the following should
work, using a pars pro toto approach.
kpsewhich -format=tex fontinst.sty
kpsewhich -format='type1 fonts' lmtl10
> Do we have CG instructions to update with respe
Le 01/12/2021 à 14:06, Werner LEMBERG a écrit :
Here is my solution for using the LM typewriter fonts for pygments
support in texinfo. It consists of the following.
* Files `lm-ot1.tex` and `lm-ot1-map.tex`. They should be executed as
follows
export TEXINPUTS="/fonts/afm/publ
> * Files `lm-ot1.tex` and `lm-ot1-map.tex`. They should be executed as
> follows
>
> export TEXINPUTS="/fonts/afm/public/lm;"
> tex lm-ot1.tex
> tex lm-ot1-maps.tex
I forgot to mention that you need the 'fontinst' TeXLive package for
that.
Werner
Here is my solution for using the LM typewriter fonts for pygments
support in texinfo. It consists of the following.
* Files `lm-ot1.tex` and `lm-ot1-map.tex`. They should be executed as
follows
export TEXINPUTS="/fonts/afm/public/lm;"
tex lm-ot1.tex
tex lm-ot
to revert mtime: /Library/Fonts
Processing
`/var/folders/r_/gm2jl2qd15195gchymxn9qqcgn/T/frescobaldi-orv4nsnc/tmp_etwhswj/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout
Hi
I use Lilypond’s Frescobaldi 3.1.2 on my MacBook Pro 10.15 Catalina. After
downloading frescobaldi 3.1.2, I go to directory and run./frescobaldi, I
got the following:
Starting lilypond 2.20.0 [Untitled]...
Unable to revert mtime: /Library/Fonts
Processing
`/var/folders/r_
Hi Owen,
It appears that my problem was just a newbie mistake after all.
Near the end of last week (Thursday or Friday, it must have been), I
decided to try out Hyper-V on my machine, just to see what it could
do. I didn't end up doing anything with it, but I didn't get rid of
it, either. I
Owen Lamb writes:
> Hi all,
>
> It appears that my problem was just a newbie mistake after all.
>
> Near the end of last week (Thursday or Friday, it must have been), I
> decided to try out Hyper-V on my machine, just to see what it could do. I
> didn't end up doing anything with it, but I
Hi all,
It appears that my problem was just a newbie mistake after all.
Near the end of last week (Thursday or Friday, it must have been), I
decided to try out Hyper-V on my machine, just to see what it could do. I
didn't end up doing anything with it, but I didn't get rid of it, either. I
never
Sure thing--it's coming your way!
On Wed, Jul 1, 2020 at 1:01 PM Michael Käppler wrote:
> Am 01.07.2020 um 21:15 schrieb Owen Lamb:
> > Hi Michael,
> >
> > 1. I've been using VBox version 6.1.8, one version behind the latest.
> > Today I updated to 6.1.10, but the problem persists.
> Can you
Am 01.07.2020 um 21:15 schrieb Owen Lamb:
Hi Michael,
1. I've been using VBox version 6.1.8, one version behind the latest.
Today I updated to 6.1.10, but the problem persists.
Can you please send me the output of 'VBoxManage showvminfo
NAMEOFYOURVM' privately, too?
Cheers,
Michael
Am 01.07.2020 um 21:15 schrieb Owen Lamb:
Hi Michael,
1. I've been using VBox version 6.1.8, one version behind the latest.
Today I updated to 6.1.10, but the problem persists.
2. No, I'm not using -j, but today I tried -j2 to see what would
happen. Both threads got stuck, one while processing
Hi Michael,
1. I've been using VBox version 6.1.8, one version behind the latest. Today
I updated to 6.1.10, but the problem persists.
2. No, I'm not using -j, but today I tried -j2 to see what would happen.
Both threads got stuck, one while processing feta11.pfb, and the other
while processing
I'd really like to see if someone can reproduce any of this on a
different
machine and a fresh LilyDev VM, so please holler if you're willing to
try!
I will try this today.
I cannot reproduce this, neither with current master (7854d1b4)
nor with dev/lamb/GSoC-2020.
I'm using LilyDev 2 in
; much--my
> > > previous message was merely a shot in the dark but I understand almost
> > > nothing
> > > about fonts. Also, I'll be going on vacation pretty soon, so I won't have
> > > time
> > > to set up LilyDev, sorry…
> > >
> >
&g
nderstand
almost nothing
about fonts. Also, I'll be going on vacation pretty soon, so I
won't have time
to setup LilyDev, sorry…
No worries. Have a great vacation!
Thanks!
That said, if CI itself started to fail recently, there must be
something broken
in the sources,
Hi Owen,
Am 01.07.2020 um 01:54 schrieb Owen Lamb:
Ctrl-C'ing yields the same output as before, plus a success message:
*** Successfully generated feta20.pfb! ***
(The file feta20.pfb does indeed exist, and can be viewed in the
build/mf/out, in a temporary folder. It contains all the glyphs
t in the dark but I understand almost
>> nothing
>> about fonts. Also, I'll be going on vacation pretty soon, so I won't have
>> time
>> to set up LilyDev, sorry…
>>
>
> No worries. Have a great vacation!
>
>> That said, if CI itself started to fa
On Tue, Jun 30, 2020 at 3:04 PM Jean Abou Samra wrote:
> So git clean didn't work? At this point, unfortunately I can't help
> much--my
> previous message was merely a shot in the dark but I understand almost
> nothing
> about fonts. Also, I'll be going on vacation pretty soon,
dn't work? At this point, unfortunately I can't help much--my
previous message was merely a shot in the dark but I understand almost
nothing
about fonts. Also, I'll be going on vacation pretty soon, so I won't
have time
to setup LilyDev, sorry…
That said, if CI itself started to fail recently, t
Hi Owen,
>>
>> To begin with, glad to meet you!
>>
>> What an annoying problem. Here's what I could suggest:
>>
>> - Try 'git -xdf' to clean your repository entirely, removing any
>> untracked or ignored files. If you're touching fonts, it may be that
>
nnoying problem. Here's what I could suggest:
>
> - Try 'git -xdf' to clean your repository entirely, removing any
> untracked or ignored files. If you're touching fonts, it may be that
> some build artifacts have to be removed (likewise, people often need
> such a procedure or a
Hi Owen,
To begin with, glad to meet you!
What an annoying problem. Here's what I could suggest:
- Try 'git -xdf' to clean your repository entirely, removing any
untracked or ignored files. If you're touching fonts, it may be that
some build artifacts have to be removed (likewise, people often
;> rm -fr build/
> >> sh autogen.sh --noconfigure
> >> mkdir -p build/
> >> cd build/
> >> ../configure
> >> make -j3 CPU_COUNT=3
> >>
> >> failed with:
> >>
> >> /home/hermann/lilypond-git/flower/jsoncpp.cc:
: In function 'void
>> Json::throwRuntimeError(const String&)':
>> /home/hermann/lilypond-git/flower/jsoncpp.cc:2620:25: error: exception
>> handling disabled, use -fexceptions to enable
>>throw RuntimeError(msg);
>> ^
>>
>> A subsequent `make' from current master i.e.
>> 751d453f9172c7dff81d11181158051065badeaf
>> succeeded.
>>
>> Not sure whether this helps...
>
>
> Ah! Sorry about that. JSON_USE_EXCEPTION should be #defined as 0. I just
> pushed a quick fix.
>
> At any rate, for me the lilypond executable builds successfully in all cases.
> The issue is only with generating fonts.
>
> --Owen
Hi Owen,
after your fix `make' succeeded here:
P.e.
Making mf/out/feta11.pfb < mf
is fine.
I'm on Ubuntu-18.04 64-bit with Ghostscript 9.26
Same as your ghostscript-version? I could try a different version...
Cheers,
Harm
On Mon, Jun 29, 2020, 4:40 PM Thomas Morley wrote:
> Let me take the opportunity to thank you for your work.
> Although it's a topic where I can't help, I enjoy reading your posts.
Same here. This is exemplary for future GSoC participants.
--
Karlin High
Missouri, USA
n::throwRuntimeError(const String&)':
> /home/hermann/lilypond-git/flower/jsoncpp.cc:2620:25: error: exception
> handling disabled, use -fexceptions to enable
>throw RuntimeError(msg);
> ^
>
> A subsequent `make' from current master i.e.
> 751d453f9172c7dff81d11181158051065badeaf
> succeeded.
>
> Not sure whether this helps...
Ah! Sorry about that. JSON_USE_EXCEPTION should be #defined as 0. I just
pushed a quick fix.
At any rate, for me the lilypond executable builds successfully in all
cases. The issue is only with generating fonts.
--Owen
Am Mo., 29. Juni 2020 um 22:43 Uhr schrieb Owen Lamb :
>
> Hi all,
>
> On Friday, make started hanging when making the first .pfb font file,
> displaying no new information after:
>
> Making mf/out/feta11.pfb < mf
> Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
>
Hi all,
On Friday, make started hanging when making the first .pfb font file,
displaying no new information after:
Making mf/out/feta11.pfb < mf
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
License GPLv3+: GNU GPL version 3 or later <
/running.itely:652: This is useful when you want to
create a font-non-embedded PDFs first
On 2020/04/28 15:51:33, lemzwerg wrote:
> Replace this and the next line with
>
> This is useful if you want to create PDFs without embedded fonts
first, letting
> Ghostscript embed the fonts in a fo
fonts
later cause garbled characters.
... causes ...
https://codereview.appspot.com/577900043/diff/577910043/Documentation/usage/running.itely#newcode670
Documentation/usage/running.itely:670: @code{gs-never-embed-fonts}
embeds TrueType fonts despite its name.
To avoid garbling characters, use
@code
://codereview.appspot.com/577900043/diff/577910043/Documentation/usage/running.itely#newcode652
Documentation/usage/running.itely:652: This is useful when you want to
create a font-non-embedded PDFs first
Replace this and the next line with
This is useful if you want to create PDFs without embedded fonts first,
letting
On 4/19/20, David Kastrup wrote:
> However, there are a few
> other problems with that regtest that should likely show with Guile-2
> (sometimes?).
Could you elaborate as to what I need to watch out for? I’ve tested it
successfully with Guile 2.2 here (but history has teached us that
unforeseen
Am Sonntag, den 19.04.2020, 23:24 +0200 schrieb David Kastrup:
> Jonas Hahnfeld writes:
> > To avoid this from happening again, can we please have the rule that
> > whoever reverts a commit or backs it out of staging is to provide
> > guidance on what's actually wrong? My feeling is that we could
Valentin Villenave writes:
> On 4/19/20, David Kastrup wrote:
>> At that day I was having one patchy run after the other and I did go
>> through the log files to indicate the failed file and the error message.
>
> Yep, and I asked for additional info both on the tracker and on
> Rietveld; the
On 4/19/20, David Kastrup wrote:
> At that day I was having one patchy run after the other and I did go
> through the log files to indicate the failed file and the error message.
Yep, and I asked for additional info both on the tracker and on
Rietveld; the only reply I did get was from James who
Jonas Hahnfeld writes:
> Am Sonntag, den 19.04.2020, 22:16 +0200 schrieb David Kastrup:
>> pkx1...@posteo.net
>> writes:
>>
>> > Hello,
>> >
>> > On 19/04/2020 17:53, David Kastrup wrote:
>> > > v.villen...@gmail.com
>> > > writes:
>> > >
>> > > > On 2020/04/11 09:44:26, Valentin Villenave
Am Sonntag, den 19.04.2020, 22:16 +0200 schrieb David Kastrup:
> pkx1...@posteo.net
> writes:
>
> > Hello,
> >
> > On 19/04/2020 17:53, David Kastrup wrote:
> > > v.villen...@gmail.com
> > > writes:
> > >
> > > > On 2020/04/11 09:44:26, Valentin Villenave wrote:
> > > > > What could be the
pkx1...@posteo.net writes:
> Hello,
>
> On 19/04/2020 17:53, David Kastrup wrote:
>> v.villen...@gmail.com writes:
>>
>>> On 2020/04/11 09:44:26, Valentin Villenave wrote:
What could be the cause?
>>> So, pushed as
>>>
Hello,
On 19/04/2020 17:53, David Kastrup wrote:
v.villen...@gmail.com writes:
On 2020/04/11 09:44:26, Valentin Villenave wrote:
What could be the cause?
So, pushed as
https://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=0cfef7069e86f85ad392f5c4bc63f6c4801aa2c9
V.
On 4/19/20, David Kastrup wrote:
> v.villen...@gmail.com writes:
> Breaks my patchy again. Whose patchy was comfortable moving it from
> staging to master?
Well, at any rate James’ patchy what fine with it. (As it went through
the review/countdown process not just once but twice.)
The regtest
v.villen...@gmail.com writes:
> On 2020/04/11 09:44:26, Valentin Villenave wrote:
>> What could be the cause?
>
> So, pushed as
> https://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=0cfef7069e86f85ad392f5c4bc63f6c4801aa2c9
>
> V.
>
> https://codereview.appspot.com/557640051/
Breaks my
On 2020/04/11 09:44:26, Valentin Villenave wrote:
> What could be the cause?
So, pushed as
https://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=0cfef7069e86f85ad392f5c4bc63f6c4801aa2c9
V.
https://codereview.appspot.com/557640051/
commit 2d40ef8ced63607cc1a9b2a0bc6a1fd1122af8c4
Author: Han-Wen Nienhuys
Date: Fri Mar 27 19:20:32 2020 +0100
mf: use python scripting for generating Emmentaler fonts
https://codereview.appspot.com/553580043/
https://codereview.appspot.com/557640051/diff/565870043/input/regression/font-name-add-files.ly
File input/regression/font-name-add-files.ly (right):
https://codereview.appspot.com/557640051/diff/565870043/input/regression/font-name-add-files.ly#newcode244
Reviewers: lemzwerg,
Message:
commit 28b894cb8d121eb7f531e193d1736b99fe593edf
Author: Han-Wen Nienhuys
Date: Sun Mar 15 17:02:16 2020 +0100
Stop installing TFM and Type1 fonts.
https://sourceforge.net/p/testlilyissues/issues/5855
http://codereview.appspot.com/577700043
On 2020/04/02 21:20:58, dak wrote:
> On 2020/04/02 21:09:57, thomasmorley651 wrote:
> > On 2020/04/02 21:04:06, dak wrote:
> > > On 2020/04/02 20:32:39, hanwenn wrote:
> > > > Jonas, what is the status of 2.21.0 ?
> > >
> > > I wanted to give Phil the go-ahead tomorrow, once some backdated
On 2020/04/02 21:09:57, thomasmorley651 wrote:
> On 2020/04/02 21:04:06, dak wrote:
> > On 2020/04/02 20:32:39, hanwenn wrote:
> > > Jonas, what is the status of 2.21.0 ?
> >
> > I wanted to give Phil the go-ahead tomorrow, once some backdated
convert-ly
> rule
> > is in. Probably depends on how
On 2020/04/02 21:04:06, dak wrote:
> On 2020/04/02 20:32:39, hanwenn wrote:
> > Jonas, what is the status of 2.21.0 ?
>
> I wanted to give Phil the go-ahead tomorrow, once some backdated
convert-ly rule
> is in. Probably depends on how well the LSR import works whether this
gets out
> then.
On 2020/04/02 20:32:39, hanwenn wrote:
> Jonas, what is the status of 2.21.0 ?
I wanted to give Phil the go-ahead tomorrow, once some backdated
convert-ly rule is in. Probably depends on how well the LSR import
works whether this gets out then.
https://codereview.appspot.com/553580043/
Jonas, what is the status of 2.21.0 ?
https://codereview.appspot.com/553580043/
On 2020/03/30 18:56:27, thomasmorley651 wrote:
> tmpnam is deprecated in guile-3.0.2
(sigh) Nice catch!
> Why introducing it, we would need to move away from it later anyway?
Well, I *would* have used mkstemp, but I need to create a directory
(rather than a file), and there’s no mkdtemp in
On 2020/03/30 18:29:37, Valentin Villenave wrote:
> On 2020/03/30 16:06:08, lemzwerg wrote:
> > Is it guaranteed that we can create this directory? What about
srcdir !=
> > builddir?
>
> Yes. It’s a (tmpnam) name, located in /tmp or $TMPDIR or whatever:
>
needs additional hooks only for
one regtest to clean after itself, but it *could* be a problem for
systems that run the regtests continuously.
Thanks for the other nits, I’ve addressed them.
V.
Description:
Issue #1204: Document, and add regtest for, external fonts.
Add a few details in NR 1
Nice idea, thanks. Some nits and questions.
https://codereview.appspot.com/557640051/diff/571940043/Documentation/notation/text.itely
File Documentation/notation/text.itely (right):
https://codereview.appspot.com/557640051/diff/571940043/Documentation/notation/text.itely#newcode1552
https://codereview.appspot.com/553580043/diff/571810043/mf/gen-emmentaler-brace.fontforge.py
File mf/gen-emmentaler-brace.fontforge.py (right):
https://codereview.appspot.com/553580043/diff/571810043/mf/gen-emmentaler-brace.fontforge.py#newcode40
mf/gen-emmentaler-brace.fontforge.py:40: #
https://codereview.appspot.com/553580043/diff/571810043/mf/gen-emmentaler-brace.fontforge.py
File mf/gen-emmentaler-brace.fontforge.py (right):
https://codereview.appspot.com/553580043/diff/571810043/mf/gen-emmentaler-brace.fontforge.py#newcode40
mf/gen-emmentaler-brace.fontforge.py:40: #
LGTM
https://codereview.appspot.com/577700043/
On 2020/02/29 22:53:43, lemzwerg wrote:
> > > Can we assume that FontForge's python support and is
> > > always enabled? Shall we check this?
> >
> > the FF page doesn't say that python is optional.
>
> It's a build option in both the old (configure) and new (cmake)
builds...
GUB doesn't have
> > Can we assume that FontForge's python support and is
> > always enabled? Shall we check this?
>
> the FF page doesn't say that python is optional.
It's a build option in both the old (configure) and new (cmake)
builds...
https://codereview.appspot.com/553580043/
https://codereview.appspot.com/553580043/diff/571780045/mf/GNUmakefile
File mf/GNUmakefile (right):
https://codereview.appspot.com/553580043/diff/571780045/mf/GNUmakefile#newcode130
mf/GNUmakefile:130: $(outdir)/emmentaler-brace.otf:
emmentaler-brace.fontforge.py
LGTM; some minor nits
https://codereview.appspot.com/553580043/diff/571780045/mf/GNUmakefile
File mf/GNUmakefile (right):
https://codereview.appspot.com/553580043/diff/571780045/mf/GNUmakefile#newcode130
mf/GNUmakefile:130: $(outdir)/emmentaler-brace.otf:
emmentaler-brace.fontforge.py
> I'll open up a ticket and upload a patch as soon as it's finished
> (it already works, but I want a proper solution).
Great, thanks!
> *By the way:* how about TABs? Obviously, gitk, Rietveld et al. seem
> to use 8 spaces per tab.
I've just committed a patch that converts tabs to spaces in
Werner LEMBERG wrote
> Yes, and avoiding overlaps everywhere would lead to unnecessarily
> complicated code. Tools like FontForge should be used to fix this in
> a post-processing stage, exactly as we do.
I totally agree. I'm going to fix the cases giving an error.
"Don't fix it if it ain't
> Unfortunately, mf overlaps can hardly be avoided in many cases,
> because lots of glyphs are being composed out of several overlapping
> predefined components.
Yes, and avoiding overlaps everywhere would lead to unnecessarily
complicated code. Tools like FontForge should be used to fix this
Sorry, my "turn" was a goof: The loop in the outline produced a tiny
fissure…
Now I've put a bit more effort in it, combining two subpaths at their
intersection so that metapost's output will be a plain and simple outline,
/exactly/ matching the original turn outline, but without any loops or
Werner LEMBERG wrote
> The output produced by the `mf2pt1` script to convert METAFONT input files
> to Type1 PostScript fonts often contains overlapping glyphs. This should
> be
> avoided in general.[1] For this reason, `mf2pt1` by default calls
> `FontForge` in batch mode to
Some time ago I was asked to document how to prepare MWE for reporting
FontForge problems with Emmentaler. Here it is.
How to report `FontForge` problems while creating LilyPond fonts
The output produced by the `mf2pt1` script
Il giorno lun 9 dic 2019 alle 11:18, Federico Bruni
ha scritto:
Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG ha
scritto:
Your `t1asm` binary crashes with a segmentation fault, as can be seen
in last two lines of `mf2pt1.strace.657213`:
--- SIGSEGV {si_signo=SIGSEGV,
Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG ha
scritto:
Your `t1asm` binary crashes with a segmentation fault, as can be seen
in last two lines of `mf2pt1.strace.657213`:
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
si_addr=0x3055683} ---
+++ killed by SIGSEGV (core
>> Please try again with
>>strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf
>> so that we can see the strace messages from `t1asm` also. Note that
>> you will get at least two files called `mf2pt1.strace.X`, where
>> `X` is a process ID.
>>
>
> Four log-files were created, and the 3
Le 08/12/2019 à 18:12, Werner LEMBERG a écrit :
Please try again with
strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf
so that we can see the strace messages from `t1asm` also. Note that
you will get at least two files called `mf2pt1.strace.X`, where
`X` is a process ID.
Four
>> Strange indeed. Can you temporarily replace `mf2pt1` with a script
>> that calls `strace`? Something like
>>strace mf2pt1 ... &> ~/mf2pt1.strace.log
>> You could then investigate in more detail which files `mf2pt1` tries
>> to open and/or execute.
>>
>
> [jcharles@pc1 mf]$ strace
Le 08/12/2019 à 17:10, Werner LEMBERG a écrit :
Strange indeed. Can you temporarily replace `mf2pt1` with a script
that calls `strace`? Something like
strace mf2pt1 ... &> ~/mf2pt1.strace.log
You could then investigate in more detail which files `mf2pt1` tries
to open and/or execute.
> which t1asm
> /usr/bin/t1asm
>
> so I don't see any reason why, just at once, it failed at running…
> after a good sleeping night!
Strange indeed. Can you temporarily replace `mf2pt1` with a script
that calls `strace`? Something like
strace mf2pt1 ... &> ~/mf2pt1.strace.log
You could
Le 08/12/2019 à 16:51, Werner LEMBERG a écrit :
Can you execute t1asm?
t1asm --help
It works either in $HOME or in my compiling folders.
Is it in your path that you use for compiling lilypond?
which t1asm
/usr/bin/t1asm
so I don't see any reason why, just at once, it failed at
> I notice, upwards in the log, that
>
> Invoking "t1asm feta11.pt1 feta11.pfb"...
> mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find
> another way to convert feta11.pt1 to feta11.pfb
>
>
> despite I've t1utils-1.41-1.fc31.x86_64 installed.
Can you execute t1asm?
Hi all,
For about two weeks now, I'm unable to build and then merge translation
with stable, even after a fresh clone. I cannot believe it has something
to do with an upgrade from Fedora 30 to 31.
Tail of the log :
--8<--
cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe
Copyright
such a set of steps but who had less
knowledge about fonts/fontforge and our make process like yourself. Then
others could open tickets with FF instead of just relying on you.
Thanks
James
>> It's not a regression, right.
>
> My first probably-not-very-correct thing to do next was check out
> stable/2.18 and make LP from there (on the same system am building
> latest master on) and search for the same errors. [...]
>
> So is this a regression?
My answer is still no. Our glyph
>> Now that Dan has made default make commands 'terser' I am noticing
>> while building our fonts that I see quite a few 'errors' that look
>> like this:
>>
>> Internal Error (overlap) in clefs.petrucci.c5_change:
>> Winding number did not return to 0 when
On 05/11/2019 12:06, David Kastrup wrote:
James writes:
Hello,
Now that Dan has made default make commands 'terser' I am noticing
while building our fonts that I see quite a few 'errors' that look
like this:
Internal Error (overlap) in clefs.petrucci.c5_change: Winding number
did not return
James writes:
> Hello,
>
> Now that Dan has made default make commands 'terser' I am noticing
> while building our fonts that I see quite a few 'errors' that look
> like this:
>
> Internal Error (overlap) in clefs.petrucci.c5_change: Winding number
> did not return to 0 w
Hello,
Now that Dan has made default make commands 'terser' I am noticing while
building our fonts that I see quite a few 'errors' that look like this:
Internal Error (overlap) in clefs.petrucci.c5_change: Winding number did
not return to 0 when x=25.9951
Internal Error (overlap
On 02.01.19 14:27, Knut Petersen wrote:
On 15.12.18 15:42, Masamichi Hosoda wrote:
I've noticed that gs-9.26 cannot embed CID fonts
for the extractpdfmark method.
In the method, we defined fonts in PostScript, and use it in PDF.
gs-9.26 cannot define the fonts for PDF in PostScript.
https
On 15.12.18 15:42, Masamichi Hosoda wrote:
I've noticed that gs-9.26 cannot embed CID fonts
for the extractpdfmark method.
In the method, we defined fonts in PostScript, and use it in PDF.
gs-9.26 cannot define the fonts for PDF in PostScript.
https://bugs.ghostscript.com/show_bug.cgi?id=700367
1 - 100 of 541 matches
Mail list logo
