Georg Baum 0cbcc8a166 Remove InsetGraphics noUnzip parameter
Being able to compile document with zipped .eps files was a useful feature of
the graphicxs package 20 years ago, but the LyX support is no longer relevant:
- The flag is ignored if preview is on
- If pdflatex is used then uncompressing happens during the compilation anyway
- If set, the flag prevents LyX from issuing proper error messages if
something with the image is wrong
- For hard disk capacities from 20 years ago not uncompressing is a useful
feature, but for current hard disk capacities it does not matter
- The external inset does not have it, and if we want to merge both insets
one day we would need to implement it there, which is even more difficult
than in InsetGraphics
2015-07-16 20:44:47 +02:00
..
2014-03-23 17:49:35 +01:00
2015-06-17 00:53:53 +02:00
2014-03-27 01:59:00 -07:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2015-06-19 10:11:17 +02:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2015-07-16 20:44:47 +02:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +01:00
2014-03-23 17:49:35 +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