From cb71658a54f93d12c4645bb779bb83ee2d115df2 Mon Sep 17 00:00:00 2001 From: Peter Breitenlohner Date: Wed, 22 Apr 2015 10:58:54 +0000 Subject: Update manpages git-svn-id: svn://tug.org/texlive/trunk@37001 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/man/man1/dvisvgm.1 | 254 +++++++++++++++++++++++-------- 1 file changed, 192 insertions(+), 62 deletions(-) (limited to 'Master/texmf-dist/doc/man/man1/dvisvgm.1') diff --git a/Master/texmf-dist/doc/man/man1/dvisvgm.1 b/Master/texmf-dist/doc/man/man1/dvisvgm.1 index 0c65adf919a..9be7787de8a 100644 --- a/Master/texmf-dist/doc/man/man1/dvisvgm.1 +++ b/Master/texmf-dist/doc/man/man1/dvisvgm.1 @@ -2,12 +2,12 @@ .\" Title: dvisvgm .\" Author: Martin Gieseking .\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 04/23/2014 +.\" Date: 04/07/2015 .\" Manual: dvisvgm Manual -.\" Source: dvisvgm 1.6 +.\" Source: dvisvgm 1.9.2 .\" Language: English .\" -.TH "DVISVGM" "1" "04/23/2014" "dvisvgm 1\&.6" "dvisvgm Manual" +.TH "DVISVGM" "1" "04/07/2015" "dvisvgm 1\&.9\&.2" "dvisvgm Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -28,7 +28,7 @@ .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" -dvisvgm \- converts DVI files to the XML\-based SVG format +dvisvgm \- converts DVI and EPS files to the XML\-based SVG format .SH "SYNOPSIS" .sp \fBdvisvgm\fR [ \fIoptions\fR ] \fIfile\fR [\&.dvi] @@ -36,7 +36,7 @@ dvisvgm \- converts DVI files to the XML\-based SVG format \fBdvisvgm\fR \-E [ \fIoptions\fR ] \fIfile\fR [\&.eps] .SH "DESCRIPTION" .sp -The command\-line utility \fBdvisvgm\fR converts DVI files, as generated by TeX/LaTeX, to the XML\-based scalable vector graphics format SVG\&. It supports the classic DVI format 2 as well as format 3 (created by pTeX in vertical mode), and format 5 which is also known as XDV (created by XeTeX)\&. Besides the basic DVI commands, dvisvgm also evaluates many so\-called \fIspecials\fR which heavily extend the capabilities of the DVI format\&. For a more detailed overview, see section \fBsupport of specials\fR below\&. +The command\-line utility \fBdvisvgm\fR converts DVI files, as generated by TeX/LaTeX, to the XML\-based scalable vector graphics format SVG\&. It supports the classic DVI format 2 as well as format 3 (created by pTeX in vertical mode), and format 5 which is also known as XDV (created by XeTeX)\&. Besides the basic DVI commands, dvisvgm also evaluates many so\-called \fIspecials\fR which heavily extend the capabilities of the DVI format\&. For a more detailed overview, see section \fBSupported Specials\fR below\&. .sp Since the current SVG standard 1\&.1 doesn\(cqt specify multi\-page graphics, dvisvgm creates separate SVG files for each DVI page\&. Because of compatibility reasons, only the first page is converted by default\&. In order to select a different page or arbitrary page sequences, use option \fB\-p\fR which is described below\&. .sp @@ -44,7 +44,7 @@ SVG is a vector\-based graphics format and therefore dvisvgm tries to convert th .sp However, TeX\(cqs main source for font descriptions is Metafont, which produces bitmap output (GF files)\&. That\(cqs why not all obtainable TeX fonts are available in a scalable format\&. In these cases, dvisvgm tries to vectorize Metafont\(cqs output by tracing the glyph bitmaps\&. The results are not as perfect as most (manually optimized) PFB or OTF counterparts, but are nonetheless really nice in most cases\&. .sp -When running dvisvgm without option \fB\-\-no\-fonts\fR, \fIfont\fR elements (\&...) are used to embed the font data into the SVG files\&. Unfortunately, only few SVG renderes support these elements yet\&. Most web browsers and vector graphics applications don\(cqt evaluate them properly so that the text components of the resulting graphics might look strange\&. In order to create more compatible SVG files, command\-line option \fB\-\-no\-fonts\fR can be given to replace the font elements by plain graphics paths\&. +When running dvisvgm without option \fB\-\-no\-fonts\fR, \fIfont\fR elements (\fB\fR\&...\fB\fR) are used to embed the font data into the SVG files\&. Unfortunately, only few SVG renderes support these elements yet\&. Most web browsers and vector graphics applications don\(cqt evaluate them properly so that the text components of the resulting graphics might look strange\&. In order to create more compatible SVG files, command\-line option \fB\-\-no\-fonts\fR can be given to replace the font elements by plain graphics paths\&. .SH "OPTIONS" .PP \fB\-a, \-\-trace\-all\fR=[\fIretrace\fR] @@ -71,7 +71,7 @@ forces dvisvgm to trace the corresponding bitmaps again\&. \fBNote\fR .ps -1 .br -This option only takes affect if font caching is active\&. Thus, +This option only takes effect if font caching is active\&. Therefore, \fB\-\-trace\-all\fR cannot be combined with option \fB\-\-cache=none\fR\&. @@ -185,10 +185,19 @@ to overwrite the default\&. Furthermore, it is also possible to disable the font is omitted, dvisvgm prints the path of the default cache directory together with further information about the stored fonts\&. Additionally, outdated and corrupted cache files are removed\&. .RE .PP +\fB\-j, \-\-clipjoin\fR +.RS 4 +This option tells dvisvgm to compute the intersection of clipping paths itself if necessary, and not to delegate this task to the SVG renderer\&. The resulting SVG files are more portable because some SVG renderers don\(cqt support intersections of clipping paths which are defined by +\fIclipPath\fR +elements that contain a +\fIclip\-path\fR +attribute\&. +.RE +.PP \fB\-\-color\fR .RS 4 Enables colorization of messages printed during the conversion process\&. The colors can be customized via the environment variable -DVISVGM_COLORS\&. See the ENVIRONMENT section below for further information\&. +\fBDVISVGM_COLORS\fR\&. See the ENVIRONMENT section below for further information\&. .RE .PP \fB\-E, \-\-eps\fR @@ -212,9 +221,9 @@ given, dvisvgm analyzes the actual shape of each character and derives a usually Loads and evaluates a single or multiple font map files\&. These files are required to resolve font file names and encodings\&. dvisvgm does not provide its own map files but tries to read available ones coming with dvips or dvipdfm\&. If option \fB\-\-fontmap\fR is omitted, dvisvgm looks for the default map files -ps2pk\&.map, -dvipdfm\&.map, and -psfonts\&.map +\fIps2pk\&.map\fR, +\fIdvipdfm\&.map\fR, and +\fIpsfonts\&.map\fR (in this order)\&. Otherwise, the listed files are used\&. Multiple filenames must be separated by commas without leading and/or trailing whitespace\&. The map files are evaluated in the given order\&. By default, redefined mappings do not replace previous ones\&. However, each filename can be preceded by an optional mode specifier (\fB+\fR, \fB\-\fR, or \fB=\fR) to change this behavior: @@ -238,27 +247,49 @@ If the first filename in the filename sequence is preceded by a mode specifier, Examples: \fB\-\-fontmap=myfile1\&.map,+myfile2\&.map\fR loads -myfile1\&.map +\fImyfile1\&.map\fR followed by -myfile2\&.map +\fImyfile2\&.map\fR where all redefinitions of -myfile2\&.map +\fBmyfile2\&.map\fR are ignored\&. \fB\-\-fontmap==myfile1\&.map,\-myfile2\&.map\fR loads the default map file followed by -myfile1\&.map +\fImyfile1\&.map\fR and -myfile2\&.map +\fImyfile2\&.map\fR where all redefinitions of -myfile1\&.map +\fImyfile1\&.map\fR replace previous entries\&. Afterwards, all definitions for the fonts given in -myfile2\&.map +\fImyfile2\&.map\fR are removed from the font map tree\&. .sp For further information about the map file formats and the mode specifiers, see the manuals of dvips and dvipdfm\&. .RE .RE .PP +\fB\-\-grad\-overlap\fR +.RS 4 +Tells dvisvgm to create overlapping grid segments when approximating color gradient fills (also see option +\fB\-\-grad\-segments\fR +below)\&. By default, adjacent segments don\(cqt overlap but only touch each other like separate tiles\&. Unfortunately, this alignment can lead to visible gaps between the segments because the background influences the color at the boundary of the segments if the SVG renderer uses anti\-aliasing to create smooth contours\&. One way to avoid this and to create seamlessly touching color regions is to enlarge the segments so that they extent into the area of their right and bottom neighbors\&. Since the latter are drawn on top of the overlapping parts, the visible size of all segments keeps unchanged\&. Just the former gaps disappear as the background is now completely covered by the correct colors\&. Currently, dvisvgm computes the overlapping segments separately for each patch of the mesh (a patch mesh may consist of multiple patches of the same type)\&. Therefore, there still might be visible gaps at the seam of two adjacent patches\&. +.RE +.PP +\fB\-\-grad\-segments\fR=\fInumber\fR +.RS 4 +Determines the maximal number of segments per column and row used to approximate gradient color fills\&. Since SVG 1\&.1 only supports a small subset of the shading algorithms available in PostScript, dvisvgm approximates some of them by subdividing the area to be filled into smaller, monochromatic segments\&. Each of these segments gets the average color of the region it covers\&. Thus, increasing the number of segments leads to smaller monochromatic areas and therefore results in a better approximation of the actual color gradient\&. As a drawback, more segments imply bigger SVG files because every segment is represented by a separate path element\&. +.sp +Currently, dvisvgm supports free\- and lattice\-form triangular patch meshes as well as Coons and tensor\-product patch meshes\&. They are approximated by subdividing the area of each patch into a +\fIn\fR\(mu\fIn\fR +grid of smaller segments\&. The maximal number of segments per column and row can be changed with option +\fB\-\-grad\-segments\fR\&. +.RE +.PP +\fB\-\-grad\-simplify\fR=\fIdelta\fR +.RS 4 +If the size of the segments created to approximate gradient color fills falls below the given delta value, dvisvgm reduces their level of detail\&. For example, B\('ezier curves are replaced by straight lines, and triangular segments are combined to tetragons\&. For a small delta these simplifications are usually not noticeable but reduce the size of the generated SVG files\&. +.RE +.PP \fB\-h, \-\-help\fR[=\fImode\fR] .RS 4 Prints a short summary of all available command\-line options\&. The optional @@ -276,13 +307,17 @@ Disables the removal of temporary files as created by Metafont (usually \&.gf, \ This option is only available if the Ghostscript library is not directly linked to dvisvgm and if PostScript support was not completely disabled during compilation\&. In this case, dvisvgm tries to load the shared GS library dynamically during runtime\&. By default, it expects the library\(cqs name to be libgs\&.so\&.X (on Unix\-like systems, where X is the ABI version of the library) or gsdll32\&.dll/gsdll64\&.dll (Windows)\&. Option \fB\-\-libgs\fR can be used to give a different name\&. Alternatively, it\(cqs also possible to set the GS library name by the environment variable -LIBGS\&. The latter has less precedence than the command\-line option\&. +\fBLIBGS\fR\&. The latter has less precedence than the command\-line option, i\&.e\&. dvisvgm ignores variable +\fBLIBGS\fR +if +\fB\-\-libgs\fR +is given\&. .RE .PP -\fB\-L, \-\-linkmark\fR=\fItype\fR +\fB\-L, \-\-linkmark\fR=\fIstyle\fR .RS 4 Selects the method how to mark hyperlinked areas\&. The -\fItype\fR +\fIstyle\fR argument can take one of the values \fInone\fR, \fIbox\fR, and @@ -290,18 +325,18 @@ argument can take one of the values \fIbox\fR is the default, i\&.e\&. a rectangle is drawn around the linked region if option \fB\-\-linkmark\fR -is omitted\&. Type +is omitted\&. Style argument \fIline\fR just draws the lower edge of the bounding rectangle, and \fInone\fR -tells dvisvgm not to add any visible objects to hyperlinks\&. The lines and boxes get the current text color selected\&. In order to apply a different, constant color, a colon followed by a color specifier can be appended to the type string\&. A +tells dvisvgm not to add any visible objects to hyperlinks\&. The lines and boxes get the current text color selected\&. In order to apply a different, constant color, a colon followed by a color specifier can be appended to the style string\&. A \fIcolor specifier\fR is either a hexadecimal RGB value of the form -\fI#RRGGBB\fR, or a dvips color name as listed here: -http://en\&.wikibooks\&.org/wiki/LaTeX/Colors#The_68_standard_colors_known_to_dvips +\fI#RRGGBB\fR, or a +dvips color name (\m[blue]http://en.wikibooks.org/wiki/LaTeX/Colors#The_68_standard_colors_known_to_dvips\m[])\&. .sp Moreover, argument -\fItype\fR +\fIstyle\fR can take a single color specifier to highlight the linked region by a frameless box filled with that color\&. An optional second color specifier separated by colon selects the frame color\&. .sp Examples: @@ -326,6 +361,21 @@ or Sets the magnification factor applied in conjunction with Metafont calls prior tracing the glyphs\&. The larger this value, the better the tracing results\&. Nevertheless, large magnification values can cause Metafont arithmetic errors due to number overflows\&. So, use this option with care\&. The default setting usually produces nice results\&. .RE .PP +\fB\-\-no\-merge\fR +.RS 4 +Puts every single character in a separate +\fItext\fR +element with corresponding +\fIx\fR +and +\fIy\fR +attributes\&. By default, new +\fItext\fR +or +\fItspan\fR +elements are only created if a string starts at a location that differs from the regular position defined by the characters\*(Aq advance values\&. +.RE +.PP \fB\-\-no\-mktexmf\fR .RS 4 Suppresses the generation of missing font files\&. If dvisvgm can\(cqt find a font file through the kpathsea lookup mechanism, it calls the external tools mktextfm or mktexmf by\&. This option disables these calls\&. @@ -380,13 +430,34 @@ By default, dvisvgm creates CSS styles and class attributes to reference fonts b Sets the name pattern of the output file\&. Parameter \fIpattern\fR is a string that may contain the variables +\fB%f\fR, +\fB%p\fR, and +\fB%P\fR\&. \fB%f\fR -and -\fB%p\fR\&. -\fB%f\fR -stands for the base name of the DVI file, i\&.e\&. the DVI filename without suffix, and +expands to the base name of the DVI file, i\&.e\&. the filename without suffix, +\fB%p\fR +is the current page number, and +\fB%P\fR +the total number of pages in the DVI file\&. An optional number (0\-9) given after the percent sign specifies the minimal number of digits to be written\&. If a particular value is shorter, the number is padded with leading zeros\&. Example: +\fB%3p\fR +enforces 3 digits for the current page number (001, 002, etc\&.)\&. Without an explicit width specifier, \fB%p\fR -is the current page number\&. The default pattern is +gets the same number of digits as +\fB%P\fR\&. +.sp +If you need more control over the numbering, you can use arithmetic expressions as part of a pattern\&. The syntax is +\fB%(expr)\fR +where +\fIexpr\fR +may contain additions, subtractions, multiplications, and integer divisions with common precedence\&. The variables +\fBp\fR +and +\fBP\fR +contain the current page number and the total number of pages, respectively\&. For example, +\fB\-\-output="%f\-%(p\-1)"\fR +creates filenames where the numbering starts with 0 rather than 1\&. +.sp +The default pattern is \fB%f\-%p\&.svg\fR if the DVI file consists of more than one page, and \fB%f\&.svg\fR @@ -436,6 +507,13 @@ degrees around the page center\&. This option is equivalent to \fB\-TR\fR\fIangle\fR\&. .RE .PP +\fB\-R, \-\-relative\fR +.RS 4 +SVG allows to define graphics paths by a sequence of absolute and/or relative commands, i\&.e\&. each command expects either absolute coordinates or coordinates relative to the current drawing position\&. By default, dvisvgm creates paths made up of absolute commands\&. If option +\fB\-\-relative\fR +is given, relative commands are created instead which slightly reduces the size of the SVG files in most cases\&. +.RE +.PP \fB\-s, \-\-stdout\fR .RS 4 Don\(cqt write the SVG output to a file but redirect it to @@ -595,10 +673,10 @@ Furthermore, you can use the length constants \fBcm\fR and \fBin\fR, e\&.g\&. -2cm +\fB2cm\fR or -1\&.6in\&. Thus, option -\-TT1in,0R45 +\fB1\&.6in\fR\&. Thus, option +\fB\-TT1in,0R45\fR moves the page content 1 inch to the right and rotates it by 45 degrees around the page center afterwards\&. .sp For single transformations you can also use options @@ -706,9 +784,9 @@ and \fIheight\fR attributes are omitted\&. .RE -.SH "SUPPORT OF SPECIALS" +.SH "SUPPORTED SPECIALS" .sp -dvisvgm supports several sets of \fIspecial commands\fR that can be used to enrich DVI files with additional features, like color, graphics, and hyperlinks\&. The evaluation of special commands is delegated to various handlers\&. Each handler is responsible for all special statements of the same command set, i\&.e\&. commands beginning with the same prefix\&. To get a list of actually provided special handlers, use option \fB\-\-list\-specials\fR (see above)\&. This section gives an overview of the special commands currently supported\&. +dvisvgm supports several sets of \fIspecial commands\fR that can be used to enrich DVI files with additional features, like color, graphics, and hyperlinks\&. The evaluation of special commands is delegated to dedicated handlers\&. Each handler is responsible for all special statements of the same command set, i\&.e\&. commands beginning with the same prefix\&. To get a list of actually provided special handlers, use option \fB\-\-list\-specials\fR (see above)\&. This section gives an overview of the special commands currently supported\&. .PP \fBbgcolor\fR .RS 4 @@ -726,21 +804,75 @@ dvisvgm offers its own small set of specials\&. The following list gives a brief .PP \fBdvisvgm:raw\fR \fItext\fR .RS 4 -Adds an arbitrary sequence of characters to the SVG output\&. dvisvgm does not perform any validation here, thus the user has to ensure that the resulting SVG is still valid\&. Parameter +Adds an arbitrary sequence of characters to the page section of the SVG document\&. dvisvgm does not perform any validation here, thus the user has to ensure that the resulting SVG is still valid\&. Parameter \fItext\fR -may contain the macros +may contain the expressions \fB{?x}\fR, \fB{?y}\fR, and \fB{?color}\fR -that are expanded to the current +that expand to the current \fIx\fR or \fIy\fR -coordinate and the current color, respectively\&. Also, macro +coordinate and the current color, respectively\&. Furthermore, \fB{?nl}\fR expands to a newline character\&. .RE .PP +\fBdvisvgm:rawdef\fR \fItext\fR +.RS 4 +This command is similar to +\fBdvisvgm:raw\fR, but puts the raw text into the section of the SVG document currently being generated\&. +.RE +.PP +\fBdvisvgm:rawset\fR \fIname\fR \&... \fBdvisvgm:endrawset\fR +.RS 4 +This pair of specials marks the begin and end of a definition of a named raw SVG fragment\&. All +\fBdvisvgm:raw\fR +and +\fBdvisvgm:rawdef\fR +specials enclosed by +\fBdvisvgm:rawset\fR +and +\fBdvisvgm:endrawset\fR +are not evaluated immediately but jointly stored under the given +\fIname\fR +for later use\&. Once defined, the named fragment can be referenced throughout the DVI file by +\fBdvisvgm:rawput\fR +(see below)\&. The two commands +\fBdvisvgm:rawset\fR +and +\fBdvisvgm:endrawset\fR +must not be nested, i\&.e\&. each call of +\fBdvisvgm:rawset\fR +has to be followed by a corresponding call of +\fBdvisvgm:endrawset\fR +before another +\fBdvisvgm:rawset\fR +may occur\&. Also, the identifier +\fIname\fR +must be unique throughout the DVI file\&. Using +\fBdvisvgm:rawset\fR +multiple times together with the same +\fIname\fR +leads to a warning message\&. +.RE +.PP +\fBdvisvgm:rawput\fR \fIname\fR +.RS 4 +Inserts raw SVG fragments previously stored under the given +\fIname\fR\&. dvisvgm distinguishes between fragments that were specified with +\fBdvisvgm:raw\fR +or +\fBdvisvgm:rawdef\fR, and handles them differently: It inserts all +\fBdvisvgm:raw\fR +parts every time +\fBdvisvgm:rawput\fR +is called, whereas the +\fBdvisvgm:rawdef\fR +portions go to the section of the current SVG document only once\&. +.RE +.PP \fBdvisvgm:img\fR \fIwidth\fR \fIheight\fR \fIfile\fR .RS 4 Creates an image element at the current graphic position referencing the given file\&. JPEG, PNG, and SVG images can be used here\&. However, dvisvgm does not check the file format or the file name suffix\&. The lengths @@ -819,8 +951,8 @@ These specials were introduced with the emTeX distribution by Eberhard Mattes\&. .PP \fBhtml\fR .RS 4 -The hyperref specials allow the definition of hyperlinks inside DVI files in various flavors\&. dvisvgm supports the plain HyperTeX special constructs as created with hyperref package option -\fIhypertex\fR\&. Internal links, i\&.e\&. references to other parts of the same document, are only converted if the link and the corresponding link target are located on the same page\&. Links between different pages are not supported yet\&. By default, all linked areas of the document are marked by a rectangle\&. Option +The hyperref specification defines several variants on how to mark hyperlinked areas in a DVI file\&. dvisvgm supports the plain HyperTeX special constructs as created with hyperref package option +\fIhypertex\fR\&. By default, all linked areas of the document are marked by a rectangle\&. Option \fB\-\-linkmark\fR allows to change this behavior\&. See above for further details\&. Information on syntax and semantics of the HyperTeX specials can be found in the hyperref manual\&. .RE @@ -831,25 +963,29 @@ pdfTeX and dvipdfmx introduced several special commands related to the generatio \fIpdf:mapfile\fR and \fIpdf:mapline\fR -are supported by dvisvgm\&. These specials allow modifying the font map tree during the processing of DVI files\&. They are used by CTeX, for example\&. dvisvgm supports both, the dvips and dvipdfm font map format\&. For further information on the command syntax and semantics, see the documentation of \epdfmapfile in the pdfTeX user manual\&. +are supported by dvisvgm\&. These specials allow modifying the font map tree during the processing of DVI files\&. They are used by CTeX, for example\&. dvisvgm supports both, the dvips and dvipdfm font map format\&. For further information on the command syntax and semantics, see the documentation of +\fB\epdfmapfile\fR +in the pdfTeX user manual\&. .RE .PP \fBps\fR .RS 4 -The famous DVI driver dvips introduced its own set of specials in order to embed PostScript code into DVI files, which greatly improves the capabilities of DVI documents\&. One aim of dvisvgm is to completely evaluate all PostScript snippets and to convert a large amount of it to SVG\&. However, in contrast to dvips, dvisvgm uses floating point arithmetics to compute the precise position of each graphic element, i\&.e\&. it doesn\(cqt round the coordinates\&. Therefore, the relative locations of the graphic elements may slightly differ from those computed by dvips\&. +The famous DVI driver dvips introduced its own set of specials in order to embed PostScript code into DVI files, which greatly improves the capabilities of DVI documents\&. One aim of dvisvgm is to completely evaluate all PostScript snippets and to convert as many of them as possible to SVG\&. In contrast to dvips, dvisvgm uses floating point arithmetics to compute the precise position of each graphic element, i\&.e\&. it doesn\(cqt round the coordinates\&. Therefore, the relative locations of the graphic elements may slightly differ from those computed by dvips\&. .sp -Since PostScript is a rather complex language, dvisvgm does not try to implement its own PostScript interpreter but relies on Ghostscript instead\&. If the Ghostscript library was not linked to the dvisvgm binary, it is looked up and loaded dynamically during runtime\&. In this case, dvisvgm looks for +Since PostScript is a rather complex language, dvisvgm does not try to implement its own PostScript interpreter but relies on +Ghostscript (\m[blue]http://ghostscript.com\m[]) +instead\&. If the Ghostscript library was not linked to the dvisvgm binary, it is looked up and loaded dynamically during runtime\&. In this case, dvisvgm looks for \fIlibgs\&.so\&.X\fR on Unix\-like systems (supported ABI versions: 7,8,9), and for \fIgsdll32\&.dll\fR or \fIgsdll64\&.dll\fR on Windows\&. You can override the default file names with environment variable -LIBGS +\fBLIBGS\fR or the command\-line option -\fB\-\-libgs\fR\&. The library must be reachable through the ld search path (*nix) or the PATH environment variable (Windows)\&. Alternatively, the absolute file path can be specified\&. If the library cannot be found, dvisvgm disables the processing of PostScript specials\&. Use option +\fB\-\-libgs\fR\&. The library must be reachable through the ld search path (*nix) or the PATH environment variable (Windows)\&. Alternatively, the absolute file path can be specified\&. If the library cannot be found, dvisvgm disables the processing of PostScript specials and prints a warning message\&. Use option \fB\-\-list\-specials\fR -to check whether PS support is available, i\&.e\&. entry +to check whether PostScript support is available, i\&.e\&. entry \fIps\fR is present\&. .sp @@ -916,11 +1052,11 @@ Converts the first page of \fIfile\&.dvi\fR to \fIfile\&.svg\fR where three tran .sp dvisvgm uses the \fBkpathsea\fR library for locating the files that it opens\&. Hence, the environment variables described in the library\(cqs documentation influence the converter\&. .sp -If dvisvgm was linked without the Ghostscript library, and if PostScript support has not been disabled, the shared Ghostscript library is looked up during runtime via dlopen()\&. The environment variable LIBGS can be used to specify path and file name of the library\&. +If dvisvgm was linked without the Ghostscript library, and if PostScript support has not been disabled, the shared Ghostscript library is looked up during runtime via dlopen()\&. The environment variable \fBLIBGS\fR can be used to specify path and file name of the library\&. .sp The pre\-compiled Windows versions of dvisvgm require a working installation of MiKTeX 2\&.9 or above\&. dvisvgm does not work together with the portable edition of MiKTeX because it relies on MiKTeX\(cqs COM interface only accessible in a local installation\&. To enable the evaluation of PostScript specials, the original Ghostscript DLL \fIgsdll32\&.dll\fR must be present and reachable through the search path\&. 64\-bit Windows builds require the 64\-bit Ghostscript DLL \fIgsdll64\&.dll\fR\&. Both DLLs come with the corresponding Ghostscript installers available from www\&.ghostscript\&.com\&. .sp -The environment variable DVISVGM_COLORS specifies the colors used to highlight various parts of dvisvgm\(cqs message output\&. It is only evaluated if option \fB\-\-color\fR is given\&. The value of DVISVGM_COLORS is a list of colon\-separated entries of the form \fIgg\fR=\fIBF\fR, where \fIgg\fR denotes one of the color group indicators listed below, and \fIBF\fR are two hexadecimal digits specifying the background (first digit) and foreground/text color (second digit)\&. The color values are defined as follows: 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=gray, 8=bright red, 9=bright green, A=bright yellow, B=bright blue, C=bright magenta, D=bright cyan, E=bright gray, F=white\&. Depending on the terminal, the colors may differ\&. Rather than changing both the text and background color, it\(cqs also possible to change only one of them: An asterisk (*) in place of a hexadecimal digit indicates the default text or background color of the terminal\&. +The environment variable \fBDVISVGM_COLORS\fR specifies the colors used to highlight various parts of dvisvgm\(cqs message output\&. It is only evaluated if option \fB\-\-color\fR is given\&. The value of \fBDVISVGM_COLORS\fR is a list of colon\-separated entries of the form \fIgg\fR=\fIBF\fR, where \fIgg\fR denotes one of the color group indicators listed below, and \fIBF\fR are two hexadecimal digits specifying the background (first digit) and foreground/text color (second digit)\&. The color values are defined as follows: 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=gray, 8=bright red, 9=bright green, A=bright yellow, B=bright blue, C=bright magenta, D=bright cyan, E=bright gray, F=white\&. Depending on the terminal, the colors may differ\&. Rather than changing both the text and background color, it\(cqs also possible to change only one of them: An asterisk (*) in place of a hexadecimal digit indicates the default text or background color of the terminal\&. .sp All malformed entries in the list are silently ignored\&. .TS @@ -992,7 +1128,7 @@ T} .TE .sp 1 .sp -\fBExample:\fR er=01:pi=*5 sets the colors of error messages (er) to red (1) on black (0), and those of progress indicators (pi) to cyan (5) on default background (*)\&. +\fBExample:\fR \fBer=01:pi=*5\fR sets the colors of error messages (\fBer\fR) to red (\fB1\fR) on black (\fB0\fR), and those of progress indicators (\fBpi\fR) to cyan (\fB5\fR) on default background (\fB*\fR)\&. .SH "FILES" .sp The location of the following files is determined by the kpathsea library\&. To check the actual kpathsea configuration you can use the \fBkpsewhich\fR utility\&. @@ -1079,25 +1215,19 @@ T} .PP Project home page .RS 4 -http://dvisvgm\&.sourceforge\&.net +\m[blue]\fBhttp://dvisvgm\&.sourceforge\&.net\fR\m[] .RE .PP SourceForge project site .RS 4 -http://sourceforge\&.net/projects/dvisvgm +\m[blue]\fBhttp://sourceforge\&.net/projects/dvisvgm\fR\m[] .RE .SH "BUGS" .sp -Please report bugs using the bug tracker at Launchpad (see https://launchpad\&.net/dvisvgm)\&. +Please report bugs using the bug tracker at Launchpad (\m[blue]https://launchpad.net/dvisvgm\m[]) or GitHub (\m[blue]https://github.com/mgieseki/dvisvgm\m[])\&. .SH "AUTHOR" .sp -Written by Martin Gieseking +Written by Martin Gieseking <\m[blue]\fBmartin\&.gieseking@uos\&.de\fR\m[]> .SH "COPYING" .sp -Copyright \(co 2005\-2014 Martin Gieseking\&. Free use of this software is granted under the terms of the GNU General Public License (GPL) version 3 or, (at your option) any later version\&. -.SH "AUTHOR" -.PP -\fBMartin Gieseking\fR <\&martin\&.gieseking@uos\&.de\&> -.RS 4 -Author. -.RE +Copyright \(co 2005\-2015 Martin Gieseking\&. Free use of this software is granted under the terms of the GNU General Public License (GPL) version 3 or, (at your option) any later version\&. -- cgit v1.2.3