> Unfortunately, non-CID-keyed fonts can not use Identity-H encoding.
> XeTeX and LuaTeX seem to convert non-CID-Keyed font to CID-keyed
font on the
> fly, and embed it to PDF, use Identity-H encoding.
Should we create a tracker for this?
I think whoever has an idea and the time to solve
On 2017/09/28 11:04:03, dak wrote:
On 2017/09/28 10:26:05, knupero wrote:
> > While we are at it, it may make sense not to refer to the no
longer
> > existing Gmane page for bug reports.
>
> I changed the message, but there are 58 more places where post.gmane
is
> referenced in the tree.
> An
On 2017/09/29 12:01:41, trueroad wrote:
LGTM
For the future, I would like to prefer Identity-H encoding rather than
3 custom
encodings.
If I understand correctly,
All glyphs can be used with Identity-H encoding.
No other encoding is necessary.
For current LilyPond and Ghostscript, whe
LGTM
For the future, I would like to prefer Identity-H encoding rather than 3
custom encodings.
If I understand correctly,
All glyphs can be used with Identity-H encoding.
No other encoding is necessary.
For current LilyPond and Ghostscript, when using CID-keyed font,
Identity-H encoding PDF i
On 2017/09/28 10:26:05, knupero wrote:
> While we are at it, it may make sense not to refer to the no longer
> existing Gmane page for bug reports.
I changed the message, but there are 58 more places where post.gmane
is
referenced in the tree.
And there 113 mor place that reference othere pl
While we are at it, it may make sense not to refer to the no longer
existing Gmane page for bug reports.
I changed the message, but there are 58 more places where post.gmane is
referenced in the tree.
And there 113 mor place that reference othere places of gmane.
At least http://lilypond.org/bu
BTW, is there any chance to reduce the width of the help screen to
stay within 78 characters?
I don't think so
https://codereview.appspot.com/325630043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/l
Werner LEMBERG writes:
>> lilypond --help gives the following output: [...]
>
>> -O, --pspdfopt=KEY set ps/pdf optimization to KEY
>> (default: size)
>> KEY is either 'size', 'TeX' or
>> 'TeX-GS'
>
> LGTM, thanks!
>
> BTW, is there any
> lilypond --help gives the following output: [...]
> -O, --pspdfopt=KEY set ps/pdf optimization to KEY
> (default: size)
> KEY is either 'size', 'TeX' or
> 'TeX-GS'
LGTM, thanks!
BTW, is there any chance to reduce the width of the he
lilypond --help gives the following output:
Usage: lilypond [OPTION]... FILE...
Typeset music and/or produce MIDI from FILE.
LilyPond produces beautiful music notation.
For more information, see http://lilypond.org
Options:
-f, --formats=FORMATs dump FORMAT,... Also as separat
On 2017/09/27 11:49:51, knupero wrote:
> How about just --pdf= ? One option less to remember. This
is going
to
> be double the fun once we can generate PDF bypassing PS altogether.
Yes, even better.
> Sounds like a good strategy. Just not in time for 2.20.
I tend to agree.
Well, s
How about just --pdf= ? One option less to remember. This
is going to
be double the fun once we can generate PDF bypassing PS altogether.
Yes, even better.
Sounds like a good strategy. Just not in time for 2.20.
I tend to agree.
https://codereview.appspot.com/325630043/
_
On 2017/09/27 09:38:21, knupero wrote:
> Bikeshedding done for the day.
Let me continue.
"lilypond --help" and "lilypond -dhelp" gives perfect help to all
users. I doubt
that there are a lot of people who know which parameters to use for a
non-trivial case even after reading the help text
Bikeshedding done for the day.
Let me continue.
"lilypond --help" and "lilypond -dhelp" gives perfect help to all users.
I doubt that there are a lot of people who know which parameters to use
for a non-trivial case even after reading the help texts.
At least the following parameters influence
Werner LEMBERG writes:
>> Somehow, concisely say "get-rid-of-anything-extra" versus
>> "keep-everything-that-comes?"
>>
>> --min-fonts and --max-fonts
>> --compress-fonts and --expand-fonts
>
> I would rather prefer --compress-fonts and --no-compress-fonts. This
> is easier to remember (and rat
On 2017/09/27 04:55:31, wl_gnu.org wrote:
> Somehow, concisely say "get-rid-of-anything-extra" versus
> "keep-everything-that-comes?"
>
> --min-fonts and --max-fonts
> --compress-fonts and --expand-fonts
I would rather prefer --compress-fonts and --no-compress-fonts. This
is easier to remembe
> Somehow, concisely say "get-rid-of-anything-extra" versus
> "keep-everything-that-comes?"
>
> --min-fonts and --max-fonts
> --compress-fonts and --expand-fonts
I would rather prefer --compress-fonts and --no-compress-fonts. This
is easier to remember (and rather common in GNU packages).
> --
On 2017/09/26 22:19:27, dak wrote:
> If you know a better name for the option I'd happy to start sed.
--final-output ? --flatten-fonts ? Not sure about the inversions of
those,
however.
Somehow, concisely say "get-rid-of-anything-extra" versus
"keep-everything-that-comes?"
--min-fonts a
On 2017/09/26 20:26:36, knupero wrote:
> Regarding the naming of the option, I'd prefer to have something
> oriented around the actual use characteristics rather than the
> internal details.
>
> Does that sound like something you can agree with?
Yes. That sounds reasonable.
If you know a b
> Remember: We used the hardcoded name "Emmentaler" at various places
> for --bigpdfs, and --use-encodings still needs and uses that portion
> of the old code.
Before remembering something, I need to know it in the first place.
Sounds like something we should get rid off in the long run.
Ye
On 2017/09/25 22:17:41, knupero wrote:
On 2017/09/25 17:33:47, dak wrote:
> I see. Still using -dgs-never-embed-fonts _without_
> --use-encodings seems like the most unusual combination, so I'd
> prefer if one had to explicitly switch encodings _off_ rather than
> _on_.
So you are absolute
On 2017/09/25 17:33:47, dak wrote:
Why are we still navigating the bleeding edge? LilyPond is more than
20 years
old.
I remember a company that failed to get flash right.
Ghostscript still fails on GoToR without the help of extractpdfmarks ;-)
On 2017/09/25 16:38:16, knupero wrote:
> >
Why are we still navigating the bleeding edge? LilyPond is more than 20
years old.
On 2017/09/25 16:38:16, knupero wrote:
> > --use-encodings switches emmentaler glyph generation from
"glyphshow" to
> > "show"+encodings and might be combined width
-dgs-never-embed-fonts.
>
> That sounds goo
I don't really have a clue here: can someone chime in with the current
Ghostscript versions in possibly concerned distributions? Naturally
including
our own Gub-based ones?
OpenSuSE Tumbleweed: 9.21
OpenSuSE Leap: 9.15, but also offers 9.21
https://codereview.appspot.com/325630043/
> --use-encodings switches emmentaler glyph generation from
"glyphshow" to
> "show"+encodings and might be combined width -dgs-never-embed-fonts.
That sounds good. It also sounds like -dgs-never-embed-fonts should
imply
--use-encodings, right?
No. There are legitimate uses for both sta
On 2017/09/25 13:21:44, dak wrote:
I don't really have a clue here: can someone chime in with the current
Ghostscript versions in possibly concerned distributions? Naturally
including
our own Gub-based ones?
GUB has Ghostscript 9.21 except freebsd-x86.
(Ghostscript 9.2x for freebsd-x86 raise
On 2017/09/25 12:54:24, knupero wrote:
A bit more far-reaching.
As newer versions of gs
- don't need the helpemmentaler functions and
- don't need the real inclusion of all font data and
- don't need some other details and
- don't work properly with our old code
we might well decid
On 2017/09/25 12:13:34, knupero wrote:
kill --bigpdfs, introduce --use-encodings, remove code not needed by
ghostscript
9.20+
On my system (Ubuntu Aarkvard) I have Ghostscript 9.21 which is fine.
Usually we try to support the last LTS versions of Ubuntu, possibly
RedHat (and Debian unstable ?
https://codereview.appspot.com/325630043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
A bit more far-reaching.
As newer versions of gs
- don't need the helpemmentaler functions and
- don't need the real inclusion of all font data and
- don't need some other details and
- don't work properly with our old code
we might well decide to kill --bigpdfs.
Instead of --bigpdfs thi
On 2017/09/24 14:32:02, trueroad wrote:
* -dgs-neverembed-fonts
Add behavior
Current behavior
- For PDF output, It does not embed fonts except TrueType fonts.
Added behavior
- Define and use some encodings for Emmentaler. (Also using "show"
instead of
"glyphshow")
- For PDF output, It
On 2017/09/24 11:03:26, dak wrote:
In my opinion, -b/--bigpdf should be simple to use for
lilypond-book-like
applications. lilypond-book should likely call lilypond using options
leading
to good results by default. For generating our own documentation, I
find 3-4GB
of disk space excessive
On 2017/09/24 10:05:43, trueroad wrote:
On 2017/09/24 00:25:17, knupero wrote:
> > If I understand correctly, `--bigpdfs` / `-b` has two effects.
> > One is to embed full set (non-subset) font.
> > The other is to define and use some encodings for Emmentaler.
>
> It also changes the way emmentale
On 2017/09/24 00:25:17, knupero wrote:
> If I understand correctly, `--bigpdfs` / `-b` has two effects.
> One is to embed full set (non-subset) font.
> The other is to define and use some encodings for Emmentaler.
It also changes the way emmentaler glyphs are printed. With --bigpdfs
we use th
Combining them means that the size of the final PDF may be smaller but
the size
of the intermediate PDFs will be larger.
In my experiment, even if there is a bug in gs's full set font
embedding, the
disk size that `make doc` eats has increased.
I did not check that, but I would expect an i
`-dgs-never-embed-fonts` doesn't effect for TrueType fonts.
Therefore, when both `-dgs-never-embed-fonts` and `--bigpdfs`/`-b` are
used at the same time, TrueType fonts are embedded as full set (ie
non-subset). (if there is no bug in gs.)
On the other hand, some intermeiate PDFs use Japanese TrueT
Reviewers: dak,
Message:
On 2017/09/23 16:02:32, dak wrote:
https://codereview.appspot.com/325630043/diff/1/make/lilypond-vars.make
File make/lilypond-vars.make (right):
https://codereview.appspot.com/325630043/diff/1/make/lilypond-vars.make#newcode54
make/lilypond-vars.make:54: -dgs-never-
https://codereview.appspot.com/325630043/diff/1/make/lilypond-vars.make
File make/lilypond-vars.make (right):
https://codereview.appspot.com/325630043/diff/1/make/lilypond-vars.make#newcode54
make/lilypond-vars.make:54: -dgs-never-embed-fonts -b
Is there a conceivable application for using -b wi
38 matches
Mail list logo
