On Thu, Oct 29, 2015 at 09:04:10AM +, Guenter Milde wrote:
> * Math.lyx uses packages that either fail to compile or produce wrong output
> with XeTeX/LuaTeX (with both, TeX fonts and non-TeX fonts) in any language
> (e.g. mhchem)
> Also, some accents (e.g. \t) in "mathematical text" are
On Thu, Oct 29, 2015 at 10:42:20PM -0400, Scott Kostyshak wrote:
> On Thu, Oct 29, 2015 at 01:38:29PM +, Guenter Milde wrote:
> > On 2015-10-29, Guenter Milde wrote:
> >
> > > -> We need a framework to handle such "generic" problems like "Xe/LuaTeX
> > >with TeX fonts".
> >
> > >Sugge
On Thu, Oct 29, 2015 at 01:38:29PM +, Guenter Milde wrote:
> On 2015-10-29, Guenter Milde wrote:
>
> > -> We need a framework to handle such "generic" problems like "Xe/LuaTeX
> >with TeX fonts".
>
> >Suggestion:
>
> >* Code changes/commits that break tests with the default expor
On Thu, Oct 29, 2015 at 04:15:20PM +, Guenter Milde wrote:
> Dear LyXers,
>
> documents that use the mhchem package (which is automatically loaded if
> required, by default) fail to compile with XeTeX or LuaTeX and TeX fonts.
>
> The Math.lyx manual also shows missing or non-transformed outpu
On Thu, Oct 29, 2015 at 11:42:58PM +0100, Kornel Benko wrote:
> Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum
>
> > Scott Kostyshak wrote:
> >
> > > Please let me know if there is anything else specifically that I should
> > > document regarding the export tests. I will try to
On Thu, Oct 29, 2015 at 10:36:57PM +0100, Georg Baum wrote:
> Unit tests are almost always worth the effort. When I implement one, it does
> almost always find a bug right away. See also the check_lstrings failure
> Vincent reported and http://www.lyx.org/trac/ticket/9799. Having these bugs
> fo
Thanks for responding, Enrico. I appreciate it!
I am sorry, but it still doesn't work.
As you can see, now it doesn't work because setProcessEnvironment() is used.
I don't understand what that script (myprog) is exactly supposed to do,
but I believe the problem is in it rather than setProces
Thanks for responding, Enrico. I appreciate it!
I am sorry, but it still doesn't work.
As you can see, now it doesn't work because setProcessEnvironment() is used.
I don't understand what that script (myprog) is exactly supposed to do,
but I believe the problem is in it rather than setProces
Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum
> Scott Kostyshak wrote:
>
> > Please let me know if there is anything else specifically that I should
> > document regarding the export tests. I will try to keep updating this
> > file.
>
> Very good! I have one question: While in
Scott Kostyshak wrote:
> On Mon, Oct 26, 2015 at 03:33:22PM +, Guenter Milde wrote:
>
>> I think we have to distinguish several test methods:
>>
>> a) automatic export tests with lots of "real life" documents (manuals,
>>templates, examples)
>>
>> b) functional tests: import/export of a
Vincent van Ravesteijn wrote:
> The entries that are different from the test_lstrings reference file are
> for the inputs
>
> {
> ...
> 1.3754937356458394574047e17,
> 1.3754937356458394574047e18,
> 1.3754937356458394574047e19,
> 1.3754937356458394574047e20,
> ...
> 1e42
> }
>
> and the outputs a
Scott Kostyshak wrote:
> Please let me know if there is anything else specifically that I should
> document regarding the export tests. I will try to keep updating this
> file.
Very good! I have one question: While investigating the language nesting
stuff further I found already a nesting bug wh
Richard Heck wrote:
> If we support the added style, then users who both use that style and
> use an older version of the package will have non-compilable documents.
> So you could have a document that worked perfectly well, you make one
> change---use the new style---and now it won't compile. Wha
Guenter Milde wrote:
> On 2015-10-29, Scott Kostyshak wrote:
>> On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote:
>>> On 10/28/2015 03:52 PM, Scott Kostyshak wrote:
>>> >
>>> >It seems there are a few different ideas. Let me see if I can summarize
>>> >them:
>>> >
>>> >1. A layout chan
On Wed, Oct 28, 2015 at 08:12:44PM -0400, PhilipPirrip wrote:
> I've been playing with SystemcallPrivate::startProcess (in Systemcall.cpp)
> and latexEnvCmdPrefix (in filetools.cpp), in an attempt to resolve the issue
> with missing BIBINPUTS, a 9 year old request at
> http://www.lyx.org/trac/ticke
Richard Heck wrote:
> On 10/28/2015 03:59 PM, Scott Kostyshak wrote:
>> On Tue, Oct 27, 2015 at 01:29:51AM +0100, Uwe Stöhr wrote:
>>> Am 26.10.2015 um 22:42 schrieb Scott Kostyshak:
>>>
>>> - There are 2 sorts of layout issues that could violate the rule:
>>> 1. Layouts for journals: We often had
Am Donnerstag, 29. Oktober 2015 um 20:28:00, schrieb Vincent van Ravesteijn
> Op 29-10-2015 om 18:33 schreef Kornel Benko:
> > The problem was, that cmake accumulated messages from runtests.py.
> > Now runtests.py is called for each file separately.
> > Vincent, have you checked if that is OK to
Uwe Stöhr wrote:
> Am 27.10.2015 um 20:32 schrieb Georg Baum:
>
>> I think LyX would be perfectly suitable for frequent updates in theory,
>> and I'd like to see those as well one day. For example, all those small
>> new features like the one we are discussing in this thread, would not
>> need to
Kornel Benko wrote:
> I see. In my installation there is no uniconvertor either.
I have it installed, but it is not called by LyX directly (at least
seraching for it in the complete 2.2 git folder results in 0 hits).
> It is 'convert' calling this, so maybe it is not 'convert' from
> image-magi
Op 29-10-2015 om 18:33 schreef Kornel Benko:
The problem was, that cmake accumulated messages from runtests.py.
Now runtests.py is called for each file separately.
Vincent, have you checked if that is OK to you?
Kornel
It indeed works much better.
I just don't understand what the fol
Vincent van Ravesteijn wrote:
> While running updatetex2lyxtest:
>
> algo2e.tex":
>Ignoring options 'boxed' of package algorithm2e.
This should be fixed one day hopefully.
> test-insets.tex:
>warning : Could not find included file 'Dummy Document.tex'. (2x)
>warning : Could not fin
Peter Kümmel wrote:
> In another project I saw speed improvements just
> by enabling C++11 (I assume mainly because of the
> move semantic).
Yes, I guess we all agree that C++11 brings many improvements.
> I would even support MSVC only for developers and do the
> release with MinGW, would simpl
Am Mittwoch, 28. Oktober 2015 um 23:35:43, schrieb Kornel Benko
> Am Mittwoch, 28. Oktober 2015 um 23:29:30, schrieb Kornel Benko
>
> > Am Mittwoch, 28. Oktober 2015 um 23:02:08, schrieb Stephan Witt
> >
> > > Am 28.10.2015 um 22:49 schrieb Vincent van Ravesteijn :
> > >
> > > > > > It is onl
Dear LyXers,
documents that use the mhchem package (which is automatically loaded if
required, by default) fail to compile with XeTeX or LuaTeX and TeX fonts.
The Math.lyx manual also shows missing or non-transformed output if used
with XeTeX/LuaTeX and non-TeX fonts.
Is there a way to make LyX
On 2015-10-29, Scott Kostyshak wrote:
> On Tue, Oct 20, 2015 at 07:16:44PM +0200, Günter Milde wrote:
>> commit 1523fc6023440f10ca0d82a681ded5c060d8fd33
>> Author: Günter Milde
>> Date: Tue Oct 20 19:14:39 2015 +0200
>> Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".
>> F
On 2015-10-29, Scott Kostyshak wrote:
> On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote:
>> On 10/28/2015 03:52 PM, Scott Kostyshak wrote:
>> >
>> >It seems there are a few different ideas. Let me see if I can summarize
>> >them:
>> >
>> >1. A layout change can be made if it is support
On 2015-10-29, Guenter Milde wrote:
> -> We need a framework to handle such "generic" problems like "Xe/LuaTeX
>with TeX fonts".
>Suggestion:
>* Code changes/commits that break tests with the default export method of
> important documents require immediate action.
>* Proble
Am Donnerstag, 29. Oktober 2015 um 10:21:15, schrieb Vincent van Ravesteijn
> On Wed, Oct 28, 2015 at 10:47 PM, Kornel Benko wrote:
> > Am Mittwoch, 28. Oktober 2015 um 22:12:19, schrieb Vincent van Ravesteijn
> >
> >> Using CMake version 2.8.10, all tex2lyx tests fail due to the use of
> >>
>
Am 24.10.2015 um 20:25 schrieb Uwe Stöhr:
Am 24.10.2015 um 07:26 schrieb Peter Kümmel:
Do you think the warning is too extreme?
No, this is sadly true. Just replacing LyX files will break
LyX's functions. One need to set the PATH prefix in LyX etc.
to keep it running. So it OK to warn peopl
Am 25.10.2015 um 20:31 schrieb Georg Baum:
Vincent van Ravesteijn wrote:
I thought we always wanted to support as many compilers as reasonably
possible in order to allow newcomers to easily compile LyX and to let
them contribute. Does it make sense to still support Qt 4.5, but to
require the
On Wed, Oct 28, 2015 at 10:47 PM, Kornel Benko wrote:
> Am Mittwoch, 28. Oktober 2015 um 22:12:19, schrieb Vincent van Ravesteijn
>
>> Using CMake version 2.8.10, all tex2lyx tests fail due to the use of
>>
>> file( TIMESTAMP .. )
>>
>> in runtests.cmake. The TIMESTAMP command is available since
On 2015-10-29, Scott Kostyshak wrote:
> On Wed, Oct 28, 2015 at 10:28:00PM +, Guenter Milde wrote:
>> On 2015-10-28, Scott Kostyshak wrote:
>> > On Wed, Oct 28, 2015 at 09:31:50AM +, Guenter Milde wrote:
>> >> On 2015-10-26, Guenter Milde wrote:
>> >> > On 2015-10-26, Scott Kostyshak wrote:
On 2015-10-28, Scott Kostyshak wrote:
> On Mon, Oct 26, 2015 at 10:59:05AM +, Guenter Milde wrote:
>> On 2015-10-26, Scott Kostyshak wrote:
>> > On Sun, Oct 25, 2015 at 11:17:15AM +0100, Georg Baum wrote:
>> >> Scott Kostyshak wrote:
...
>> >> If some features of a document are implemented in
33 matches
Mail list logo
