Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 76 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       openjade [-vCegG2s] [-b encoding] [-f error_file]
                [-c catalog_sysid] [-D dir] [-a link_type]
                [-A arch] [-E max_errors] [-i entity]
                [-w warning_type] [-d dsssl_spec] [-V variable=value]
                [-t output_type] [-o output_file] [sysid...]


       openjade is an implementation of  the  ISO/IEC  10179:1996
       standard  DSSSL  language.  The  DSSSL  engine receives as
       input an SGML or XML document and transforms it into  for­
       mats like:

       * XML representation of the flow object tree.

       *  RTF  format  that  can  be  rendered  and  printed with
       Microsoft's free Word Viewer 97

       * TeX format

       * MIF  format  that  can  be  rendered  and  printed  with

       *  SGML  or  XML  format. This is used in conjunction with
       non-standard flow object classes to  generate  SGML,  thus
       allowing openjade to be used for SGML/XML transformations.

       The system identifier of the document to be  processed  is
       specified  as an argument to openjade. If this is omitted,
       standard input will be read.

       openjade determines the system identifier  for  the  DSSSL
       specification as follows:

       1. If the -d option is specified, it will use the argument
       as the system identifier.

       2. Otherwise, it will look for processing instructions  in
       the  prolog  of  the  document.  Two  kinds  of processing
       instruction are recognized:
       identifier of the DSSSL specification.

       <?dsssl sysid>

       The system identifier is the portion of the system data of
       the processing instruction following the initial name  and
       any whitespace.

       Although  the processing instruction is only recognized in
       the prolog, it need not occur in the document entity.  For
       example,  it  could  occur in a DTD. The system identifier
       will be interpreted relative to where the  the  processing
       instruction occurs.

       3.  Otherwise,  it  will  use the system identifier of the
       document with any extension changed to .dsl.

       A DSSSL specification document can contain more  than  one
       style-specification. If the system identifier of the DSSSL
       specification is followed by #id, then openjade  will  use
       the  style-specification  whose  unique  identifier is id.
       This is allowed both with the -d option and with the  pro­
       cessing instructions.

       The  DSSSL specification must be an SGML document conform­
       ing  to  the  DSSSL  architecture.  For  an  example,  see

       openjade supports the following options in addition to the
       normal OpenSP (see  onsgmls(1))  options  (note  that  all
       options  are  case-sensitive,  ie  -g and -G are different

       -d dsssl_spec
              This specifies that dsssl_spec is the system  iden­
              tifier of the DSSSL specification to be used.

       -G     Debug  mode. When an error occurs in the evaluation
              of an expression, openjade  will  display  a  stack
              trace.  Note that this disables tail-call optimiza­

       -t output_type
              output_type  specifies  the  type of output as fol­

              fot  An XML representation of the flow object tree

              rtf rtf-95  RTF (used for SGML/XML to RTF transfor­
              mations)  Microsoft's Rich Text Format. rtf-95 pro­
              duces output optimized for Word 95 rather than Word

              tex TeX (used for SGML/XML to TeX transformations)

              sgml  sgml-raw  SGML  (used  for  SGML/XML  to SGML
              transformations). sgml-raw doesn't emit  linebreaks
              in tags.

              xml xml-raw XML (used for SGML/XML to XML transfor­
              mations). xml-raw doesn't emit linebreaks in  tags.

              html   HTML  (used for SGML/XML to HTML transforma­

              mif MIF (used for SGML/XML to MIF transformations)

       -o output_file
              Write output to output_file instead of the default.
              The  default filename is the name of the last input
              file with its extension replaced by the name of the
              type of output. If there is no input filename, then
              the extension is added onto jade-out.

       -V variable
              This is equivalent to doing  (define  variable  #t)
              except that this definition will take priority over
              any definition of variable in a style-sheet.

       -V variable=value
              This  is  equivalent  to  doing  (define   variable
              "value") except that this definition will take pri­
              ority over any definition of variable in  a  style-

       -V (define variable value)
              This is equivalent to doing (define variable value)
              except that this definition will take priority over
              any  definition  of variable in a style-sheet. Note

              sgmldecl Warn about various  dubious  constructions
              in the SGML declaration.

              should  Warn  about various recommendations made in
              ISO 8879 that the document does  not  comply  with.
              (Recommendations  are expressed with ``should'', as
              distinct  from  requirements  which   are   usually
              expressed with ``shall''.)

              default Warn about defaulted references.

              duplicate Warn about duplicate entity declarations.

              undefined Warn about undefined  elements:  elements
              used in the DTD but not defined.

              unclosed Warn about unclosed start and end-tags.

              empty Warn about empty start and end-tags.

              net  Warn  about  net-enabling  start-tags and null

              min-tag Warn about minimized  start  and  end-tags.
              Equivalent  to  combination  of unclosed, empty and
              net warnings.

              unused-map Warn about unused short reference  maps:
              maps  that are declared with a short reference map­
              ping declaration but never used in a  short  refer­
              ence use declaration in the DTD.

              unused-param Warn about parameter entities that are
              defined but not used  in  a  DTD.  Unused  internal
              parameter  entities whose text is INCLUDE or IGNORE
              won't get the warning.

              notation-sysid Warn about notations  for  which  no
              system identifier could be generated.

              all  Warn  about  conditions that should usually be
              avoided (in the opinion of the author).  Equivalent
              to:  mixed,  should,  default, undefined, sgmldecl,
              unused-map, unused-param, empty and unclosed.

              A warning can be disabled by using  its  name  pre­
              fixed  with  no-.  Thus  -wall  -wno-duplicate will
              enable all warnings except  those  about  duplicate
              entity declarations.

              The   following  values  for  warning_type  disable
              valid. This has the effect  of  changing  the  SGML
              declaration to specify VALIDITY NOASSERT and IMPLY­
              DEF ATTLIST YES ELEMENT YES. An option  of  -wvalid
              has  the effect of changing the SGML declaration to
              specify VALIDITY TYPE and IMPLYDEF ATTLIST NO  ELE­
              MENT  NO.  If  neither  -wvalid  nor -wno-valid are
              specified, then the VALIDITY and IMPLYDEF specified
              in the SGML declaration will be used.


       OpenJade   ignores   the   SP_CHARSET_FIXED   and  SP_SYS­
       TEM_CHARSET environment variables and always uses  Unicode
       as  its internal character set, as if SP_CHARSET_FIXED was
       1 and SP_SYSTEM_CHARSET was unset. Thus only the SP_ENCOD­
       ING  environment  variable  is relevant to OpenJade's han­
       dling of character sets.


       The following external  procedures  are  available.  These
       external procedures are defined by a prototype in the same
       manner as in the standard. To use one  of  these  external
       procedures,  you  must  make use of the standard external-
       procedure procedure, using a public identifier of  "UNREG­
       ISTERED::James  Clark//Procedure::name"  where name is the
       name given here, typically by including the  following  in
       the DSSSL specification:

       (define   name   (external-procedure  "UNREGISTERED::James

       Note that external-procedure returns #f if it doesn't know
       about the specified public identifier. You can use this to
       enable your DSSSL specifications to work  gracefully  with
       other  implementations  which  do not support these exten­

       For external procedures added by the OpenJade team, use  a
       public   identifier   of   the  form  "UNREGISTERED::Open­

       An easy way to get access to all external procedures is to
       use  the  style  specification dsssl/extensions.dsl#proce­
       dures. The file dsssl/extensions.dsl also  contains  style
       specifications  which  make  the  nonstandard  flow object
       classes and inherited  characteristics  supported  by  the
       backends available in a convenient way.

       (if-first-page sosofo1 sosofo2)

       This can be used only in the specification of the value of
       one  of  the header/footer characteristics of simple-page-
       sequence. It returns a sosofo that will display as sosofo1
       if  the page is the first page of the simple-page-sequence
       and as sosofo2 otherwise.

       (if-front-page sosofo1 sosofo2)

       This can be used only in the specification of the value of
       one  of  the header/footer characteristics of simple-page-
       sequence. It returns a sosofo that will display as sosofo1
       if  the  page is a front (ie recto, odd-numbered) page and
       as sosofo2 if it is a back (ie verso, even-numbered) page.



       (all-element-number osnl)

       This  is  the same as element-number except it counts ele­
       ments with any generic identifier. If osnl is not an  ele­
       ment  returns  #f,  otherwise returns 1 plus the number of
       elements that started before osnl. This provides an  effi­
       cient  way of creating a unique identifier for any element
       in a document.

       External entity access

       (read-entity string)

       This returns a  string  containing  the  contents  of  the
       external entity with system identifier string. This should
       be used only for textual entities (CDATA and  SDATA),  and
       not for binary entities (NDATA).

       POSIX locale access

       Extended standard procedures

       (sgml-parse sysid #!key active: parent: architecture:)

       This  allows  you  to  specify  an  SGML architecture with
       respect to which the document should be parsed. It  is  an
       OpenJade addition.

       (expt q k)

       This  allows you to raise a quantity to an integral power.
       It is an OpenJade addition.


       This section describes the limitations  of  the  front-end
       (the  general-purpose DSSSL engine); each backend also has
       its own limitations.

       openjade doesn't allow internal definitions at the  begin­
       ning of bodies and the (test => recipient) variant of cond

       openjade supports only a single, fixed  grove  plan  which
       comprises the following modules:

       * baseabs

       * prlgabs0

       * prlgabs1

       * instabs

       * basesds0

       * instsds0

       * subdcabs

       Character/glyph handling

       It  only  supports  a  single pre-defined character reper­
       toire. A character name of the form U-XXXX where XXXX  are
       four  upper-case  hexadecimal  digits,  is  recognized  as
       referring to the Unicode character  with  that  code.  For
       many  characters,  it  is also possible to use the ISO/IEC
       10646 name in lower-case with words separated by  hyphens.

       Some  common  SDATA  entity names from the ISO entity sets
       are recognized and mapped to characters.  In  addition  an
       SDATA  entity name of the form U-XXXX, where XXXX are four
       upper-case hexadecimal digits, is mapped  to  the  Unicode
       character with that code.

       OpenJade   now  supports  the  standard-chars,  map-sdata-
       entity,  add-name-chars,  add-separator-chars  and   char-
       repertoire  declaration  element  forms, allowing a style-
       sheet to define additional character names,  sdata  entity
       mappings,  name  characters  (i.e.  characters  allowed in
       identifiers) and separator characters. Currently the  only
       recognized  character  repertoire  is  the built-in reper­
       toire. It has the public  identifier  "UNREGISTERED::Open­
       Jade//Character Repertoire::OpenJade".


       Several  things that it would be desirable to have checked
       aren't checked:

       * When the allowed value of an inherited characteristic is
       a  symbol, OpenJade checks only that the value is a symbol
       that is allowed as the value of  some  characteristic;  #t
       and  #f  are  treated  as a special kind of symbol in this

       * OpenJade doesn't check whether a flow object  is  occur­
       ring in a context where it is allowed.

       * OpenJade does not prevent flow objects being attached to
       the principal port of a flow object when the  flow  object
       shouldn't have a principal port.

       The following primitives are just stubs:

       char-script-case Always returns last argument.

       address-visited? Always returns #f.


       Given an SGML file file.sgml, use the stylesheet  file.dsl
       and publish as an rtf file.

       openjade -t rtf file.sgml

       Using a different stylesheet:

       openjade -t rtf -d docbook.dsl file.sgml

       Using  the  print style specification contained within the

       openjade -t rtf -d docbook.dsl#print file.sgml

       And use the html specification within the style  sheet  to
       convert to html

       openjade -t sgml -i html -d docbook.dsl#html file.sgml




       James Clark, Ian Castle <ian.castle@looksystems.co.uk>.

OpenJade                   January 2002               OPENJADE(1)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =




Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds