Re: new compiler warnings in master

2015-03-23 Thread Jürgen Spitzmüller
2015-03-22 18:27 GMT+01:00 Georg Baum: This would look like the attached. Before I commit: Any wishes for other names? Perhaps: hyphen - softhyphen slash - breakableslash to make their semantics more explicit. Jürgen Georg

Re: new compiler warnings in master

2015-03-23 Thread Georg Baum
Jürgen Spitzmüller wrote: Perhaps: hyphen - softhyphen slash - breakableslash to make their semantics more explicit. Good idea, I did it like that. Georg

Re: new compiler warnings in master

2015-03-23 Thread Jürgen Spitzmüller
2015-03-22 18:27 GMT+01:00 Georg Baum: > This would look like the attached. Before I commit: Any wishes for other > names? > Perhaps: hyphen -> softhyphen slash -> breakableslash to make their semantics more explicit. Jürgen > > > Georg

Re: new compiler warnings in master

2015-03-23 Thread Georg Baum
Jürgen Spitzmüller wrote: > Perhaps: > hyphen -> softhyphen > slash -> breakableslash > > to make their semantics more explicit. Good idea, I did it like that. Georg

Re: new compiler warnings in master

2015-03-22 Thread Georg Baum
Georg Baum wrote: OK, I will change it. But since the LyX file format really has nothing to do with LaTeX (except for math), I will remove all backslashes and {} pairs from InsetSpecialChar. BTW, LaTeX2E is not the only one which is different. This would look like the attached. Before I

Re: new compiler warnings in master

2015-03-22 Thread Jean-Marc Lasgouttes
Le 22/03/15 18:27, Georg Baum a écrit : Georg Baum wrote: OK, I will change it. But since the LyX file format really has nothing to do with LaTeX (except for math), I will remove all backslashes and {} pairs from InsetSpecialChar. BTW, LaTeX2E is not the only one which is different. This

Re: new compiler warnings in master

2015-03-22 Thread Georg Baum
Georg Baum wrote: > OK, I will change it. But since the LyX file format really has nothing to > do with LaTeX (except for math), I will remove all backslashes and {} > pairs from InsetSpecialChar. BTW, LaTeX2E is not the only one which is > different. This would look like the attached. Before I

Re: new compiler warnings in master

2015-03-22 Thread Jean-Marc Lasgouttes
Le 22/03/15 18:27, Georg Baum a écrit : Georg Baum wrote: OK, I will change it. But since the LyX file format really has nothing to do with LaTeX (except for math), I will remove all backslashes and {} pairs from InsetSpecialChar. BTW, LaTeX2E is not the only one which is different. This

Re: Re: new compiler warnings in master

2015-03-21 Thread José Matos
On Friday 20 March 2015 21:57:43 Georg Baum wrote: OK, I will change it. But since the LyX file format really has nothing to do with LaTeX (except for math), I will remove all backslashes and {} pairs from InsetSpecialChar. BTW, LaTeX2E is not the only one which is different. Georg +1

Re: Re: new compiler warnings in master

2015-03-21 Thread José Matos
On Friday 20 March 2015 21:57:43 Georg Baum wrote: > OK, I will change it. But since the LyX file format really has nothing to do > with LaTeX (except for math), I will remove all backslashes and {} pairs > from InsetSpecialChar. BTW, LaTeX2E is not the only one which is different. > > > Georg

Re: new compiler warnings in master

2015-03-20 Thread Georg Baum
Jean-Marc Lasgouttes wrote: Le 18/03/15 20:27, Georg Baum a écrit : Oops! Thanks for the fix. Why do you think that the LyX file format needs to follow the LaTeX restrictions? IMHO it does not need to match (therefore I did not include the {} in the LyX file format, which is done for other

Re: new compiler warnings in master

2015-03-20 Thread Georg Baum
Jean-Marc Lasgouttes wrote: > Le 18/03/15 20:27, Georg Baum a écrit : >> Oops! Thanks for the fix. >> >> Why do you think that the LyX file format needs to follow the LaTeX >> restrictions? IMHO it does not need to match (therefore I did not include >> the {} in the LyX file format, which is done

Re: new compiler warnings in master

2015-03-18 Thread Jean-Marc Lasgouttes
Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) It's my fault. I will fix this. JMarc

Re: new compiler warnings in master

2015-03-18 Thread Jean-Marc Lasgouttes
Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) The warnings should be gone now. Please confirm. THis uses integer arithmetic

Re: new compiler warnings in master

2015-03-18 Thread Georg Baum
Jean-Marc Lasgouttes wrote: Georg, note that there was an error for LaTeX 2e (\LaTeX2e instead of \LaTeXe). I fixed it in LaTeX output, but I suspect that we should change the file format too for consistency sake. Oops! Thanks for the fix. Why do you think that the LyX file format needs to

new compiler warnings in master

2015-03-18 Thread Uwe Stöhr
Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) ..\..\..\src\insets\InsetSpecialChar.cpp(57): warning C4244: '=': convesion from 'double' to 'int', possible dataloss

Re: new compiler warnings in master

2015-03-18 Thread Jean-Marc Lasgouttes
Le 18/03/15 20:27, Georg Baum a écrit : Oops! Thanks for the fix. Why do you think that the LyX file format needs to follow the LaTeX restrictions? IMHO it does not need to match (therefore I did not include the {} in the LyX file format, which is done for other special characters). Well, it

Re: new compiler warnings in master

2015-03-18 Thread Abdelrazak Younes
On 18/03/2015 11:39, Jean-Marc Lasgouttes wrote: Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) The warnings should be gone

new compiler warnings in master

2015-03-18 Thread Uwe Stöhr
Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) ..\..\..\src\insets\InsetSpecialChar.cpp(57): warning C4244: '=': convesion from 'double' to 'int', possible dataloss

Re: new compiler warnings in master

2015-03-18 Thread Jean-Marc Lasgouttes
Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) It's my fault. I will fix this. JMarc

Re: new compiler warnings in master

2015-03-18 Thread Jean-Marc Lasgouttes
Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) The warnings should be gone now. Please confirm. THis uses integer arithmetic

Re: new compiler warnings in master

2015-03-18 Thread Georg Baum
Jean-Marc Lasgouttes wrote: > Georg, note that there was an error for LaTeX 2e (\LaTeX2e instead of > \LaTeXe). I fixed it in LaTeX output, but I suspect that we should > change the file format too for consistency sake. Oops! Thanks for the fix. Why do you think that the LyX file format needs

Re: new compiler warnings in master

2015-03-18 Thread Jean-Marc Lasgouttes
Le 18/03/15 20:27, Georg Baum a écrit : Oops! Thanks for the fix. Why do you think that the LyX file format needs to follow the LaTeX restrictions? IMHO it does not need to match (therefore I did not include the {} in the LyX file format, which is done for other special characters). Well, it

Re: new compiler warnings in master

2015-03-18 Thread Abdelrazak Younes
On 18/03/2015 11:39, Jean-Marc Lasgouttes wrote: Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) The warnings should be gone