On Mon, Mar 13, 2006 at 06:06:10PM +0000, Angus Leeming wrote:
> Rainer Dorsch <[EMAIL PROTECTED]> writes:
 
...
 
> > > This is exactly the sort of thing that a new contributer (hint, hint...)
> > > could pick up and run with 
> > 
> > I see you point, but I think that piece is too big for me. Let me start 
> > with 
> > the charstyle wiki....
> 
> That'd be great too. Why not write a page (pictures too?) describing what you
> think the charstyle UI should be? Can be as rough as you like...
> 
> I imagine that there would be a separation here between "defining a char 
> style"
> and "using a char style", something like the existing stuff to define and use 
> a
> branch. Presumably, "defining a char style" would require a fairly complex
> dialog but "using a char style" would require only a CS menu with a list of
> available styles.
> 
> Interesting questions:
> Presumably there will be char styles associated with the layout. Could there
> also be char styles specified by the user on a per-document basis?

Yes, I have something like this in my local tree. The per-document
charstyles are defined in the minibuffer and take the font at the cursor
location as the inset's font definition. (A GUI for defining them rather
than the minibuffer would be nice, but I'm sure this already will make
many people happy.)

These per-document charstyles output the same font to the screen and
to the LaTeX file. They have initially no displayed label (Jean-Marc
objected to their real-estate demand when I proposed to use them in
LaTeX to replace emph and noun.) They are added to the menu below the
layout-specific charstyles.

> If so, where would these per-document char styles be saved? Presumably in the
> lyx documnent. 

Yes... haven't done that yet. Otherwise seems to work.

> Presumably, these per-document char styles override the layout
> char style of the same name?

Hmmm...
 
> Perhaps this will start off people like John Levon talking about UI design and
> you could collate the info into a wiki page... :-P
> 
> (And, if no one has said so already --- welcome! :))

Hear, hear.

- Martin
 

Attachment: pgphdPTxr5a3B.pgp
Description: PGP signature

Reply via email to