Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(3768)

Issue 191360043: Suggest font encoding from Knut

Can't Edit
Can't Publish+Mail
Start Review
Created:
9 years, 4 months ago by Keith
Modified:
9 years, 4 months ago
Reviewers:
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Use of PostScript glyphshow, rather than show, for all characters seems to have started with http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=c3d6497157576dc0d4ae77c44978d54e7a212074 after some discussion at http://lists.gnu.org/archive/html/lilypond-devel/2004-10/msg00150.html The Ghostscript maintainer explains that for purposes of creating a PDF, ghostscript emulates glyphshow by collecting the glyphshow-ed glyphs into a font with an encoding : http://bugs.ghostscript.com/show_bug.cgi?id=695728 When several segments of Lilypond output are merged into one PDF, several of these fonts created on-the-fly take up space in the output file. This patch goes back to PostScript show for some glyphs, and disables subsetting of the fonts by Ghostscript (presumably to let a second-pass optimizer more easily merge any identical fonts).

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+100 lines, -29 lines) Patch
A ps/encodingdefs.ps View Binary file 0 comments Download
M scm/backend-library.scm View 1 chunk +1 line, -0 lines 0 comments Download
M scm/framework-ps.scm View 3 chunks +64 lines, -6 lines 0 comments Download
M scm/output-ps.scm View 2 chunks +35 lines, -23 lines 0 comments Download

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b