Note: If you installed these packages using your
OS vendors package management
software make sure the header files... are also installed.
Some systems have separated packages: one for binaries and shared libraries
and an additional one (mostly called "xxx developer support")
containing C header files and other material needed to compile programs
using the library.
The source code is available at http://sourceforge.net/projects/fig2vect.
The usual procedure
./configure make make install
can be used to install the software.
If it is possible for you to copy the GhostScript fonts from the GhostScript source package to a directory on a web server, provide the ``--with-fontbase'' option to configure:
./configure --with-fontbase=http://my-server.my-domain.com/gs-fontsSo if you use the Java output driver to create classes implementing the java.awt.Printable interface these applications can retrieve the fonts from your server, you don't need to package them into the *.jar file.
The dklibs-win32 package of the dklibs SourceForge project at
http://sourceforge.net/projects/dklibs
contains the executable files
dklibs-win32-user-*.exe and dklibs-win32-base-*.exe.
The dklibs-win32-user-*.exe file is the recommended setup, it installs
binaries and documentation to the local hard disk. The dklibs-win32-base-*.exe
file only installs the binaries, start menu entries for documentation will
point to web resources. This is recommended only for computers connected
to the internet permanently.
This is possible, of course. Good skills in using your development environment, C compiler linker and make program are required. The file http://dklibs.sourceforge.net/inst_w32.html a detailed description how to build the dklibs and dklibs-based software like fig2vect from source on Windows systems.
Fig2vect version 1.1.7 (and above) provides support for UTF-8 encoded
texts in Fig files.
By default fig2vect inspects the LANG environment variable, if it ends
on ``.UTF-8'' UTF-8 support is enabled, otherwise it is disabled.
This default setting is ok for users using XFig but not for jFig.
JFig -- or one of the libraries it uses -- is UTF-8-aware and
converts UTF-8 encoded data
from keyboard events into an internal representation and saves text
in Fig files not UTF-8 encoded. So fig2vect must not UTF-8-decode
the text again.
There are different ways to change the default setting:
[*/fig2vect] /utf-8 = noor
[*/fig2vect] /utf-8 = yesto the $sysconfdir/appdefaults file
[fig2vect] /utf-8 = noor
[fig2vect] /utf-8 = yesto the $HOME/.defaults/all file.
When running fig2vect you can override the default setting specifying the ``-o utf-8=yes'' or ``-o utf-8=no'' command line options to fig2vect.
The fig2vect installation process does not overwrite an existing fig2vect.cfg file
(you may have edited it). Some fig2vect updates may introduce new default configurations
in section 1 of the configuration file.
So after upgrading fig2vect you should manually edit the per-machine file fig2vect.cfg
and transfer section 1 from the fig2vect.cfg file in the source distribution into
your existing version of the configuration file.