Am Montag, den 15.04.2019, 10:01 -0700 schrieb Sergei Winitzki:
> Thank you Jürgen for a quick response! I have been using LyX since
> 1999 for every technical document I write, and I am glad to see that
> the project is going strong after 20 years.
Meanwhile, I also encountered that we already ha
On Mon, Apr 15, 2019 at 10:52:26AM +0300, Veselin wrote:
> 15.04.19 ??. ?? 8:02 ??., Jürgen Spitzmüller :
>> Am Samstag, den 13.04.2019, 00:37 +0300 schrieb Veselin:
>>> Hello,
>>>
>>>
>>> Attached is the bulgarian translation for Lyx. It is more than 40%
>>> ready.
Hi Veso,
whil
Thank you Jürgen for a quick response! I have been using LyX since 1999 for
every technical document I write, and I am glad to see that the project is
going strong after 20 years.
Sergei
Am Mo., 15. Apr. 2019 um 03:00 Uhr schrieb Jürgen Spitzmüller :
> Am Sonntag, den 14.04.2019, 22:26 -0700 sch
On 2019-04-15, Enrico Forestieri wrote:
> On Mon, Apr 15, 2019 at 12:16:26PM +0200, Jean-Marc Lasgouttes wrote:
>> Le 12/04/2019 à 05:23, Isaac Oscar Gariano a écrit :
>> > * It supports unicode input. LyX seems supports this as well, but when
>> > I put '→' in the autocorrect file instead o
On Mon, Apr 15, 2019 at 05:33:13PM +0200, Enrico Forestieri wrote:
> On Mon, Apr 15, 2019 at 05:18:52PM +0200, Jean-Marc Lasgouttes wrote:
> >
> > In this case of this rightarrow, why was it decided that it is a text thing?
> > The unicode reference puts in the the Symbol and Math categories. I wo
On Mon, Apr 15, 2019 at 05:18:52PM +0200, Jean-Marc Lasgouttes wrote:
> Le 15/04/2019 à 16:54, Enrico Forestieri a écrit :
> > > I guess this is the question: what is the reason why the character is
> > > entered as text? Don't we have means to know that this one could be
> > > entered
> > > direc
Le 15/04/2019 à 16:54, Enrico Forestieri a écrit :
I guess this is the question: what is the reason why the character is
entered as text? Don't we have means to know that this one could be entered
directly as math character?
We already do that with some symbols such as è, which is entered in ma
On Mon, Apr 15, 2019 at 04:33:16PM +0200, Jean-Marc Lasgouttes wrote:
>
> [Enrico, please try to keep Isaac in the loop for now, at least until we
> know he is subscribed]
Will try to remember.
> Le 15/04/2019 à 16:28, Enrico Forestieri a écrit :
> > On Mon, Apr 15, 2019 at 12:16:26PM +0200, Jea
On Mon, Apr 15, 2019 at 04:28:16PM +0200, Jean-Marc Lasgouttes wrote:
> Le 15/04/2019 à 16:08, Enrico Forestieri a écrit :
> > On Mon, Apr 15, 2019 at 12:16:26PM +0200, Jean-Marc Lasgouttes wrote:
> > >
> > > OK, it was just a suggestion. More important would be to have new bindings
> > > that use
[Enrico, please try to keep Isaac in the loop for now, at least until we
know he is subscribed]
Le 15/04/2019 à 16:28, Enrico Forestieri a écrit :
On Mon, Apr 15, 2019 at 12:16:26PM +0200, Jean-Marc Lasgouttes wrote:
Let's go through the remaining issues now.
Le 12/04/2019 à 05:23, Isaac
On Mon, Apr 15, 2019 at 12:16:26PM +0200, Jean-Marc Lasgouttes wrote:
>
> Let's go through the remaining issues now.
>
> Le 12/04/2019 à 05:23, Isaac Oscar Gariano a écrit :
> > * It supports unicode input. LyX seems supports this as well, but when
> > I put '→' in the autocorrect file inst
Le 15/04/2019 à 16:08, Enrico Forestieri a écrit :
On Mon, Apr 15, 2019 at 12:16:26PM +0200, Jean-Marc Lasgouttes wrote:
OK, it was just a suggestion. More important would be to have new bindings
that use the feature. I guess one candidate is
-- >\longrightarrow
Another interesting f
On Mon, Apr 15, 2019 at 12:16:26PM +0200, Jean-Marc Lasgouttes wrote:
>
> OK, it was just a suggestion. More important would be to have new bindings
> that use the feature. I guess one candidate is
> --> \longrightarrow
Another interesting feature made possible by this patch is the
foll
Hi again,
Let's go through the remaining issues now.
Le 12/04/2019 à 05:23, Isaac Oscar Gariano a écrit :
* It supports unicode input. LyX seems supports this as well, but when
I put '→' in the autocorrect file instead of '\rightarrow' it shows
in lyx with a different font, however it
Le 12/04/2019 à 05:23, Isaac Oscar Gariano a écrit :
The main reason I made this change was because I am a frequent Micrsofot
Word user, however at work I do not have windows and am usually required
to write things following LaTeX styles, hence I wanted to use lyx (which
works great!). However,
Am Sonntag, den 14.04.2019, 22:26 -0700 schrieb Sergei Winitzki:
>
> "I hereby grant permission to license my contributions to LyX
> under the GNU General Public License, version 2 or later."
Thanks, Sergei. Patch is in (master).
Riki, this could also be backported.
Jürgen
signature.asc
Desc
Am Montag, den 15.04.2019, 10:52 +0300 schrieb Veselin:
> Dear All,
>
> I hereby grant permission to license my contributions to LyX
> under the GNU General Public License, version 2 or later.
Thanks, Veso! I have committed your contribution to the master
repository (2.4.dev).
Note that we need
I am still very puzzled by this bug for the following reason:
If the changes are accepted, it works as expected. But then, why is the
output not just shown *as if* changes were accepted if they are not
accepted (and "Show changes in output" is not activated)?
https://www.lyx.org/trac/ticket/1
Dear All,
I hereby grant permission to license my contributions to LyX
under the GNU General Public License, version 2 or later.
Best Regards,
Veso
На 15.04.19 г. в 8:02 ч., Jürgen Spitzmüller написа:
Am Samstag, den 13.04.2019, 00:37 +0300 schrieb Veselin:
Hello,
Attached is the bulgarian
Dear Isaac,
I forward your e-mail to the developers list because this is the right
place to discuss. I understand that we forgot to keep you in cc: of the
discussion. To avoid this in the future (although we'll try to do our
best), I propose two solutions:
* that you subscribe to the list
* o
On 12/04/2019 19:54, Daniel wrote:
On 12/04/2019 16:22, Daniel wrote:
This threat is an attempt to share experiences with Advanced F&R as a
replacement of Simple F&R. I think this might be a necessary
replacement due to for the user non-obvious severe limitations of
Simple F&R, e.g.
https://
21 matches
Mail list logo
