Am Sonntag, 21. Juli 2019, 00:15:57 CEST schrieb Jean-Marc Lasgouttes:
> Le 20/07/2019 à 20:35, Kornel Benko a écrit :
> >> I think that would be fine and, potentially, save some hassle.
> >>
> >> Riki
> >
> > +1 for doing it as soon as possible (now?)
> > I will take care for the cmake part.
>
Le 20/07/2019 à 16:31, Jürgen Spitzmüller a écrit :
Am Samstag, den 20.07.2019, 16:29 +0200 schrieb Jean-Marc Lasgouttes:
It would be usable in the sense that the already used languages are
grouped together and I guess the cursor would be on it by default.
But this is already the case. I
Le 20/07/2019 à 16:36, Jürgen Spitzmüller a écrit :
Am Samstag, den 20.07.2019, 16:31 +0200 schrieb Jürgen Spitzmüller:
It would be usable in the sense that the already used languages
are
grouped together and I guess the cursor would be on it by default.
But this is already the case. I
Le 20/07/2019 à 20:35, Kornel Benko a écrit :
I think that would be fine and, potentially, save some hassle.
Riki
+1 for doing it as soon as possible (now?)
I will take care for the cmake part.
I have done it now. The cmake part should not be too difficult
considering what I had to do.
Am Samstag, 20. Juli 2019, 14:23:05 CEST schrieb Richard Kimberly Heck:
> On 7/20/19 1:01 AM, Jürgen Spitzmüller wrote:
> > Am Freitag, den 19.07.2019, 21:19 +0200 schrieb Jean-Marc Lasgouttes:
> >> It is more and more absurd to have a front end named qt4 these days.
> >> What about renaming
On 7/20/19 1:01 AM, Jürgen Spitzmüller wrote:
> Am Freitag, den 19.07.2019, 21:19 +0200 schrieb Jean-Marc Lasgouttes:
>> It is more and more absurd to have a front end named qt4 these days.
>> What about renaming everything qt? It looks like a good idea before
>> release to ease backport. Note
Am Samstag, den 20.07.2019, 16:31 +0200 schrieb Jürgen Spitzmüller:
> > It would be usable in the sense that the already used languages
> are
> > grouped together and I guess the cursor would be on it by default.
>
> But this is already the case. I meant, would the huge menu of all
> other
>
Am Samstag, den 20.07.2019, 16:29 +0200 schrieb Jean-Marc Lasgouttes:
> > Granted, but the argument I was discussing was "it is a bit far
> > away".
>
> FWIW, LibreOffice has this.
Note that I am not opposed to this as an additional thing. I was just
arguing that we already have an accessible
Am Samstag, den 20.07.2019, 16:29 +0200 schrieb Jean-Marc Lasgouttes:
> It would be usable in the sense that the already used languages are
> grouped together and I guess the cursor would be on it by default.
But this is already the case. I meant, would the huge menu of all other
languages be
Le 20/07/2019 à 16:26, Jürgen Spitzmüller a écrit :
Am Samstag, den 20.07.2019, 08:19 -0600 schrieb Joel Kulesza:
It is visible.
Granted, but the argument I was discussing was "it is a bit far away".
FWIW, LibreOffice has this.
JMarc
Am Samstag, den 20.07.2019, 16:28 +0200 schrieb Jean-Marc Lasgouttes:
> Yes, but only when there are at least two languages.
We could add "Change Language..." when we have only one.
Jürgen
signature.asc
Description: This is a digitally signed message part
Le 20/07/2019 à 16:25, Jürgen Spitzmüller a écrit :
Am Samstag, den 20.07.2019, 16:17 +0200 schrieb Jean-Marc Lasgouttes:
BTW, would it be possible/desirable to put all the languages in the
Edit/Language submenu but have the buffer languages at the top of
the
list with a separator?
This would
Le 20/07/2019 à 16:25, Jürgen Spitzmüller a écrit :
Am Samstag, den 20.07.2019, 16:17 +0200 schrieb Jean-Marc Lasgouttes:
BTW, would it be possible/desirable to put all the languages in the
Edit/Language submenu but have the buffer languages at the top of
the
list with a separator?
This would
Am Samstag, den 20.07.2019, 08:19 -0600 schrieb Joel Kulesza:
> It is visible.
Granted, but the argument I was discussing was "it is a bit far away".
Jürgen
signature.asc
Description: This is a digitally signed message part
Am Samstag, den 20.07.2019, 16:17 +0200 schrieb Jean-Marc Lasgouttes:
> BTW, would it be possible/desirable to put all the languages in the
> Edit/Language submenu but have the buffer languages at the top of
> the
> list with a separator?
This would be a long list. Is this usable?
> It feels
On Sat, Jul 20, 2019 at 8:11 AM Jürgen Spitzmüller wrote:
> Am Samstag, den 20.07.2019, 15:40 +0200 schrieb Jean-Marc Lasgouttes:
> > > As to the flag icon idea, I have to say (with my sociolinguist hat
> > > on)
> > > that I am not particularly thrilled by the underpinning association
> > > of
Le 20/07/2019 à 16:10, Jürgen Spitzmüller a écrit :
Am Samstag, den 20.07.2019, 15:40 +0200 schrieb Jean-Marc Lasgouttes:
As to the flag icon idea, I have to say (with my sociolinguist hat
on)
that I am not particularly thrilled by the underpinning association
of
languages with
Am Samstag, den 20.07.2019, 15:40 +0200 schrieb Jean-Marc Lasgouttes:
> > As to the flag icon idea, I have to say (with my sociolinguist hat
> > on)
> > that I am not particularly thrilled by the underpinning association
> > of
> > languages with countries/nations.
>
> Indicate language in status
Le 20/07/2019 à 14:44, Jürgen Spitzmüller a écrit :
Am Samstag, den 20.07.2019, 14:11 +0200 schrieb Jean-Marc Lasgouttes:
But how does the algorithm decide if multiple possible languages
are
used in the document? I would say the context language is a very
good
bet.
Could you give a concrete
Le 20/07/2019 à 15:24, Jürgen Spitzmüller a écrit :
Note that we provide a switch via menu (and context menu) already for
all languages of the current buffer.
Yes, but it is a bit far away for easy typing.
As to the flag icon idea, I have to say (with my sociolinguist hat on)
that I am not
Le 20/07/2019 à 14:25, Cor Blom a écrit :
Op 20-07-19 om 13:34 schreef Jean-Marc Lasgouttes:
To be clear, this feature is mainly a request of Hebrew writers, as I
see it.
As someone writing stuff in multiple western languages and Hebrew I
welcome this change, but I think it is overdone. My
Am Samstag, den 20.07.2019, 15:28 +0200 schrieb Kornel Benko:
> Right, but I was not able to find any icons for languages ... and I
> also have no idea, how they should look alike.
I am not challenging your personal solution. I just would not want to
implement this in our general UI. I don't see
Am Samstag, 20. Juli 2019, 15:24:06 CEST schrieb Jürgen Spitzmüller:
> Am Samstag, den 20.07.2019, 15:00 +0200 schrieb Jean-Marc Lasgouttes:
> > It would be nice to have an automatic toolbar that does this (with
> > the nice flags) at least for the languages of the current buffer. I
> >
Am Samstag, den 20.07.2019, 15:00 +0200 schrieb Jean-Marc Lasgouttes:
> It would be nice to have an automatic toolbar that does this (with
> the nice flags) at least for the languages of the current buffer. I
> understand it does not solve your use case, but it not possible to
> have everyone's
Le 20/07/2019 à 14:38, Kornel Benko a écrit :
I have something similar ... but without keyboard change.
Implemented as part of stdtoolbars.inc.
The attached may make it more clear (The flags represent the languages)
(Added
+ Separator
+ Item "Set language german"
Am Samstag, den 20.07.2019, 14:11 +0200 schrieb Jean-Marc Lasgouttes:
> > But how does the algorithm decide if multiple possible languages
> > are
> > used in the document? I would say the context language is a very
> > good
> > bet.
>
> Could you give a concrete example?
Let's say I am writing
Am Samstag, 20. Juli 2019, 13:34:39 CEST schrieb Jean-Marc Lasgouttes:
> Le 19/07/2019 à 18:41, Jürgen Spitzmüller a écrit :
> > To make this point a bit more clear, hopefully: The keyboard layouts of
> > de_DE and de_AT are exactly identical. I don't want to setup two input
> > methods for this
Op 20-07-19 om 13:34 schreef Jean-Marc Lasgouttes:
To be clear, this feature is mainly a request of Hebrew writers, as I
see it.
As someone writing stuff in multiple western languages and Hebrew I
welcome this change, but I think it is overdone. My keyboard setup is
that I use a different
Le 20/07/2019 à 14:00, Jürgen Spitzmüller a écrit :
But how does the algorithm decide if multiple possible languages are
used in the document? I would say the context language is a very good
bet.
Could you give a concrete example?
JMarc
Am Samstag, den 20.07.2019, 13:30 +0200 schrieb Jean-Marc Lasgouttes:
> I am not sure I can follow, but it would not be good if it would not
> be
> > aware of language varieties. This is probably a general problem
> > with
> > the approach: if I have selected to write a document in Austrian
> >
Am Samstag, den 20.07.2019, 13:34 +0200 schrieb Jean-Marc Lasgouttes:
> I could argue that the easiest way to write a document in German and
> Austrian (assuming this makes any sense) would be to set up two
> keyboards, at least temporarily, and switch using Super-space. It
> might be a good
Le 19/07/2019 à 18:41, Jürgen Spitzmüller a écrit :
To make this point a bit more clear, hopefully: The keyboard layouts of
de_DE and de_AT are exactly identical. I don't want to setup two input
methods for this just to use these two varieties in parallel in LyX.
I could argue that the easiest
Le 19/07/2019 à 18:34, Jürgen Spitzmüller a écrit :
I am not sure I can follow, but it would not be good if it would not be
aware of language varieties. This is probably a general problem with
the approach: if I have selected to write a document in Austrian German
(de_AT), I would not want LyX
Le 19/07/2019 à 12:46, Kornel Benko a écrit :
Please make it configurable, with default to old behaviour.
To be clear: this has always been my intent. I did it now in master, and
the feature done as far I I am concerned.
Now is the time for valid complaints ;)
JMarc
Le 20/07/2019 à 07:03, Jürgen Spitzmüller a écrit :
Am Freitag, den 19.07.2019, 22:03 +0200 schrieb Jean-Marc Lasgouttes:
I do not see the point of doing that, so I want to know what I miss.
AFAIU the point is just to increase the version number to let older
versions on LyX know that these
35 matches
Mail list logo
