LaTeX/Introduction - Historique des versions

Nicolas Brouard : /* Open Type font */

2011-05-31T19:17:46Z

‎Open Type font

Nicolas Brouard : /* Open Type font */ otfinfo link (to be explored)

2011-05-31T19:05:38Z

‎Open Type font : otfinfo link (to be explored)

Nicolas Brouard : /* Emacs headers */ polyglossia for xetex instead of babel

2011-05-30T20:21:51Z

‎Emacs headers : polyglossia for xetex instead of babel

Nicolas Brouard : /* Which packages or classes should I use? */

2011-05-29T21:57:57Z

‎Which packages or classes should I use?

Nicolas Brouard : /* Computer modern or OT1 fonts */

2011-05-29T20:56:12Z

‎Computer modern or OT1 fonts

Nicolas Brouard : /* Headers */

2011-05-29T20:47:40Z

‎Headers

Nicolas Brouard : /* Emacs headers */

2011-05-28T18:38:16Z

‎Emacs headers

Nicolas Brouard le 28 mai 2011 à 15:48

2011-05-28T15:48:35Z

Nicolas Brouard : /* TeXWorks headers */ Confusion between engine and formats

2011-05-28T12:37:55Z

‎TeXWorks headers : Confusion between engine and formats

Nicolas Brouard : /* Which TeX engine should I choose? */ Both headers

2011-05-28T12:30:15Z

‎Which TeX engine should I choose? : Both headers

@@ Ligne 258 : / Ligne 258 : @@
 OpenType fonts contain both the screen and printer font data in a single component. The OpenType format can contain either TrueType or PostScript font data. It supports expanded character sets (up to 65.000) and special typographic features. Tese may include various versions of figures (tabular, old-style, lining), small caps, ligatures, ordinals, and other extras. While OpenType allows type designers to build complex fonts, not many fonts take advantage of these possibilities. Most OpenType fonts available today are simply converted PostScript fonts, limited to 220 characters in a set.
-OpenType fonts are platform independent and can thus be used on all operating systems. Here is a link to a recent explanation on how to implement specific OpenType fonts ( http://members.fortunecity.com/odradek5/otf-LaTeX ).
+OpenType fonts are platform independent and can thus be used on all operating systems. Here are links to a recent explanation on OpentType fonts (http://xml.web.cern.ch/XML/lgc2/xetexmain.pdf) and how to implement them on LaTeX ( http://members.fortunecity.com/odradek5/otf-LaTeX ).
 == Which encoding system should I use ==

@@ Ligne 258 : / Ligne 258 : @@
 OpenType fonts contain both the screen and printer font data in a single component. The OpenType format can contain either TrueType or PostScript font data. It supports expanded character sets (up to 65.000) and special typographic features. Tese may include various versions of figures (tabular, old-style, lining), small caps, ligatures, ordinals, and other extras. While OpenType allows type designers to build complex fonts, not many fonts take advantage of these possibilities. Most OpenType fonts available today are simply converted PostScript fonts, limited to 220 characters in a set.
-OpenType fonts are platform independent and can thus be used on all operating systems.
+OpenType fonts are platform independent and can thus be used on all operating systems. Here is a link to a recent explanation on how to implement specific OpenType fonts ( http://members.fortunecity.com/odradek5/otf-LaTeX ).
 == Which encoding system should I use ==

@@ Ligne 135 : / Ligne 135 : @@
 % !TEX encoding = UTF-8 Unicode
 \documentclass{memoir}
 </source>

@@ Ligne 272 : / Ligne 272 : @@
 == Which packages or classes should I use?==
-Once you choose LaTeX (and a TeX engine of your choice to compile your source text), you have to make a choice within the classes offered by LaTeX, depending on the class of your text: a book, a report, an article, a presentation, you will alter the first line of your document with a command such as <tt>\documentclass{article}</tt> for an article. If you use a figure using PGF/Tikz TeX code, you need a second command <tt>\usepackage{pgf,tikz}</tt> .
+=== Coding and fonts packages ===
 A package is also a set of macros. Even if computers are 10,000 more powerful than when running on DOS in the mid 80's, they are still very limited in speed and memory management and you can't load all the macros of the CTAN TeX public Library. That the main reason of using packages.

@@ Ligne 237 : / Ligne 237 : @@
 Donald Knuth created around 1978 the so-called Computer Modern fonts (CM fonts or OT1) which make the look of TeX documents so special and easily recognizable. The memory of the first mainframes was tiny and for example, the glyphs <, >, \, {, and } are only available in the typewriter fonts and the $ and £ signs share the same position (in different font shapes). Typing a < in a document can yield ‘¿’ depending on the current font used. The OT1 fonts (O for old, T for text, 1 for Western languages) contain only 128 characters.
-With the availability of 8 bits characters (ISO8859-1 or Latin 1) in mid 80's, Tex Users designed during the Cork Tug conference the T1 fonts which includes most of Western accented characters (including the French `œ' which had been suppressed from earlier version of 8 bits characters by a non-French speaking Belgian replacing the French representative at the ISO conference). The French `œ' has been included lately in the ISO-8859-15 character set (2001). The OT2 as well as T2 are for the cyrillic characters (see [http://mirrors.ircam.fr/pub/CTAN/macros/latex/doc/encguide.pdf] for example). But you can't mix both characters in a text without indicating that you are changing the font. This is no more true with Unicode characters and XeTeX or LuaTeX.
+With the availability of 8 bits characters (ISO8859-1 or Latin 1) in mid 80's, Tex users designed during the Cork TUG conference the T1 fonts which include most of Western accented characters (even the French `œ' which had been suppressed from earlier version of 8 bits characters made by DIGITAL on VT220 terminals). The French `œ' has been included lately in the ISO-8859-15 character set (2001). The OT2 as well as T2 are for the Cyrillic characters (see [http://mirrors.ircam.fr/pub/CTAN/macros/latex/doc/encguide.pdf] for example). But you can't mix both characters in a text without indicating that you are changing the font. This is no more true with Unicode characters and XeTeX or LuaTeX.
 ===PostScript Type 1 font ===

@@ Ligne 71 : / Ligne 71 : @@
 In order to let you know which TeX engine you are using for a text, some editors are recognizing header comments that are on top of the text.
-== Headers ==
+=== Headers comments to help determining TeX engine ===
-=== TeXShop headers ===
+==== TeXShop headers ====
 For example TeXShop (as well as TeXWorks) lets you include:
 <source lang=latex>
@@ Ligne 84 : / Ligne 84 : @@
 In order to simplify (does it?) there is a confusion between the TeX engine to be used (here xetex) and the format (here LaTeX) and the TS-program specifies <tt>xelatex</tt>.
-=== TeXWorks headers ===
+==== TeXWorks headers ====
 TeXWorks 4.0 (April 2011), the successor of TeXShop, lets you have similar headers which tell the editor how to typeset the text, which encoding is used, which default language to use for the spell checker as well as which file is the ''master'' file when your report or thesis is split in parts or chapters belonging to different files which are included at compile time by the master file: the compilation is applied to the master file and not the current file.
@@ Ligne 97 : / Ligne 97 : @@
 </source>
-=== Emacs headers ===
+==== Emacs headers ====
 For another kind of editor, the emacs family, it is different:
 <source lang=latex>

@@ Ligne 121 : / Ligne 121 : @@
-Fortunately, if you include both kind of headers in your text, emacs mode first and texworks as second, it may work for both kinds of editors.
+Fortunately, if you include both kinds of headers in your text, emacs mode first and texworks as second, it may work for both editors.
 <source lang=latex>
 %%% Local Variables:
 %%% TeX-engine: xetex
@@ Ligne 128 : / Ligne 130 : @@
 %%% End:
-% These lines tell TeXShop to typeset with xelatex, and to open and
+% These lines tell TeXworks to typeset with xelatex, and to open and
 % save the source with Unicode encoding.
-%!TEX TS-program = xelatex
+% !TEX program = xelatex
-%!TEX encoding = UTF-8 Unicode
+% !TEX encoding = UTF-8 Unicode
 \documentclass{memoir}
 </source>

@@ Ligne 34 : / Ligne 34 : @@
 The Literate Programming concept is not over and Sweave is a nice way to incorporate some R (the ancestor of R was named S) code within your LaTeX document.
-== Four TeX engines ==
+== Which TeX engine should I choose amongst at least three TeX engines ==
-===TeX82 or tex===
 TeX82, the first TeX engine, was only able to read ASCII characters and did run only on mainframes like the[[Wikipedia:en:PDP-10|PDP-10]] (36 bits) at Stanford or IBM (32 bits) at the Faculty of Orsay, and then on Vax machines. TeX evolved and has been ported to PC (16 bits) with a commercial very efficient product PCTeX and, in 1990, the first Public Domain distribution of TeX and LaTeX has been built by the French Gutenberg association (see http://www.tug.org/TUGboat/tb11-1/tb27brouard.pdf). Despite efforts to make TeX able to read accented characters, the standard TeX engine produce a DVI (device independent) format which is based only on single byte (ASCII) characters even if the fonts used can display any character. A standard DVI file even transformed to PDF (with dvipdf) is therefore unsearchable for accented characters. For example, you can search for Jacques Vallin in the previous PDF document but you can't search (neither copy and paste correctly) for his sentence
 :''Éberluée, décontenancée, hébétée, défaite de toute sérénité devant cet abécédaire décapité, étêté, évidé, émasculé, désagrégé, débilité, dégénéré, parce que privé de lettres accentuées et correctement orthographiées, Thérèse-Éléonore a décrété avec sincérité et opiniâtreté l'immortalité des çàçâcécècêcëcïçôçöçùçûçü''
@@ Ligne 41 : / Ligne 41 : @@
 (see also http://cahiers.gutenberg.eu.org/cg-bin/article/CG_1989___3_48_0.pdf). During the Cork conference, the type T1 fonts were created and most Western diacritics characters can be searched (see below on fontenc)?
-===pdfTeX ===
+=== 1 pdfTeX ===
 [http://ctan.mines-albi.fr/systems/pdftex/pdftex-a.pdf pdfTeX] is currently the default TeX engine. It incorporates all the previous modifications of other side TeX engines, like mlTeX (multilingual TeX was able to hyphenate words containing accented characters) as well as eTeX and encTeX. It is also compatible whith original TeX82 engine and produces by default  standard DVI. But its main advantage, as suggested by its name, is that it can produce a PDF output file.
@@ Ligne 62 : / Ligne 62 : @@
 Another advantage of pdfTeX is that you can incorporate hypertext links using packages such as hyperref for your presentation (Beamer) and bibliography at least.
-===XeTeX ===
+=== 2 XeTeX ===
 With the XeTeX engine project which started in 2004, TeX is now able to manage any Unicode character and not only western accented characters and to process right to left characters. If the final output format is PDF, the intermediate format, .xdv, is an extended DVI format which can be transformed to PDF whith xdvipdfxm. XeTeX might be preferred to pdfTeX for non English languages. It is installed by default in any TeXLive distribution and can be used at the price of a change concerning font encoding and input encoding.
-=== LuaTeX ===
+=== 3 LuaTeX ===
 More recently a TeX engine, named LuaTeX lets you use any font and not only TeX fonts and simplify the use of any language with a single fontenc package (see a recent document of December 2010 http://ctan.mines-albi.fr/info/luatex/lualatex-doc/lualatex-doc.pdf which promotes LuaTeX). A stable version of LuaTeX will be announced for late 2012.
-== Which TeX engine should I choose?==
+Most of TeX distributions on any of the main three OS (Windows, MaC OS/X and Linux) are offering the 4 four main TeX engines. Most of the editors let you choose the TeX engine of your choice. If you are writing in English only, your choice will probably be pdfTeX. If you need to mix with some other Western languages you can still use pdfTeX at the price of a line specifying the coding used, but if you need to mix Western European languages with Eastern European languages as well as Arabic and Cyrillic you need to use XeTeX or LuaTeX. LuaTeX may not currently offer the same functionality and stability.
-Most of TeX distributions on any of the main three OS (Windows, MaC OS/X and Linux) are offering the 4 four main TeX engines. Most of the editors let you choose the TeX engine of your choice. If you are writing in English only, your choice will probably be pdfTeX until XeTeX or LuaTeX offers the same functionality and stability.
+In order to let you know which TeX engine you are using for a text, some editors are recognizing header comments that are on top of the text.
+== Headers ==
-In order to let you know which TeX engine you are using for a text, some editors are recognizing the comments that are on top of the text.
+=== TeXShop headers ===
-=== TeXWorks headers ===
+For example TeXShop (as well as TeXWorks) lets you include:
-For example TeXShop (or newer TeXWorks) lets you include:
 <source lang=latex>
 % These lines tell TeXShop to typeset with xelatex, and to open and
@@ Ligne 84 : / Ligne 83 : @@
 In order to simplify (does it?) there is a confusion between the TeX engine to be used (here xetex) and the format (here LaTeX) and the TS-program specifies <tt>xelatex</tt>.
 === Emacs headers ===

← Version précédente		Version du 28 mai 2011 à 12:37
Ligne 83 :		Ligne 83 :
	</source>		</source>

		+	In order to simplify (does it?) there is a confusion between the TeX engine to be used (here xetex) and the format (here LaTeX) and the TS-program specifies <tt>xelatex</tt>.

	=== Emacs headers ===		=== Emacs headers ===