On 04/14/2016 09:16 AM, Neal Becker wrote:
Guillaume Munch wrote:
Le 14/04/2016 13:59, Neal Becker a écrit :
Problem is, I use black text on white background. The source preview is
unreadable because it's dark text with a black background. I went to
preferences/colors and tried changing ever
I tried to incluide an SVG graphic in a LyX file and it appears horribly corrupted (black triangles everywhere in the image boundary). PDF output is fine. LyX 2.1 did not have this issue and SVG looks correct.
Am Freitag, 15. April 2016 um 09:01:52, schrieb Andrew Parsloe
> On 14/04/2016 11:00 p.m., Kornel Benko wrote:
> > Am Donnerstag, 14. April 2016 um 22:48:32, schrieb Andrew Parsloe
> >
> >> (Ahem, me again.) This is rc1 from a new clean reinstall with the later
> >> windows installer. If I try
On 14/04/2016 11:00 p.m., Kornel Benko wrote:
Am Donnerstag, 14. April 2016 um 22:48:32, schrieb Andrew Parsloe
(Ahem, me again.) This is rc1 from a new clean reinstall with the later
windows installer. If I try to create a new shortcut, say for
flex-insert blah
I can reach the stage where t
On 15/04/2016 7:11 a.m., Georg Baum wrote:
Andrew Parsloe wrote:
Double hyphens in LyX-Code are now not merged to an en dash in rc1,
either in LyX or the pdf. Good. But if the font is changed, they become
an en dash in the pdf -- even something as simple as emphasis or bolding
has this effect.
Uwe Stöhr wrote:
> Not from my side. I would only like that the po-files are remerged so
> that our translators can do their work after RC1 is released.
Does that mean we had string changes again? I thougt that the strings in .po
files were up to date after your last remerge.
Georg
Le 14/04/16 21:01, Georg Baum a écrit :
Jean-Marc Lasgouttes wrote:
I would like also to see a strategy for 2.2.1. Do we reserve this
milestone for urgent fixes and keep 2.2.2 for more mundane backports? Or
do we treat it just like any other stable release.
I would recommend to reserve it for
Kornel Benko wrote:
> Am Donnerstag, 7. April 2016 um 17:02:42, schrieb Richard Heck
>
>>
>> Maybe a simple solution would be to add something into CMakeLists.txt
>> that would strip all the "\r" before sending the files through gettext.
>
> Maybe, see my other mail. But I prefer the solution w
Richard Heck wrote:
> On 04/09/2016 11:36 AM, Uwe Stöhr wrote:
>> Am 07.04.2016 um 23:37 schrieb Richard Heck:
>>
>>> Then maybe the solution is to disable the writing of native line
>>> endings. Apparently, we can do this by opening the output files in
>>> binary mode. The attached patch does thi
Scott Kostyshak wrote:
> On Sat, Apr 09, 2016 at 10:00:24AM +, Guenter Milde wrote:
>
>> I'd like to see all Unicode characters allowed in LyX labels but agree
>> that this is stuff for 2.3...
Agreed to both.
> Yes and just to add I tested that the unicode strings shows up fine in
> LyX so
Andrew Parsloe wrote:
> Double hyphens in LyX-Code are now not merged to an en dash in rc1,
> either in LyX or the pdf. Good. But if the font is changed, they become
> an en dash in the pdf -- even something as simple as emphasis or bolding
> has this effect. Is this expected behaviour? (I was hop
Le 14/04/2016 19:53, Stephan Witt a écrit :
Am 14.04.2016 um 20:16 schrieb Guillaume Munch :
Le 14/04/2016 19:05, Stephan Witt a écrit :
Yes, it’s attached. Thanks for testing.
Works well on Linux+qt{4,5}.
Two remarks:
* isFixedPitch() would be in an anonymous namespace by what I know o
Richard Heck wrote:
> Then I propose to go ahead and create 2.3-staging and 2.2.1-staging now.
> The former will be open for all commits, as if it were master, and will
> eventually be merged to master; the latter will be treated as stable and
> will be managed by me alongside 2.1.x.
Why so many
Jean-Marc Lasgouttes wrote:
> I would like also to see a strategy for 2.2.1. Do we reserve this
> milestone for urgent fixes and keep 2.2.2 for more mundane backports? Or
> do we treat it just like any other stable release.
I would recommend to reserve it for urgent fixes. I have made very good
Am 14.04.2016 um 20:16 schrieb Guillaume Munch :
>
> Le 14/04/2016 19:05, Stephan Witt a écrit :
>>
>> Yes, it’s attached. Thanks for testing.
>>
>
>
> Works well on Linux+qt{4,5}.
>
> Two remarks:
>
> * isFixedPitch() would be in an anonymous namespace by what I know of LyX's
> code style.
Le 14/04/2016 19:05, Stephan Witt a écrit :
Yes, it’s attached. Thanks for testing.
Works well on Linux+qt{4,5}.
Two remarks:
* isFixedPitch() would be in an anonymous namespace by what I know of
LyX's code style.
* In my patch I compute typewriterFontName() from typewriterSystemFont.
Wo
Am 14.04.2016 um 19:46 schrieb Guillaume Munch :
>
> Le 14/04/2016 18:41, Stephan Witt a écrit :
>> Am 14.04.2016 um 19:28 schrieb Guillaume Munch :
>>>
>>> Le 14/04/2016 18:10, Stephan Witt a écrit :
Am 14.04.2016 um 18:18 schrieb Joel Kulesza
:
>
> On Thu, Apr 14, 2016 at 10:
Le 14/04/2016 18:41, Stephan Witt a écrit :
Am 14.04.2016 um 19:28 schrieb Guillaume Munch :
Le 14/04/2016 18:10, Stephan Witt a écrit :
Am 14.04.2016 um 18:18 schrieb Joel Kulesza
:
On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch
wrote:
Can you please try the attached patch?
That patch
Am 14.04.2016 um 19:28 schrieb Guillaume Munch :
>
> Le 14/04/2016 18:10, Stephan Witt a écrit :
>> Am 14.04.2016 um 18:18 schrieb Joel Kulesza :
>>>
>>> On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch
>>> wrote:
>>>
>>> Can you please try the attached patch?
>>>
>>> That patch seemed to wor
Le 14/04/2016 18:10, Stephan Witt a écrit :
Am 14.04.2016 um 18:18 schrieb Joel Kulesza :
On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch
wrote:
Can you please try the attached patch?
That patch seemed to work to correct the issue in both places (see
attached). The font seems small (I'm no
Am 14.04.2016 um 18:18 schrieb Joel Kulesza :
>
> On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch wrote:
>
> Can you please try the attached patch?
>
> That patch seemed to work to correct the issue in both places (see attached).
> The font seems small (I'm not sure if that's perception or r
Le 14/04/2016 17:18, Joel Kulesza a écrit :
On Thu, Apr 14, 2016 at 10:24 AM, Guillaume Munch mailto:g...@lyx.org>> wrote:
Can you please try the attached patch?
That patch seemed to work to correct the issue in both places (see
attached). The font seems small (I'm not sure if that's perc
Le 14/04/2016 16:21, Guillaume Munch a écrit :
Le 14/04/2016 14:36, Neal Becker a écrit :
Guillaume Munch wrote:
Le 14/04/2016 14:16, Neal Becker a écrit :
Guillaume Munch wrote:
Le 14/04/2016 13:59, Neal Becker a écrit :
Problem is, I use black text on white background. The source previe
On 2016-04-14, Neal Becker wrote:
> Problem is, I use black text on white background. The source preview is
> unreadable because it's dark text with a black background. I went to
> preferences/colors and tried changing everything that was black, but nothing
> seemed to fix it. I didn't see an
Le 14/04/2016 01:50, Uwe Stöhr a écrit :
This one is in the tar ball here.
I use the tar.xz tarball and there is only a file
spelling-continously.svgz
but not
spellcheck-continously.svgz
You are right, spellcheck-continously.svgz should be removed from the
git repo.
JMarc
Le 14/04/2016 14:36, Neal Becker a écrit :
Guillaume Munch wrote:
Le 14/04/2016 14:16, Neal Becker a écrit :
Guillaume Munch wrote:
Le 14/04/2016 13:59, Neal Becker a écrit :
Problem is, I use black text on white background. The source preview
is
unreadable because it's dark text with a bl
Le 14/04/2016 13:33, Joel Kulesza a écrit :
On Thu, Apr 14, 2016 at 8:29 AM, Joel Kulesza mailto:jkule...@gmail.com>> wrote:
On Thu, Apr 14, 2016 at 8:18 AM, Guillaume Munch mailto:g...@lyx.org>> wrote:
Yes it's there. Code is very now similar to the source panel.
What font
Hi all:
It would be possible an icon in the lyx interface from which you can
activate JabRef or Mendeley ... check the cite, and close it and not do
it from JabRef through lyxpipe?
Regards
Miguel
Guillaume Munch wrote:
> Le 14/04/2016 14:16, Neal Becker a écrit :
>> Guillaume Munch wrote:
>>
>>> Le 14/04/2016 13:59, Neal Becker a écrit :
Problem is, I use black text on white background. The source preview
is
unreadable because it's dark text with a black background. I went
Le 14/04/2016 14:16, Neal Becker a écrit :
Guillaume Munch wrote:
Le 14/04/2016 13:59, Neal Becker a écrit :
Problem is, I use black text on white background. The source preview is
unreadable because it's dark text with a black background. I went to
preferences/colors and tried changing ever
Le 14/04/2016 13:59, Neal Becker a écrit :
Problem is, I use black text on white background. The source preview is
unreadable because it's dark text with a black background. I went to
preferences/colors and tried changing everything that was black, but nothing
seemed to fix it. I didn't see an
Problem is, I use black text on white background. The source preview is
unreadable because it's dark text with a black background. I went to
preferences/colors and tried changing everything that was black, but nothing
seemed to fix it. I didn't see any items under 'color' that appeared to
ap
Am 14.04.2016 um 14:06 schrieb Neal Becker :
>
> Just for fun, I'm trying building this on fedora 23. Being a modern guy, I
> thought I'd try --enable-qt5. I started with the SPEC file for fedora F25. I
> didn't get very far.
>
> One thing strange, configure choked on:
> g++ -o conftest -O2 -g
Le 14/04/2016 14:06, Neal Becker a écrit :
Just for fun, I'm trying building this on fedora 23. Being a modern guy, I
thought I'd try --enable-qt5. I started with the SPEC file for fedora F25. I
didn't get very far.
One thing strange, configure choked on:
Could you send your complete config.l
Stephan Witt wrote:
> Am 14.04.2016 um 14:06 schrieb Neal Becker :
>>
>> Just for fun, I'm trying building this on fedora 23. Being a modern guy,
>> I thought I'd try --enable-qt5. I started with the SPEC file for fedora
>> F25. I didn't get very far.
>>
>> One thing strange, configure choked o
Le 14/04/2016 12:13, Joel Kulesza a écrit :
On Wed, Feb 17, 2016 at 10:39 PM, Scott Kostyshak mailto:skost...@lyx.org>> wrote:
On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote:
> Seems to me a change better for 2.2.0, if Scott is all right with it.
Yes go ahead. And thank
Just for fun, I'm trying building this on fedora 23. Being a modern guy, I
thought I'd try --enable-qt5. I started with the SPEC file for fedora F25. I
didn't get very far.
One thing strange, configure choked on:
g++ -o conftest -O2 -g -pipe -Wall -Werror=format-security -Wp,-
D_FORTIFY_SOURCE=
On Wed, Feb 17, 2016 at 10:39 PM, Scott Kostyshak wrote:
> On Wed, Feb 17, 2016 at 10:11:27PM -0500, Richard Heck wrote:
> > Seems to me a change better for 2.2.0, if Scott is all right with it.
> Yes go ahead. And thanks for the patch.
> Scott
>
Is this a feature that would have been included i
Am Donnerstag, 14. April 2016 um 22:48:32, schrieb Andrew Parsloe
> (Ahem, me again.) This is rc1 from a new clean reinstall with the later
> windows installer. If I try to create a new shortcut, say for
>
> flex-insert blah
>
> I can reach the stage where the blank key is depressed waiting fo
(Ahem, me again.) This is rc1 from a new clean reinstall with the later
windows installer. If I try to create a new shortcut, say for
flex-insert blah
I can reach the stage where the blank key is depressed waiting for a key
sequence, but nothing is recorded, whatever keys I press (as if the
f
Original Message
From: Jürgen Lange
Sent: Donnerstag, 14. April 2016 07:45
To: lyx-devel@lists.lyx.org; Uwe Stöhr
Subject: Re: lyx 2.2.0 RC 1 failed to start in Windows 10
> The new installer works, but I can't reproduce the error anymore by
uninstalling VC++ redist 2015.
It is possible, tha
Am Mittwoch, 13. April 2016 um 20:36:47, schrieb Scott Kostyshak
> On Wed, Apr 13, 2016 at 10:26:13AM +0200, Kornel Benko wrote:
> > Am Mittwoch, 13. April 2016 um 01:20:56, schrieb Uwe Stöhr
> >
> > > Am 13.04.2016 um 00:15 schrieb Kornel Benko:
> > >
> > > > Could you check where the files c
Am Donnerstag, 14. April 2016 um 10:04:02, schrieb Kornel Benko
> > > Sorry. I meant, there is a file
> > > lyx.svg
> > > in Git master and also in the tarball but after the compilation there is
> > > only a
> > > lyx.png
> > > in the resulting folder ~\LYX_INSTALLED\Resources\images
> >
> > Sho
Am Donnerstag, 14. April 2016 um 09:58:15, schrieb Kornel Benko
> Am Donnerstag, 14. April 2016 um 01:50:44, schrieb Uwe Stöhr
>
> > Am 13.04.2016 um 11:15 schrieb Jean-Marc Lasgouttes:
> >
> > >> I noticed that we have the files
> > >> - lyx.svgz
> > >
> > > I cannot find this in our git tree.
Am Donnerstag, 14. April 2016 um 01:50:44, schrieb Uwe Stöhr
> Am 13.04.2016 um 11:15 schrieb Jean-Marc Lasgouttes:
>
> >> I noticed that we have the files
> >> - lyx.svgz
> >
> > I cannot find this in our git tree.
>
> Sorry. I meant, there is a file
> lyx.svg
> in Git master and also in the ta
45 matches
Mail list logo
