>> PS: How did I get the EPS-file? With lilypond.
>
> The file lilypond creates doesn't have a %%BoundingBox comment,
> so PSPIC doesn't know how the "picture" should be scaled.
> (This can be fixed with a little shell script calling
> "gs -sDEVICE=bbox" to get the bounding box and sed to
> inse
Bernd,
please create a ChangeLog file in groff/contrib/lilypond and add all
further commit messages to that file. This is true for all stuff in
the `contrib' directory, BTW.
> Adding lilypond parts into groff files by using groff requests
> `.lilypond start' and `.lilytpond end'.
>
> These pa
> In other words, using .PSPIC with lilypond EPS files works out of
> the box.
And please ignore the harmless warnings of grops; this is due to a
sloppy definition of the CFF resource in the PS reference manual
(example 5.7) which omits the version arguments to the `procset'
resource, and which Li
> Today is 2013, not 1993.
Possibly :-)
But I still mistrust things I can't repair with a text editor.
> And CFF fonts, AFAIK, can't be embedded in hex form at all
> in PostScript files.
According to Adobe, CFF fonts are "based on all of the same
concepts for drawing paths and hinting" as Type
Sorry, forgot the file.
#!/bin/bash
file="$1"
tempfile="$file.edited.$$"
sed -e '
/^%%DocumentMedia:/d
/^%%HiResBoundingBox:/d
/^%%PageBoundingBox:/d
/^%%BoundingBox:/d
/^%%DocumentSuppliedResources:
font/s/DocumentSuppliedResources/DocumentNeededResources/
/^%%BeginFont:/,/
Hello all,
I'm trying to use the ASCII escape character as the groff escape
character, but it doesn't seem to work. If I try this code :
.ec @
@fBtest@fR
Where all `@' must be replace by ASCII 27, I obtained `fBtestfR' on
output. Is there a solution for using a non printable character as the
gr
Hi Jérôme,
> I'm trying to use the ASCII escape character as the groff escape
> character, but it doesn't seem to work.
I don't think you can do that.
> Is there a solution for using a non printable character as the groff
> escape character ?
Yes, pick one of the allowed ones.
$ cat -A jer
On Sun, 10 Feb 2013 13:47:15 +, Ralph Corderoy wrote:
> Yes, pick one of the allowed ones.
>
> $ cat -A jerome
> .ec @$
> foo@fBbar@fPxyzzy$
> .ec ^@$
> foo^@fBbar^@fPxyzzy$
> .ec ^B$
> foo^BfBbar^BfPxyzzy$
> .ec ^[$
> foo^[fBbar^[fPxyzzy$
> $ nroff jerom
> But I still mistrust things I can't repair with a text editor.
:-)
> According to Adobe, CFF fonts are "based on all of the same concepts
> for drawing paths and hinting" as Type 1 fonts, and "a Type 1 font
> can be converted into CFF/Type2 format, and back to Type 1 again,
> without any loss
> Type 2 charstrings have some extensions like the `random'
> operator which isn't supported in Type 1 fonts.
Ah. So the reason otf -> pfa usually works is because most
fonts contain "regular" character outlines that are just
packaged as CFF, without actually making use of the new
features.
(Of c
>> * Lilypond outputs a space character at the top left. Since I have
>>no experience with lilypond I don't know what generates this,
>>and my solution is to simply edit it out.
>
> IIRC, this is a bug which I haven't been able to catch yet (mostly
> due to time constraints).
I have to
> Ah. So the reason otf -> pfa usually works is because most fonts
> contain "regular" character outlines that are just packaged as CFF,
> without actually making use of the new features.
Yes, AFAIK. Actually, Type 1 fonts can contain *any* PS code (and
some fonts like `Optima' actually make use
> Von: "Werner LEMBERG"
>
> There is another Lilypond option to let the fonts be loaded by
> GhostScript directly:
>
> lilypond --ps -dbackend=eps -dgs-load-fonts ...
>
> This uses GhostScript's `.loadfont' operator, making the section look
> like this on my GNU/Linux box:
>
> %%BeginProlo
>> A nice side effect is that the EPS files become much smaller, but
>> of course they are no longer self-contained. Again, grops
>> understands this just fine, but you *must* use GhostScript
>> afterwards to further process the output file.
>
> How is Ghostscript to be used for that?
For examp
In groff_lilypond there are now 2 modes for generating the EPS
files:
--ly2eps (the new default) and
--pdf2eps (that's the old mode from version v0.1 with pdf to ps to eps).
With ly2eps mode, lilypond generates the EPS files itself, for each page
one EPS file.
Unfortunately the .PSPIC works o
15 matches
Mail list logo
