On Mon, 05 Nov 2007 15:07:32 +0100
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> >> Also, why exactly is ERT a special case?
> >
> > At least that I can answer ;-) Because we want ERT output to be
> > "naked". In any locale. No \L stuff or the like around it.
>
> Hmm, could we use noFontChange for that?
>
> /**
> * Is this inset allowed within a font change?
> *
> * FIXME: noFontChange means currently that the font change is closed
> * in LaTeX before the inset, and that the contents of the inset
> * will be in default font. This should be changed so that the inset
> * changes the font again.
> */
> virtual bool noFontChange() const { return false; }
No, because that is _not_ what we want. We want _nothing_ either before
or after the inset, also no font change close / reopen.
> But I am not sure I understand. Why is forceLTR true for ERT? Just for
> display purpose?
Hmmm. It is to force the language, and thus the encoding, to Latin1.
LaTeX needs that; LyX display would be happy with Unicode, but isn't
smart enough to convert it to Latin1 without some help (i.e., the
language attribute).
> BTW, about ERT, do you know why the following entries are in
> getStatus?
>
> case LFUN_CLIPBOARD_PASTE:
> case LFUN_INSET_MODIFY:
> case LFUN_PASTE:
> case LFUN_PRIMARY_SELECTION_PASTE:
> case LFUN_QUOTE_INSERT:
> status.enabled(true);
> return true;
>
> // this one is difficult to get right. As a half-baked
> // solution, we consider only the first action of the sequence
> case LFUN_COMMAND_SEQUENCE: {
>
> I do not see what is so special about ERT for these things.
Hmmm... I'm a stranger here myself ;-)
If these are enabled in Collapsable, I suppose they can go.
> JMarc
- Martin
