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; }
But I am not sure I understand. Why is forceLTR true for ERT? Just for
display purpose?
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.
JMarc
