How to specify fontmap in ghospcl - ghostscript

In ghostcript, you can use the -FONTMAP option to specify your font file. Is there such a possibility in ghostpcl. This option does not work. I am using ghostpcl 9.52 for Windows x64.
Thank you so much in advance!

There is no fontmap for GhostPCL. The fontmap in Ghostscript is actually written in PostScript, so it can't work with GhostPCL.
For GhostPCL you get the standard fonts (which are not AGPL-compatible), everything else needs to be downloaded as part of the PCL.

Related

Configure Ghostscript to work with "MT Extra" font

I'm using MathType to write mathematical expressions, which uses "MT Extra" font to do some extra symbols. MathType saves the equation in a .eps format, which I want to add to a Scribus document as an image.
Exporting to .pdf with "embed .eps files" option doesn't show the extra symbols written with the MT Extra font. Since Scribus works with Ghostscript, I believe I have to configure ghostscript to use MT Extra font. Am I right? How can I do that?
ThankYou for your time.
Thank you for your answer, #KenS. I'm using Windows. The font is embed, but I really can't understand (reading the ghostscript documentation) how to use the -I switch on ghostscript command line to include the font path. When I use GSView I can configure it in "Advanced configure" (using -sFONTPATH=c:\windows\fonts), and the .eps looks ok, but it doesn't change the behaviour of ghostscript when I insert the .eps into Scribus (and ghostscript is configured to be the ps interpreter). I don't know how to tell directly to ghostscript to include the fontpath. I'm sorry to ask you again, #KenS, and thank you again for your time.
If the font is embedded in the EPS file, then you don't need to do anything. If they are not then you should get a warning from Ghostscript that a font can't be found and a substitute is being used. If you get that warning then you need to add the font, otherwise you don't. Its poor practice not to embed fconts though.
Adding fonts to Ghostscript is documented in ghostpdl/gs/doc/Fonts.htm See Section 7 in particular.
Assuming you are on Linux you may, or may not, have a ROM file system, depending on how your distribution has chosen to package Ghostscript. If you are using a ROM file system then you will I think need to use the -I switch to include different font paths (again there is documentation on this). If you are not using a ROM file system, or the package already includes fonts on disk then its only necessary to follow the steps described in the documentation.

How to run GhostScript on AS400 server

We have PDF files on the AS/400 and we need to convert them to PCL for printing . So for this we found Ghostscript for converting PDF file to PCL format , so we're looking for a way to run Ghostscript commands on the AS/400.
Have you please any idea how to do it , if no I am looking for another "free" method to do what we need.
Any help will be appreciated
Ghostscript doesn't accept PCL as input, you need Ghostpdl for that, and more specifically the pcl6 executable.
You can't 'run Ghostscript commands' you can run the executable with the PCL file as an input and suitable command line switches.
In order to do this you will need to compile Ghostscript for your target environment (AS/400 apparently). Ghostscript is written in standard C so you will need a C compiler, the build process is convoluted and requires running a number of executables in order to generate some platform specific files.
Your first task is going to be porting Ghostscript and its build process onto your target platform. I'm not aware of anyone having done this for AS/400 but we'd be interested to hear how you get on.

Tlib.exe (Borland / Embarcadero) doesn't handle paths properly that contain hifen-minus symbols, what can I do?

When I try to execute something similar to this line below:
tlib.exe /C mylib.lib
+-obj\Release\lib-10\src\object\objectFile.obj
I get this output:
TLIB 6.2 Copyright (c) 1987-2010 Embarcadero Technologies, Inc.
Warning: '.\obj\Release\objectFile.obj' not found in library
If I remove the "lib-10" manually and put the objectFile.obj at the "obj\Release\src\object\" dir it works fine.
What can I do?
At the website there are no useful information about this. If there is no workaroud I will try this manual solution. Just to clarify: tlib.exe is my only choice.
Thanks
Recent versions of Tlib will handle properly quoted paths with -/+ on the command line, but older versions do not. If the IDE or your shell isn't properly quoting these paths, your best bet is to use a different path.
I would discourage use of paths containing those characters. I know it's a remnant of times past, but many console applications grew out of those legacy times and still have the old constraints.

Routine for compressing folders in Visual studio

I am trying to write a routine that compress folder/multiple files for Embedded applications in Visual studio.For that I thought of using combination of zlib and tar.I could successfully run the zlib in visual studio but in case of tar the source code refers to some linux headers and results in error.I am a newbie in this area.Could any one tell me how to create the routine.I found a UnxUtils (sourceforge, GNU utilities for Win32 http://unxutils.sourceforge.net.) while browsing,Is that useful? Any help is appreciated.
You might also look at DotNetZip library, as it may work in your situation.
Quote:
Is this thing supported on Mono/Linux?
It's not supported at all. But, it apparently works on Mono/Ubuntu. I don't test it that way. If you'd like to volunteer, let me know.

Create BOM (bill-of-material) file on Windows

I have to create (or rather modify) software package for MacOSX on Windows. I can do what I need with .pax files, so the only thing left is bill-of-material.
Does anyone know of a library that can do it? Is there BOM file format (Apple-version) available?
TIA
There is now an open source version of mkbom which also compiles for windows at:
http://hogliux.github.io/bomutils/
The windows version still contains some bugs (no special characters in file names and limitations on file path length). However, it should work for simple installers.
The website also has an easy to follow step-by-step tutorial on how to create a Mac OS X installer (however, the tutorial is for linux, see http://hogliux.github.io/bomutils/tutorial.html ).
Well, BOM is not necessary, MacOSX package is a simple directory structure with optional elements, BOM being one of them.

Resources