When compiling the LyX 2.3.3 tarball, I get this compilation error:
D:\LyXGit\LyX23\development\cmake\lyx.rc(1): error RC2135: file not
found: lyx.ico [D:\LyXGit\LyX23\compile-2017\src\tex2lyx\tex2lyx.vcxproj]
I just pushed a fix to the 2.3 branch
regards Uwe
--
lyx-devel mailing list
Am 04.04.2019 um 01:53 schrieb Richard Kimberly Heck:
You said I have to *compile* LyX on Windows. Of course I *install* LyX
under Windows to test it.
This is fine since you test if the compiled version works.
I agree, of course, that it would be better if the person responsible
for the
Am 02.04.2019 um 03:02 schrieb Richard Kimberly Heck:
You see why I insist that proper Windows support is only possible if the
whole process, compilation, installer building and testing the
installation is run on different Win systems.
No, I don't see why it matters whether we compile LyX on
Am 01.04.2019 um 18:22 schrieb Richard Kimberly Heck:
I use gcc in a cross-platform environment. I.e., I compile for Windows
on Linux.
Hmm, but how do you check what fits to the different Windows systems?
For example last weekend I discovered that the FindProc NSIS plugin that
normally
On 01.04.2019 02:29, Uwe Stöhr wrote:
Am 26.03.2019 um 21:03 schrieb Richard Kimberly Heck:
> > Why is this insulting?
If you can't understand that, then there's nothing anyone can do to
help you.
I forgot to say that it hurt me a lot to hear that after more than 10
years contri
Dear LyXers,
as you might have noticed, I don't provide any official LyX for Windows
installers since a while due to fundamental differences with other
developers how LyX should be installed under Windows.
Due to requests from LyX users I provided now an installer for LyX 2.3.2
with the old
Am 26.03.2019 um 21:03 schrieb Richard Kimberly Heck:
> > Why is this insulting?
>
> If you can't understand that, then there's nothing anyone can do to
help you.
I think I made clear what I meant, if you are insulted by any criticism
then I can't help you.
But you never asked me for help but
On 26.03.2019 03:55, Richard Kimberly Heck wrote:
That has not been true for a while now. It is very much not true now
that we've shifted lyx.org to a much more reliable server.
Every server can stop working. Therefore having mirror is always a good
idea.
It has been said before, but I'll
On 26.03.2019 04:01, Richard Kimberly Heck wrote:
-!define ImageMagickVersion "7.0.7"
+!define ImageMagickVersion "7.0.8"
Please do not change such things on your own. I will change them when I
update such things in my own build tree.
So this is a new rule? In the past the consensus was to
Am 11.02.2019 um 06:10 schrieb Richard Kimberly Heck:
Yes, we decided no longer to offer a bundled installer. That was a
decision we made as a group.
My point of view is: A group of non-Windows developers (at least not on
a daily basis) and with lots of background knowledge made a decision
Am 18.03.2019 um 02:31 schrieb Scott Kostyshak:
Bump. Did we get this figured out?
Well, the -depth8 restriction for ImageMagick can definitely go and i
now just did this. Nevertheless convertDefault.py is broken under python
3.7.x
regards Uwe
On 28.02.2019 08:38, Scott Kostyshak wrote:
I confirm that after updating TL 2018, I can now compile the Embedded
Objects manual. Uwe let me know that the bug was in arydshln 1.75 and
since last weekend the new version 1.76 of this package is available
where the bug is fixed.
For the records:
InstantPreview fails with Python 3.7.2 and I cannot figure out why. In
the console I see:
- graphics\PreviewLoader.cpp (781):
PreviewLoader::finishedInProgress(1): processing failed for python -tt
$$s/scripts/lyxpreview2bitmap.py --png
Dear LyXers,
I have been away for some months because of health problems, new job
etc. but also because I don't use LyX anymore since a while because all
documents I have to work with need collaborative access. And others
don't like to collaborate with me with LyX but with Office365 and the
Today I tried LyX 2.3.2 with Python 3.7.2 and found that all image
conversions failed. I investigated and I found out that this commit
introduced the problem:
5b160e82
Line 38 fails since there is no .decode() for strings.
Also line 35 fails but strangely not line 29.
Attached is the diff to
Compiling the current 2.3.x branch gives me this warning
D:\LyXGit\2.3.x\src\RowPainter.cpp(528): warning C4244: 'argument':
conversion from 'double' to 'int', possible loss of data
[D:\LyXGit\2.3.x\compile-2015\src\LyX.vcxproj]
D:\LyXGit\2.3.x\src\RowPainter.cpp(530): warning C4244: 'argument':
I compiled LyX 2.3.2 from the tarball and get one CMake error that the
file lyx.ico is missing.
I could fix it by putting it into the folder ~\development\cmake.
Either the file is missing or Cmake needs to be adapted that there is no
longer this file.
regards Uwe
As of today the update servers are working again. However, one needs a
workaround because the buggy DLL of MiKTeX prevents the updates from
being applied.
it seems that the bug affects all users of Windows 7 while Win 10 is not
affected. For the affected users there is a workaround but you
Am 29.08.2018 um 03:30 schrieb Uwe Stöhr:
I hope this issue will be fixed soon and report back.
Status report: The problem persists. The fix for MiKTeX was already
released but the main update server of MiKTeX is down. One cannot
retrieve any update yet, no matter what update server
Dear LyX Windows users,
yesterday I noticed a severe bug in the LaTeX system "MiKTeX" that LyX
is usually using under Windows. The problem is that if you
- upgrade MiKTeX or LyX
or
- install a new LaTeX package
or
- refresh the MiKTeX package database
you will end up in a broken LaTeX with
After a long time I could compile LyX. While the 2.3.x branch works
well, I get these compilation errors in current master:
D:\LyXGit\Master\src\insets\InsetTabular.cpp(6575): error C2664:
'void lyx::swap(lyx::Counters &,lyx::Counters &)': cannot convert
argument 1 from
Am 14.07.2018 um 19:05 schrieb Richard Kimberly Heck:
Is there a reason why Qt 5.10 instead of 5.11 was used? Qt 5.11 seems
to have a nice fix for windows users:
https://bugreports.qt.io/browse/QTBUG-43190
Qt 5.10 is what mingw currently provides on Fedora.
Are you saying you create a
Am 07.07.2018 um 00:07 schrieb Richard Kimberly Heck:
Finally, there was the 'style' issue. We now install the
qwindowsvistastyle.dll file, as Enrico suggested. Apparently, it is new
in Qt 5.10 that these are separate files [1].
Why did you use Qt 5.10. We once agreed with Scott to use LTS
Am 10.07.2018 um 00:19 schrieb Uwe Stöhr:
As result I wrote this lengthy mail and hope you read it till
the end where I make some proposals:
Obviously nobody has any comments on my thoughts about LyX's future.
That is sad because I only got few private mails as replies stating that
indeed
Am 09.07.2018 um 23:41 schrieb Richard Kimberly Heck:
At first apologies. My shoulder still doesn't allow me to spend much
time on the PC.
Actually, no, that's certainly not my focus, and I don't think it's the
focus of the rest of the team, either. The only substantial change I
made to the
Dear LyX colleagues,
apologies for being off so long I had an accident hindering me to use
keyboards. However, this gave me some time to think about LyX in
general. As result I wrote this lengthy mail and hope you read it till
the end where I make some proposals:
- I was developing LyX for
Am 09.07.2018 um 20:16 schrieb Richard Kimberly Heck:
Due to a bug in MiKTeX, installation of LyX 2.3.0 can sometimes
cause the MiKTeX installation to be corrupted. We highly recommend
that MiKTeX users update to the latest version *before* installing LyX
2.3.0. (If you run into problems, the
(to deselect third-party programs etc.).
As I understood it, there will be a new installer for LyX under Windows
from the LyX developers based on the code of LyXWinInstaller. I can and
will not give support for this installer because I was not involved in
this development.
regards
Uwe Stöhr
Am 14.05.2018 um 04:11 schrieb Richard Kimberly Heck:
The ONLY question at the moment is
about a warning
dialog at the outset:
Yes. and i made clear why I won't take the responsibility to do this.
You try to please the, let's say 5 % of our expert users who might have
some reasons not to
Am 12.05.2018 um 05:13 schrieb Richard Kimberly Heck:
No, I may wish to make use of it. I am in the process of figuring out
how to build the Windows installer myself, as you suggested. The code
belongs to LyX, not to you.
I never said that it belongs to me.
Please make your decision and
Am 07.04.2018 um 00:48 schrieb Richard Kimberly Heck:
installer that is as automatic as it can be. Many of the rest of us have
real doubts about the wisdom of this,
That is what annoys me. You doubt that I am wise enough to set up LyX
for Windows users.
First of all, I specifically said
Am 07.04.2018 um 00:40 schrieb Richard Kimberly Heck:
If MiKTeX can be broken some other
way, that's a bug in MiKTeX and not one we should be trying to fix via
the LyX installer.
That is the fundamental difference between my and your approach. I see
the user perspective. And for the user it
Am 05.04.2018 um 04:47 schrieb Scott Kostyshak:
In my opinion it is that important, because updating LyX could break
something else on a user's computer.
No! Why do you claim this again? Don't mix potential bugs in a LaTeX
package on CTAN with LyX. With this argumentation every package
Am 05.04.2018 um 03:02 schrieb Richard Kimberly Heck:
It is not true that people don't trust you, and it really isn't helpful
to phrase it that way. This is not an issue of expertise, experience, or
anythinng of that sort. It's a judgement call about what to do in what
is obviously a difficult
Am 31.03.2018 um 19:37 schrieb Scott Kostyshak:
I've included something along these lines in the newest proposal for a
dialog.
Dear Developers,
yes, I take it personally that you cannot trust me as Windows developer
who has experiences with LyX under Windows for more than 10 years. I
gave
Am 23.03.2018 um 05:22 schrieb Scott Kostyshak:
I understand your argument. I disagree that adding a dialog would hurt
the vast majority more than it would help it
That is the fundamental disagreement.
It doesn't help if you ask users who knows what a package is, if they
would understand
Dear Ben,
many thanks for your reply. I am forwarding it to the mailing list that
others can follow the discussion:
Thanks for the answer,
First point:
What I mean is that when you choose
LyX:Preferences -> Language Settings -> Default
Keyboard
Am 22.03.2018 um 06:34 schrieb Scott Kostyshak:
Thank you for this detailed explanation. It's unfortunate that we have
this disagreement on what is best for the users, but I appreciate that
you have put a lot of thought into your decision and I know that you
care a lot about the users.
Don't
Am 21.03.2018 um 15:07 schrieb Ben Houcine:
I will drop some of my remarks here:
- Key binding in LyX should be improved because the standard keybinding
bundled with LyX fit more the American qwerty keyboard. I have my own
keybinding to the French azerty keyboard
Dear Ben,
LyX can be used
Dear LyXers,
I just uploaded a new installer version 6:
http://ftp.lyx.de/LyXWinInstaller/LyX2.3.0/
The only change compared to the previous version is that the bundle
installer contains the latest miktex-basic installer. This fixes some
bugs for users installing LyX (with LaTeX) the first
Am 19.03.2018 um 00:44 schrieb Pavel Sanda:
I checked it out. When I used the installer I did not give me any option,
it just 'informed' that MiKTeX is going to be upgraded and forced me to
accept it. That's what I said can make some people mad and decent application
should not do without
Am 19.03.2018 um 10:17 schrieb Sivan Frenkel:
I am a Win10 user and Scott has directed me to the LyX 2.3 win
installer, which is still not on the website. The installer worked. I
have updated my MiKTeX before I ran the installer but it still took a
while when the MiKTeX was updated in the
Am 16.03.2018 um 09:56 schrieb Pavel Sanda:
Uwe Stöhr wrote:
So my plan is to use the 2.3.0 installer also as repair kit.
Yes, this was kind of clear and pretty much everyone on this list thinks that
we should not do such things hiddenly without advertising.
This is not hidden. As you have
Am 15.03.2018 um 18:29 schrieb Richard Heck:
I was talking about whether anything would happen *as a result of
someone running
the installer*. I understand that there are *other* ways that the MiKTeX
installation can
be damaged, as happened to your mother. That is a really horrible MiKTeX
bug,
Am 14.03.2018 um 04:31 schrieb Richard Heck:
If this dialog is popped at the very beginning of the installation,
before ANYTHING
is actually done, then it is impossible that the MiKTeX installation
should be affected.
This is not true and I don't get why I cannot make this clear to you.
Am 13.03.2018 um 04:17 schrieb Scott Kostyshak:
I definitely agree that every additional dialog is an additional
possibility for confusion. I think where we disagree is on the benefit
that the dialog could bring.
Yes. You don't understand that users who don't about LaTeX and deny the
update
Am 12.03.2018 um 04:32 schrieb Richard Heck:
That is a serious mistake: to focus on "average users". But it has
clearly become pointless to discuss this any longer.
Dear Richard,
I cannot leave this commented because it is too fundamental. I tried to
calm down, but cannot.
What is LyX
Am 11.03.2018 um 18:12 schrieb Scott Kostyshak:
I think that's what we're doing. The basic disagreement we have is that
I think adding a dialog will bring more benefit than harm.
And I made clear why I am opposed to this.
In the end it costs my spare time if something does not work. Users
Am 11.03.2018 um 05:08 schrieb Scott Kostyshak:
So there are already 3 possible workarounds for experienced users in the LyX
installer and these options are all translated.
That behavior sounds good. My concern though is that even experienced
users will not guess that LyX will update MiKTeX.
Am 11.03.2018 um 01:29 schrieb Scott Kostyshak:
I think our main point of difference is below. If the LyX 2.3.0
installer successfully installs LyX, but has a bad secondary effect, I'm
guessing you would agree that a dialog would make sense, right?
I am not the developer of MiKTeX but I see
Am 10.03.2018 um 21:37 schrieb Uwe Stöhr:
Meanwhile I got the report that version 4 of the LyX Win installer fails
on some 64bit Windows. I am currently working on this and will most
probably come up with another version of the installer that fixes this.
I could fix this now. I indeed forgot
Am 11.03.2018 um 00:57 schrieb Scott Kostyshak:
If in the LyX 2.3.0 installer we provide an informative dialog, the user
might say "oh I did not know that LyX needed to update MiKTeX. I will
not install LyX now because I need to submit my paper tomorrow. After I
submit my paper, I can deal with
Am 11.03.2018 um 00:57 schrieb Scott Kostyshak:
I believe their goal is to get a working LyX, but they are not aware
that they might be paying a cost. They might not want to update MiKTeX,
and they should not expect that LyX is going to update MiKTeX. Thus,
although they might want a working
Am 10.03.2018 um 21:37 schrieb Uwe Stöhr:
I understand what you wrote but not your goal behind it.
I use the LyX installer to install LyX. Therefore I expect a working LyX
afterwards.
In other words:
- we agree that users who run an installer of LyX want
* to get LyX
* a working LyX
So
Am 09.03.2018 um 18:33 schrieb Scott Kostyshak:
Do you understand the argument that I, Richard, Jean-Marc, and racoon
have expressed (to those I cite, please correct me if I misrepresent
your opinion)?
I understand what you wrote but not your goal behind it.
I use the LyX installer to install
Am 09.03.2018 um 05:58 schrieb Uwe Stöhr:
Am 09.03.2018 um 05:34 schrieb Scott Kostyshak:
From what I understand, I think we still need to come to an agreement on
whether to provide a dialog to the user asking if they would like to
either cancel the installation or proceed and have
Am 09.03.2018 um 05:34 schrieb Scott Kostyshak:
From what I understand, I think we still need to come to an agreement on
whether to provide a dialog to the user asking if they would like to
either cancel the installation or proceed and have the installer update
MiKTeX.
Please, I wrote now so
Am 08.03.2018 um 22:19 schrieb Scott Kostyshak:
Unfortunately I think the MiKTeX issues also affect the installer (see
the email from Uwe on Feb. 26).
I just post that all known issues have been fixed from my Windows
perspective. You can in my opinion go an release.
regards Uwe
Am 07.03.2018 um 16:17 schrieb Uwe Stöhr:
I am going nuts. MiKTeX released now some fixes to its package handling
but they arrived broken on the package servers. Therefore since today
the solution we found for LyX in combination with MiKTeX doesn't work.
This was not correct. In fact MiKTeX
Am 07.03.2018 um 18:16 schrieb Jean-Marc Lasgouttes:
OK, I see now. But wasn't there something equivalent before that?
The console is a new concept. Before there exist 2 different programs,
one for the settings, one for the package handling. the new console
unites them.
What makes
Am 07.03.2018 um 17:27 schrieb Uwe Stöhr:
I must admit that I haven't tested the
"never" case for a long time.
I tested this now and the installer correctly respects the setting
"never". So never means never. You don't get any updates nor packages if
you really don't wa
Am 06.03.2018 um 16:37 schrieb Jean-Marc Lasgouttes:
In general: I have no problem in being criticized. But I have a problem
that I am talking directly to the MiKTeX developer to find a solution
and when I do what he proposes you are telling me that it can be done
better.
The goal is
Am 04.03.2018 um 19:36 schrieb Uwe Stöhr:
I would nevertheless wait with the announcement because the MiKTeX
developer promised to make a release just for us soon. If it will be
available by Tuesday, I will create a new installer, if not, let's
release LyX 2.3.0 with the installer version 3 I
Am 05.03.2018 um 17:58 schrieb Joel Kulesza:
At least, the way I read the step, the installer is the component not
finding the latex.exe executable, not the LyX executable itself
Just for information:
The LyX installer searches for the latex.exe. If it cannot find it, LyX
cannot find it as
Am 04.03.2018 um 16:50 schrieb Scott Kostyshak:
The following statements are specific to Windows users:
...
- After the installation of LyX, the MiKTeX package manager pops up. You
can just close it.
This item can be removed. This is now fixed in MiKTeX.
regards Uwe
Am 06.03.2018 um 04:47 schrieb Richard Heck:
What? So I should deliver a LyX installer leading to a broken LaTeX
that can only be fixed by reinstalling MiKTeX? That cannot be the goal!
The proposal is to *abort* the LyX installation, if the user does not
want to update. You can explain in a
Am 05.03.2018 um 09:13 schrieb Jürgen Spitzmüller:
Am Sonntag, den 04.03.2018, 21:51 +0100 schrieb Uwe Stöhr:
tex2lyx in master is no longer compilable with MSVC. The reason is
that
we have now too many else if clauses in text.cpp:
Should be fixed.
Many thanks! Your solution
Am 05.03.2018 um 23:46 schrieb Richard Heck:
Uwe, even if LyX will not work without the updated installation, we
CANNOT update the user's LaTeX installation without asking for
permission---which means giving them the option to cancel the entire
install. Otherwise, we can break things, as in the
Am 05.03.2018 um 19:37 schrieb racoon:
However, it does not give the user a choice on whether to update MiKTeX
or not.
Yes, that is correct and I explained now in several mails why and that
there is no other option.
Also, I noticed that the MiKTeX Package Manager opens up for some reason
Am 04.03.2018 um 18:59 schrieb Jean-Marc Lasgouttes:
So I install texlive with the medium size install
Sure, but to do this you need Internet access.
Having to wait
until I actually use LyX to decide what packages to install would be a
recipe for failure.
Again, the problem I had is not
tex2lyx in master is no longer compilable with MSVC. The reason is that
we have now too many else if clauses in text.cpp:
D:\LyXGit\Master\src\tex2lyx\text.cpp(5269): fatal error C1061:
compiler limit: blocks nested too deeply
[D:\LyXGit\Master\compile-2015\src\tex2lyx\tex2lyx.vcxproj]
Am 04.03.2018 um 16:19 schrieb Uwe Stöhr:
Good news: There will be a new MiKTeX installer soon and the MiKTeX
maintainer proposed a workaround for the main bug. I cannot promise that
I will find time today to check if this will work for all cases.
OK, I could check it and it works. The new
Am 04.03.2018 um 16:59 schrieb Scott Kostyshak:
I don't want to write pages to describe the problematic in detail.
Summarized, the problem is that MiKTeX uses a new package handling system
and in order to use LyX with MiKTeX this new system must be used.
LyX works on Windows with a TeX Live
Am 04.03.2018 um 00:32 schrieb Uwe Stöhr:
As soon there is a new MiKTeX installer available I will release another
installer
Good news: There will be a new MiKTeX installer soon and the MiKTeX
maintainer proposed a workaround for the main bug. I cannot promise that
I will find time today
Am 03.03.2018 um 21:26 schrieb Scott Kostyshak:
- If you have a problem compiling the document Help > User Guide after
installation, consider uninstalling LyX and MiKTeX, and then using
the LyX *bundle* installer, which will automatically reinstall
MiKTeX.
Please replace
Am 03.03.2018 um 19:24 schrieb Scott Kostyshak:
I have a similar concern to Richard (and a similar disclaimer that I
don't know much about Windows). Even if what you put is the case, I
would prefer for the LyX installer to just give an error such as "Cannot
install LyX without the newest
Am 02.03.2018 um 20:16 schrieb Uwe Stöhr:
- Conclusion: I cannot do more right now to wait until MiKTeX releases
the fixes for the 2 bugs.
Here is the solution in form of a new installer:
http://ftp.lyx.de/LyXWinInstaller/LyX2.3.0/
I don't want to write pages to describe the problematic
Am 02.03.2018 um 20:59 schrieb Richard Heck:
I don't know a lot about Windows, but let me just ask: Do we really want
to force people to upgrade some other package when they install LyX?
As I wrote in a previous post, the thing is that MiKTeX released in
February a new package handling
Am 02.03.2018 um 20:39 schrieb José Abílio Matos:
This is mater of style, but personally I think that the next option is
more readable:...
Hello José,
fine with me. All I did was to find the missing " and adding them.
Please change the line as you like and commit to master. I will backport
Here is the final analysis:
- there is definitely no Virus or so, these false positives can be ignored
- there is a bug in LyX we need to fix:
https://www.lyx.org/trac/ticket/11053
- I created a new installer that forces a silent MiKTeX update. This
assures that every user gets the current
Am 02.03.2018 um 08:14 schrieb racoon:
I am quite sure that MiKTeX wasn't the problem in my case.
Well, I worked a lot:
- I asked now as many friends as possible to installer. Nobody had a
problem but except of one they all installed MiKTeX the first time
together with LyX. The other one,
Am 28.02.2018 um 10:25 schrieb racoon:
Strange. I just ran the installer again and now it works.
Have you run MiKTeX update on every run of the installer as the
installer suggested? If so your virus scanner is not to blame.
I have not yet a solution for this other than to reinstall MiKTeX.
Am 01.03.2018 um 17:18 schrieb Scott Kostyshak:
If this is the cause of all the problems, I guess all we can do is put
a note in the announcement. I do not think we can officially recommend
disabling anti-virus during the installation, but at least we can
explain the situation.
I am opposed
> Strange. I just ran the installer again and now it works.
The installer checks the Windows registry to locate LaTeX program. If you have
MiKTeX or TeXLive installed but the installer cannot find it, your virus
scanner blocks that the installer have read access to the registry. This should
I could successfully build LyX 2.3.0 from the tarball and the installer
is ready. Nevertheless there are some issues in CMake that we should
consider to change:
- after the compilation I get a subfolder named "LYX_INSTALLED". it
contains everything one needs to build the installer, except of
Am 23.02.2018 um 04:03 schrieb Scott Kostyshak:
Uwe, I included the same note that we did for 2.2.0, mentioning that if you
installed a pre-release, you should uninstall those versions. Is this
still the correct note?
Yes, this is still correct.
My experience is that some users e.g. only
Am 20.02.2018 um 22:03 schrieb Scott Kostyshak:
even for documentation
or changing comments or whitespace, be posted to the list explicitly
saying why it should be included for 2.3.0. The only exceptions to this
are po files and lib/layouttranslations.
Hi Scott,
I would like to allow also
Am 20.02.2018 um 19:27 schrieb Scott Kostyshak:
Uwe, will you have time to fix this issue soon?
it should be fixed now, please test.
regards Uwe
> After deleting the offending character I see new changes in el & uk,
which went uncommitted.
I installed now the polib python extension and tried to generate
layouttranslations. After removing the BOM I get this error:
File "C:\Program Files (x86)\Python36-32\lib\encodings\cp1252.py", line
Am 20.02.2018 um 00:06 schrieb Uwe Stöhr:
is encoded in UTF-8 with BOM. So maybe the first character you see is
the BOM:
I first realized it thanks to your report. I found out that this is the
default setting of my text editor when saving as UTF-8. For me on
Windows the BOM is a good ideas
Am 20.02.2018 um 00:00 schrieb Pavel Sanda:
Uwe, you are likely committing some crap, look at the first character on the
first line.
Hi Pavel,
I don't like this sound. I don't commit crap, maybe I made a mistake.
In this case I cannot see a problem. The file I committed is correct. It
is
Am 19.02.2018 um 03:07 schrieb Scott Kostyshak:
I've found the Hungarian translator, and sent him an email to a
different email address. If he is still interested in doing
translations, I will updated his email address. But what if he is no
longer interested?
Alex quit LyX when he became a
Am 13.02.2018 um 00:19 schrieb Scott Kostyshak:
I agree that the 2.3. branch is stable I used it recently for a larger
document. The strange, random Win-only crash is annoying but we cannot do
much right now.
Just to make sure, the crash you're talking about also exists for 2.2.x,
right?
Am 10.02.2018 um 19:51 schrieb Scott Kostyshak:
I'm planning to be more strict now on which bug fixes go in for 2.3.0. I
might prefer that even a simple bug fix not be committed, unless it
fixes an important bug.
Hello Scott,
I agree that the 2.3. branch is stable I used it recently for a
Am 01.02.2018 um 18:21 schrieb Scott Kostyshak:
On Thu, Feb 01, 2018 at 02:14:34PM +, emile lunardon wrote:
LyX for Windows offers incomplete support for non-TeX fonts. This is the
case, for example, of the Gyre Schola font, which although proposed by
Miktex 2.9 , is unknown to LyX 2.3 RC2
Am 29.01.2018 um 06:04 schrieb rgh...@lyx.org:
Author: rgheck
Date: Mon Jan 29 06:04:55 2018
New Revision: 41164
URL: http://www.lyx.org/trac/changeset/41164
>
-$branch_tag = "2.2.x";
+$branch_tag = "master";
Hello Richard,
I think this page should show the translations of the current
Am 29.01.2018 um 04:53 schrieb Scott Kostyshak:
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.3/lyx-2.3.0rc2/
Packagers, please send me your binaries.
Here is the Win build:
http://ftp.lyx.de/LyXWinInstaller/LyX2.3.0-RC2/
regards Uwe
Am 28.01.2018 um 06:58 schrieb Scott Kostyshak:
Please do not commit anything to the 2.3.x branch after 22:00 UTC today
(Sunday). I would like to do the final testing and preparation for
2.3.0rc2.
Sh... I saw this too late.
Sorry and regards
Uwe
Am 23.01.2018 um 19:18 schrieb Scott Kostyshak:
Qt 5.9.4 was released today:
http://blog.qt.io/blog/2018/01/23/qt-5-9-4-released/
Many thanks. I upgraded and can compile LyX with it. I also built an
installer using current 2.3.x branch and all tests were passed.
However,
Am 15.01.2018 um 19:18 schrieb Scott Kostyshak:
I think there are still changes in beamer.lyx. Should those be
distributed?
Thanks for the hint. Most were already distributed. I accepted now the
changed and fixed a compilation error in the French beamer.lyx
regards Uwe
1 - 100 of 9455 matches
Mail list logo
