Juergen Vigna <[EMAIL PROTECTED]> writes:
| Well I guess this is not that easily done if we want this feature implemented
| right. As you tell us below the big question is how to display this and IMO
| to realize this good from the beginning we have to insert some
| simple formating
| stuff to this too f.ex. display()-style it should use it's own row as a
| display()-inset and I guess some more other stuff too.
The question is if we really want to support this in the LCS, rembemer
this is for single words and short terms only.
| Then we surely need
| a feature-string which tells us if we have to include a special-LaTeX package
| to use the command, we cannot suppose that the user knows for system-wide
| declared LCS's what LaTeX package (s)he should add in the LaTeX preamble,
| moreover there are some commands valid only in certain layout-types how do
| we handle this?
Not a problem.
|
| >
| > 3.1 Creating LCS
| >
| > There will be a dialog where the user can set the name of the logical
| > style as well as the font to use for it. It will also be possible
| > to use the LCS command style where the user can provide the name of
| > the command used for the LCS([footnote] What about different documents
| > formats? Can this be handled in a nice way?) , the user has to provide
| > the actual command, either in the preamble or as part of LaTeX or
| > an addon package. Emph and noun will use this method. The storage
| > will be in some configuration file, perhaps .lyxrc.
| >
|
| I guess there should be also a way to create this styles inside a layout-file
| and I think this should be for now the only way to do this as then we exactly
| know what we need and what layout we are in.
No, ok it should be possible to have this in layout files. But LCS are
not primarily for the class layout it is for use by users to mark
"concepts", e.g. I write on a documnet about airports I want "Fornebu"
marked as "airport". No way we can support this through layout files.
the only times a LCS should be defined in a layout file is when the
underlying format/class contains specific code for f.eks. \file then
we want a LCS "file" for this.
| I'm sure the general way you propose would be VERY nice but also very error
| prone.
I don't agree.
Lgb
