Différences

Ci-dessous, les différences entre deux révisions de la page.

--- fichiers:xml:convertir_du_html_en_latex2 [2018/06/03 15:09] – joseph.wright
+++ 5_fichiers:xml:convertir_du_html_en_latex2 [2023/03/05 20:52] (Version actuelle) – Remise en forme de la page. Ajout de liens. jejust
@@ Ligne 1: / Ligne 1: @@
----
+====== Conversion from SGML or HTML to TeX ======
-title: Conversion from SGML or HTML to TeX
-category: misc
-permalink: /FAQ-SGML2TeX
-redirect_from: /FAQ-sgml2tex
----
 SGML is a very important system for document storage and interchange,
 but it has no formatting features; its companion ISO standard
-DSSSL
+DSSSL (see [[http://www.jclark.com/dsssl/]]) is designed for writing
-(see <http://www.jclark.com/dsssl/>) is designed for writing
 transformations and formatting,
-but this has not yet been widely implemented. Some SGML authoring
+but this has not yet been widely implemented. Some SGML authoring systems
-systems (e.g., SoftQuad `Author/Editor`) have formatting
+(//e.g.// [[wp>SoftQuad_Software|SoftQuad]] ''Author/Editor'') have formatting abilities,
-abilities, and
+and there are high-end specialist SGML typesetting systems (//e.g.// [[https://www.miles33.com/|Miles33]]'s
-there are high-end specialist SGML typesetting systems (e.g., Miles33's
+''Genera'').  However, the majority of SGML users probably transform
-`Genera`).  However, the majority of SGML users probably transform
 the source to an existing typesetting system when they want to print.
-TeX is a good candidate for this. There are three approaches to writing a
+TeX is a good candidate for this.
-translator:
+There are three approaches to writing a translator:
+  - Write a free-standing translator in the traditional way, with tools like ''yacc'' and ''lex''; this is hard, in practice, because of the complexity of SGML.
+  - Use a specialist language designed for SGML transformations; the best known are probably [[wp>OmniMark≤|Omnimark]] and [[https://en-academic.com/dic.nsf/enwiki/2668749|Balise]]. They are expensive, but powerful, incorporating SGML query and transformation abilities as well as simple translation.
+  - Build a translator on top of an existing SGML parser.  By far the best-known (and free!) parser is James Clark's ''nsgmls'', and this produces a much simpler output format, called ESIS, which can be parsed quite straightforwardly (one also has the benefit of an SGML parse against the DTD). Two good public domain packages use this method:
+    * David Megginson's [[http://www.perl.com/CPAN/modules/by-module/SGMLS|''sgmlspm'']], written in Perl 5.
+    * Joachim Schrod and Christine Detig's [[ftp://ftp.tu-darmstadt.de/pub/text/sgml/stil|''STIL'']], ("SGML Transformations in Lisp").
+Both of these allow the user to write "handlers" for every SGML element, with plenty of access to attributes, entities, and information about the context within the document tree.
-.  Write a free-standing translator in the traditional way, with
+If these packages don't meet your needs for an average SGML typesetting job,
-    tools like `yacc` and `lex`; this is hard, in
+you need the big commercial stuff.
-    practice, because of the complexity of SGML.
-.  Use a specialist language designed for SGML transformations; the
-    best known are probably `Omnimark` and `Balise`.
-    They are expensive, but powerful, incorporating SGML query and
-    transformation abilities as well as simple translation.
-.  Build a translator on top of an existing SGML parser.  By far
-    the best-known (and free!) parser is James Clark's
-    `nsgmls`, and this produces a much simpler output format,
-    called ESIS, which can be parsed quite straightforwardly (one also
-    has the benefit of an SGML parse against the DTD). Two
-    good public domain packages use this method:
-. David Megginson's
-       [`sgmlspm`](http://www.perl.com/CPAN/modules/by-module/SGMLS),
-        written in `Perl` 5.
-. Joachim Schrod and Christine Detig's
-        [`STIL`](ftp://ftp.tu-darmstadt.de/pub/text/sgml/stil),
-         ("SGML Transformations in Lisp").
-    Both of these allow the user to write "handlers" for every SGML
-    element, with plenty of access to attributes, entities, and
-    information about the context within the document tree.
-    If these packages don't meet your needs for an average SGML
-    typesetting job, you need the big commercial stuff.
 Since HTML is simply an example of SGML, we do not need a specific
-system for HTML.  However, Nathan Torkington developed
+system for HTML.  However, Nathan Torkington developed ''html2latex''
-`html2latex` from the HTML parser in NCSA's
+from the HTML parser in NCSA's Xmosaic package.
-Xmosaic package.
 The program takes an HTML file and generates a LaTeX file from it.
 The conversion code is subject to NCSA restrictions, but the whole
 source is available on CTAN.
-Michel Goossens and Janne Saarela published a very useful summary of
+Michel Goossens and Janne Saarela published a [[https://tug.org/TUGboat/tb16-2/tb47goo1.pdf|very useful summary of SGML]],
-SGML, and of public domain tools for writing and manipulating it, in
+and of public domain tools for writing and manipulating it, in [[https://tug.org/tugboat/Contents/contents16-2.html|TUGboat 16(2), June 1995]].
-TUGboat 16(2).
+-----
+//Source:// [[faquk>FAQ-SGML2TeX|Conversion from SGML or HTML to TeX]]
+{{htmlmetatags>metatag-keywords=(LaTeX,conversion, document XML, langage structuré)
+metatag-og:title=(Conversion from SGML or HTML to TeX)
+metatag-og:site_name=(FAQ LaTeX francophone)
+}}