Revision [3625]

Last edited on 2011-07-04 10:55:22 by DarTar [Code and examples uploaded to GitHub]
Additions:
""Fork me on GitHub""
''4 July 2011'' Code and examples uploaded to [[https://github.com/dartar/The-Beauty-of-LaTeX GitHub]].
These examples were created on a Mac, partly on Mac OS 10.3.9, Microsoft Word v.X and ""TeXShop"" 1.35, partly on Mac OS 10.5.3 with Word:Mac 2008 and ""TeXShop"" 2.x, the {{XeTeX}} engine with the ##fontspec## package, and using the following fonts: ""Adobe Garamond Pro, Adobe Minion Pro"" (commercial fonts), ""Hoefler Text, Skia, Zapfino"" (fonts bundled with Mac OS X). This article, the PDF samples and {{tex}} sources are licensed under a ""Creative Commons Attribution-Share Alike 3.0 Unported License. A backlink is sufficient for attribution."" All materials used in this article can be obtained via [[http://github.com/dartar/The-Beauty-of-LaTeX GitHub]]. The {{tex}}, {{latex}} and {{xetex}} logos on this page are rendered via a [[texlogo nifty XHTML and CSS hack]] by [[http://edward.oconnor.cx/2007/08/tex-poshlet Edward O'Connor]]. ""[
Deletions:
''2 July 2011'' Added titling caps example.
These examples were created on a Mac, partly on Mac OS 10.3.9, Microsoft Word v.X and ""TeXShop"" 1.35, partly on Mac OS 10.5.3 with Word:Mac 2008 and ""TeXShop"" 2.x, the {{XeTeX}} engine with the ##fontspec## package, and using the following fonts: ""Adobe Garamond Pro, Adobe Minion Pro"" (commercial fonts), ""Hoefler Text, Skia, Zapfino"" (fonts bundled with Mac OS X). This article, the PDF samples and {{tex}} sources are licensed under a ""Creative Commons Attribution-Share Alike 3.0 Unported License. A backlink is sufficient for attribution."" The {{tex}}, {{latex}} and {{xetex}} logos on this page are rendered via a [[texlogo nifty XHTML and CSS hack]] by [[http://edward.oconnor.cx/2007/08/tex-poshlet Edward O'Connor]]. ""[

Revision [3622]

Edited on 2011-07-02 09:30:43 by DarTar [Added titling caps example]
Additions:
Most word processors create //fake// small capitals by adjusting the size of capitals. Professional fonts contain different sets of glyphs for small capitals and full-size capitals that any serious typesetting system should be able to use in the appropriate context. In particular, //real small capitals// are more than resized versions of uppercase capitals: they have a relatively heavier stroke and are designed to be visually compatible with lowercase characters of the same typeface. Some ""OpenType"" fonts have special “titling” alternates that are designed for all-uppercase type set at large sizes and have a lighter stroke.
Deletions:
Most word processors create //fake// small capitals by adjusting the size of capitals. Professional fonts contain different sets of glyphs for small capitals and full-size capitals that any serious typesetting system should be able to use in the appropriate context. In particular, //real small capitals// are more than resized versions of uppercase capitals: they have a relatively heavier stroke and are designed to be visually compatible with lowercase characters of the same typeface. Some OpenType fonts have special “titling” alternates that are designed for all-uppercase type set at large sizes and have a lighter stroke.

Revision [3621]

Edited on 2011-07-02 09:29:24 by DarTar [Added titling caps example]
Additions:
''2 July 2011'' Added titling caps example.
~1)[[http://nitens.org/taraborelli/latex#smallcaps Real Small Caps & Titling Caps]]
===2. Real small caps and titling caps ===
Most word processors create //fake// small capitals by adjusting the size of capitals. Professional fonts contain different sets of glyphs for small capitals and full-size capitals that any serious typesetting system should be able to use in the appropriate context. In particular, //real small capitals// are more than resized versions of uppercase capitals: they have a relatively heavier stroke and are designed to be visually compatible with lowercase characters of the same typeface. Some OpenType fonts have special “titling” alternates that are designed for all-uppercase type set at large sizes and have a lighter stroke.
=={{latex}} (regular vs titling caps):==
{{image class="border" src="../img/latex/titling_latex.png" alt="[example of titling alternates in LaTeX]" title="Regular vs. titling caps in LaTeX"}}
''[Adobe Garamond Pro, 120pt]'' #%[[http://nitens.org/img/latex/docs/beauty_of_latex_titling.pdf pdf]]#% #%[[http://nitens.org/img/latex/docs/beauty_of_latex_titling.tex tex]]#%
Deletions:
''03 Dec 2010'' Fixed typo.
~1)[[http://nitens.org/taraborelli/latex#smallcaps Real Small Caps]]
===2. Real small caps ===
Most word processors create //fake// small capitals by adjusting the size of capitals. Professional fonts contain different sets of glyphs for small capitals and full-size capitals that any serious typesetting system should be able to use in the appropriate context. In particular, //real small capitals// are more than resized versions of uppercase capitals: they have a relatively heavier stroke and are designed to be visually compatible with lowercase characters of the same typeface.

Revision [3594]

Edited on 2011-04-04 23:23:32 by DarTar [removing dropcap]
Additions:
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}There are several reasons why one should prefer {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the [[TeXOpenType advanced typographic features]] of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.
Deletions:
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}""There are several reasons"" why one should prefer {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the [[TeXOpenType advanced typographic features]] of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.

Revision [3411]

Edited on 2010-12-03 07:21:42 by DarTar [Fixed typo]
Additions:
''03 Dec 2010'' Fixed typo.
Expert fonts often include variants or alternate shapes for alphabetic characters and numbers. {{XeTeX}} with the [[tools fontspec package]] offers the possibility to access and select variants on single characters or for a whole text block.
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//, //Ehud Kaplan//, //Henri Langenhoven//.
Deletions:
''20 Aug 2010'' Fixed typo.
Expert fonts often include variants or alternate shapes for alphabetic characters and numbers. {{XeTeX}} with the [[tools fonstpec package]] offers the possibility to access and select variants on single characters or for a whole text block.
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//, //Ehud Kaplan//.

Revision [3336]

Edited on 2010-08-20 04:50:56 by DarTar [Fixed typo]
Additions:
''20 Aug 2010'' Fixed typo.
Readability results not only from a good selection of typefaces, but also from a correct distribution of characters and whitespace per line. To attain this goal, most ""WYSIWYG"" word processors use relatively dumb justification/hyphenation procedures (i.e. algorithms that establish the position for line breaks by processing text //line by line//). {{latex}} uses an advanced algorithm, based on [[http://www3.interscience.wiley.com/journal/113445055/ seminal work]] by Donald Knuth and Michael F. Plass and enhanced by Frank Liang in 1983 for his ""PhD"" dissertation, which considers paragraphs as `wholes´ in order to decide where to add line breaks. The algorithm uses language-specific patterns in order to decide the preferred position for hyphenation. The engine then selects line breaks so as to make paragraphs look //as good as possible//. Information that is taken into account for calculating optimal line breaks includes the number of consecutive lines ending with hyphens, word tightness on each line, the change of tightness between consecutive lines. Further development has enabled the {{latex}} engine to allow certain characters to stick into the margin, thus generating an //optically// straight margin - i.e., a margin that //looks// straight without being geometrically so. {{latex}}'s hyphenation settings can be fine-tuned by expert users.
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//, //Ehud Kaplan//.
Deletions:
''12 Aug 2010'' Updating links.
Readability results not only from a good selection of typefaces, but also from a correct distribution of characters and whitespace per line. To attain this goal, most ""WYSIWYG"" word processors use relatively dumb justification/hyphenation procedures (i.e. algorithms that establish the position for line breaks by processing text //line by line//). {{latex}} uses an advanced algorithm, based on [[http://www3.interscience.wiley.com/journal/113445055/ seminal work]] by Donald Knuth and Michael F. Plass and enhanced by Frank Liang in 1983 for his ""PhD"" dissertation and, which considers paragraphs as `wholes´ in order to decide where to add line breaks ''[Thanks to Olaf 'Rhialto' Seibert for the correct attribution]''. The algorithm uses language-specific patterns in order to decide the preferred position for hyphenation. The engine then selects line breaks so as to make paragraphs look //as good as possible//. Information that is taken into account for calculating optimal line breaks includes the number of consecutive lines ending with hyphens, word tightness on each line, the change of tightness between consecutive lines. Further development has enabled the {{latex}} engine to allow certain characters to stick into the margin, thus generating an //optically// straight margin - i.e., a margin that //looks// straight without being geometrically so. {{latex}}'s hyphenation settings can be fine-tuned by expert users.
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//.

Revision [3332]

Edited on 2010-08-13 16:05:59 by DarTar
Additions:
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}""There are several reasons"" why one should prefer {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the [[TeXOpenType advanced typographic features]] of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.
Deletions:
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}""There are several reasons why one should prefer {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the [[TeXOpenType advanced typographic features]] of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.

Revision [3331]

Edited on 2010-08-13 16:05:40 by DarTar
Additions:
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}""There are several reasons why one should prefer {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the [[TeXOpenType advanced typographic features]] of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.
Deletions:
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}""There are several reasons why one should prefer"" {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the [[TeXOpenType advanced typographic features]] of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.

Revision [3330]

Edited on 2010-08-12 12:57:18 by DarTar [Updating links]
Additions:
{{image class="left_border" src="images/mini/opentype.jpg" alt="[latex]" title="Accessing OpenType font features in XeTeX" link="TeXOpenType"}} [[TeXOpenType Accessing OpenType features in XeTeX]]: how to control expert font features via ##fontspec##.
Deletions:
{{image class="left_border" src="images/mini/opentype.jpg" alt="[latex]" title="Accessing OpenType font features in LaTeX" link="TeXOpenType"}} [[TeXOpenType Accessing OpenType features in LaTeX via fontspec]]: how to control expert font features via fontspec.

Revision [3329]

Edited on 2010-08-12 12:56:05 by DarTar [Updating links]
Additions:
''12 Aug 2010'' Updating links.
>>==Breaking news==
==See also==
{{image class="left_border" src="images/mini/cvtex.jpg" alt="[latex]" title="Typesetting an academic CV in LaTeX" link="cvtex"}} [[cvtex Typesetting an academic CV in LaTeX]]. 6 templates to compile a cv using {{XeTeX}} and expert fonts. ---
{{image class="left_border" src="images/mini/tools.jpg" alt="[latex tools]" title="LaTeX on Mac OS" link="tools"}} [[tools LaTeX on Mac OS X]]: my open source {{latex}} toolbox for Mac OS. ---
{{image class="left_border" src="images/mini/opentype.jpg" alt="[latex]" title="Accessing OpenType font features in LaTeX" link="TeXOpenType"}} [[TeXOpenType Accessing OpenType features in LaTeX via fontspec]]: how to control expert font features via fontspec.
Deletions:
''18 Jun 2010'' Adding link to [[TeXOpenType OpenType]] feature table.
>>==""OpenType"" and {{xetex}}==
For a summary of ""OpenType"" features supported in {{xetex}} via the ##fontspec## package, check [[TeXOpenType this page]].
==Breaking news==
~-[[tools LaTeX on Mac OS X]]: a selection of {{latex}}-related opensource software for Mac.
~-[[TeXOpenType Accessing OpenType features in LaTeX via fontspec]]: a summary of fontspec options to control expert font features.
~-[[cvtex Typesetting an academic CV in LaTeX]]. Templates and examples of how to [[cvtex compose an academic curriculum vitæ]] or resume using {{XeTeX}} and expert fonts.

Revision [3300]

Edited on 2010-06-18 11:40:12 by DarTar
Additions:
>>==""OpenType"" and {{xetex}}==
==Breaking news==
Deletions:
>>===""OpenType"" and {{xetex}}===
===Breaking news===

Revision [3299]

Edited on 2010-06-18 11:39:51 by DarTar
Additions:
>>===""OpenType"" and {{xetex}}===
Deletions:
>>===""OpenType and {{xetex}}===

Revision [3298]

Edited on 2010-06-18 11:39:30 by DarTar
Additions:
>>===""OpenType and {{xetex}}===
For a summary of ""OpenType"" features supported in {{xetex}} via the ##fontspec## package, check [[TeXOpenType this page]].
===Breaking news===
Deletions:
>>===Breaking news===

Revision [3282]

Edited on 2010-06-18 10:53:08 by DarTar [Adding link to OpenType feature table]
Additions:
''18 Jun 2010'' Adding link to [[TeXOpenType OpenType]] feature table.
Deletions:
''18 Jun 2010'' Adding link to OpenType feature table.

Revision [3281]

Edited on 2010-06-18 10:52:28 by DarTar [Adding link to OpenType feature table]
Additions:
''18 Jun 2010'' Adding link to OpenType feature table.
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}""There are several reasons why one should prefer"" {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the [[TeXOpenType advanced typographic features]] of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.
~-[[TeXOpenType Accessing OpenType features in LaTeX via fontspec]]: a summary of fontspec options to control expert font features.
Deletions:
''14 May 2010'' Adding ""COinS"" metadata.
{{image class="right_floated" src="../img/latex/tex_showcase.jpg" alt="[latex fonts screenshot]" title="Excerpt from the TeX for the Humanities Showcase"}}""There are several reasons why one should prefer"" {{latex}} to a ""WYSIWYG"" word processor like Microsoft Word: //portability, lightness, security// are just a few of them (not to mention that {{latex}} is //free//). There is still a further reason that definitely convinced me to [[tools abandon MS Word]] when I wrote my dissertation: you will never be able to produce //professionally typeset// and //well-structured// documents using most ""WYSIWYG"" word processors. {{latex}} is a free typesetting system that allows you to focus on //content// without bothering about the layout: the software takes care of the actual typesetting, structuring and page formatting, producing documents of astonishing elegance. The [[tools software]] I use to write in {{latex}} on a Mac compiles documents in [[http://www.openformats.org/en65 PDF]] format (but exporting to other formats such as [[http://www.openformats.org/en63 RTF]] or [[http://www.openformats.org/en61 HTML]] is also possible). It supports [[http://en.wikipedia.org/wiki/Unicode unicode]] and all the advanced typographic features of [[http://en.wikipedia.org/wiki/OpenType OpenType]] and [[http://en.wikipedia.org/wiki/Apple_Advanced_Typography AAT]] fonts, like //Adobe Garamond Pro// and //Hoefler Text//. It allows fine-tuned control on a number of typesetting options, although just using the default configuration results in documents with high typographic quality. In what follows I review some examples, comparing how fonts are rendered in MS Word and in {{latex}}.

Revision [3199]

Edited on 2010-05-14 03:49:14 by DarTar [Adding COinS metadata]
Additions:
''14 May 2010'' Adding ""COinS"" metadata.
These examples were created on a Mac, partly on Mac OS 10.3.9, Microsoft Word v.X and ""TeXShop"" 1.35, partly on Mac OS 10.5.3 with Word:Mac 2008 and ""TeXShop"" 2.x, the {{XeTeX}} engine with the ##fontspec## package, and using the following fonts: ""Adobe Garamond Pro, Adobe Minion Pro"" (commercial fonts), ""Hoefler Text, Skia, Zapfino"" (fonts bundled with Mac OS X). This article, the PDF samples and {{tex}} sources are licensed under a ""Creative Commons Attribution-Share Alike 3.0 Unported License. A backlink is sufficient for attribution."" The {{tex}}, {{latex}} and {{xetex}} logos on this page are rendered via a [[texlogo nifty XHTML and CSS hack]] by [[http://edward.oconnor.cx/2007/08/tex-poshlet Edward O'Connor]]. ""[
Deletions:
''14 May 2010'' Adding COinS metadata.
These examples were created on a Mac, partly on Mac OS 10.3.9, Microsoft Word v.X and ""TeXShop"" 1.35, partly on Mac OS 10.5.3 with Word:Mac 2008 and ""TeXShop"" 2.x, the {{XeTeX}} engine with the ##fontspec## package, and using the following fonts: ""Adobe Garamond Pro, Adobe Minion Pro"" (commercial fonts), ""Hoefler Text, Skia, Zapfino"" (fonts bundled with Mac OS X). This article, the PDF samples and {{tex}} sources are licensed under a ""Creative Commons Attribution-Share Alike 3.0 Unported License. A backlink is sufficient for attribution."" The {{tex}}, {{latex}} and {{xetex}} logos on this page are rendered via a [[texlogo nifty XHTML and CSS hack]] by [[http://edward.oconnor.cx/2007/08/tex-poshlet Edward O'Connor]].
""[

Revision [3198]

Edited on 2010-05-14 03:47:47 by DarTar [Adding COinS metadata]
Additions:
''14 May 2010'' Adding COinS metadata.
""[ class="Z3988"
title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&rfr_id=info%3Asid%2Focoins.info%3Agenerator&rft.title=The+Beauty+of+LaTeX&rft.creator=Dario+Taraborelli&rft.date=2008&rft.source=http%3A%2F%2Fnitens.org%2Ftaraborelli%2Flatex">
COinS metadata
]""
Deletions:
''19 Feb 2010'' Fixed link to Maarten Sneep's article.

Revision [3124]

Edited on 2010-03-10 13:14:42 by DarTar
Additions:
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//.
Deletions:
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//, //Mojca Miklavec//.

Revision [3123]

Edited on 2010-03-09 01:42:16 by DarTar [fixed link to Maarten Sneep's article]
Additions:
''19 Feb 2010'' Fixed link to Maarten Sneep's article.
~-For visual examples of the differences between paragraph and line-by-line based justification algorithms, see this [[http://web.archive.org/web/20070203140340/http://www.nat.vu.nl/~sneep/ars/type/ analysis]] by **Maarten Sneep**.
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//, //Mojca Miklavec//.
Deletions:
''19 Feb 2010'' Added link to Bram Stein's typeset project.
~-For visual examples of the differences between paragraph and line-by-line based justification algorithms, see this [[http://www.nat.vu.nl/~sneep/ars/type/ analysis]] by **Maarten Sneep**.
Many of the examples in this article are based on the [[http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf documentation]] of the ##fontspec## package by //Will Robertson//, who deserves most of the credits for making expert font features in {{XeTeX}} so easy to use. Thanks to all those who helped improve this article with valuable feedback: //Bastien Guerry//, //Nicholas Shera//, //Mark Dancer//, //Olaf 'Rhialto' Seibert//, //David Crossland//, //Tiago Tresoldi//.

Revision [3069]

The oldest known version of this page was created on 2010-02-19 09:40:37 by DarTar
Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by WikkaWiki