1
- *print.txt* For Vim version 8.0 . Last change: 2010 Jul 20
1
+ *print.txt* For Vim version 8.1 . Last change: 2010 Jul 20
2
2
3
3
4
4
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -99,25 +99,25 @@ If the option is empty, then vim will use the system default printer for
99
99
HPUX: hp-roman8,
100
100
EBCDIC: ebcdic-uk)
101
101
global
102
- Sets the character encoding used when printing. This option tells VIM which
102
+ Sets the character encoding used when printing. This option tells Vim which
103
103
print character encoding file from the "print" directory in 'runtimepath' to
104
104
use.
105
105
106
106
This option will accept any value from | encoding-names | . Any recognized names
107
- are converted to VIM standard names - see 'encoding' for more details. Names
108
- not recognized by VIM will just be converted to lower case and underscores
107
+ are converted to Vim standard names - see 'encoding' for more details. Names
108
+ not recognized by Vim will just be converted to lower case and underscores
109
109
replaced with '-' signs.
110
110
111
- If 'printencoding' is empty or VIM cannot find the file then it will use
112
- 'encoding' (if VIM is compiled with | +multi_byte | and it is set an 8-bit
113
- encoding) to find the print character encoding file. If VIM is unable to find
111
+ If 'printencoding' is empty or Vim cannot find the file then it will use
112
+ 'encoding' (if Vim is compiled with | +multi_byte | and it is set an 8-bit
113
+ encoding) to find the print character encoding file. If Vim is unable to find
114
114
a character encoding file then it will use the "latin1" print character
115
115
encoding file.
116
116
117
- When 'encoding' is set to a multi-byte encoding, VIM will try to convert
117
+ When 'encoding' is set to a multi-byte encoding, Vim will try to convert
118
118
characters to the printing encoding for printing (if 'printencoding' is empty
119
119
then the conversion will be to latin1). Conversion to a printing encoding
120
- other than latin1 will require VIM to be compiled with the | +iconv | feature.
120
+ other than latin1 will require Vim to be compiled with the | +iconv | feature.
121
121
If no conversion is possible then printing will fail. Any characters that
122
122
cannot be converted will be replaced with upside down question marks.
123
123
@@ -203,7 +203,7 @@ header is used when this option is empty.
203
203
'printmbcharset' 'pmbcs' string (default "")
204
204
global
205
205
Sets the CJK character set to be used when generating CJK output from
206
- | :hardcopy | . The following predefined values are currently recognised by VIM :
206
+ | :hardcopy | . The following predefined values are currently recognised by Vim :
207
207
208
208
Value Description ~
209
209
Chinese GB_2312-80
@@ -270,7 +270,7 @@ Japanese text you would do the following; >
270
270
271
271
If 'printmbcharset' is not one of the above values then it is assumed to
272
272
specify a custom multi-byte character set and no check will be made that it is
273
- compatible with the value for 'printencoding' . VIM will look for a file
273
+ compatible with the value for 'printencoding' . Vim will look for a file
274
274
defining the character set in the "print" directory in 'runtimepath' .
275
275
276
276
*pmbfn-option*
@@ -420,10 +420,10 @@ There are currently a number of limitations with PostScript printing:
420
420
possible to get all the characters in an encoding to print by installing a
421
421
new version of the Courier font family.
422
422
423
- - Multi-byte support - Currently VIM will try to convert multi-byte characters
423
+ - Multi-byte support - Currently Vim will try to convert multi-byte characters
424
424
to the 8-bit encoding specified by 'printencoding' (or latin1 if it is
425
425
empty). Any characters that are not successfully converted are shown as
426
- unknown characters. Printing will fail if VIM cannot convert the multi-byte
426
+ unknown characters. Printing will fail if Vim cannot convert the multi-byte
427
427
to the 8-bit encoding.
428
428
429
429
==============================================================================
@@ -434,35 +434,35 @@ you need to define your own PostScript font encoding vector. Details on how
434
434
to define a font encoding vector is beyond the scope of this help file, but
435
435
you can find details in the PostScript Language Reference Manual, 3rd Edition,
436
436
published by Addison-Wesley and available in PDF form at
437
- http://www.adobe.com/ . The following describes what you need to do for VIM to
437
+ http://www.adobe.com/ . The following describes what you need to do for Vim to
438
438
locate and use your print character encoding.
439
439
440
440
i. Decide on a unique name for your encoding vector, one that does not clash
441
- with any of the recognized or standard encoding names that VIM uses (see
441
+ with any of the recognized or standard encoding names that Vim uses (see
442
442
| encoding-names | for a list), and that no one else is likely to use.
443
443
ii. Copy $VIMRUNTIME/print/latin1.ps to the print subdirectory in your
444
444
'runtimepath' and rename it with your unique name.
445
445
iii. Edit your renamed copy of latin1.ps, replacing all occurrences of latin1
446
446
with your unique name (don't forget the line starting %%Title:), and
447
447
modify the array of glyph names to define your new encoding vector. The
448
448
array must have exactly 256 entries or you will not be able to print!
449
- iv. Within VIM , set 'printencoding' to your unique encoding name and then
450
- print your file. VIM will now use your custom print character encoding.
449
+ iv. Within Vim , set 'printencoding' to your unique encoding name and then
450
+ print your file. Vim will now use your custom print character encoding.
451
451
452
- VIM will report an error with the resource file if you change the order or
452
+ Vim will report an error with the resource file if you change the order or
453
453
content of the first 3 lines, other than the name of the encoding on the line
454
454
starting %%Title: or the version number on the line starting %%Version:.
455
455
456
- [Technical explanation for those that know PostScript - VIM looks for a file
456
+ [Technical explanation for those that know PostScript - Vim looks for a file
457
457
with the same name as the encoding it will use when printing. The file
458
458
defines a new PostScript Encoding resource called /VIM-name, where name is the
459
- print character encoding VIM will use.]
459
+ print character encoding Vim will use.]
460
460
461
461
==============================================================================
462
462
5. PostScript CJK Printing *postscript-cjk-printing*
463
463
*E673* *E674* *E675*
464
464
465
- VIM supports printing of Chinese, Japanese, and Korean files. Setting up VIM
465
+ Vim supports printing of Chinese, Japanese, and Korean files. Setting up Vim
466
466
to correctly print CJK files requires setting up a few more options.
467
467
468
468
Each of these countries has many standard character sets and encodings which
@@ -483,7 +483,7 @@ option allows you to specify different fonts to use when printing characters
483
483
which are syntax highlighted with the font styles normal, italic, bold and
484
484
bold-italic.
485
485
486
- No CJK fonts are supplied with VIM . There are some free Korean, Japanese, and
486
+ No CJK fonts are supplied with Vim . There are some free Korean, Japanese, and
487
487
Traditional Chinese fonts available at:
488
488
489
489
http://examples.oreilly.com/cjkvinfo/adobe/samples/
@@ -498,15 +498,15 @@ CJK fonts can be large containing several thousand glyphs, and it is not
498
498
uncommon to find that they only contain a subset of a national standard. It
499
499
is not unusual to find the fonts to not include characters for codes in the
500
500
ASCII code range. If you find half-width Roman characters are not appearing
501
- in your printout then you should configure VIM to use the Courier font the
501
+ in your printout then you should configure Vim to use the Courier font the
502
502
half-width ASCII characters with 'printmbfont' . If your font does not include
503
503
other characters then you will need to find another font that does.
504
504
505
505
Another issue with ASCII characters, is that the various national character
506
506
sets specify a couple of different glyphs in the ASCII code range. If you
507
507
print ASCII text using the national character set you may see some unexpected
508
508
characters. If you want true ASCII code printing then you need to configure
509
- VIM to output ASCII characters for the ASCII code range with 'printmbfont' .
509
+ Vim to output ASCII characters for the ASCII code range with 'printmbfont' .
510
510
511
511
It is possible to define your own multi-byte character set although this
512
512
should not be attempted lightly. A discussion on the process if beyond the
@@ -525,13 +525,13 @@ print job completing.
525
525
There are a number of possible causes as to why the printing may have failed:
526
526
527
527
- Wrong version of the prolog resource file. The prolog resource file
528
- contains some PostScript that VIM needs to be able to print. Each version
529
- of VIM needs one particular version. Make sure you have correctly installed
528
+ contains some PostScript that Vim needs to be able to print. Each version
529
+ of Vim needs one particular version. Make sure you have correctly installed
530
530
the runtime files, and don't have any old versions of a file called prolog
531
531
in the print directory in your 'runtimepath' directory.
532
532
533
533
- Paper size. Some PostScript printers will abort printing a file if they do
534
- not support the requested paper size. By default VIM uses A4 paper. Find
534
+ not support the requested paper size. By default Vim uses A4 paper. Find
535
535
out what size paper your printer normally uses and set the appropriate paper
536
536
size with 'printoptions' . If you cannot find the name of the paper used,
537
537
measure a sheet and compare it with the table of supported paper sizes listed
@@ -668,7 +668,7 @@ complex print document creation.
668
668
669
669
N-UP PRINTING
670
670
671
- The psnup utility takes an existing PostScript file generated from VIM and
671
+ The psnup utility takes an existing PostScript file generated from Vim and
672
672
convert it to an n-up version. The simplest way to create a 2-up printout is
673
673
to first create a PostScript file with: >
674
674
@@ -724,16 +724,16 @@ There are a couple of points to bear in mind:
724
724
==============================================================================
725
725
8. Formfeed Characters *printing-formfeed*
726
726
727
- By default VIM does not do any special processing of | formfeed | control
728
- characters. Setting the 'printoptions' formfeed item will make VIM recognize
727
+ By default Vim does not do any special processing of | formfeed | control
728
+ characters. Setting the 'printoptions' formfeed item will make Vim recognize
729
729
formfeed characters and continue printing the current line at the beginning
730
730
of the first line on a new page. The use of formfeed characters provides
731
731
rudimentary print control but there are certain things to be aware of.
732
732
733
- VIM will always start printing a line (including a line number if enabled)
733
+ Vim will always start printing a line (including a line number if enabled)
734
734
containing a formfeed character, even if it is the first character on the
735
735
line. This means if a line starting with a formfeed character is the first
736
- line of a page then VIM will print a blank page.
736
+ line of a page then Vim will print a blank page.
737
737
738
738
Since the line number is printed at the start of printing the line containing
739
739
the formfeed character, the remainder of the line printed on the new page
@@ -742,7 +742,7 @@ lines of a long line when wrap in 'printoptions' is enabled).
742
742
743
743
If the formfeed character is the last character on a line, then printing will
744
744
continue on the second line of the new page, not the first. This is due to
745
- VIM processing the end of the line after the formfeed character and moving
745
+ Vim processing the end of the line after the formfeed character and moving
746
746
down a line to continue printing.
747
747
748
748
Due to the points made above it is recommended that when formfeed character
0 commit comments