Kornel Benko | 29 May 22:30 2015

Re: Compilation failure un c++11 mode with gcc 4.6

Am Freitag, 29. Mai 2015 um 21:59:16, schrieb pdv <pdvisschere <at> edpnet.be>
> On 29/05/15 20:10, Kornel Benko wrote:
> > Am Freitag, 29. Mai 2015 um 19:52:03, schrieb Jean-Marc Lasgouttes <lasgouttes <at> lyx.org>
> >> Le 28/05/2015 23:23, pdv a écrit :
> >>> Starting with commit b596330 lyx fails to compile with cmake/xcode.
> >>> This seems to be due to "boost::next" having been replaced by "next" and
> >>> this generates "ambiguous call to 'next'" semantic issues, one of the 2
> >>> possibilities being the "next" in lyxalgo.h mentioned in this message.
> >>> So this might be related to this;
> >>> I expected LYX_USE_CXX11 to be set (with the later commits that is), but
> >>> that's not the case;
> >>> When I manually define LYX_USE_CXX11 the problems with "next" go away,
> >>> but similar and much more semantic issues surface with "bind".
> >>
> >> I suspect that there is a problem with clang, which implements parts of
> >> C++11 even when not in c++11 mode.
> >>
> >> Patrick, what are the options passed to cmake? What is your clang version?
> >>
> >> JMarc
> >
> > Good idea JMarc.
> >
> > Patrick, do you use '-DLYX_ENABLE_CXX11=ON' in cmake call? (Default is OFF)
> >
> > 	Kornel
> >
> 
> (I'm using the CMake GUI and I define the macro's directly)
> Previously I defined LYX_USE_CXX11 and this showed up in config.h but 
(Continue reading)

Richard Heck | 29 May 17:12 2015

LyX 2.1.4


I'd like to start the 2.1.4 release process by freezing strings, etc. 
Any fixes that need to go in before I do that?

Richard

Uwe Stöhr | 29 May 02:09 2015
Picon

configure.py questions

Hello LyXers,

since I was forced to send many texts I wrote with LyX in the format of 
MS word, I spend a lot of time to get this to work. The solution is 
surprisingly simple:
- creating a HTML file via eLyXer* and then importing it to Word or 
LibreOffice-

This way I can now also use MS word or LibreOffice to view and update 
the view of my LyX files. This is really great and make LyX much more 
attractive in the Windows world.

I only have one problem: In configure.py there is already a LaTeX to 
OpenDocument converter defined. (This is the tex4ht converter which 
never worked on Windows and which is dead for many years now.)
I had to add a LyX  to OpenDocument converter. But in LyX when I view my 
LyX file as OpenDocument always the tex4ht converter is executed not my one.

What can I do?
- How can I tell LyX that my to OpenDocument converter is preferred?
- Can we maybe get rid of tex4ht or does anybody use this and gets 
acceptable results.

For now I only get it to work by deleting the tex4ht converter from 
configure.py.

Besides this, I noticed that we add by default the eLyXer footer to the 
converted HTML files. eLyXer provides the --nofooter option to suppress 
this "advertisement" to its own and there is no license reason that 
doesn't allow use to suppress the footer. So Am I allowed to add the 
(Continue reading)

hatim ali | 28 May 15:55 2015
Picon

Numbers types

Dear lyx Team
I hope you added option for document to select numbers type ( hindi , arabic ).
Now, in arabtex or arabi (  hindi is the default numbers ).

Best regards
Hatim
Richard Heck | 28 May 00:14 2015

Goodbye, File> Print


Support for printing from within LyX has been remvoed at 3c2b3e69. I assume this must mean some of the documentation needs updating, as well as something in release notes? What else?

Richard

Georg Baum | 27 May 17:06 2015
Picon
Picon

consider tex2lyx + tests locked in master

Please do not submit anything in tex2lyx source code and tests for ca. two 
days (I'll send a message when the lock is over). One tex2lyx test is still 
failing, and I am going to work on the tests to show what is currently 
broken. Unfortunately the test references where updated with errornous 
contents, so some bugs which were introduced are currently hidden.

If somebody submits stuff before I am finished I will revert it. If you 
think you have urgent changes which need to go in before I am finished, 
please tell _before_ submit, so that we can find a procedure which works for 
everybody.

Georg

Stephan Witt | 27 May 16:35 2015
Picon
Picon

Re: LyX banner has strange bottom line for me

Am 27.05.2015 um 16:05 schrieb Jürgen Spitzmüller <spitz <at> lyx.org>:

2015-05-27 12:41 GMT+02:00 Stephan Witt:

<lyx - Bildschirmfoto 2015-05-27 um 12.35.34.png>

BTW I'd suggest to move the version string up- and rightwards in the grey field.

The dirty, hard coded way is to change the position (and size) in GuiView.cpp.

Stephan

Scott Kostyshak | 26 May 15:05 2015

Re: Is fontenc supposed to be used for XeTeX?

On Tue, May 26, 2015 at 7:58 AM, Jürgen Spitzmüller <spitz <at> lyx.org> wrote:
> 2015-05-26 13:37 GMT+02:00 Scott Kostyshak <skostysh <at> lyx.org>:
>>
>> If I create a new document, write "abc", and export to LaTeX (XeTeX),
>> there is the following line:
>>
>> \usepackage[T1]{fontenc}
>>
>> Günter suggested that this should not happen (unless we are in
>> compatibility mode).
>>
>> Is this expected?
>
>
> Yes, iff you use TeX fonts.

I think I understand now. Are the phrases "compatibility mode" and
"using TeX fonts" approximately the same?

Scott

hatim ali | 26 May 14:13 2015
Picon

RE: update arabic translation

Dear Uwe Stohr
Thank you.
i hope you can help me:
1st: Nomenclature and indexs not work in arabic language?!

2nd: can i translate this string or not?

<All indexes>
&New:[[index]]

i add sample file in attachment.
best regards




> Date: Tue, 26 May 2015 01:27:39 +0200
> From: uwestoehr <at> lyx.org
> To: dr.hatim <at> hotmail.com
> Subject: Re: update arabic translation
>
> Am 25.05.2015 um 05:05 schrieb hatim ali:
>
> > I apologize, it was just an inadvertent mistake.
>
> Hi Hatim,
>
> no problem!
>
> I changed it before I committed.
>
> regards Uwe
Attachment (الطاقة وحفظها.lyx): application/octet-stream, 23 KiB
Scott Kostyshak | 26 May 13:37 2015

Is fontenc supposed to be used for XeTeX?

If I create a new document, write "abc", and export to LaTeX (XeTeX),
there is the following line:

\usepackage[T1]{fontenc}

Günter suggested that this should not happen (unless we are in
compatibility mode).

Is this expected?

Scott

Scott Kostyshak | 26 May 13:34 2015

LyX banner has strange bottom line for me

Attached is a screenshot of how the LyX banner looks for me on Ubuntu
with Qt 5.5dev.

The bottom line has some strangely colored pixels, instead of just
being a black/grey line.

One time, it was extreme (e.g. almost rainbow colored). This is
attached. I annot reproduce that though. But even now it seems
slightly strange, although I do have to look very close to see the
difference. But to me there is a clear difference between the bottom
and the top lines.

Does anyone else see something like this?

Scott

Gmane