Georg Baum cb5dd33475 Split pdf format as discussed on the list
Previously, the format used for included pdf files was the same as for
document export via ps2pdf. This caused unwanted conversion routes, e.g.
export via odt->pdf instead of dvi->ps->pdf.
I renamed the format for included graphics and not for exported documents,
since otherwise the command line syntax for export would change. This would
require more adaptions for the users, since with the chosen solution the
custom converters are almost always changed correctly in prefs2prefs(),
so that only custom external templates need manual adjustement.
2013-03-21 20:13:02 +01:00
..
2012-05-23 17:35:08 +02:00
2012-11-08 01:22:07 +01:00
2011-07-19 20:57:36 +00:00
2012-05-23 17:35:08 +02:00
2012-05-23 17:35:08 +02:00
2012-05-23 17:35:08 +02:00
2011-07-19 20:57:36 +00:00
2011-07-19 20:57:36 +00:00
2011-07-19 20:57:36 +00:00
2012-05-23 17:35:08 +02:00
2012-05-23 17:35:08 +02:00
2012-05-23 17:35:08 +02:00
2013-02-16 17:48:43 +01:00
2013-02-06 20:38:54 +01:00
2013-02-16 17:48:43 +01:00
2013-02-23 05:45:45 +01:00
2013-01-12 19:44:08 +01:00

README.Documentation

by John Weiss [3/2000] jpweiss@idsi.net


================
Introduction

    The purpose of this file is *used* *to* *be* to provide a style
    sheet and helpful hints to those wishing to help with the
    LyX Documentation Project.  There's now a separate style-sheet for
    that.

    If you're actually looking for documentation, check out the "Help"
    menu.  Start by reading the Introduction.

================
Why a separate documentation project?  Can't the developers do it?

    In a word, no.  They're too busy adding features and squishing
    bugs.

    Also, g++ is far more forgiving of style changes than a human
    brain.  As long as the code is correct, g++ will happilly compile
    it, and compile it the same way from machine to machine.  Human
    brains are far less forgiving and far more individualized.  So,
    the documentation needs to all be in a uniform style, in addition
    to being grammatically correct and easily readable.  That's a
    pretty big undertaking - which is why I volunteered to
    administrate the docs back in 1997.  Since then, I've passed the
    duty of maintaining the docs on to others.

================
Helping Out

    If you'd like to contribute to the LyX Documentation Project,
    start by reading the file Intro.lyx.  It contains a description of
    the style of the documentation from a reader's perspective.  After
    that, read the LyX Documentation Style Sheet (DocStyle.lyx) and
    commit it to memory!


John Weiss
March, 2000