[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lyx-devel
Subject:    Re: annoying behavior of Lyx 2.02+ -- Language toggle
From:       Ronen Abravanel <ronena () gmail ! com>
Date:       2012-05-23 18:59:37
Message-ID: CACTp8RhKuk4td5OfTzEniFTdH3dxfgE380Ltp18TZ89CfCQQgQ () mail ! gmail ! com
[Download RAW message or body]

So, which one of the suggestions should I implement?

On Mon, May 7, 2012 at 1:39 PM, Ronen Abravanel <ronena@gmail.com> wrote:

> If there are only few such commands, the 1st options seems best.
> If there are many, the last..
>
> Ronen
>
>
> On Wed, May 2, 2012 at 11:58 AM, Jean-Marc Lasgouttes <lasgouttes@lyx.org=
>wrote:
>
>> Le 29/04/2012 14:13, Vincent van Ravesteijn a =C3=A9crit :
>>
>>  I think it is a bug. I would vote for disabling the LFUN when the
>>> languages are the same. This will make it possible for the reporter to
>>> define: "command-alternatives language hebrew; language english" to
>>> toggle.
>>>
>>> I especially object to introduce a difference in behaviour based on the
>>> fact whether there is a selection or not. I would not expect something
>>> different to happen.
>>>
>>
>> I think these lfuns have two faces: interactive and API.
>> * as an API, I would expect to be able to set language to "french" and
>> not care about what the language was before that
>> * as an interactive function, toggling between the given value and the
>> default is very desirable and fits what is done by other font-changing
>> functions.
>>
>> We probably need to offer the two possibilities, either by
>> * two sets of lfuns language/language-set, font-emph/font-emph-set
>> * an optional argument "set"
>> * a prefix command "notoggle" ("notoggle language french")
>>
>> Of course, a way that preserves the preexisting semantics of lfuns would
>> be best.
>>
>> Similarly, having the possibility to have "layout" toggle between the
>> given layout and standard layout could be useful for toolbars.
>>
>> JMarc
>>
>
>

[Attachment #3 (text/html)]

<div dir="ltr">So, which one of the suggestions should I implement?<br><br><div \
class="gmail_quote">On Mon, May 7, 2012 at 1:39 PM, Ronen Abravanel <span \
dir="ltr">&lt;<a href="mailto:ronena@gmail.com" \
target="_blank">ronena@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">If there are only few such commands, the 1st \
options seems best.<br>If there are many, the last..<span class="HOEnZb"><font \
color="#888888"><br>

<br>Ronen</font></span><div><div class="h5"><br><br><div class="gmail_quote">On Wed, \
May 2, 2012 at 11:58 AM, Jean-Marc Lasgouttes <span dir="ltr">&lt;<a \
href="mailto:lasgouttes@lyx.org" target="_blank">lasgouttes@lyx.org</a>&gt;</span> \
wrote:<br>


<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Le 29/04/2012 14:13, Vincent van Ravesteijn a écrit \
:<div><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"> I think it is a bug. I would vote for disabling the \
LFUN when the<br> languages are the same. This will make it possible for the reporter \
                to<br>
define: &quot;command-alternatives language hebrew; language english&quot; to \
toggle.<br> <br>
I especially object to introduce a difference in behaviour based on the<br>
fact whether there is a selection or not. I would not expect something<br>
different to happen.<br>
</blockquote>
<br></div>
I think these lfuns have two faces: interactive and API.<br>
* as an API, I would expect to be able to set language to &quot;french&quot; and not \
                care about what the language was before that<br>
* as an interactive function, toggling between the given value and the default is \
very desirable and fits what is done by other font-changing functions.<br> <br>
We probably need to offer the two possibilities, either by<br>
* two sets of lfuns language/language-set, font-emph/font-emph-set<br>
* an optional argument &quot;set&quot;<br>
* a prefix command &quot;notoggle&quot; (&quot;notoggle language french&quot;)<br>
<br>
Of course, a way that preserves the preexisting semantics of lfuns would be best.<br>
<br>
Similarly, having the possibility to have &quot;layout&quot; toggle between the given \
layout and standard layout could be useful for toolbars.<br> <br>
JMarc<br>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]