🚀 go-pugleaf

>.right now we are trying to understand what is been written in those programs and trying to reengineer them with latest programming language. 

PostScript has not changed, the PostScript doesn't need updating
unless it is badly written (which you probably aren't yet in a
position to judge) or doesn't do it's job any longer.

> or are there any tools which can convert them to a popular language or any debugger to understand the code.

There is a debugger for PostScript. My company sells it, in fact. It
is limited to level 2 PostScript, but the chances are 10 year old code
will be level 2.

Some useful background on PostScript
* PostScript is a programming language understood by some printers
* 99.99% of PostScript files are not written by programmers, but
automatically written by software such as print drivers.

I am interested in your idea of "converting to a popular language".
PostScript is a programming language, certainly, but one with a
special purpose. It is the language understood by PostScript printers.

So, in a typical scenario, this PostScript is understood by your
printer(s). Your printer probably doesn't understand anything else, so
conversion isn't an option.

Conversion to PDF is a possibility, if that is more helpful for you.
PDF is designed for both viewing on screen and printing but note the
following:
* PDF is NOT a language, but a graphical file format
* You do not edit PDF files, So you would still absolutely want to
keep the PostScript, and learn PostScript, for any future changes.
Think of them as the raw and compiled program, source code and exe, if
that helps.
* PDF files are generated from PostScript automatically using Acrobat
Distiller.

If this doesn't point you in the right direction for your project, it
would probably be best to discuss the purpose of the files: what is
done with these PostScript files in your workflow, in your
organisation?


Aandi Inston