PrettyPrinter

What is pretty printed?

The PrettyPrinter is able to read CR files version 2.1 and 2.0, and generates an SDL/PR representation. Layout information from the syntax oriented editor are not supported, i.e. the layout is comuted from scratch. ASN.1 inclusions (in SITE text between asntype and endasntype) may be printed conform to Z.105. Note, the automatic transformation of SDL expressions is not possible.

Back to the start

Wich formats are supported?

The PrettyPrinter can print the following formats:

SDL/PR ASCII text
HTML
PostScript
LaTeX

If the target formats are able to support it, the following layout information are used:

keyword are printed bold,
strings are set in typewriter,
commentare are emphisized,
there is an automatic indention,
left shifting if if the indention level becames to large,
there is no automatic libe break, some target formats or viewer break lines themself, however.

There are a lot of options to switch special layout parameters.

Back to the start

How th output can be changed?

The output can be changed by modification of the source code. Two files are important:

pretty.k: This file contains the unparse rules, how the CR nodes are represented as ASCII. Lexical elements are printed with special functions, same for indensions and diferences between Z.100 and Z.105.
printer.k: Here are all lecem specific functions, which intregrates depending on the output format additional information into the output stream. The printer function itself is a Kimwitu typical printer function

For changes or new formats you have to modify the lexem specific functions and to introduce corresponding format flags. Hints and sources are wellcome!

Some sources are functional overloaded (yet). The functionality is given by other SITE components. However, an html Pretty Printer with reference resolution need that., see it as an investment for the future development.

Back to the start

Wich errors are known?

Some special comments are not printed. This is importand for further paring of the generated sources. The Z.105 output has language specific problems:

There are new keywords. The automatic renaiming can cause conflicts.
Z.105 is case insensitiv, i.e. name conflicts are possible in ASN.1 context.
SITE allows expressions (. x,,y .) to manage optional fields in SDL user friendly. These expressions has to be transformed to { ... } by the user, itself.
Z.105 output is not well tested.

Back to the start

Were are the sources?

The sources are on the ftp server. Note, there are the general restrictions of the SITE components. New ideas or other implementations are wellcome!

Back to the start

Can referenced be resolved with the Pretty Printer?

No! But the semantical analysis resolves <referenced definition>s and is able to print this CR on request. Such a CR file can be pretty printed, the SDL/PR specification does not contain external packages and <referenced definition>s .

Back to the start

created 05-May-1997 by SITE maintenance crew
last change at Di Mai 4 11:44:49 CEST 2004