Thomas Templin <[EMAIL PROTECTED]> writes:
| For my own documents i am using a file with a lot of \newcommand's
| like
| \newcommand{\company} [1] {\textbf{#1}}
yes...
| and then
| \newcommand{\redhat} {\company{RedHat}\xspace}
but this would be a combination of what I call (static)
"abbreviations" and character styles.
| so what I get are two things. First a Character style \company and
| an acronym \redhat,
nahh... redhat is not an acronym. PINE is an acronym (a recursive
acronym even ... Pine Is Not Elm)
| a better example should be DNA for
| Desoxyribonucleinacid :).
| This could be placed somwhere in the ~/.lyx path or the user LaTeX
| path and then nested to a character pulldown menu and a shorttag
| pulldown menu in LyX.
To have these defined as LaTeX (be it character styles, acronyms or
abbreviation), is something I would be against. I do not want LyX to
be any more (La)TeX specific than it already is. To be able to import
these kind of definitions might be good though.
| The only problem is that this tags will not be used for a html
| output with pdflatex (up to now).
We need to translate them into some LyX specific format.
| May be a standalone preamble file could be an other way to get this
| behaviour. Then the files could be packed into a tgz file
| including the original lyx file and the preamble file.
Naahh... not unless we have to.
| Another
| benefit would be to use a user customizable editor for the
| preamble. To my opinion the pramble window is at least a painfull
| thing. :) (German: Ich finde, dass Arbeiten mit dem Präambel
| Fenster ist zumindestens als schmerzhaft zu bezeichnen.)
Abbrevs, acronyms and character styles will not be settable from the
preamble... unless you also use ERT of course...
--
Lgb
