Re: possible tag and tar of 2.2.0rc1 on Tuesday

Scott Kostyshak wrote: > On Tue, Apr 05, 2016 at 08:40:39AM +0200, Georg Baum wrote: >> Scott Kostyshak wrote: >> >> > On Mon, Apr 04, 2016 at 10:21:52PM +0200, Georg Baum wrote: >> >> Unfortunately I overlooked something in the portuguese translation, I

Re: acmsiggraph layout: update or new version?

Guenter Milde wrote: > There was well based objection to the proposal of a new version-layout by > Georg in http://permalink.gmane.org/gmane.editors.lyx.devel/161202 from > 28 March: > > Before discussing the case of incompatible versions with the same name > further, I'd like to see an

Re: po-files with trailing

Pavel Sanda wrote: > Georg Baum wrote: >> python script we should forbid .po file remerging on windows IMHO. > > Except it is Uwe who took the burden to be recipient of po updates sent > to po-upda...@lyx.org and care for them in the long term fashion... > Pavel Yes, fix

Re: acmsiggraph layout: update or new version? (was: patch for aastex6)

Guenter Milde wrote: > On 2016-04-05, Richard Heck wrote: >> On 04/05/2016 04:36 AM, Guenter Milde wrote: > > For the other patch (acmsiggraph.layout with incompatible version > but same cls file name), I would wait for an agreement whether to > update the layout (file format change

Re: po-files with trailing

Kornel Benko wrote: > Nice article. So for us it would suffice to create '.gitattributes' file > with the content: *.po text Almost. The last time I investigated this I was about to add the attached one, but it is not enough. Not only the line ends of the files are broken, but they do contain

Re: possible tag and tar of 2.2.0rc1 on Tuesday

Scott Kostyshak wrote: > On Mon, Apr 04, 2016 at 10:21:52PM +0200, Georg Baum wrote: > >> I'd really like to wait for the final updates for pt_PT and pt_BR for RC1 >> if possible. > > OK we'll wait. Thank you very much. The brazialian translation is OK now (but it t

Re: patch for aastex6

Scott Kostyshak wrote: > On Mon, Apr 04, 2016 at 08:45:17AM +, Guenter Milde wrote: > >> For the other patch (acmsiggraph.layout with incompatible version but >> same cls file name), I would wait for an agreement whether to update the >> layout (file format change needed) or add a new one.

Re: patch for aastex6

Guenter Milde wrote: > The patch is ready. > > This is the "new layout for new cls file name" case, similar to what we > already have for, e.g. scrltr2. > > As it looks like we all agree that a new layout does *not* require a file > format update, we could also put this in after rc1. > >

Re: Proposal for a guide on updating layouts

Guenter Milde wrote: > > Dear Georg, > > thank you for your feedback. > > On 2016-04-03, Georg Baum wrote: > >> Concerning the list in section 2.2 I'd prefer it to stay simple. It >> starts to become too complicated for my taste. There is too much >> n

Re: possible tag and tar of 2.2.0rc1 on Tuesday

Scott Kostyshak wrote: > Dear all, > > Thanks to the help of several LyX developers who addressed needed issues > for 2.2.0rc1, we are getting close. I would like to propose Tuesday as > the tentative date to tag and tar rc1. There are still some issues that > are pending but I hope that they

Re: [LyX/master] Arabic translations have been reviewed

Pavel Sanda wrote: > Georg, > I am somewhat confused. Was the ack from arabic translator > for all these changes already? Yes, on the users list: http://www.mail-archive.com/lyx-users@lists.lyx.org/msg102705.html Georg

Re: Proposal for a guide on updating layouts

Guenter Milde wrote: > Thank you for the commit. > > I did a review (patch appended). OK to commit? Thanks for the update about the modules, this makes it more clear. Concerning the list in section 2.2 I'd prefer it to stay simple. It starts to become too complicated for my taste. There is

Re: Proposal for a guide on updating layouts

Guenter Milde wrote: > I tried to start a chapter about new and updated layouts in > Development.lyx. Of course, this is a biased view based on my experiences > and ideas, so please correct and amend before this can be the base for a > consensus. > > Patch below, OK to commit? I like it, but I

Re: possible tag and tar of 2.2.0rc1 on Tuesday

Scott Kostyshak wrote: > 2. There is a mysterious crash with the MSVC2015 > http://www.lyx.org/trac/ticket/10009 which does not happen with a merged > build. Since we do not understand why a merged build "fixes" the crash we > do not know what other problems might be created by the same cause.

Re: patch for aastex6

Guenter Milde wrote: > On 2016-03-31, Georg Baum wrote: >> Guenter Milde wrote: > >>> For a safe "last minute commit", it would be good if somone could check >>> the code itself, and the notes in the updated template and example file >>> and then

Re: Proposal for a guide on updating layouts

Guenter Milde wrote: > On 2016-03-29, Georg Baum wrote: > >> I assumed that we update the template, but I still don't understand how >> an updated template will remind a user that he needs to change the >> document class of existing documents. Where is the connection

Re: patch for aastex6

Guenter Milde wrote: > For a safe "last minute commit", it would be good if somone could check > the code itself, and the notes in the updated template and example file > and then give an explicit +1 or not. I did not test anything, but I looked at the code and the notes. They are all OK. The

Re: patch for acmsiggraph

Guenter Milde wrote: > Thinking about it while writing aastex6.layout, there is a major > disadvantage of the "old loads new" approach: > > * aastex6.layout inputs aastex.layout and currently only changes the name > and referenced LaTeX class file. > > I future, it should also support

Re: Issues to discuss for 2.2.0rc1

Scott Kostyshak wrote: > Do you think Monday (April 4) is enough time? That would give the > weekend, at least. OK, I'll try that. >> Where can I get a >> current list of the email addresses of the translators? > > Others have taken care of contacting the translators, so I'm not sure > what

Re: Issues to discuss for 2.2.0rc1

Jean-Marc Lasgouttes wrote: > I get your point. Anyway I still think there would be value in compiling > LyX on windows with several Qt and compilers. The fact that we do that > in Linux has been very useful IMO. Definitely. I always try to compile my stuff with as many compilers/platforms as

Re: [LyX/master] Norwegian files: add missing \origin tag

Scott Kostyshak wrote: > Can you confirm that the following instances do not cause any problems > and that I only need to check in lib/doc ? > > $ grep -R '\\origin unavailable' > development/MacOSX/ReadMe/LisezMoi.lyx:\origin unavailable > development/MacOSX/ReadMe/Leame.lyx:\origin unavailable

Re: Issues to discuss for 2.2.0rc1

Jean-Marc Lasgouttes wrote: > Le 27/03/2016 21:38, Uwe Stöhr a écrit : >> As I just wrote in the other thread I prefer Qt 5.6. >> I can nevertheless release RC1 with Qt5.5.1/MSVC2010 and also a Qt 5.6 >> version. However, for the final release I won't maintain/offer support >> for a Qt 5.5.1

Re: Proposal for a guide on updating layouts

Guenter Milde wrote: > On 2016-03-28, Georg Baum wrote: >> Guenter Milde wrote: >>> On 2016-03-25, Richard Heck wrote: > >>> As the package name on CTAN is still "aastex" >>> (http://www.ctan.org/pkg/aastex), the template could also keep the >&

Re: Proposal for a guide on updating layouts

Richard Heck wrote: > On 03/28/2016 06:50 AM, Georg Baum wrote: > >> We need to be very careful here: Producing a PDF from a LyX file must not >> produce different results depending on the LaTeX installation, this would >> be very confusing. > > Is this avoid

Re: Proposal for a guide on updating layouts

Guenter Milde wrote: > On 2016-03-25, Richard Heck wrote: >> On 03/25/2016 02:34 AM, Scott Kostyshak wrote: > >>> In the example (#10027), the new layout name would be aastex6.layout >>> and the new template name would be aastex6.lyx. > > As the package name on CTAN is still "aastex" >

Re: Proposal for a guide on updating layouts

Kornel Benko wrote: > Am Freitag, 25. März 2016 um 02:34:38, schrieb Scott Kostyshak > > >> ***2 Automatic detection of changes in class files >> Another good idea for a feature request was by Uwe: >> >> - we run a script every month that checks if a document class was >>

Re: Proposal for a guide on updating layouts

Scott Kostyshak wrote: > We would like to update our layout files for various reasons: > > 1. The layout file format was changed (e.g. a new class parameter was > added). > - this case is only relevant for master and in this case we update the > layout > files so that we can ensure that

Re: Proposal for a guide on updating layouts

Richard Heck wrote: > Comments interspersed. Let me say right away that, as far as this goes, > it all seems sensible. But, as I'll say below, it doesn't address what > has always been the most serious problem. > > On 03/25/2016 02:34 AM, Scott Kostyshak wrote: >> 3. The LaTeX class file

Re: [LyX/master] Norwegian files: add missing \origin tag

Stephan Witt wrote: > Am 27.03.2016 um 19:10 schrieb Uwe Stöhr : >> >> Am 23.03.2016 um 21:29 schrieb Helge Hafting: >> >>> Just a little question - what is this \origin tag? I didn't find it in >>> the user's guide. Is it available somewhere in the document settings? >> >>

Re: Issues to discuss for 2.2.0rc1

Scott Kostyshak wrote: > On Sun, Mar 27, 2016 at 11:45:33AM +0200, Georg Baum wrote: >> Pavel Sanda wrote: > >> It is highest time to call for reviews. The last call is here: >> http://www.mail-archive.com/lyx-docs@lists.lyx.org/msg07949.html >> >> Scott,

Re: Static member initialization ordering bug

Richard Heck wrote: > On 03/27/2016 03:09 PM, Jean-Marc Lasgouttes wrote: >> >> Therefore, if can happen than plain_insetlayout_ is initialized before >> sane_font and inherit_font have been initialized, which creates the >> problems that Kornel sees. >> >> What is the right construct to avoid

Re: Handling of \SpecialChar

Andrew Parsloe wrote: > On this subject, shouldn't there also be a logo for XeTeX? If you need one it could be added. So far nobody asked for it, and there are a couple more (LuaTeX, XeLaTeX etc). Georg

Re: Handling of \SpecialChar

Andrew Parsloe wrote: > I notice (in 2.2 beta2 on windows7) on typing LyX, TeX, LaTeX, LaTeX2e, > that these strings are *not* converted to the logos. Nor does saving, > closing and reopening the document convert them to the logos, nor do > they display as logos in the pdf. > > However, if I

Re: Issues to discuss for 2.2.0rc1

Pavel Sanda wrote: > I keep track of missing things in layouttranslations.review. > In last releases when strings were frozen, I wrote to all translators to > check few additional items. > > I missed the freeze-string message on the dev list to react appropriately > at the time; I still planned

Re: Issues to discuss for 2.2.0rc1

José Matos wrote: > For python 3 the strings are now unicode strings and so all works: > > $ ipython3 --no-banner > > In [1]: type( "123%s" % "") > Out[1]: str > > In [2]: type( "123%s" % u"") > Out[2]: str > > So a safe bet would be to prefix all the strings with an u, overkill sure > but it

Re: Issues to discuss for 2.2.0rc1

Scott Kostyshak wrote: > - What am I missing? While testing the changed lyx_pot.py file I did also update lib/layouttranslations. The result is attached. Either I missed it, or there was no call for confirmation of changed layout translations. If there was no call, then we definitely need it

Re: Issues to discuss for 2.2.0rc1

José Matos wrote: > So Georg if you got the code to work with python2 in you have my +1. :-) Thanks for looking at this. > There are two possible source of problems: > 1) input files should be utf-8. Since I think that is the case the patch > is safe. Yes, all input files are encoded in utf8,

Re: Issues to discuss for 2.2.0rc1

Scott Kostyshak wrote: > - I do not understand if we need to do something for #9979? IMHO only if there is some volunteer who has a fix ready in time. The conditions for this bug are so special that it also can wait a little bit longer. > - Georg has provided a patch to improve building with

Re: LyX 2.2.0 compile crashes on first attempt after clone

Kornel Benko wrote: > That said, I did not know that we are python3 ready. We are not. When python scripts are called by LyX it is ensured that python2 is called. This is not done during building, although some python scripts used for building require python2 as well. The error Helge was

Re: LyX 2.2.0 compile crashes on first attempt after clone

Scott Kostyshak wrote: > On Thu, Mar 17, 2016 at 08:12:03PM +0100, Georg Baum wrote: >> >> The error Helge was seeing is most likely a python3 incompatibility. IIRC >> one thing that changed for python3 is that you need to give the encoding >> to use on file ope

Re: Plan for 2.2.0rc1

Uwe Stöhr wrote: > This one of Georg's special posts ;-). I read it now again at least 5 > times and still don't understand what I should do. > So I should > 1. rename the existing layout (I guess that is meant with old), but to > what name? A name with the version in it: acmsiggraph080.layout

Re: Plan for 2.2.0rc1

Uwe Stöhr wrote: > - we still haven't done anything to fix the 2 layouts that will produce > uncompilable files (acmsiggraph and agutex). Please make a decision and > I will apply it that way.. It would be embarassing when we include > outdated layouts despite that we are aware of this. These

Re: Plan for 2.2.0rc1

Jean-Marc Lasgouttes wrote: > Le 14/03/2016 01:21, Uwe Stöhr a écrit : >>> And I only propose a 2.2.0 release with Qt 5.5.1 and msvc10. We could >>> not change compilers and Qt versions like socks. >> >> But the idea of LyX 2.2 was to use Qt 5.6 because this will be a long >> term support

Re: [LyX/master] Fix cursor movement for large logos (#9628)

Scott Kostyshak wrote: > I looked for a better way to find out whether an inset has a context > menu and did not find one. Note that display math does not seem to have > a context name but does have a context menu. > > I did significant testing with the patch and it works well. Thanks for

Re: [LyX/master] Fix cursor movement for large logos (#9628)

Jean-Marc Lasgouttes wrote: > So when left-clicking insets will not have the same behavior depending > on them having a context menu? Yes, but I could not find an inset where this matters. I originally tried to use the mouse button information last year, but unfortunately I do not remember

Re: [LyX/master] Fix cursor movement for large logos (#9628)

Scott Kostyshak wrote: > I think this caused the following change in behavior for me: it is > possible for me to get the context menu when right-clicking on a newline > inset but to have the options greyed out. I think this happens more > often when I right-click on the far right of the red,

Re: Plan for 2.2.0rc1

Scott Kostyshak wrote: > Guillaume committed a fix that was tested by Enrico and Uwe. If you have > time to check it, take a look at b3bed292. Works fine and fast for me (but I did never see the crash, only the slowlyness). Very nice, this is exactly what I had in mind but did not now how to

Re: Plan for 2.2.0rc1

Scott Kostyshak wrote: > Dear all, > > I think we are getting close to being able to release 2.2.0rc1. We have > not discussed whether to release a beta3 or move directly to rc1. If > others disagree with moving directly to rc1, please do speak up and > let's discuss. rc1 is fine. > Below are

Re: int64 compiler warnings

Jean-Marc Lasgouttes wrote: > Le 07/03/2016 13:21, Alex Vergara Gil a écrit : >> Best way for this is to use native int as integer variables and you >> forget about it, this works even on windows, so instead of int use >> long and thats it: http://en.cppreference.com/w/cpp/language/types > > In

Re: Bug in Insert > Special Character > Symbols in beta1 & 2

Jean-Marc Lasgouttes wrote: > Amain drawback of gprof is that it only covers code that is compiled > with -pg, which means only LyX code here. You don't get to see anything > related to Qt, librairies that it uses, or even kernel. This makes it > pretty useless in this case. Of course you are

Re: Hyphens in LyX-Code in beta2

Andrew Parsloe wrote: > I have created a ticket #9987. Thanks for the report Andrew. This was indeed not wanted and an oversight from my side. Jean-Marc, thanks for looking at the issue, you have my +1 for the patch posted at

Re: [patch] support Bosnian, Macedonian, Piedmontese and Romansh

Guillaume Munch wrote: > Thank you for your taking time for making these points. So nobody seem > to agree that this is as low risk / high reward as Uwe thinks (I cannot > judge by myself since I am not familiar with this part of LyX; for > instance, I thought that this would provide also

Re: [patch] support Bosnian, Macedonian, Piedmontese and Romansh

Uwe Stöhr wrote: > Am 22.02.2016 um 20:23 schrieb Georg Baum: > >>> Le 21/02/2016 20:52, Scott Kostyshak a écrit : >>>> On Sun, Feb 21, 2016 at 06:06:14PM +0100, Uwe Stöhr wrote: >>>>> I also don't see a reason why this cannot be done now since otherwis

Re: Bug in Insert > Special Character > Symbols in beta1 & 2

Liviu Andronic wrote: > This I can replicate. However, it's not a permanent freeze. I can see > the CPU spiking, and LyX takes something like 10-15sec to settle, but > then the dialog appears and scrolls fine. I would imagine LyX attempts > to load quite a number of symbols, including hard to

Re: Remove date external template for 2.2.0?

Jean-Marc Lasgouttes wrote: > Le 18/02/2016 04:50, Scott Kostyshak a écrit : >> There have been various discussions about how the date external material >> template is useless. I think it was kept around mostly just to be an >> example of what could be done. >> >> Two questions: >> 1. Do we want

Re: lyx-cvs messages: show file names changed

Jean-Marc Lasgouttes wrote: > Le 18/02/2016 02:58, Scott Kostyshak a écrit : >> Would anyone else find it useful if the lyx-cvs messages showed the file >> names that were changed at the beginning of a message? One example is >> that I would often like to know if a commit is documentation only or

Re: [patch] support Bosnian, Macedonian, Piedmontese and Romansh

Guillaume Munch wrote: > Le 21/02/2016 20:52, Scott Kostyshak a écrit : >> On Sun, Feb 21, 2016 at 06:06:14PM +0100, Uwe Stöhr wrote: >>> I also don't see a reason why this cannot be done now since otherwise >>> users of than languages would have to wait 2 more years until LyX 2.3. Every LyX

Re: 2.2.0beta1 tar balls are available

Pavel Sanda wrote: > Georg Baum wrote: >> Pavel Sanda wrote: >> >> > -Wall -Wextra -std=c++11 -g -O2 -Wno-deprecated-declarations >> >> I cannot reproduce using these flags with gcc 4.9.2. > > Shouldn't matter IMHO, but running 32 bit here. That migh

Re: 2.2.0beta1 tar balls are available

Pavel Sanda wrote: > Georg Baum wrote: >> No, but I believe I know the reason: self made rounding in combination >> with optimization (I created the test reference with a debug build). >> Which compiler switches do you use? > > -Wall -Wextra -std=c++11 -g -O2 -Wno

Re: 2.2.0beta1 tar balls are available

Jean-Marc Lasgouttes wrote: > Looks like there is an extra pair of parenthesis. Thanks, I noticed that meanwhile as well. Update patch follows soon. Georg

Re: [LyX/master] Add missing boost files to source package

Peter Kümmel wrote: > Am 15.02.2016 um 22:06 schrieb Georg Baum: >> > > Done . Thanks. >> What about the unused files libs/regex/regex.vcproj, >> libs/signals/signals.vcproj, libs/regex/src/icu.cpp, >> libs/regex/src/usinstances.cpp and libs/regex/src/wc_regex_

Re: State of master and release process

Scott Kostyshak wrote: > Just an update for those who have not been following the other > conversations, and also a question: > > beta2 has been tagged, and the tars have been posted. We have not > formally released it because we are still trying to make it so that it > is possible to compile on

Re: [LyX/master] Add missing boost files to source package

Peter Kümmel wrote: > commit 6de524e6cf2d13636b04b9bb850d0a8b1eaa398b > Author: Peter Kümmel > Date: Sat Feb 13 18:34:08 2016 +0100 > > Add missing boost files to source package > > and remove Visual Studio files, we build with CMake on Windows. > > diff --git

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

Guenter Milde wrote: > I assume, heb1.tex is "splash_good.tex" and heb2.tex is "splash_bad.tex", > right? I guess so. My newsreader did not display any names for the attachments at Scotts message. > >> So, the real diferences of this change are: > >> 1) LyX writes cp1255 encoding instead of

Re: beta2?

Peter Kümmel wrote: > Am 14.02.2016 um 19:03 schrieb Scott Kostyshak: Why is numeric_cast_traits_common.hpp not being found? >>> >>> Have you checked if it's part of the tar you send to Uwe? >> >> The files I listed above are part of the tar. I will send the tar to you >> privately.

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

Scott Kostyshak wrote: > On Sat, Feb 13, 2016 at 08:54:57PM +, Guenter Milde wrote: >> On 2016-02-13, Scott Kostyshak wrote: >> >> > After this commit, when I run the command >> >> > lyx -e luatex lib/doc/he/Intro.lyx >> >> > it either fails to produce Intro.tex or (on current master) it

Re: beta2?

Scott Kostyshak wrote: > I agree that it would be nice to remove unnecessary files. As far as > figuring out which files are unnecessary, I volunteer to take any > experimental patch, build a tar ball, and send it to Uwe to see if he > has time to build the test tar ball so we can see if he gets

Re: Please re-generate po/pt_BR.gmo from po/pt_BR.po in lyxgit

Georger Araujo wrote: > I have submitted some updates for the Brazilian Portuguese translation and > I'd like to see those make it in 2.2.0. Done: 5a9a23a5da Georg

Re: beta2?

Jean-Marc Lasgouttes wrote: > Le 11/02/2016 21:40, Georg Baum a écrit : >> Comparing the complete 3rdparty directory from the tar ball with the one >> in git shows also that some boost files are missing (see attached). >> However, on linux building with included boo

Re: [LyX/master] New LFUN tabular-feature: update docs

Jean-Marc Lasgouttes wrote: > Le 09/02/2016 19:06, Scott Kostyshak a écrit : >> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx >> index ff4068a..fae083f 100644 >> --- a/lib/doc/LFUNs.lyx >> +++ b/lib/doc/LFUNs.lyx >> @@ -102,7 +102,7 @@ The \SpecialChar LyX >> \end_layout >> >>

Re: 2.2.0 beta 1: Xetex not working

Jürgen Lange wrote: > Hello, > thank you very much for 2.2.0 beta 1. > Compiling one of my documents does not work anymore in 2.2.0 beta 1. The > format is PDF (XeTeX). > The error-message is: > Kann keinen Latex Befehl für das Zeichen ḫ (Code-Punkt 0x1e2b) finden. > Einige Zeichen Ihres

Re: 2.2.0beta1 tar balls are available

Uwe Stöhr wrote: > Am 10.02.2016 um 04:18 schrieb Scott Kostyshak: > > > Hi Scott, > > the tarball is incomplete. There are several 3rdparty files missing: Thank you very much for building from the tar ball! The procedure did its job: It found out that we did some mistakes when adding files

Re: [LyX/master] New LFUN tabular-feature: update docs

Scott Kostyshak wrote: > On Wed, Jan 27, 2016 at 06:53:04PM +0100, Guillaume Munch wrote: >> commit 360742c515fcb74e6b8b5383f2e3002edb2d00cf >> Author: Guillaume Munch >> Date: Wed Jan 27 18:35:10 2016 +0100 >> >> New LFUN tabular-feature: update docs >> >> Simply

Re: 2.2.0beta1 tar balls are available

Pavel Sanda wrote: > Pavel Sanda wrote: >> Pavel Sanda wrote: >> > Scott Kostyshak wrote: >> > > Packagers, please prepare your binaries. >> > >> > Gentoo build now fails for tests/test_Length. P >> >> diff: >> --- runtime.output 2016-02-10 18:47:27.0 -0800 >> +++ Length 2015-07-22

Re: beta2?

Scott Kostyshak wrote: > Should we do a quick beta2 release? If so, is everything set on master > so we just need to tag and tar it? Or is something else missing? The tar ball must be generated after ff9ba203ff6d, otherwise it would miss the files again. Comparing the complete 3rdparty

Re: ACM-siggraph failing with newest class/style files

Uwe Stöhr wrote: > I reverted siggraph stuff now. Please do me the favor and don't require > to introduce another fileformat change. The probability that a user used > LyX 2.2git to write a real ACM submission is almost zero thus I won't > make it more complicated that it is. Thanks a lot.

Re: Proposal for releasing beta quickly

Scott Kostyshak wrote: > On Mon, Feb 01, 2016 at 09:39:32PM +0100, Georg Baum wrote: >> >> If we do revert, then we have to make the 504->505 file format conversion >> an empty one, and if we later re-introduce an updated layout file, we >> have to use a new file fo

Re: ACM-siggraph failing with newest class/style files

Uwe Stöhr wrote: > Why do you want to revert a fix for a real problem? I fixed it the way > we always did in the past. If it is more important for you to be > bureaucratically correct than fixing issues, be it. I am too old for this. My motivation for insisting that the +1 rule is followed is

Re: Proposal for releasing beta quickly

Jean-Marc Lasgouttes wrote: > Le 01/02/16 20:49, Scott Kostyshak a écrit : >> So in summary, I think we should revert, release beta, have beta being >> tested while we figure out updating the layouts, and then go forward >> from there. > > Go for it. We cannot allow each and every bug that is

Re: ACM-siggraph failing with newest class/style files

Kornel Benko wrote: > Am Sonntag, 31. Januar 2016 um 13:25:07, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> >> Kornel Benko wrote: >> >> Why? The layout in LyX 2.1 works for acmsiggraph.cls version 0.80, the >> new one for acmsiggraph.cls version 0.92

Re: ACM-siggraph failing with newest class/style files

Am 31.01.2016 um 21:43 schrieb Uwe Stöhr: Am 31.01.2016 um 12:12 schrieb Georg Baum: Sorry, this is a completely different topic. If you want such a procedure, make a suggestion how it should look like, who is going to implement it and how it is supposed to be maintained. Currently we do

Re: ACM-siggraph failing with newest class/style files

Jean-Marc Lasgouttes wrote: > If we had a description of what the problem is/was, it would be easier. > The cls file only says: > > % - version 0.92 2015/11/04 Boris Veytsman > % - Added new copyright, conference info and doi commands > > This does not look very scary to me. Apart from that

Re: ACM-siggraph failing with newest class/style files

Guenter Milde wrote: > On 2016-01-30, Kornel Benko wrote: >> Am Samstag, 30. Januar 2016 um 10:40:23, schrieb Georg Baum >> <georg.b...@post.rwth-aachen.de> > >>> We can discuss this, but it is also very easy to provide a layout file >>> for

Re: ACM-siggraph failing with newest class/style files

Uwe Stöhr wrote: > Am 30.01.2016 um 10:40 schrieb Georg Baum: > >>> I was arguing against this but the majority decided to go that way. But >>> nothing happened. >> >> What did you expect to happen? > > Well, a democratic decision was made and I of cou

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > After applying the patches I get: > > $ (cd lyx-build/cmake/2.2.0dev;ctest -C debug -R tex2lyx) > Test project /Users/stephan/git/lyx-build/cmake/2.2.0dev > > … > > 86% tests passed, 4 tests failed out of 28 > > Label Time Summary: > cmplyx = 21.45 sec (14 tests)

Re: ACM-siggraph failing with newest class/style files

Kornel Benko wrote: > Am Sonntag, 31. Januar 2016 um 11:49:56, schrieb Georg Baum >> >> I suggested to do this renaming automatically in lyx2lyx. > > Hm, OK, but this change is only partly dependent on lyx version. What > matters is the tex + layout combination. Making

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

Uwe Stöhr wrote: > Am 29.01.2016 um 22:32 schrieb Georg Baum: > >> Does anybody give a +1 subsequently for the ACM layout update? If yes, we >> should update the version numbers of the tex2lyx tests. If not, I propose >> that Uwe reverts the layout file changes an

Re: ACM-siggraph failing with newest class/style files

Uwe Stöhr wrote: > Am 29.01.2016 um 22:46 schrieb Georg Baum: > >> There are cases where users do not need the latest version. We had this >> discussion several times now, and I am not entering it again. > > That there are cases where the old version can still be

Re: #9794: inset-modify tabular commands are incorrectly disabled

Kornel Benko wrote: > Am Donnerstag, 28. Januar 2016 um 13:03:02, schrieb Jean-Marc Lasgouttes > >> Le 27/01/2016 18:55, Guillaume Munch a écrit : >> > I have found the motivation to re-do the format increase and the >> > patches are now committed. >> >> Congratulation for

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

Scott Kostyshak wrote: > On Wed, Jan 27, 2016 at 08:11:09AM +0100, Guillaume Munch wrote: >> >> Am I mistaken or nobody gave Uwe the +1 to do this format increment? > > As discussed in the other thread, you are correct. So what are we going to do now? The tex2lyx tests are currently failing

Re: ACM-siggraph failing with newest class/style files

Uwe Stöhr wrote: > Am 28.01.2016 um 17:31 schrieb Scott Kostyshak: > >> How can the issue be solved if a minimum version is required? I'm >> guessing the old version will never work. >> >> Should the tests assume that the developer running the tests has the >> newest version of the LaTeX files

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > Am 24.01.2016 um 19:08 schrieb Georg Baum > <georg.b...@post.rwth-aachen.de>: >> >> This is the idea, yes, but before implementing it I'd like to know >> whether it works in principle. This would require a two step approach for >>

Re: [PATCH] Re: Update boost in 2.1 branch?

Jean-Marc Lasgouttes wrote: > Le 25/01/2016 10:58, Kornel Benko a écrit : >> Am Montag, 25. Januar 2016 um 10:43:15, schrieb Jean-Marc Lasgouttes >> >>> Le 22/01/2016 17:15, Kornel Benko a écrit : >> Even with this patch, I could not compile src/support/ForkedCalls.cpp

Re: [PATCH] Re: Update boost in 2.1 branch?

Jean-Marc Lasgouttes wrote: > Le 21/01/2016 15:42, Jean-Marc Lasgouttes a écrit : >> >> Sigh. Now that I can test it with an older compiler (gcc 4.6, Ubuntu >> 12.04) I find that it does not compile in C++98 mode because of >> boost::next/prior. This has been fixed already in master, so I >>

Re: [patch] fix bug 9884

a/lib/doc/LaTeXConfig.lyx b/lib/doc/LaTeXConfig.lyx index ec0de6f..638ea77 100644 --- a/lib/doc/LaTeXConfig.lyx +++ b/lib/doc/LaTeXConfig.lyx @@ -69,6 +69,7 @@ \html_be_strict true \html_latex_start \html_latex_end +\author -195340706 "Georg Baum" \end_header \begin_body @@ -

Re: [LyX/master] Invert and document test for "longest labeling label" problem.

Kornel Benko wrote: > Am Sonntag, 24. Januar 2016 um 22:19:25, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> >> >> See http://www.lyx.org/trac/ticket/4595 for label insets, there are >> similar bugs for other insets that expect LaTeX code. Unfortunate

Re: [patch] fix bug 9925

Richard Heck wrote: > On 01/24/2016 08:55 AM, Georg Baum wrote: >> The date inset does currently not produce any output. This is a >> regression of http://www.lyx.org/trac/changeset/f09a9fe2/lyxgit. Before >> that change it did work only by accident: compare_timestamps()

Re: [LyX/master] Do not allow paralist + enumitem modules

Richard Heck wrote: > This tag cannot be used in a module. I've committed the correct fix. Oops, thanks for doing that. Georg

[patch] fix bug 9925

The date inset does currently not produce any output. This is a regression of http://www.lyx.org/trac/changeset/f09a9fe2/lyxgit. Before that change it did work only by accident: compare_timestamps() is called with two temp files which both have not been written to yet, so the time stamp

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > For latin1 documents (e.g. algo2e.tex) it works better. The test now > passed. > > For CJK.lex it’s obviously a problem: > $ /Users/stephan/git/lyx-build/cmake/2.2.0dev/bin/Debug/tex2lyx -f > -roundtrip /Users/stephan/git/lyx/src/tex2lyx/test/CJK.tex >

<    1   2   3   4   5   6   7   8   9   10   >