Mercurial > vim
view runtime/print/cidfont.ps @ 14806:7cc2d28778ac v8.1.0415
patch 8.1.0415: not actually using 16 colors with vtp
commit https://github.com/vim/vim/commit/d4f73438bb6c88a0d3e315f0eebef30993b5921c
Author: Bram Moolenaar <Bram@vim.org>
Date: Fri Sep 21 12:24:12 2018 +0200
patch 8.1.0415: not actually using 16 colors with vtp
Problem: Not actually using 16 colors with vtp.
Solution: Always use 256 colors when vtp is used. (Nobuhiro Takasaki,
closes #3432)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Fri, 21 Sep 2018 12:30:06 +0200 |
parents | 631143ac4a01 |
children |
line wrap: on
line source
%!PS-Adobe-3.0 Resource-ProcSet %%Title: VIM-CIDFont %%Version: 1.0 0 %%EndComments % Editing of this file is NOT RECOMMENDED. You run a very good risk of causing % all PostScript printing from VIM failing if you do. PostScript is not called % a write-only language for nothing! /CP currentpacking d T setpacking /SB 256 string d /CIDN? systemdict/composefont known d /GS? systemdict/.makeoperator known d CIDN?{ GS?{/vim_findresource{2 copy resourcestatus not{1 index SB cvs runlibfile}{ pop pop}ifelse findresource}bd/vim_composefont{0 get/CIDFont vim_findresource exch/CMap vim_findresource exch[exch]composefont pop}bd}{/vim_findresource /findresource ld/vim_composefont{composefont pop}bd}ifelse }{ /vim_fontname{0 get SB cvs length dup SB exch(-)putinterval 1 add dup SB exch dup 256 exch sub getinterval 3 -1 roll exch cvs length add SB exch 0 exch getinterval cvn}bd/vim_composefont{vim_fontname findfont d}bd } ifelse /cfs{exch scalefont d}bd /sffs{findfont 3 1 roll 1 index mul exch 2 index/FontMatrix get matrix copy scale makefont d}bd CP setpacking % vim:ff=unix: %%EOF