mirror of
https://git.lyx.org/repos/lyx.git
synced 2024-11-07 12:32:26 +00:00
954be90e11
The key is the new copier script lib/scripts/ext_copy.py. Usage: ext_copy.py [-e ext1,ext2,...] <from file> <to file> Given a <from file> and <to file>, it will copy all files in the directory in which from_file is found that have the extensions given in the -e option, or all files in that directory if no such argument is given. So, for example, we can do: python ext_copy.py -e png,html,css /path/from/file.html /path/to/file.html and all html, png, and css files in /path/from/ will be copied to the (possibly new) directory /path/to/file.html.LyXconv/. The -t option determines the extension added to the output filename passed to the script ($$o, in the copier definition), the default being "LyXconv". If just . is given, then no extension is added. Other changes: * configure.py: added appropriate copier definitions for html and wordhtml formats, as well as for the Program pseudo-format. * lib/Makefile.am and development/scons/scons_manifest.py: add ext_copy.py. * lib/doc/Customization.lyx: update documentation. git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@18791 a592a061-630c-0410-9148-cb99ea01b6c8 |
||
---|---|---|
.. | ||
clipart | ||
cs | ||
da | ||
de | ||
es | ||
eu | ||
fr | ||
gl | ||
he | ||
hu | ||
it | ||
nb | ||
nl | ||
pl | ||
pt | ||
ro | ||
ru | ||
sk | ||
sl | ||
sv | ||
ChangeLog | ||
Customization.lyx | ||
depend.py | ||
doc_toc.py | ||
DocStyle.lyx | ||
DummyDocument1.lyx | ||
DummyDocument2.lyx | ||
DummyTextDocument.txt | ||
EmbeddedObjects.lyx | ||
Extended.lyx | ||
FAQ.lyx | ||
Intro.lyx | ||
LaTeXConfig.lyx.in | ||
Makefile.am | ||
Makefile.depend | ||
README.Documentation | ||
Reference.lyx | ||
Tutorial.lyx | ||
UserGuide.lyx |
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