[LyX/master] ePub: detect and use xsltproc.
Pavel Sanda
sanda at lyx.org
Fri Feb 12 20:37:43 UTC 2021
On Mon, Feb 08, 2021 at 04:18:17PM +0100, Thibaut Cuvelier wrote:
> > I am happy to give xsltproc a try under linux. Is the output supposed to
> > give identical result to saxon -- or is there some realistic way how to
> > tell that xslproc output is on par with saxon, which you tested already?
> >
> > I don't have trained eyes to look on xml/epub and see possible issues.
> > Pavel
> >
>
> There should not be any significant differences between the XSLT processors.
So I tried our saxon and xsltproc 1.1.32 (stable debian) and the result is not
identical. The xmldiff output is unfortunately beyond my comprehension so
I have no clue whether the difference is 'significant'. You can check the
attachments.
But I have not been able to spot any significant difference when viewing
through epubreader.
Anyway I think it's fair to add to release notes that xsltproc works
under linux (and Mac if I read correctly Stephan's email).
Pavel
-------------- next part --------------
PK ??LRoa?, mimetypeapplication/epub+zipPK ??LR????> ?> OEBPS/index.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Introduction to LyX</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/><link rel="next" href="ar01s02.xhtml" title="Navigating the Documentation"/></head><body><header/><section xml:lang="en_US" class="article" title="Introduction to LyX" id="d0e2"><div class="titlepage"><div><div><h1 class="title">Introduction to LyX</h1></div><div><div class="author"><h3 class="author">by the LyX Team<a href="#ftn.d0e9" class="footnote"><sup class="footnote" id="d0e9">[1]</sup></a></h3></div></div></div><hr/></div><section class="section" title="The Philosophy of LyX" epub:type="division" id="d0e13"><div class="titlepage"><div><div><h2 class="title" style="clear: both">The Philosophy of LyX</h2></div></div></div><section class="section" title="What is LyX?" epub:type="division" id="d0e16"><div class="titlepage"><div><div><h3 class="title">What is LyX?</h3></div></div></div><p>LyX is a document preparation system. It excels at letting you create complex technical and scientific articles with mathematics, cross-references, bibliographies, indexes, etc. It is very good for working with documents of any length in which the usual processing abilities are required: automatic sectioning and pagination, spell checking and so forth. It can also be used to write a letter to your mom, though granted, there are probably simpler programs available for that. It is definitely not the best tool for creating banners, flyers, or advertisements (we'll explain why later), though with some effort all these can be done, too. Here are some examples of what it is used for: memos, letters, dissertations and theses, lecture notes, seminar notebooks, conference proceedings, software documentation, books, articles in refereed scientific journals, scripts for plays and movies, business proposals, presentations ???</p><p>LyX is a program that provides a modern approach to writing documents with a computer by using a markup language paradigm, an approach that breaks with the obsolete tradition of the ???typewriter concept???. It is designed for authors who want professional output quickly with a minimum of effort and without becoming specialists in typesetting. The job of typesetting is done mostly by the computer, not the author; with LyX, the author can concentrate on the contents of his writing.</p><p>Part of the initial challenge of using LyX comes from the change in thinking that you, the user, must make. At one time, all we had for creating documents were typewriters, so we all learned certain tricks to get around their limitations. Underlining, which is little more than overstriking with the ???_??? character, became a way to emphasize text. You were forced to figure out column sizes and tab stops, and set them, before creating a table. The same applied for letters and other right justified text. Hyphenation at the end of a line required a careful eye and a lot of foresight.</p><p>In other words, we've all been trained to worry about the little details of which character goes where. Consequently, almost all word processors have this mentality. They still use tab stops for adding whitespace. You still need to worry about exactly where on the page something will appear. Emphasizing text means changing a font, similar to changing the typewriter wheel. This is the underlying philosophy of a WYSIWYG word processor: ???What You See Is What You Get???. Unfortunately, that paradigm often results in ???What You See Is All You Get???.</p><p>This is where LyX differs from an ordinary word processor. You don't concern yourself with what character goes where. You tell LyX <span class="emphasis"><em>what you're doing</em></span> and LyX takes care of the rest, following a set of rules called a <span class="emphasis"><em>style</em></span>.<a href="#ftn.d0e35" class="footnote"><sup class="footnote" id="d0e35">[2]</sup></a> Let's look at a little example:</p><p>Suppose you are writing a report. To begin your report, you want a section called ???Introduction.??? So, you go into whatever menu it is in your word processor that changes font sizes and decide on a new font size. Then you turn on bold face. Then you type, ???1.????Introduction???. Of course, if you later decide that this section belongs someplace else in the document or if you insert a new section before it, you need to change the numbering for this and all following sections, as well as any entry in the table of contents.</p><p>In LyX, you go to the pull-down on the far left of the button bar and select <span class="sans">Section</span>, and type ???Introduction???.</p><p>Yes, that's all. If you cut and paste the section, it will automatically be renumbered ??? everywhere. And if you enter references to that section correctly (by inserting cross-reference tags), LyX will automatically update them all throughout the file so that you never, ever type a section number.</p><p>Now let's look at the problem of consistency. Five days later, you reopen your report and start Section??4. However, you forget that you were using 18???pt bold instead of 16???pt, so you type in the heading for Section??4 in a different font from the one you used for Section??1. That problem doesn't even exist in LyX. The computer takes care of all that silly bookkeeping about which thing has what size font, not you. After all, that's what a computer is good at.</p><p>Here's another example. Suppose you're making a list. In other word processors, a list is just a bunch of tab stops and newlines. You need to figure out where to put the label for each list item, what that label should be, how many blank lines to put between each item, and so on. Under LyX, you have only two concerns: what kind of list is this, and what do I want to put in it? That is it.</p><p>So, the basic idea behind LyX is: specify <span class="emphasis"><em>what</em></span> you're doing, not <span class="emphasis"><em>how</em></span> to do it. Instead of ???What You See Is What You Get,??? the LyX model is ???What You See Is What You <span class="emphasis"><em>Mean</em></span>??? or ???WYSIWYM.??? It's a powerful idea that greatly simplifies the mechanics of writing documents. This is also why LyX isn't so good for creating posters and flyers. In this case, you <span class="emphasis"><em>do</em></span> want to specify exactly where everything goes, because there are no functional units like paragraphs, sections, etc. This doesn't mean LyX is missing some cool function. It simply means that it isn't the right tool for the job ??? you don't use a screwdriver to drive in nails.</p></section><section class="section" title="Differences between LyX and Other Word Processors" epub:type="division" id="d0e66"><div class="titlepage"><div><div><h3 class="title">Differences between LyX and Other Word Processors</h3></div></div></div><p>Here's a list of things you won't find in LyX:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>The document ruler</p></li><li class="listitem" epub:type="list-item"><p>Tab stops</p></li><li class="listitem" epub:type="list-item"><p>Extra whitespace (e.???g. hitting <span class="sans">Enter</span> or <span class="sans">Space</span> two or more times)</p></li></ul></div><p>Tab stops, along with a ruler showing you the position of things on the page, are useless in LyX. The program worries about where things go on the page, not you. Extra whitespace is similar; LyX adds it where necessary, depending on context. Not being able to type two blank lines in a row will be annoying at first, but it makes more sense once you're thinking in WYSIWYM terms.</p><p>Here are some things that exist in LyX, but aren't used as you might think:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>Indenting controls</p></li><li class="listitem" epub:type="list-item"><p>Page breaks</p></li><li class="listitem" epub:type="list-item"><p>Line spacing (e.???g. single spaced, double spaced, etc.)</p></li><li class="listitem" epub:type="list-item"><p>Whitespace, horizontal and vertical</p></li><li class="listitem" epub:type="list-item"><p>Fonts and font sizes</p></li><li class="listitem" epub:type="list-item"><p>Typefaces (bold, italic, underline, etc.)</p></li></ul></div><p>Although they exist in LyX, you generally don't need them. LyX will take care of these things for you, depending on what you're doing. Different parts of the document are automatically set in a different typeface and font size. Paragraph indenting is context dependent; different types of paragraphs get indented differently. Page breaks get handled automatically, as well. In general, the space between lines, between words, and between paragraphs is variable, set by LyX.<a href="#ftn.d0e112" class="footnote"><sup class="footnote" id="d0e112">[3]</sup></a></p><p>Lastly, there are a few areas where we believe LyX (and LaTeX) surpasses many word processors:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>Hyphenation</p></li><li class="listitem" epub:type="list-item"><p>Lists of any type</p></li><li class="listitem" epub:type="list-item"><p>Mathematics</p></li><li class="listitem" epub:type="list-item"><p>Tables</p></li><li class="listitem" epub:type="list-item"><p>Cross-referencing</p></li></ul></div><p>Granted, many modern word processors can handle mathematical symbols, tables, and hyphenation, and many have moved towards style definitions and the WYSIWYM concept. However, they've only recently been able to do so, whereas LyX is built upon the LaTeX document preparation system. LaTeX has been around since 1985, and <span class="emphasis"><em>works</em></span>.</p></section><section class="section" title="What is LaTeX?" epub:type="division" id="d0e144"><div class="titlepage"><div><div><h3 class="title">What is LaTeX?</h3></div></div></div><p>LaTeX is a document preparation system designed by Leslie Lamport in 1985.<a href="#ftn.d0e149" class="footnote"><sup class="footnote" id="d0e149">[4]</sup></a> It was built up from a typesetting language called TeX, created by Donald Knuth in 1984. TeX takes a sequence of typesetting commands, written in a script in an ASCII file, and executes them. Many of the ???tricks??? of the printing trade were modeled by Knuth as computer algorithms and incorporated into TeX, hence its excellent printed appearance. What comes directly out of TeX is the portable document format <span class="emphasis"><em>pdf</em></span> or the so-called ???device independent??? format file <span class="emphasis"><em>dvi</em></span>. The dvi format is often used for previews and can later be converted to other formats like PostScript. </p><p>TeX isn't only a typesetting engine; it also allows you to define macros. Most people who use TeX are actually using a macro package which Knuth created to hide a lot of the typesetting details. This is where Leslie Lamport enters our story. He wanted a macro package that was more user- and less typesetter-oriented, with a set of commands that consistently typeset things like sections, tables or math formulas in a uniform, consistent fashion. This is how LaTeX was born.</p><p>Now, in parallel with the development and growth of LaTeX, other folks were creating their own custom macro packages for TeX, ones to make slides or articles for math journals and so on. Some used the raw TeX facilities to do this, others began modifying LaTeX. To try and unify this mess, a team of LaTeX-nicians began to work on LaTeX2??, the current version of LaTeX, during the late 1980's. This new version of LaTeX has commands which provide an easier-to-use interface to TeX's macro-creating commands, aid in the use of new fonts, and so on. In fact, LaTeX is quite an extensive language in its own right! Users around the world have been creating their own add-ons for LaTeX beyond the standard ones.</p><p>There are two ways to extend LaTeX: classes and styles. A <span class="emphasis"><em>class</em></span> is a set of LaTeX macros describing a new type of document, like a book, or an article. There are classes for slides, for physics and math journals??? many universities even have a class for their thesis format. A <span class="emphasis"><em>style</em></span> differs from a class in that it doesn't define a new type of document, but a different type of <span class="emphasis"><em>behavior</em></span> that any document can use. For example, LyX controls page margins and line spacing using two different LaTeX style-files designed for these purposes. There are style-files for a whole slew of things: printing labels or envelopes, changing indentation behavior, adding new fonts, manipulating graphics, designing fancy page headings, customizing bibliographies, altering the location and appearance of footnotes, tables, and figures, customizing lists, etc.</p><p>Here is a summary:</p><div class="variablelist" epub:type="list"><dl class="variablelist"><dt><span class="term">TeX:</span></dt><dd><p>Typesetting language with macro capability.</p></dd><dt><span class="term">LaTeX:</span></dt><dd><p>Macro package built upon TeX.</p></dd><dt><span class="term">classes:</span></dt><dd><p>Descriptions of types of document used with LaTeX.</p></dd><dt><span class="term">styles:</span></dt><dd><p>Descriptions of the default behavior of particular elements of LaTeX.</p></dd><dt><span class="term">LyX:</span></dt><dd><p>Visual, WYSIWYM document processor that uses LaTeX to do its typesetting.</p></dd></dl></div><p>This section attempts to explain the difference between LyX and a word processor. Simply put, LaTeX is the difference. By using LaTeX as its backend, LyX helps you to think more about<span class="emphasis"><em> what</em></span> (as in the <span class="emphasis"><em>words</em></span>) you write. The computer then handles <span class="emphasis"><em>how</em></span> they should look.</p></section></section><div class="footnotes" epub:type="footnotes"><br/><hr class="footnote-hr"/><div id="ftn.d0e9" class="footnote" epub:type="footnote"><p><a href="#d0e9" class="para"><sup class="para">[1] </sup></a>If you have comments on or corrections to this documentation, please send them to the LyX Documentation mailing list: <a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a></p></div><div id="ftn.d0e35" class="footnote" epub:type="footnote"><p><a href="#d0e35" class="para"><sup class="para">[2] </sup></a>To be fair, most recent versions of the most popular office suites now have some sort of style sheets which follow a similar markup method. However, our experience is that they are still rarely used in practice.</p></div><div id="ftn.d0e112" class="footnote" epub:type="footnote"><p><a href="#d0e112" class="para"><sup class="para">[3] </sup></a>There are ways to adjust all of these (only some of which require knowledge of LaTeX), either for a whole document or for a specific location in a document. See the <span class="emphasis"><em>User's Guide</em></span> and/or the <span class="emphasis"><em>Additional Features</em></span> manual for details.</p></div><div id="ftn.d0e149" class="footnote" epub:type="footnote"><p><a href="#d0e149" class="para"><sup class="para">[4] </sup></a>The source for the info in this section is <span class="emphasis"><em>A Guide to LaTeX2??</em></span>, by Helmut Kopka and Patrick Daly, which has an entry in the bibliography of the <span class="emphasis"><em>User's Guide</em></span>.</p></div></div></section><footer/></body></html>PK ??LR?7? 7 7 OEBPS/ar01s02.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Navigating the Documentation</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/><link rel="prev" href="index.xhtml" title="Introduction to LyX"/><link rel="next" href="ar01s03.xhtml" title="Contributing to the LyX Project"/></head><body><header/><section class="section" title="Navigating the Documentation" epub:type="division" id="d0e224"><div class="titlepage"><div><div><h2 class="title" style="clear: both">Navigating the Documentation</h2></div></div></div><p>To make it easier to answer your questions and describe all of the features of LyX, the documentation has been split up into several different files. Each one has its own purpose, as described below. Before you go ploughing into any of those files, however, you should read this chapter thoroughly, since it contains a lot of useful information and commentary that can save you some time.</p><p>Hopefully, the development of LyX will never stop; so some of the documentation may be incomplete or a bit out of date, though we try to keep up-to-date. Like the rest of LyX, the manuals are the work of a group of volunteers who have ???Real Jobs???, families, dishes to clean, <span class="emphasis"><em>et cetera</em></span>. If you want to help out, be sure to read Section??<a class="xref" href="ar01s03.xhtml" title="Contributing to the LyX Project">the section called ???Contributing to the LyX Project???</a> in addition to the rest of this document.</p><p>Also, please do us a favor: if anything in these manuals confuses you, is unclear, or wrong, don't hesitate to let us know! You can reach the current document maintainers by emailing <a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a>. </p><section class="section" title="Where To Get Help" epub:type="division" id="d0e240"><div class="titlepage"><div><div><h3 class="title">Where To Get Help</h3></div></div></div><p>If you have questions that are not obviously answered in the documentation and need help fast, there is an active users' mailing list which you can reach at <a class="link" href="lyx-users at lists.lyx.org" target="_top">lyx-users at lists.lyx.org</a>. You do not have to register to post, but you may wish to do so. See <a class="link" href="https://www.lyx.org/MailingLists" target="_top">the LyX website</a> for further information. LyX also has a <a class="link" href="http://wiki.lyx.org/" target="_top">http://wiki.lyx.org/</a> that will answer many questions about how to get LyX to do various things.</p></section><section class="section" title="The Format of the Manuals" epub:type="division" id="d0e252"><div class="titlepage"><div><div><h3 class="title">The Format of the Manuals</h3></div></div></div><p>Some of you may have printed out the manuals. Others may be reading them within LyX. There are some differences between the LyX-file and the printed version. In LyX, the title is simply at the top of the document, not formatted on a separate page as in some of the printed versions. Nor are any of the footnotes or the Table of Contents fully visible. To open a footnote, which looks like this: <span class="inlinemediaobject"><img src="images/footnote.png" width="513"/></span>
, click on it with the left mouse button. For the Table of Contents, either click on the grey box or click on the <span class="sans">Navigate</span> menu, where the contents are displayed automatically.</p><p>In the printed manuals, all cross-references appear as the actual numbers for a chapter, section, subsection, and so on. In the LyX-file, however, all cross-references appear as light-grey boxes like the following: <span class="inlinemediaobject"><img src="images/reference.png" width="513"/></span>
. If you click on such a box with the left mouse button, a dialog box will appear containing a list of all the cross-references in the document. You can go to the referenced section by right-clicking on the box or by clicking the button <span class="sans">Go??to??Label</span> in the opened dialog. Going back to where you came from is just as easy. Click on <span class="sans">Go??Back</span> to go back to your earlier location.</p><p>Now that we've cleared up some of the differences between the printed and LyX-file versions of this file, we can start looking at the format of this document. You'll occasionally notice things in different fonts:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p><span class="emphasis"><em>Emphasized Style</em></span> is used for general emphasis, generic arguments, book titles, names of sections of other manuals, and notes from the authors.</p></li><li class="listitem" epub:type="list-item"><p><code class="code">Typewriter</code> is used for program and file names, LyX code and functions.</p></li><li class="listitem" epub:type="list-item"><p><span class="sans">Sans Serif</span> is used for menu, button, or dialog box names, and the names of keyboard keys.</p></li><li class="listitem" epub:type="list-item"><p><span class="personname">Noun Style</span> is used for people's names.</p></li><li class="listitem" epub:type="list-item"><p><span class="bold"><strong>Bold</strong></span> is used for LaTeX code</p></li></ul></div><p>When we do need to reference keys, we'll use the following prefixing convention:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>???<span class="sans">Ctrl+</span>??? indicates the <span class="sans">Control</span> key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Shift+</span>??? indicates the <span class="sans">Shift</span> key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Alt+</span>??? indicates the <span class="sans">Alt</span> (<span class="sans">Meta</span>) key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">F1</span>??? ??? ???<span class="sans">F12</span>??? are the function keys.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Esc</span>??? is the escape key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Left</span>??? ???<span class="sans">Right</span>??? ???<span class="sans">Up</span>??? ???<span class="sans">Down</span>???: self-explanatory.</p></li><li class="listitem" epub:type="list-item"><p><span class="sans">???Insert</span>??? ???<span class="sans">Delete</span>??? ???<span class="sans">Home</span>??? ???<span class="sans">End</span>??? ???<span class="sans">PageUp</span>??? ???<span class="sans">PageDown</span>???: these are the 6??keys that appear above the cursor keys on many PC keyboards. ???<span class="sans">PageUp</span>??? and ???<span class="sans">PageDown</span>??? are called ???<span class="sans">Prior</span>??? and ???<span class="sans">Next</span>??? on some keyboards.</p></li><li class="listitem" epub:type="list-item"><p><span class="sans">Return</span> and <span class="sans">Enter</span> both refer to the same key. Some keyboards label the <span class="sans">Return</span> key as ???Return,??? others as ???Enter,??? still others have two keys. LyX treats all of them as the same key, so we'll use <span class="sans">Return</span> and <span class="sans">Enter</span> interchangeably.</p></li></ul></div><p>The list with the currently set shortcuts can be found in the <span class="sans">Help</span> menu under <span class="sans">Shortcuts</span>.</p></section><section class="section" title="Units used in the Manuals" epub:type="division" id="d0e424"><div class="titlepage"><div><div><h3 class="title">Units used in the Manuals</h3></div></div></div><p>To understand the units described in this documentation, Table??<a class="xref" href="ar01s02.xhtml#tab.Units" title="Table??1.??Units">Table??1, ???Units???</a> explains all units available in LyX.</p><div class="table" id="tab.Units"><div class="table-title">Table??1.??Units</div><div class="table-contents"><table xml:id="tab.Units"><tbody><tr>
<td align="center" valign="top">unit</td>
<td align="center" valign="top">name/description</td>
</tr><tr>
<td align="center" valign="top">mm</td>
<td align="center" valign="top">millimeter</td>
</tr><tr>
<td align="center" valign="top">cm</td>
<td align="center" valign="top">centimeter</td>
</tr><tr>
<td align="center" valign="top">in</td>
<td align="center" valign="top">inch (1???in = 2.54???cm)</td>
</tr><tr>
<td align="center" valign="top">pt</td>
<td align="center" valign="top">point (72.27???pt = 1???in)</td>
</tr><tr>
<td align="center" valign="top">pc</td>
<td align="center" valign="top">pica (1???pc = 12???pt)</td>
</tr><tr>
<td align="center" valign="top">sp</td>
<td align="center" valign="top">scaled point (65536???sp = 1???pt)</td>
</tr><tr>
<td align="center" valign="top">bp</td>
<td align="center" valign="top">big point (72???bp = 1???in)</td>
</tr><tr>
<td align="center" valign="top">dd</td>
<td align="center" valign="top">didot (72???dd <m:math xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude">
<m:mrow><m:mo>???</m:mo>
</m:mrow>
</m:math> 37.6???mm)</td>
</tr><tr>
<td align="center" valign="top">cc</td>
<td align="center" valign="top">cicero (1???cc = 12???dd)</td>
</tr><tr>
<td align="center" valign="top">Scale%</td>
<td align="center" valign="top">% of original image width</td>
</tr><tr>
<td align="center" valign="top">text%</td>
<td align="center" valign="top">% of text width</td>
</tr><tr>
<td align="center" valign="top">col%</td>
<td align="center" valign="top">% of column width</td>
</tr><tr>
<td align="center" valign="top">page%</td>
<td align="center" valign="top">% of paper width</td>
</tr><tr>
<td align="center" valign="top">line%</td>
<td align="center" valign="top">% of line width</td>
</tr><tr>
<td align="center" valign="top">theight%</td>
<td align="center" valign="top">% of text height</td>
</tr><tr>
<td align="center" valign="top">pheight%</td>
<td align="center" valign="top">% of paper height</td>
</tr><tr>
<td align="center" valign="top">ex</td>
<td align="center" valign="top">height of letter x in current font</td>
</tr><tr>
<td align="center" valign="top">em</td>
<td align="center" valign="top">width of letter M in current font</td>
</tr><tr>
<td align="center" valign="top">mu</td>
<td align="center" valign="top">math unit (1???mu = 1/18???em)</td>
</tr></tbody></table></div></div></section><section class="section" title="The Manuals" epub:type="division" id="d0e606"><div class="titlepage"><div><div><h3 class="title">The Manuals</h3></div></div></div><p>The following list describes the contents of the basic documentation files that you find in the <span class="sans">Help</span> menu:</p><div class="variablelist" epub:type="list"><dl class="variablelist"><dt><span class="term">Introduction</span></dt><dd><p>This file.</p></dd><dt><span class="term">Tutorial</span></dt><dd><p>If you are new to LyX, and have never used LaTeX before, you should start here. If you have used LaTeX before, you should still read the <span class="emphasis"><em>Tutorial</em></span>, starting with the section on ???LyX for LaTeX users.??? (Skimming through the rest of the document wouldn't hurt, either.)</p></dd><dt><span class="term">User's??Guide</span></dt><dd><p>The primary documentation. We'll cover <span class="emphasis"><em>most</em></span> of the basic operation and available features of LyX here. The main manual assumes that you have read the <span class="emphasis"><em>Tutorial</em></span>.</p></dd><dt><span class="term">Embedded??Objects</span></dt><dd><p>Extension of the <span class="emphasis"><em>User's Guide</em></span>. Documents in detail how to use tables, graphics, floats, notes, program listings and boxes. It also includes many tricks of the LaTeX masters.</p></dd><dt><span class="term">Math</span></dt><dd><p>Extension of the <span class="emphasis"><em>User's Guide</em></span>. Documents in detail how to typeset any kind of formula.</p></dd><dt><span class="term">Additional??Features</span></dt><dd><p>Extension of the <span class="emphasis"><em>User's Guide</em></span>. Documents how to use raw LaTeX commands, additional layouts and special-purpose editing features.</p></dd><dt><span class="term">Customization</span></dt><dd><p>A description of advanced LyX features, including how to customize the overall behavior of LyX. This includes such things as keybindings, internationalization and configuration files. It also includes information about layout files, which are needed to get LyX to support LaTeX classes or packages.</p></dd><dt><span class="term">Shortcuts</span></dt><dd><p>Tables of the currently defined LyX shortcuts.</p></dd><dt><span class="term">LaTeX??Configuration</span></dt><dd><p>A report produced by LyX about your system. This file contains information on what LyX learned about your installation. Check it to see if you're missing something you might like to have.</p></dd></dl></div><p>These files will reference one another as necessary. For example, the <span class="emphasis"><em>User's Guide</em></span> contains <span class="emphasis"><em>some</em></span> information on installation and customization, but refers the reader to the <span class="emphasis"><em>Customization Manual</em></span> for more information.</p><p>We'll state again an important point:</p><p>If you are new to LyX, read the <span class="emphasis"><em>Tutorial</em></span>. Now.</p><p>Otherwise, you could needlessly frustrate yourself.</p></section></section><footer/></body></html>PK ??LR9?U?? ? OEBPS/ar01-toc.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Introduction to LyX</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/></head><body><header/><h1>Introduction to LyX</h1><div class="toc"><div class="toc-title">Table of Contents</div><nav epub:type="toc"><ol><li><a href="index.xhtml#d0e13">The Philosophy of LyX</a><ol><li><a href="index.xhtml#d0e16">What is LyX?</a></li><li><a href="index.xhtml#d0e66">Differences between LyX and Other Word Processors</a></li><li><a href="index.xhtml#d0e144">What is LaTeX?</a></li></ol></li><li><a href="ar01s02.xhtml">Navigating the Documentation</a><ol><li><a href="ar01s02.xhtml#d0e240">Where To Get Help</a></li><li><a href="ar01s02.xhtml#d0e252">The Format of the Manuals</a></li><li><a href="ar01s02.xhtml#d0e424">Units used in the Manuals</a></li><li><a href="ar01s02.xhtml#d0e606">The Manuals</a></li></ol></li><li><a href="ar01s03.xhtml">Contributing to the LyX Project</a><ol><li><a href="ar01s03.xhtml#d0e710">Contributing to LyX</a><ol hidden=""><li><a href="ar01s03.xhtml#d0e715">Reporting a bug</a></li><li><a href="ar01s03.xhtml#d0e734">Contributing fixes and new features</a></li></ol></li><li><a href="ar01s03.xhtml#d0e739">Contributing to the Documentation</a><ol hidden=""><li><a href="ar01s03.xhtml#d0e744">Reporting Errors in the Manuals</a></li><li><a href="ar01s03.xhtml#d0e751">Joining the Documentation Team.</a></li></ol></li></ol></li></ol></nav></div><div class="list-of-tables"><nav epub:type="lot"><h4 class="toc-title">List of Tables</h4><ol><li><a href="ar01s02.xhtml#tab.Units">1. Units</a></li></ol></nav></div><footer/></body></html>PK ??LR%*?? OEBPS/package.opf<?xml version="1.0" encoding="utf-8" standalone="no"?>
<package xmlns="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" version="3.0" xml:lang="en" unique-identifier="pub-identifier">
<metadata>
<dc:identifier id="pub-identifier">_d0e2</dc:identifier>
<meta id="meta-identifier" property="dcterms:identifier">_d0e2</meta>
<dc:title id="pub-title">Introduction to LyX</dc:title>
<meta property="dcterms:title" id="meta-title">Introduction to LyX</meta>
<dc:language id="pub-language">en</dc:language>
<meta property="dcterms:language" id="meta-language">en</meta>
<meta property="dcterms:modified">2021-02-12T21:22:13Z</meta><!--The preceding date value is actually local time (not UTC) in UTC format because there is no function in XSLT 1.0 to generate a correct UTC time-->
<meta id="meta-creator2" property="dcterms:creator">by the LyX Team[1]</meta>
<dc:creator id="pub-creator2">by the LyX Team[1]</dc:creator>
</metadata>
<manifest>
<item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml"/>
<item id="htmltoc" properties="nav" media-type="application/xhtml+xml" href="ar01-toc.xhtml"/>
<item media-type="text/css" id="docbook-css" href="docbook-epub.css"/>
<item id="id-d0e2" href="index.xhtml" media-type="application/xhtml+xml"/>
<item id="id-d0e224" href="ar01s02.xhtml" media-type="application/xhtml+xml" properties="mathml"/>
<item id="id-d0e707" href="ar01s03.xhtml" media-type="application/xhtml+xml"/>
<item id="d164e1" href="images/footnote.png" media-type="image/png"/>
<item id="d164e4" href="images/reference.png" media-type="image/png"/>
</manifest>
<spine toc="ncx">
<itemref idref="htmltoc" linear="yes"/>
<itemref idref="id-d0e2"/>
<itemref idref="id-d0e224"/>
<itemref idref="id-d0e707"/>
</spine>
<guide>
<reference href="ar01-toc.xhtml" type="toc" title="Table of Contents"/>
</guide>
</package>PK ??LR?5??O
O
OEBPS/toc.ncx<?xml version="1.0" encoding="utf-8" standalone="no"?><ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1"><head><meta name="dtb:uid" content="_d0e2"/></head><docTitle><text>Introduction to LyX</text></docTitle><navMap><navPoint id="d0e2" playOrder="1"><navLabel><text>Introduction to LyX</text></navLabel><content src="index.xhtml"/></navPoint><navPoint id="d0e13" playOrder="2"><navLabel><text>The Philosophy of LyX</text></navLabel><content src="index.xhtml#d0e13"/><navPoint id="d0e16" playOrder="3"><navLabel><text>What is LyX?</text></navLabel><content src="index.xhtml#d0e16"/></navPoint><navPoint id="d0e66" playOrder="4"><navLabel><text>Differences between LyX and Other Word Processors</text></navLabel><content src="index.xhtml#d0e66"/></navPoint><navPoint id="d0e144" playOrder="5"><navLabel><text>What is LaTeX?</text></navLabel><content src="index.xhtml#d0e144"/></navPoint></navPoint><navPoint id="d0e224" playOrder="6"><navLabel><text>Navigating the Documentation</text></navLabel><content src="ar01s02.xhtml"/><navPoint id="d0e240" playOrder="7"><navLabel><text>Where To Get Help</text></navLabel><content src="ar01s02.xhtml#d0e240"/></navPoint><navPoint id="d0e252" playOrder="8"><navLabel><text>The Format of the Manuals</text></navLabel><content src="ar01s02.xhtml#d0e252"/></navPoint><navPoint id="d0e424" playOrder="9"><navLabel><text>Units used in the Manuals</text></navLabel><content src="ar01s02.xhtml#d0e424"/></navPoint><navPoint id="d0e606" playOrder="10"><navLabel><text>The Manuals</text></navLabel><content src="ar01s02.xhtml#d0e606"/></navPoint></navPoint><navPoint id="d0e707" playOrder="11"><navLabel><text>Contributing to the LyX Project</text></navLabel><content src="ar01s03.xhtml"/><navPoint id="d0e710" playOrder="12"><navLabel><text>Contributing to LyX</text></navLabel><content src="ar01s03.xhtml#d0e710"/><navPoint id="d0e715" playOrder="13"><navLabel><text>Reporting a bug</text></navLabel><content src="ar01s03.xhtml#d0e715"/></navPoint><navPoint id="d0e734" playOrder="14"><navLabel><text>Contributing fixes and new features</text></navLabel><content src="ar01s03.xhtml#d0e734"/></navPoint></navPoint><navPoint id="d0e739" playOrder="15"><navLabel><text>Contributing to the Documentation</text></navLabel><content src="ar01s03.xhtml#d0e739"/><navPoint id="d0e744" playOrder="16"><navLabel><text>Reporting Errors in the Manuals</text></navLabel><content src="ar01s03.xhtml#d0e744"/></navPoint><navPoint id="d0e751" playOrder="17"><navLabel><text>Joining the Documentation Team.</text></navLabel><content src="ar01s03.xhtml#d0e751"/></navPoint></navPoint></navPoint></navMap></ncx>PK ??LRU?? ? OEBPS/ar01s03.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Contributing to the LyX Project</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/><link rel="prev" href="ar01s02.xhtml" title="Navigating the Documentation"/></head><body><header/><section class="section" title="Contributing to the LyX Project" epub:type="division" id="sec.Contrib"><div class="titlepage"><div><div><h2 class="title" style="clear: both">Contributing to the LyX Project</h2></div></div></div><section class="section" title="Contributing to LyX" epub:type="division" id="d0e710"><div class="titlepage"><div><div><h3 class="title">Contributing to LyX</h3></div></div></div><p>LyX is mostly written in C++ (the LaTeX importer is written in Python). It is a large project, and as a result it is not free from bugs, or the need for improvements in the source code.</p><section class="section" title="Reporting a bug" epub:type="division" id="d0e715"><div class="titlepage"><div><div><h4 class="title">Reporting a bug</h4></div></div></div><p>While using LyX, you may find behavior which you consider a bug. Crashes, though rare, can happen. User interface problems are considered major bugs by the LyX team: especially helpful are indications of parts of the LyX interface you find confusing, or unclear.</p><p>LyX has a bug tracking system, which you can find at</p><p><a class="link" href="https://www.lyx.org/trac/wiki/BugTrackerHome" target="_top">https://www.lyx.org/trac/wiki/BugTrackerHome</a>. You should check the bug tracker before reporting any bugs, in case it has already been reported. If you have a comment on an existing bug, or wish to report a new bug, you may either use the bug tracker, or send an e-mail to the development mailing list, <a class="link" href="lyx-devel at lists.lyx.org" target="_top">lyx-devel at lists.lyx.org</a>. Archives of this list are linked from the main LyX website, <a class="link" href="http://www.lyx.org" target="_top">http://www.lyx.org</a>.</p><p>A useful bug report will at a minimum include the version of LyX you are having the problem with. Accurate, detailed descriptions are preferred ??? the more time developers have to spend to pinpoint the source of a bug, the less time they have for other improvements. Mention the system and system version on which you are running LyX. Give the versions of the libraries you have installed on your system, and, if relevant, the versions of external programs that LyX uses. If it's a compilation or configuration problem, include the file <code class="code">config.log</code>, and mention which compiler you are using.</p></section><section class="section" title="Contributing fixes and new features" epub:type="division" id="d0e734"><div class="titlepage"><div><div><h4 class="title">Contributing fixes and new features</h4></div></div></div><p>If you have made changes to LyX's source that you think should become part of LyX, send your changes as a diff file (in unified format) to the development list referenced above, along with a change log, and a description of what your patch does.</p></section></section><section class="section" title="Contributing to the Documentation" epub:type="division" id="d0e739"><div class="titlepage"><div><div><h3 class="title">Contributing to the Documentation</h3></div></div></div><p>LyX's documentation is extensive; however LyX is under constant development, and each new release adds new features. You may find some documentation needs improvement. This section describes what to do if you find an error, or have some suggestions for improving the documentation.</p><section class="section" title="Reporting Errors in the Manuals" epub:type="division" id="d0e744"><div class="titlepage"><div><div><h4 class="title">Reporting Errors in the Manuals</h4></div></div></div><p>If you find a problem with the documentation, send a message to the mailing list <a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a>. The documentation team will make any necessary fixes.</p></section><section class="section" title="Joining the Documentation Team." epub:type="division" id="d0e751"><div class="titlepage"><div><div><h4 class="title">Joining the Documentation Team.</h4></div></div></div><p>The LyX Documentation Project, like anything else in the LyX project, can always use assistance! If you're interested in contributing to the Documentation Project, you need to do the following:</p><div class="orderedlist" epub:type="list"><ol class="orderedlist" type="1"><li class="listitem" epub:type="list-item"><p>Get the latest LyX source code from</p><p> <a class="link" href="https://www.lyx.org/trac/browser/lyxgit/lib/doc?rev=master " target="_top">https://www.lyx.org/trac/browser/lyxgit/lib/doc?rev=master </a></p></li><li class="listitem" epub:type="list-item"><p>Next, read the <span class="emphasis"><em>User's Guide</em></span> and the <span class="emphasis"><em>Tutorial</em></span></p><p>The point of this exercise is to give you ideas. The <span class="emphasis"><em>Tutorial</em></span> and <span class="emphasis"><em>User's Guide</em></span> are likely to be the most up-to-date of all of the documentation. You should be able to glean some insights into how we want the manuals to read and to look.</p></li><li class="listitem" epub:type="list-item"><p>Contact the team at:</p><p><a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a></p><p>to discuss your intended changes and to get some feedback on them.</p></li></ol></div><p>The changes you wish to make may range from improving clarity of the text, to doing major re-structuring of the documentation. Any and all improvements are gladly received.</p></section></section></section><footer/></body></html>PK ??LR[?r=? ? OEBPS/docbook-epub.css
/********************************/
/* start of styles in block.xsl */
.formalpara-title {
font-weight: bold;
}
div.blockquote-title {
font-weight: bold;
margin-top: 1em;
margin-bottom: 1em;
}
span.msgmain-title {
font-weight: bold;
}
span.msgsub-title {
font-weight: bold;
}
span.msgrel-title {
font-weight: bold;
}
div.msglevel, div.msgorig, div.msgaud {
margin-top: 1em;
margin-bottom: 1em;
}
span.msglevel-title, span.msgorig-title, span.msgaud-title {
font-weight: bold;
}
div.msgexplan {
margin-top: 1em;
margin-bottom: 1em;
}
span.msgexplan-title {
font-weight: bold;
}
div.sidebar {
border: 0.5pt solid black;
margin-top: 1em;
margin-bottom: 1em;
padding: 8px;
}
/* end of styles in block.xsl */
/********************************/
/********************************/
/* start of styles in autotoc.xsl */
/* top level entries */
nav>ol>li>a {
margin-top: 1em;
margin-bottom: 1em;
}
/* end of styles in autotoc.xsl */
/********************************/
/********************************/
/* start of styles in formal.xsl */
div.figure-title {
font-weight: bold;
}
div.example-title {
font-weight: bold;
}
div.equation-title {
font-weight: bold;
}
div.table-title {
font-weight: bold;
}
div.sidebar-title {
font-weight: bold;
}
/* end of styles in formal.xsl */
/********************************/
/********************************/
/* start of styles in verbatim.xsl */
div.programlisting {
white-space: pre-wrap;
font-family: monospace;
}
div.screen {
white-space: pre-wrap;
font-family: monospace;
}
div.synopsis {
white-space: pre-wrap;
font-family: monospace;
}
/* end of styles in verbatim.xsl */
/********************************/
/********************************/
/* NAVIGATION */
nav ol {
list-style-type: none;
margin: 0 0 0 2em;
padding: 0 0 0 0;
}
nav ol li {
margin: 0 0 0 0;
padding: 0 0 0 0;
}
nav ol li a {
text-decoration: none;
color: black;
font-family: sans-serif;
}
#guide {
display: none;
}
PK ??LRN??,E E OEBPS/images/footnote.png?PNG
IHDR & ?? ? sRGB ?? ? gAMA ?? ?a pHYs ? ??o?d ?IDATHK??1? E=???0^? ???+:Z????ug ?Y?%H?&? ?3?? V/9???I??k??h\?Y??"0}?????UW
?? ?p?I???q??(X??N??*T???4????ae??W
?t?:??????i[?|$,????0?4????%\:???$?lH?i??J??????;r>i?<???9? ? ? ?b??Z???? oRq?????k3??7 IEND?B`?PK ??LR??{? ? OEBPS/images/reference.png?PNG
IHDR ???x sRGB ?? ? gAMA ?? ?a pHYs ? ??o?d uIDAThC?V;r1 ?B?0?dg(?4T?a;:n@?-=5u?l??v??k^?x?yz? 6_?GG+t?[???]?????DW?%X??y??l?$~???]S????F??;?a??Z?k?f?dR??7??? TG\o??Y>y *D??{?8??
?|??V_F?U??2??T??i??????^???m;?
??????a F?2?_h??tTY??\y?h??U!}?9?'NX0???????\,?bI#?s?L?B??cXi?6%??%H??J9?\???OXr}@??(
????????9co??QR2?h8h???;H?DC??'?Rp ??OZk?M!O??V???}
???5>???^?vh?k?b6#?1?]??6?# ???\??j?J??????2? ?Y^??^???3?? :8????Ft?S?C#??4?f???:??????<&am???kJyQN?5~??Yqv??R?d3Vwh`???C???Z??????' ??*??b?J?N???????iqB'f??+??x??f????I m??Yb`?>;?L? ?O???-(8??? ?1 ?Q&!?F?p|??S?? q?B ?a?QB??`? ?I????,Hf`?C?i`?fTBB-?(????GW?%??-??o??~;< ?%nl\??? IEND?B`?PK ??LRa??? ? META-INF/container.xml<?xml version="1.0" encoding="utf-8" standalone="no"?><container xmlns="urn:oasis:names:tc:opendocument:xmlns:container" version="1.0"><rootfiles><rootfile full-path="OEBPS/package.opf" media-type="application/oebps-package+xml"/></rootfiles></container>PK ??LRoa?, ?? mimetypePK ??LR????> ?> ??: OEBPS/index.xhtmlPK ??LR?7? 7 7 ??g? OEBPS/ar01s02.xhtmlPK ??LR9?U?? ? ???v OEBPS/ar01-toc.xhtmlPK ??LR%*?? ???~ OEBPS/package.opfPK ??LR?5??O
O
???? OEBPS/toc.ncxPK ??LRU?? ? ??K? OEBPS/ar01s03.xhtmlPK ??LR[?r=? ? ??e? OEBPS/docbook-epub.cssPK ??LRN??,E E ??u? OEBPS/images/footnote.pngPK ??LR??{? ? ???? OEBPS/images/reference.pngPK ??LRa??? ? ?? ? META-INF/container.xmlPK ? ;?
-------------- next part --------------
PK v?LRoa?, mimetypeapplication/epub+zipPK v?LR?????> ?> OEBPS/index.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Introduction to LyX</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/><link rel="next" href="ar01s02.xhtml" title="Navigating the Documentation"/></head><body><header/><section xml:lang="en_US" class="article" title="Introduction to LyX" id="idm1"><div class="titlepage"><div><div><h1 class="title">Introduction to LyX</h1></div><div><div class="author"><h3 class="author">by the LyX Team<a href="#ftn.idm6" class="footnote"><sup class="footnote" id="idm6">[1]</sup></a></h3></div></div></div><hr/></div><section class="section" title="The Philosophy of LyX" epub:type="division" id="idm9"><div class="titlepage"><div><div><h2 class="title" style="clear: both">The Philosophy of LyX</h2></div></div></div><section class="section" title="What is LyX?" epub:type="division" id="idm11"><div class="titlepage"><div><div><h3 class="title">What is LyX?</h3></div></div></div><p>LyX is a document preparation system. It excels at letting you create complex technical and scientific articles with mathematics, cross-references, bibliographies, indexes, etc. It is very good for working with documents of any length in which the usual processing abilities are required: automatic sectioning and pagination, spell checking and so forth. It can also be used to write a letter to your mom, though granted, there are probably simpler programs available for that. It is definitely not the best tool for creating banners, flyers, or advertisements (we'll explain why later), though with some effort all these can be done, too. Here are some examples of what it is used for: memos, letters, dissertations and theses, lecture notes, seminar notebooks, conference proceedings, software documentation, books, articles in refereed scientific journals, scripts for plays and movies, business proposals, presentations ???</p><p>LyX is a program that provides a modern approach to writing documents with a computer by using a markup language paradigm, an approach that breaks with the obsolete tradition of the ???typewriter concept???. It is designed for authors who want professional output quickly with a minimum of effort and without becoming specialists in typesetting. The job of typesetting is done mostly by the computer, not the author; with LyX, the author can concentrate on the contents of his writing.</p><p>Part of the initial challenge of using LyX comes from the change in thinking that you, the user, must make. At one time, all we had for creating documents were typewriters, so we all learned certain tricks to get around their limitations. Underlining, which is little more than overstriking with the ???_??? character, became a way to emphasize text. You were forced to figure out column sizes and tab stops, and set them, before creating a table. The same applied for letters and other right justified text. Hyphenation at the end of a line required a careful eye and a lot of foresight.</p><p>In other words, we've all been trained to worry about the little details of which character goes where. Consequently, almost all word processors have this mentality. They still use tab stops for adding whitespace. You still need to worry about exactly where on the page something will appear. Emphasizing text means changing a font, similar to changing the typewriter wheel. This is the underlying philosophy of a WYSIWYG word processor: ???What You See Is What You Get???. Unfortunately, that paradigm often results in ???What You See Is All You Get???.</p><p>This is where LyX differs from an ordinary word processor. You don't concern yourself with what character goes where. You tell LyX <span class="emphasis"><em>what you're doing</em></span> and LyX takes care of the rest, following a set of rules called a <span class="emphasis"><em>style</em></span>.<a href="#ftn.idm20" class="footnote"><sup class="footnote" id="idm20">[2]</sup></a> Let's look at a little example:</p><p>Suppose you are writing a report. To begin your report, you want a section called ???Introduction.??? So, you go into whatever menu it is in your word processor that changes font sizes and decide on a new font size. Then you turn on bold face. Then you type, ???1.????Introduction???. Of course, if you later decide that this section belongs someplace else in the document or if you insert a new section before it, you need to change the numbering for this and all following sections, as well as any entry in the table of contents.</p><p>In LyX, you go to the pull-down on the far left of the button bar and select <span class="sans">Section</span>, and type ???Introduction???.</p><p>Yes, that's all. If you cut and paste the section, it will automatically be renumbered ??? everywhere. And if you enter references to that section correctly (by inserting cross-reference tags), LyX will automatically update them all throughout the file so that you never, ever type a section number.</p><p>Now let's look at the problem of consistency. Five days later, you reopen your report and start Section??4. However, you forget that you were using 18???pt bold instead of 16???pt, so you type in the heading for Section??4 in a different font from the one you used for Section??1. That problem doesn't even exist in LyX. The computer takes care of all that silly bookkeeping about which thing has what size font, not you. After all, that's what a computer is good at.</p><p>Here's another example. Suppose you're making a list. In other word processors, a list is just a bunch of tab stops and newlines. You need to figure out where to put the label for each list item, what that label should be, how many blank lines to put between each item, and so on. Under LyX, you have only two concerns: what kind of list is this, and what do I want to put in it? That is it.</p><p>So, the basic idea behind LyX is: specify <span class="emphasis"><em>what</em></span> you're doing, not <span class="emphasis"><em>how</em></span> to do it. Instead of ???What You See Is What You Get,??? the LyX model is ???What You See Is What You <span class="emphasis"><em>Mean</em></span>??? or ???WYSIWYM.??? It's a powerful idea that greatly simplifies the mechanics of writing documents. This is also why LyX isn't so good for creating posters and flyers. In this case, you <span class="emphasis"><em>do</em></span> want to specify exactly where everything goes, because there are no functional units like paragraphs, sections, etc. This doesn't mean LyX is missing some cool function. It simply means that it isn't the right tool for the job ??? you don't use a screwdriver to drive in nails.</p></section><section class="section" title="Differences between LyX and Other Word Processors" epub:type="division" id="idm33"><div class="titlepage"><div><div><h3 class="title">Differences between LyX and Other Word Processors</h3></div></div></div><p>Here's a list of things you won't find in LyX:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>The document ruler</p></li><li class="listitem" epub:type="list-item"><p>Tab stops</p></li><li class="listitem" epub:type="list-item"><p>Extra whitespace (e.???g. hitting <span class="sans">Enter</span> or <span class="sans">Space</span> two or more times)</p></li></ul></div><p>Tab stops, along with a ruler showing you the position of things on the page, are useless in LyX. The program worries about where things go on the page, not you. Extra whitespace is similar; LyX adds it where necessary, depending on context. Not being able to type two blank lines in a row will be annoying at first, but it makes more sense once you're thinking in WYSIWYM terms.</p><p>Here are some things that exist in LyX, but aren't used as you might think:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>Indenting controls</p></li><li class="listitem" epub:type="list-item"><p>Page breaks</p></li><li class="listitem" epub:type="list-item"><p>Line spacing (e.???g. single spaced, double spaced, etc.)</p></li><li class="listitem" epub:type="list-item"><p>Whitespace, horizontal and vertical</p></li><li class="listitem" epub:type="list-item"><p>Fonts and font sizes</p></li><li class="listitem" epub:type="list-item"><p>Typefaces (bold, italic, underline, etc.)</p></li></ul></div><p>Although they exist in LyX, you generally don't need them. LyX will take care of these things for you, depending on what you're doing. Different parts of the document are automatically set in a different typeface and font size. Paragraph indenting is context dependent; different types of paragraphs get indented differently. Page breaks get handled automatically, as well. In general, the space between lines, between words, and between paragraphs is variable, set by LyX.<a href="#ftn.idm61" class="footnote"><sup class="footnote" id="idm61">[3]</sup></a></p><p>Lastly, there are a few areas where we believe LyX (and LaTeX) surpasses many word processors:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>Hyphenation</p></li><li class="listitem" epub:type="list-item"><p>Lists of any type</p></li><li class="listitem" epub:type="list-item"><p>Mathematics</p></li><li class="listitem" epub:type="list-item"><p>Tables</p></li><li class="listitem" epub:type="list-item"><p>Cross-referencing</p></li></ul></div><p>Granted, many modern word processors can handle mathematical symbols, tables, and hyphenation, and many have moved towards style definitions and the WYSIWYM concept. However, they've only recently been able to do so, whereas LyX is built upon the LaTeX document preparation system. LaTeX has been around since 1985, and <span class="emphasis"><em>works</em></span>.</p></section><section class="section" title="What is LaTeX?" epub:type="division" id="idm79"><div class="titlepage"><div><div><h3 class="title">What is LaTeX?</h3></div></div></div><p>LaTeX is a document preparation system designed by Leslie Lamport in 1985.<a href="#ftn.idm82" class="footnote"><sup class="footnote" id="idm82">[4]</sup></a> It was built up from a typesetting language called TeX, created by Donald Knuth in 1984. TeX takes a sequence of typesetting commands, written in a script in an ASCII file, and executes them. Many of the ???tricks??? of the printing trade were modeled by Knuth as computer algorithms and incorporated into TeX, hence its excellent printed appearance. What comes directly out of TeX is the portable document format <span class="emphasis"><em>pdf</em></span> or the so-called ???device independent??? format file <span class="emphasis"><em>dvi</em></span>. The dvi format is often used for previews and can later be converted to other formats like PostScript. </p><p>TeX isn't only a typesetting engine; it also allows you to define macros. Most people who use TeX are actually using a macro package which Knuth created to hide a lot of the typesetting details. This is where Leslie Lamport enters our story. He wanted a macro package that was more user- and less typesetter-oriented, with a set of commands that consistently typeset things like sections, tables or math formulas in a uniform, consistent fashion. This is how LaTeX was born.</p><p>Now, in parallel with the development and growth of LaTeX, other folks were creating their own custom macro packages for TeX, ones to make slides or articles for math journals and so on. Some used the raw TeX facilities to do this, others began modifying LaTeX. To try and unify this mess, a team of LaTeX-nicians began to work on LaTeX2??, the current version of LaTeX, during the late 1980's. This new version of LaTeX has commands which provide an easier-to-use interface to TeX's macro-creating commands, aid in the use of new fonts, and so on. In fact, LaTeX is quite an extensive language in its own right! Users around the world have been creating their own add-ons for LaTeX beyond the standard ones.</p><p>There are two ways to extend LaTeX: classes and styles. A <span class="emphasis"><em>class</em></span> is a set of LaTeX macros describing a new type of document, like a book, or an article. There are classes for slides, for physics and math journals??? many universities even have a class for their thesis format. A <span class="emphasis"><em>style</em></span> differs from a class in that it doesn't define a new type of document, but a different type of <span class="emphasis"><em>behavior</em></span> that any document can use. For example, LyX controls page margins and line spacing using two different LaTeX style-files designed for these purposes. There are style-files for a whole slew of things: printing labels or envelopes, changing indentation behavior, adding new fonts, manipulating graphics, designing fancy page headings, customizing bibliographies, altering the location and appearance of footnotes, tables, and figures, customizing lists, etc.</p><p>Here is a summary:</p><div class="variablelist" epub:type="list"><dl class="variablelist"><dt><span class="term">TeX:</span></dt><dd><p>Typesetting language with macro capability.</p></dd><dt><span class="term">LaTeX:</span></dt><dd><p>Macro package built upon TeX.</p></dd><dt><span class="term">classes:</span></dt><dd><p>Descriptions of types of document used with LaTeX.</p></dd><dt><span class="term">styles:</span></dt><dd><p>Descriptions of the default behavior of particular elements of LaTeX.</p></dd><dt><span class="term">LyX:</span></dt><dd><p>Visual, WYSIWYM document processor that uses LaTeX to do its typesetting.</p></dd></dl></div><p>This section attempts to explain the difference between LyX and a word processor. Simply put, LaTeX is the difference. By using LaTeX as its backend, LyX helps you to think more about<span class="emphasis"><em> what</em></span> (as in the <span class="emphasis"><em>words</em></span>) you write. The computer then handles <span class="emphasis"><em>how</em></span> they should look.</p></section></section><div class="footnotes" epub:type="footnotes"><br/><hr class="footnote-hr"/><div id="ftn.idm6" class="footnote" epub:type="footnote"><p><a href="#idm6" class="para"><sup class="para">[1] </sup></a>If you have comments on or corrections to this documentation, please send them to the LyX Documentation mailing list: <a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a></p></div><div id="ftn.idm20" class="footnote" epub:type="footnote"><p><a href="#idm20" class="para"><sup class="para">[2] </sup></a>To be fair, most recent versions of the most popular office suites now have some sort of style sheets which follow a similar markup method. However, our experience is that they are still rarely used in practice.</p></div><div id="ftn.idm61" class="footnote" epub:type="footnote"><p><a href="#idm61" class="para"><sup class="para">[3] </sup></a>There are ways to adjust all of these (only some of which require knowledge of LaTeX), either for a whole document or for a specific location in a document. See the <span class="emphasis"><em>User's Guide</em></span> and/or the <span class="emphasis"><em>Additional Features</em></span> manual for details.</p></div><div id="ftn.idm82" class="footnote" epub:type="footnote"><p><a href="#idm82" class="para"><sup class="para">[4] </sup></a>The source for the info in this section is <span class="emphasis"><em>A Guide to LaTeX2??</em></span>, by Helmut Kopka and Patrick Daly, which has an entry in the bibliography of the <span class="emphasis"><em>User's Guide</em></span>.</p></div></div></section><footer/></body></html>PK v?LR0????6 ?6 OEBPS/ar01s02.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Navigating the Documentation</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/><link rel="prev" href="index.xhtml" title="Introduction to LyX"/><link rel="next" href="ar01s03.xhtml" title="Contributing to the LyX Project"/></head><body><header/><section class="section" title="Navigating the Documentation" epub:type="division" id="idm120"><div class="titlepage"><div><div><h2 class="title" style="clear: both">Navigating the Documentation</h2></div></div></div><p>To make it easier to answer your questions and describe all of the features of LyX, the documentation has been split up into several different files. Each one has its own purpose, as described below. Before you go ploughing into any of those files, however, you should read this chapter thoroughly, since it contains a lot of useful information and commentary that can save you some time.</p><p>Hopefully, the development of LyX will never stop; so some of the documentation may be incomplete or a bit out of date, though we try to keep up-to-date. Like the rest of LyX, the manuals are the work of a group of volunteers who have ???Real Jobs???, families, dishes to clean, <span class="emphasis"><em>et cetera</em></span>. If you want to help out, be sure to read Section??<a class="xref" href="ar01s03.xhtml" title="Contributing to the LyX Project">the section called ???Contributing to the LyX Project???</a> in addition to the rest of this document.</p><p>Also, please do us a favor: if anything in these manuals confuses you, is unclear, or wrong, don't hesitate to let us know! You can reach the current document maintainers by emailing <a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a>. </p><section class="section" title="Where To Get Help" epub:type="division" id="idm128"><div class="titlepage"><div><div><h3 class="title">Where To Get Help</h3></div></div></div><p>If you have questions that are not obviously answered in the documentation and need help fast, there is an active users' mailing list which you can reach at <a class="link" href="lyx-users at lists.lyx.org" target="_top">lyx-users at lists.lyx.org</a>. You do not have to register to post, but you may wish to do so. See <a class="link" href="https://www.lyx.org/MailingLists" target="_top">the LyX website</a> for further information. LyX also has a <a class="link" href="http://wiki.lyx.org/" target="_top">http://wiki.lyx.org/</a> that will answer many questions about how to get LyX to do various things.</p></section><section class="section" title="The Format of the Manuals" epub:type="division" id="idm134"><div class="titlepage"><div><div><h3 class="title">The Format of the Manuals</h3></div></div></div><p>Some of you may have printed out the manuals. Others may be reading them within LyX. There are some differences between the LyX-file and the printed version. In LyX, the title is simply at the top of the document, not formatted on a separate page as in some of the printed versions. Nor are any of the footnotes or the Table of Contents fully visible. To open a footnote, which looks like this: <span class="inlinemediaobject"><img src="images/footnote.png" width="513"/></span>
, click on it with the left mouse button. For the Table of Contents, either click on the grey box or click on the <span class="sans">Navigate</span> menu, where the contents are displayed automatically.</p><p>In the printed manuals, all cross-references appear as the actual numbers for a chapter, section, subsection, and so on. In the LyX-file, however, all cross-references appear as light-grey boxes like the following: <span class="inlinemediaobject"><img src="images/reference.png" width="513"/></span>
. If you click on such a box with the left mouse button, a dialog box will appear containing a list of all the cross-references in the document. You can go to the referenced section by right-clicking on the box or by clicking the button <span class="sans">Go??to??Label</span> in the opened dialog. Going back to where you came from is just as easy. Click on <span class="sans">Go??Back</span> to go back to your earlier location.</p><p>Now that we've cleared up some of the differences between the printed and LyX-file versions of this file, we can start looking at the format of this document. You'll occasionally notice things in different fonts:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p><span class="emphasis"><em>Emphasized Style</em></span> is used for general emphasis, generic arguments, book titles, names of sections of other manuals, and notes from the authors.</p></li><li class="listitem" epub:type="list-item"><p><code class="code">Typewriter</code> is used for program and file names, LyX code and functions.</p></li><li class="listitem" epub:type="list-item"><p><span class="sans">Sans Serif</span> is used for menu, button, or dialog box names, and the names of keyboard keys.</p></li><li class="listitem" epub:type="list-item"><p><span class="personname">Noun Style</span> is used for people's names.</p></li><li class="listitem" epub:type="list-item"><p><span class="bold"><strong>Bold</strong></span> is used for LaTeX code</p></li></ul></div><p>When we do need to reference keys, we'll use the following prefixing convention:</p><div class="itemizedlist" epub:type="list"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem" epub:type="list-item"><p>???<span class="sans">Ctrl+</span>??? indicates the <span class="sans">Control</span> key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Shift+</span>??? indicates the <span class="sans">Shift</span> key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Alt+</span>??? indicates the <span class="sans">Alt</span> (<span class="sans">Meta</span>) key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">F1</span>??? ??? ???<span class="sans">F12</span>??? are the function keys.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Esc</span>??? is the escape key.</p></li><li class="listitem" epub:type="list-item"><p>???<span class="sans">Left</span>??? ???<span class="sans">Right</span>??? ???<span class="sans">Up</span>??? ???<span class="sans">Down</span>???: self-explanatory.</p></li><li class="listitem" epub:type="list-item"><p><span class="sans">???Insert</span>??? ???<span class="sans">Delete</span>??? ???<span class="sans">Home</span>??? ???<span class="sans">End</span>??? ???<span class="sans">PageUp</span>??? ???<span class="sans">PageDown</span>???: these are the 6??keys that appear above the cursor keys on many PC keyboards. ???<span class="sans">PageUp</span>??? and ???<span class="sans">PageDown</span>??? are called ???<span class="sans">Prior</span>??? and ???<span class="sans">Next</span>??? on some keyboards.</p></li><li class="listitem" epub:type="list-item"><p><span class="sans">Return</span> and <span class="sans">Enter</span> both refer to the same key. Some keyboards label the <span class="sans">Return</span> key as ???Return,??? others as ???Enter,??? still others have two keys. LyX treats all of them as the same key, so we'll use <span class="sans">Return</span> and <span class="sans">Enter</span> interchangeably.</p></li></ul></div><p>The list with the currently set shortcuts can be found in the <span class="sans">Help</span> menu under <span class="sans">Shortcuts</span>.</p></section><section class="section" title="Units used in the Manuals" epub:type="division" id="idm214"><div class="titlepage"><div><div><h3 class="title">Units used in the Manuals</h3></div></div></div><p>To understand the units described in this documentation, Table??<a class="xref" href="ar01s02.xhtml#tab.Units" title="Table??1.??Units">Table??1, ???Units???</a> explains all units available in LyX.</p><div class="table" id="tab.Units"><div class="table-title">Table??1.??Units</div><div class="table-contents"><table xml:id="tab.Units"><tbody><tr>
<td align="center" valign="top">unit</td>
<td align="center" valign="top">name/description</td>
</tr><tr>
<td align="center" valign="top">mm</td>
<td align="center" valign="top">millimeter</td>
</tr><tr>
<td align="center" valign="top">cm</td>
<td align="center" valign="top">centimeter</td>
</tr><tr>
<td align="center" valign="top">in</td>
<td align="center" valign="top">inch (1???in = 2.54???cm)</td>
</tr><tr>
<td align="center" valign="top">pt</td>
<td align="center" valign="top">point (72.27???pt = 1???in)</td>
</tr><tr>
<td align="center" valign="top">pc</td>
<td align="center" valign="top">pica (1???pc = 12???pt)</td>
</tr><tr>
<td align="center" valign="top">sp</td>
<td align="center" valign="top">scaled point (65536???sp = 1???pt)</td>
</tr><tr>
<td align="center" valign="top">bp</td>
<td align="center" valign="top">big point (72???bp = 1???in)</td>
</tr><tr>
<td align="center" valign="top">dd</td>
<td align="center" valign="top">didot (72???dd <m:math>
<m:mrow><m:mo>???</m:mo>
</m:mrow>
</m:math> 37.6???mm)</td>
</tr><tr>
<td align="center" valign="top">cc</td>
<td align="center" valign="top">cicero (1???cc = 12???dd)</td>
</tr><tr>
<td align="center" valign="top">Scale%</td>
<td align="center" valign="top">% of original image width</td>
</tr><tr>
<td align="center" valign="top">text%</td>
<td align="center" valign="top">% of text width</td>
</tr><tr>
<td align="center" valign="top">col%</td>
<td align="center" valign="top">% of column width</td>
</tr><tr>
<td align="center" valign="top">page%</td>
<td align="center" valign="top">% of paper width</td>
</tr><tr>
<td align="center" valign="top">line%</td>
<td align="center" valign="top">% of line width</td>
</tr><tr>
<td align="center" valign="top">theight%</td>
<td align="center" valign="top">% of text height</td>
</tr><tr>
<td align="center" valign="top">pheight%</td>
<td align="center" valign="top">% of paper height</td>
</tr><tr>
<td align="center" valign="top">ex</td>
<td align="center" valign="top">height of letter x in current font</td>
</tr><tr>
<td align="center" valign="top">em</td>
<td align="center" valign="top">width of letter M in current font</td>
</tr><tr>
<td align="center" valign="top">mu</td>
<td align="center" valign="top">math unit (1???mu = 1/18???em)</td>
</tr></tbody></table></div></div></section><section class="section" title="The Manuals" epub:type="division" id="idm286"><div class="titlepage"><div><div><h3 class="title">The Manuals</h3></div></div></div><p>The following list describes the contents of the basic documentation files that you find in the <span class="sans">Help</span> menu:</p><div class="variablelist" epub:type="list"><dl class="variablelist"><dt><span class="term">Introduction</span></dt><dd><p>This file.</p></dd><dt><span class="term">Tutorial</span></dt><dd><p>If you are new to LyX, and have never used LaTeX before, you should start here. If you have used LaTeX before, you should still read the <span class="emphasis"><em>Tutorial</em></span>, starting with the section on ???LyX for LaTeX users.??? (Skimming through the rest of the document wouldn't hurt, either.)</p></dd><dt><span class="term">User's??Guide</span></dt><dd><p>The primary documentation. We'll cover <span class="emphasis"><em>most</em></span> of the basic operation and available features of LyX here. The main manual assumes that you have read the <span class="emphasis"><em>Tutorial</em></span>.</p></dd><dt><span class="term">Embedded??Objects</span></dt><dd><p>Extension of the <span class="emphasis"><em>User's Guide</em></span>. Documents in detail how to use tables, graphics, floats, notes, program listings and boxes. It also includes many tricks of the LaTeX masters.</p></dd><dt><span class="term">Math</span></dt><dd><p>Extension of the <span class="emphasis"><em>User's Guide</em></span>. Documents in detail how to typeset any kind of formula.</p></dd><dt><span class="term">Additional??Features</span></dt><dd><p>Extension of the <span class="emphasis"><em>User's Guide</em></span>. Documents how to use raw LaTeX commands, additional layouts and special-purpose editing features.</p></dd><dt><span class="term">Customization</span></dt><dd><p>A description of advanced LyX features, including how to customize the overall behavior of LyX. This includes such things as keybindings, internationalization and configuration files. It also includes information about layout files, which are needed to get LyX to support LaTeX classes or packages.</p></dd><dt><span class="term">Shortcuts</span></dt><dd><p>Tables of the currently defined LyX shortcuts.</p></dd><dt><span class="term">LaTeX??Configuration</span></dt><dd><p>A report produced by LyX about your system. This file contains information on what LyX learned about your installation. Check it to see if you're missing something you might like to have.</p></dd></dl></div><p>These files will reference one another as necessary. For example, the <span class="emphasis"><em>User's Guide</em></span> contains <span class="emphasis"><em>some</em></span> information on installation and customization, but refers the reader to the <span class="emphasis"><em>Customization Manual</em></span> for more information.</p><p>We'll state again an important point:</p><p>If you are new to LyX, read the <span class="emphasis"><em>Tutorial</em></span>. Now.</p><p>Otherwise, you could needlessly frustrate yourself.</p></section></section><footer/></body></html>PK v?LRPo? ? ? OEBPS/ar01-toc.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Introduction to LyX</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/></head><body><header/><h1>Introduction to LyX</h1><div class="toc"><div class="toc-title">Table of Contents</div><nav epub:type="toc"><ol><li><a href="index.xhtml#idm9">The Philosophy of LyX</a><ol><li><a href="index.xhtml#idm11">What is LyX?</a></li><li><a href="index.xhtml#idm33">Differences between LyX and Other Word Processors</a></li><li><a href="index.xhtml#idm79">What is LaTeX?</a></li></ol></li><li><a href="ar01s02.xhtml">Navigating the Documentation</a><ol><li><a href="ar01s02.xhtml#idm128">Where To Get Help</a></li><li><a href="ar01s02.xhtml#idm134">The Format of the Manuals</a></li><li><a href="ar01s02.xhtml#idm214">Units used in the Manuals</a></li><li><a href="ar01s02.xhtml#idm286">The Manuals</a></li></ol></li><li><a href="ar01s03.xhtml">Contributing to the LyX Project</a><ol><li><a href="ar01s03.xhtml#idm343">Contributing to LyX</a><ol hidden=""><li><a href="ar01s03.xhtml#idm346">Reporting a bug</a></li><li><a href="ar01s03.xhtml#idm356">Contributing fixes and new features</a></li></ol></li><li><a href="ar01s03.xhtml#idm359">Contributing to the Documentation</a><ol hidden=""><li><a href="ar01s03.xhtml#idm362">Reporting Errors in the Manuals</a></li><li><a href="ar01s03.xhtml#idm366">Joining the Documentation Team.</a></li></ol></li></ol></li></ol></nav></div><div class="list-of-tables"><nav epub:type="lot"><h4 class="toc-title">List of Tables</h4><ol><li><a href="ar01s02.xhtml#tab.Units">1. Units</a></li></ol></nav></div><footer/></body></html>PK v?LR??X?? ? OEBPS/package.opf<?xml version="1.0" encoding="utf-8" standalone="no"?>
<package xmlns="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" version="3.0" xml:lang="en" unique-identifier="pub-identifier">
<metadata>
<dc:identifier id="pub-identifier">_idm1</dc:identifier>
<meta id="meta-identifier" property="dcterms:identifier">_idm1</meta>
<dc:title id="pub-title">Introduction to LyX</dc:title>
<meta property="dcterms:title" id="meta-title">Introduction to LyX</meta>
<dc:language id="pub-language">en</dc:language>
<meta property="dcterms:language" id="meta-language">en</meta>
<meta property="dcterms:modified">2021-02-12T21:19:44Z</meta>
<!--The preceding date value is actually local time (not UTC) in UTC format because there is no function in XSLT 1.0 to generate a correct UTC time-->
<meta id="meta-creator2" property="dcterms:creator">by the LyX Team[1]</meta>
<dc:creator id="pub-creator2">by the LyX Team[1]</dc:creator>
</metadata>
<manifest>
<item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml"/>
<item id="htmltoc" properties="nav" media-type="application/xhtml+xml" href="ar01-toc.xhtml"/>
<item media-type="text/css" id="docbook-css" href="docbook-epub.css"/>
<item id="id-idm1" href="index.xhtml" media-type="application/xhtml+xml"/>
<item id="id-idm120" href="ar01s02.xhtml" media-type="application/xhtml+xml" properties="mathml"/>
<item id="id-idm341" href="ar01s03.xhtml" media-type="application/xhtml+xml"/>
<item id="idp1" href="images/footnote.png" media-type="image/png"/>
<item id="idp2" href="images/reference.png" media-type="image/png"/>
</manifest>
<spine toc="ncx">
<itemref idref="htmltoc" linear="yes"/>
<itemref idref="id-idm1"/>
<itemref idref="id-idm120"/>
<itemref idref="id-idm341"/>
</spine>
<guide>
<reference href="ar01-toc.xhtml" type="toc" title="Table of Contents"/>
</guide>
</package>
PK v?LR?guFL
L
OEBPS/toc.ncx<?xml version="1.0" encoding="utf-8" standalone="no"?>
<ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1"><head><meta name="dtb:uid" content="_idm1"/></head><docTitle><text>Introduction to LyX</text></docTitle><navMap><navPoint id="idm1" playOrder="1"><navLabel><text>Introduction to LyX</text></navLabel><content src="index.xhtml"/></navPoint><navPoint id="idm9" playOrder="2"><navLabel><text>The Philosophy of LyX</text></navLabel><content src="index.xhtml#idm9"/><navPoint id="idm11" playOrder="3"><navLabel><text>What is LyX?</text></navLabel><content src="index.xhtml#idm11"/></navPoint><navPoint id="idm33" playOrder="4"><navLabel><text>Differences between LyX and Other Word Processors</text></navLabel><content src="index.xhtml#idm33"/></navPoint><navPoint id="idm79" playOrder="5"><navLabel><text>What is LaTeX?</text></navLabel><content src="index.xhtml#idm79"/></navPoint></navPoint><navPoint id="idm120" playOrder="6"><navLabel><text>Navigating the Documentation</text></navLabel><content src="ar01s02.xhtml"/><navPoint id="idm128" playOrder="7"><navLabel><text>Where To Get Help</text></navLabel><content src="ar01s02.xhtml#idm128"/></navPoint><navPoint id="idm134" playOrder="8"><navLabel><text>The Format of the Manuals</text></navLabel><content src="ar01s02.xhtml#idm134"/></navPoint><navPoint id="idm214" playOrder="9"><navLabel><text>Units used in the Manuals</text></navLabel><content src="ar01s02.xhtml#idm214"/></navPoint><navPoint id="idm286" playOrder="10"><navLabel><text>The Manuals</text></navLabel><content src="ar01s02.xhtml#idm286"/></navPoint></navPoint><navPoint id="idm341" playOrder="11"><navLabel><text>Contributing to the LyX Project</text></navLabel><content src="ar01s03.xhtml"/><navPoint id="idm343" playOrder="12"><navLabel><text>Contributing to LyX</text></navLabel><content src="ar01s03.xhtml#idm343"/><navPoint id="idm346" playOrder="13"><navLabel><text>Reporting a bug</text></navLabel><content src="ar01s03.xhtml#idm346"/></navPoint><navPoint id="idm356" playOrder="14"><navLabel><text>Contributing fixes and new features</text></navLabel><content src="ar01s03.xhtml#idm356"/></navPoint></navPoint><navPoint id="idm359" playOrder="15"><navLabel><text>Contributing to the Documentation</text></navLabel><content src="ar01s03.xhtml#idm359"/><navPoint id="idm362" playOrder="16"><navLabel><text>Reporting Errors in the Manuals</text></navLabel><content src="ar01s03.xhtml#idm362"/></navPoint><navPoint id="idm366" playOrder="17"><navLabel><text>Joining the Documentation Team.</text></navLabel><content src="ar01s03.xhtml#idm366"/></navPoint></navPoint></navPoint></navMap></ncx>PK v?LR?u?? ? OEBPS/ar01s03.xhtml<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Contributing to the LyX Project</title><link rel="stylesheet" type="text/css" href="docbook-epub.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.2"/><link rel="prev" href="ar01s02.xhtml" title="Navigating the Documentation"/></head><body><header/><section class="section" title="Contributing to the LyX Project" epub:type="division" id="sec.Contrib"><div class="titlepage"><div><div><h2 class="title" style="clear: both">Contributing to the LyX Project</h2></div></div></div><section class="section" title="Contributing to LyX" epub:type="division" id="idm343"><div class="titlepage"><div><div><h3 class="title">Contributing to LyX</h3></div></div></div><p>LyX is mostly written in C++ (the LaTeX importer is written in Python). It is a large project, and as a result it is not free from bugs, or the need for improvements in the source code.</p><section class="section" title="Reporting a bug" epub:type="division" id="idm346"><div class="titlepage"><div><div><h4 class="title">Reporting a bug</h4></div></div></div><p>While using LyX, you may find behavior which you consider a bug. Crashes, though rare, can happen. User interface problems are considered major bugs by the LyX team: especially helpful are indications of parts of the LyX interface you find confusing, or unclear.</p><p>LyX has a bug tracking system, which you can find at</p><p><a class="link" href="https://www.lyx.org/trac/wiki/BugTrackerHome" target="_top">https://www.lyx.org/trac/wiki/BugTrackerHome</a>. You should check the bug tracker before reporting any bugs, in case it has already been reported. If you have a comment on an existing bug, or wish to report a new bug, you may either use the bug tracker, or send an e-mail to the development mailing list, <a class="link" href="lyx-devel at lists.lyx.org" target="_top">lyx-devel at lists.lyx.org</a>. Archives of this list are linked from the main LyX website, <a class="link" href="http://www.lyx.org" target="_top">http://www.lyx.org</a>.</p><p>A useful bug report will at a minimum include the version of LyX you are having the problem with. Accurate, detailed descriptions are preferred ??? the more time developers have to spend to pinpoint the source of a bug, the less time they have for other improvements. Mention the system and system version on which you are running LyX. Give the versions of the libraries you have installed on your system, and, if relevant, the versions of external programs that LyX uses. If it's a compilation or configuration problem, include the file <code class="code">config.log</code>, and mention which compiler you are using.</p></section><section class="section" title="Contributing fixes and new features" epub:type="division" id="idm356"><div class="titlepage"><div><div><h4 class="title">Contributing fixes and new features</h4></div></div></div><p>If you have made changes to LyX's source that you think should become part of LyX, send your changes as a diff file (in unified format) to the development list referenced above, along with a change log, and a description of what your patch does.</p></section></section><section class="section" title="Contributing to the Documentation" epub:type="division" id="idm359"><div class="titlepage"><div><div><h3 class="title">Contributing to the Documentation</h3></div></div></div><p>LyX's documentation is extensive; however LyX is under constant development, and each new release adds new features. You may find some documentation needs improvement. This section describes what to do if you find an error, or have some suggestions for improving the documentation.</p><section class="section" title="Reporting Errors in the Manuals" epub:type="division" id="idm362"><div class="titlepage"><div><div><h4 class="title">Reporting Errors in the Manuals</h4></div></div></div><p>If you find a problem with the documentation, send a message to the mailing list <a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a>. The documentation team will make any necessary fixes.</p></section><section class="section" title="Joining the Documentation Team." epub:type="division" id="idm366"><div class="titlepage"><div><div><h4 class="title">Joining the Documentation Team.</h4></div></div></div><p>The LyX Documentation Project, like anything else in the LyX project, can always use assistance! If you're interested in contributing to the Documentation Project, you need to do the following:</p><div class="orderedlist" epub:type="list"><ol class="orderedlist" type="1"><li class="listitem" epub:type="list-item"><p>Get the latest LyX source code from</p><p> <a class="link" href="https://www.lyx.org/trac/browser/lyxgit/lib/doc?rev=master " target="_top">https://www.lyx.org/trac/browser/lyxgit/lib/doc?rev=master </a></p></li><li class="listitem" epub:type="list-item"><p>Next, read the <span class="emphasis"><em>User's Guide</em></span> and the <span class="emphasis"><em>Tutorial</em></span></p><p>The point of this exercise is to give you ideas. The <span class="emphasis"><em>Tutorial</em></span> and <span class="emphasis"><em>User's Guide</em></span> are likely to be the most up-to-date of all of the documentation. You should be able to glean some insights into how we want the manuals to read and to look.</p></li><li class="listitem" epub:type="list-item"><p>Contact the team at:</p><p><a class="link" href="lyx-docs at lists.lyx.org" target="_top">lyx-docs at lists.lyx.org</a></p><p>to discuss your intended changes and to get some feedback on them.</p></li></ol></div><p>The changes you wish to make may range from improving clarity of the text, to doing major re-structuring of the documentation. Any and all improvements are gladly received.</p></section></section></section><footer/></body></html>PK v?LR[?r=? ? OEBPS/docbook-epub.css
/********************************/
/* start of styles in block.xsl */
.formalpara-title {
font-weight: bold;
}
div.blockquote-title {
font-weight: bold;
margin-top: 1em;
margin-bottom: 1em;
}
span.msgmain-title {
font-weight: bold;
}
span.msgsub-title {
font-weight: bold;
}
span.msgrel-title {
font-weight: bold;
}
div.msglevel, div.msgorig, div.msgaud {
margin-top: 1em;
margin-bottom: 1em;
}
span.msglevel-title, span.msgorig-title, span.msgaud-title {
font-weight: bold;
}
div.msgexplan {
margin-top: 1em;
margin-bottom: 1em;
}
span.msgexplan-title {
font-weight: bold;
}
div.sidebar {
border: 0.5pt solid black;
margin-top: 1em;
margin-bottom: 1em;
padding: 8px;
}
/* end of styles in block.xsl */
/********************************/
/********************************/
/* start of styles in autotoc.xsl */
/* top level entries */
nav>ol>li>a {
margin-top: 1em;
margin-bottom: 1em;
}
/* end of styles in autotoc.xsl */
/********************************/
/********************************/
/* start of styles in formal.xsl */
div.figure-title {
font-weight: bold;
}
div.example-title {
font-weight: bold;
}
div.equation-title {
font-weight: bold;
}
div.table-title {
font-weight: bold;
}
div.sidebar-title {
font-weight: bold;
}
/* end of styles in formal.xsl */
/********************************/
/********************************/
/* start of styles in verbatim.xsl */
div.programlisting {
white-space: pre-wrap;
font-family: monospace;
}
div.screen {
white-space: pre-wrap;
font-family: monospace;
}
div.synopsis {
white-space: pre-wrap;
font-family: monospace;
}
/* end of styles in verbatim.xsl */
/********************************/
/********************************/
/* NAVIGATION */
nav ol {
list-style-type: none;
margin: 0 0 0 2em;
padding: 0 0 0 0;
}
nav ol li {
margin: 0 0 0 0;
padding: 0 0 0 0;
}
nav ol li a {
text-decoration: none;
color: black;
font-family: sans-serif;
}
#guide {
display: none;
}
PK v?LRN??,E E OEBPS/images/footnote.png?PNG
IHDR & ?? ? sRGB ?? ? gAMA ?? ?a pHYs ? ??o?d ?IDATHK??1? E=???0^? ???+:Z????ug ?Y?%H?&? ?3?? V/9???I??k??h\?Y??"0}?????UW
?? ?p?I???q??(X??N??*T???4????ae??W
?t?:??????i[?|$,????0?4????%\:???$?lH?i??J??????;r>i?<???9? ? ? ?b??Z???? oRq?????k3??7 IEND?B`?PK v?LR??{? ? OEBPS/images/reference.png?PNG
IHDR ???x sRGB ?? ? gAMA ?? ?a pHYs ? ??o?d uIDAThC?V;r1 ?B?0?dg(?4T?a;:n@?-=5u?l??v??k^?x?yz? 6_?GG+t?[???]?????DW?%X??y??l?$~???]S????F??;?a??Z?k?f?dR??7??? TG\o??Y>y *D??{?8??
?|??V_F?U??2??T??i??????^???m;?
??????a F?2?_h??tTY??\y?h??U!}?9?'NX0???????\,?bI#?s?L?B??cXi?6%??%H??J9?\???OXr}@??(
????????9co??QR2?h8h???;H?DC??'?Rp ??OZk?M!O??V???}
???5>???^?vh?k?b6#?1?]??6?# ???\??j?J??????2? ?Y^??^???3?? :8????Ft?S?C#??4?f???:??????<&am???kJyQN?5~??Yqv??R?d3Vwh`???C???Z??????' ??*??b?J?N???????iqB'f??+??x??f????I m??Yb`?>;?L? ?O???-(8??? ?1 ?Q&!?F?p|??S?? q?B ?a?QB??`? ?I????,Hf`?C?i`?fTBB-?(????GW?%??-??o??~;< ?%nl\??? IEND?B`?PK v?LR%??? ? META-INF/container.xml<?xml version="1.0" encoding="utf-8" standalone="no"?>
<container xmlns="urn:oasis:names:tc:opendocument:xmlns:container" version="1.0"><rootfiles><rootfile full-path="OEBPS/package.opf" media-type="application/oebps-package+xml"/></rootfiles></container>PK v?LRoa?, ?? mimetypePK v?LR?????> ?> ??: OEBPS/index.xhtmlPK v?LR0????6 ?6 ??^? OEBPS/ar01s02.xhtmlPK v?LRPo? ? ? ??v OEBPS/ar01-toc.xhtmlPK v?LR??X?? ? ??~ OEBPS/package.opfPK v?LR?guFL
L
??? OEBPS/toc.ncxPK v?LR?u?? ? ???? OEBPS/ar01s03.xhtmlPK v?LR[?r=? ? ???? OEBPS/docbook-epub.cssPK v?LRN??,E E ???? OEBPS/images/footnote.pngPK v?LR??{? ? ??8? OEBPS/images/reference.pngPK v?LR%??? ? ??P? META-INF/container.xmlPK ? ??
More information about the lyx-devel
mailing list