The Mac version works on Intel and Silicon (my (torture test) handbook)
greetings, el
On 2024-02-08 00:20, Richard Kimberly Heck wrote:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please report bugs to lyx-devel@lists.lyx.org, or email me directly.
>
> Riki
>
>
--
To email
Dear Richard,
First of all, thanks for your invaluable help to the scientific community.
I was a user of LyX in my previous life as an active professor of Economics
at the University of the Basque Country.
Now, to the point. I have not tested yet your RCs. But please let me tell
you what
Here:
http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
Please report bugs to lyx-devel@lists.lyx.org, or email me directly.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 2/6/24 18:23, Stephan Witt wrote:
Am 06.02.2024 um 23:17 schrieb Dr Eberhard W Lisse :
Anyone doing the Mac version?
Yes, it‘s already done. The upload is available to release management.
And I'll get to it tomorrow probably.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
Thanks, can't see it on ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
am I looking at the wrong place?
el
On 2024-02-07 01:23, Stephan Witt wrote:
>> Am 06.02.2024 um 23:17 schrieb Dr Eberhard W Lisse
>> :
>>
>> Anyone doing the Mac version?
>
> Yes, it‘s already done. The upload is available to
> Am 06.02.2024 um 23:17 schrieb Dr Eberhard W Lisse :
>
> Anyone doing the Mac version?
Yes, it‘s already done. The upload is available to release management.
BR, Stephan
> greetings, el
>
>> On 2024-02-05 05:10, Richard Kimberly Heck wrote:
>> are here:
>>
>>
Anyone doing the Mac version?
greetings, el
On 2024-02-05 05:10, Richard Kimberly Heck wrote:
> are here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries.
>
--
To email me replace 'nospam' with 'el'
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
Am Mo., 5. Feb. 2024 um 04:10 Uhr schrieb Richard Kimberly Heck:
> are here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries.
>
Done, uploaded as usual.
--
Eugene
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sun, Feb 04, 2024 at 10:10:34PM -0500, Richard Kimberly Heck wrote:
> are here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries.
looks ok on debian. p
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sun, 2024-02-04 at 22:10 -0500, Richard Kimberly Heck wrote:
> are here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries.
Done for Fedora/RHEL (distro/archs):
Centos-stream+epel-next 8
aarch64 ppc64le x86_64
Centos-stream+epel-next 9
are here:
http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
Please prepare binaries.
--
Richard Kimberly (Riki) Heck
Professor of Philosophy
Brown University
Pronouns: they/them/their
Website: http://rkheck.frege.org/
--
lyx-devel mailing list
Le 30/01/2024 à 18:32, Richard Kimberly Heck a écrit :
We've had some feedback from RC1, and mostly things look good. The
encoding problem on OSX needs testing, though, and there's a new problem
with refstyle that cropped upon on the user list. Anything else we
should include in RC2? I'm
We've had some feedback from RC1, and mostly things look good. The
encoding problem on OSX needs testing, though, and there's a new problem
with refstyle that cropped upon on the user list. Anything else we
should include in RC2? I'm hoping to get it out by next week.
Riki
--
lyx-devel
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
Am 13.01.2018 um 05:15 schrieb Jean-Pierre:
Uwe, could you try the test file attached in
https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg203152.html
(perform an advanced search & replace of string '{}' in TeX code by
letter 'C').
Neither Scott nor me could reproduce on Linux, but the
On Sat, Jan 13, 2018 at 12:57:17AM +, Uwe Stöhr wrote:
> Am 11.01.2018 um 09:40 schrieb Scott Kostyshak:
>
> > I would like to email translators on Sunday. Please try to get
> > documentation touchups that should be translated done as soon as you
> > can.
>
> I did so and distributed all
Le 13 janvier 2018 4:00:13 AM Scott Kostyshak <skost...@lyx.org> a écrit :
On Sat, Jan 13, 2018 at 12:57:17AM +, Uwe Stöhr wrote:
Am 11.01.2018 um 09:40 schrieb Scott Kostyshak:
I'm fine with not waiting on translators for rc2. But we are not ready
to release rc2 now. We ha
; I did so and distributed all available changes. If I missed something,
> please let me know.
Thanks! I also have to put in some changes that Koji sent me, but I
think they are just for the Japanese docs so I don't think you will need
to do any follow-up work from that.
> Instead of waiting 2
of waiting 2 weeks for RC2, I propose to release RC2 right now
and let the translators some time to test until the final 2.3.0.
If Rc2 is released, we should assure that no strings will be changed
anymore unless a bug is fixed.
Just my two cents.
regards Uwe
I would like to email translators on Sunday. Please try to get
documentation touchups that should be translated done as soon as you
can.
I propose to leave the translators two weeks or so, and then release rc2
after that. I'm not sure our packagers will be able to produce binaries
then, but I
I also have this problem with Adobe Reader X.
You can't just update and view a pdf
as usual, you have to go through the long
process of exporting every time, and
adobe reader x opens a screen saying:
Open recent documents etc
I also have this problem with Adobe Reader X.
You can't just update and view a pdf
as usual, you have to go through the long
process of exporting every time, and
adobe reader x opens a screen saying:
"Open recent documents" etc
Julien Rioux jrioux at physics.utoronto.ca writes:
On 31/03/2011 7:23 AM, Jürgen Spitzmüller wrote:
Liviu Andronic wrote:
I've just compiled RC2 (from beta4) and to my surprise the 'Use
non-TeX fonts' option is always disabled, either when creating a new
document or when opening
Hello
This discussion seems to have been badly handled by gmane.
Have you tried the following? See Tools TeX info Rescan.
Liviu
-- Forwarded message --
From: Liviu Andronic landronim...@gmail.com
Date: Fri, Apr 1, 2011 at 5:39 PM
Subject: Re: rc2 and non-tex fonts
Julien Rioux physics.utoronto.ca> writes:
>
> On 31/03/2011 7:23 AM, Jürgen Spitzmüller wrote:
> > Liviu Andronic wrote:
> >> I've just compiled RC2 (from beta4) and to my surprise the 'Use
> >> non-TeX fonts' option is always disabled, either when creating a
Hello
This discussion seems to have been badly handled by gmane.
Have you tried the following? See Tools > TeX info > Rescan.
Liviu
-- Forwarded message --
From: Liviu Andronic <landronim...@gmail.com>
Date: Fri, Apr 1, 2011 at 5:39 PM
Subject: Re: rc2 and n
Am 17.04.2011 um 22:16 schrieb Jim Oldfield:
From: Joost Verburg jo...@lyx.org
Julien Rioux jri...@physics.utoronto.ca wrote in message
news:iod00u$hei$1...@dough.gmane.org...
You would need to make aspell visible to the configure script by putting
the
path to aspell.exe in your
Am 17.04.2011 um 22:16 schrieb Jim Oldfield:
>> From: Joost Verburg
>>
>> "Julien Rioux" wrote in message
>> news:iod00u$hei$1...@dough.gmane.org...
>>> You would need to make aspell visible to the configure script by putting
>>> the
>>
>> path
Am 17.04.2011 um 03:12 schrieb Joost Verburg:
Julien Rioux jri...@physics.utoronto.ca wrote in message
news:iod00u$hei$1...@dough.gmane.org...
You would need to make aspell visible to the configure script by putting the
path to aspell.exe in your PATH environment variable or alternatively
Am 17.04.2011 um 03:12 schrieb Joost Verburg:
> "Julien Rioux" wrote in message
> news:iod00u$hei$1...@dough.gmane.org...
>> You would need to make aspell visible to the configure script by putting the
>> path to aspell.exe in your PATH environment variable or
Le 12/04/2011 10:39, LyX Ticket Tracker a écrit :
#7407: Crash under Linux of compiled Lyx 2.0.0dev and rc2
-+--
Reporter: rkrug| Owner: lasgouttes
Type: defect | Status: new
Priority: high
I am happy to say that my problem is solved in rc3: labelled equations are now
correctly previewed when I use my favorite hyperref call.
Thank you everybody,
Jean Kaplan
Le 1 avr. 2011 à 16:33, Julien Rioux a écrit :
On 01/04/2011 5:52 AM, Jean Kaplan wrote:
The problems appears to be linked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/11 11:10, Jean-Marc Lasgouttes wrote:
Le 12/04/2011 10:39, LyX Ticket Tracker a écrit :
#7407: Crash under Linux of compiled Lyx 2.0.0dev and rc2
-+--
Reporter
Le 12/04/2011 10:39, LyX Ticket Tracker a écrit :
#7407: Crash under Linux of compiled Lyx 2.0.0dev and rc2
-+--
Reporter: rkrug| Owner: lasgouttes
Type: defect | Status: new
Priority: high
I am happy to say that my problem is solved in rc3: labelled equations are now
correctly previewed when I use my favorite hyperref call.
Thank you everybody,
Jean Kaplan
Le 1 avr. 2011 à 16:33, Julien Rioux a écrit :
> On 01/04/2011 5:52 AM, Jean Kaplan wrote:
>> The problems appears to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/11 11:10, Jean-Marc Lasgouttes wrote:
> Le 12/04/2011 10:39, LyX Ticket Tracker a écrit :
>> #7407: Crash under Linux of compiled Lyx 2.0.0de
No, I was talking about Adobe Reader X only.
---
Diego Queiroz
2011/4/6 Joost Verburg jo...@lyx.org
Diego Queiroz queiroz.di...@gmail.com wrote in message
news:BANLkTim6fQ-7u+04_zMnOf5Zb2vh1=e...@mail.gmail.com...
Here is the screenshot of C:\Program Files\Adobe\Reader
No, I was talking about Adobe Reader X only.
---
Diego Queiroz
2011/4/6 Joost Verburg
> "Diego Queiroz" wrote in message
>> news:BANLkTim6fQ-7u+04_zMnOf5Zb2vh1=e...@mail.gmail.com...
>>
>> Here is the screenshot of C:\Program Files\Adobe\Reader
>>
Alejandro.
They are now available at the ftp server (
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/rc2).
But they won't solve your problem.
I've found this bug when I installed Adobe Acrobat X also (when you click to
view PDF, the Adobe Acrobat app starts as well but the file is not oppened
Diego Queiroz queiroz.di...@gmail.com wrote in message
news:banlktinv39cbo6klvortkyfodtymtka...@mail.gmail.com...
I've found this bug when I installed Adobe Acrobat X also (when you click
to view PDF, the Adobe Acrobat app starts as well but the file is not
oppened), but it is not exactly
Diego Queiroz queiroz.di...@gmail.com wrote in message
news:BANLkTim6fQ-7u+04_zMnOf5Zb2vh1=e...@mail.gmail.com...
Here is the screenshot of C:\Program Files\Adobe\Reader
10.0\Reader\AcroRd32.exe.
You're talking about Adobe Acrobat, right? Not Adobe Reader?
If yes please also send the info of
Alejandro.
They are now available at the ftp server (
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.0/rc2).
But they won't solve your problem.
I've found this bug when I installed Adobe Acrobat X also (when you click to
view PDF, the Adobe Acrobat app starts as well but the file is not oppened
"Diego Queiroz" wrote in message
news:banlktinv39cbo6klvortkyfodtymtka...@mail.gmail.com...
I've found this bug when I installed Adobe Acrobat X also (when you click
to view PDF, the Adobe Acrobat app starts as well but the file is not
oppened), but it is not exactly
"Diego Queiroz" wrote in message
news:BANLkTim6fQ-7u+04_zMnOf5Zb2vh1=e...@mail.gmail.com...
Here is the screenshot of C:\Program Files\Adobe\Reader
10.0\Reader\AcroRd32.exe.
You're talking about Adobe Acrobat, right? Not Adobe Reader?
If yes please also send the info
Enrico Forestieri wrote:
On Mon, Apr 04, 2011 at 05:45:28PM +0200, venom00 wrote:
do you remember my fear of only one man understands this
code situation in the
very beginning? :)
Well, Enrico made useful comments about the code. There
were a pair of stupid
errors,
venom00 wrote:
we are eagerly waiting for the patch :)
Here it is. I've added a general, step-by-step description of what the script
does to the top of the files and some comments here and there. I've moved out
of
main functions some code so it's more readable and fixed the FIXME I put
Pavel Sanda wrote:
thanks for your efforts, i'll put it in.
but only after you post this patch as an attachment,
its unapplicable in this form...
pavel
Pavel Sanda wrote:
thanks for your efforts, i'll put it in.
but only after you post this patch as an attachment,
its unapplicable in this form...
pavel
You're welcome. I forgot to attach it.
venom00
Index: lib/scripts/lyxpreview2bitmap.py
venom00 wrote:
Pavel Sanda wrote:
thanks for your efforts, i'll put it in.
but only after you post this patch as an attachment,
its unapplicable in this form...
pavel
You're welcome. I forgot to attach it.
its in. p
venom00 wrote:
Pavel Sanda wrote:
thanks for your efforts, i'll put it in.
but only after you post this patch as an attachment,
its unapplicable in this form...
pavel
You're welcome. I forgot to attach it.
its in. P
So what's the final decision? Will it be in 2.0?
venom00 wrote:
its in. P
So what's the final decision? Will it be in 2.0?
its in means it has been committed into trunk, ie it will appear in the next
release.
http://www.lyx.org/trac/changeset/38256
http://www.lyx.org/trac/changeset/38243
pavel
> Enrico Forestieri wrote:
> > On Mon, Apr 04, 2011 at 05:45:28PM +0200, venom00 wrote:
> >
> > > > do you remember my fear of "only one man understands this
> > > > code" situation in the
> > > > very beginning? :)
> > >
> > > Well, Enrico made useful comments about the code. There
> were a
venom00 wrote:
> > we are eagerly waiting for the patch :)
>
> Here it is. I've added a general, step-by-step description of what the script
> does to the top of the files and some comments here and there. I've moved out
> of
> main functions some code so it's more readable and fixed the FIXME I
Pavel Sanda wrote:
> thanks for your efforts, i'll put it in.
but only after you post this patch as an attachment,
its unapplicable in this form...
pavel
> Pavel Sanda wrote:
> > thanks for your efforts, i'll put it in.
>
> but only after you post this patch as an attachment,
> its unapplicable in this form...
> pavel
You're welcome. I forgot to attach it.
venom00
Index: lib/scripts/lyxpreview2bitmap.py
venom00 wrote:
> > Pavel Sanda wrote:
> > > thanks for your efforts, i'll put it in.
> >
> > but only after you post this patch as an attachment,
> > its unapplicable in this form...
> > pavel
>
> You're welcome. I forgot to attach it.
its in. p
> venom00 wrote:
> > > Pavel Sanda wrote:
> > > > thanks for your efforts, i'll put it in.
> > >
> > > but only after you post this patch as an attachment,
> > > its unapplicable in this form...
> > > pavel
> >
> > You're welcome. I forgot to attach it.
>
> its in. P
So what's the final
venom00 wrote:
> > its in. P
>
> So what's the final decision? Will it be in 2.0?
"its in" means it has been committed into trunk, ie it will appear in the next
release.
http://www.lyx.org/trac/changeset/38256
http://www.lyx.org/trac/changeset/38243
pavel
venom00 wrote:
Sorry I read too fast. That message about xeCJK is targeted
at 1.6.9, so
unrelated.
I'm honestly not sure what to do for the preview. I don't
understand all
of the new code, but I also could not make it fail. I do feel that
venom00 is committed to be around and
On 04/04/2011 7:41 AM, Pavel Sanda wrote:
i see, Julien please put it in.
Committed at r38243
Cheers,
Julien
venom00 wrote:
Sorry I read too fast. That message about xeCJK is targeted
at 1.6.9, so
unrelated.
I'm honestly not sure what to do for the preview. I don't
understand all
of the new code, but I also could not make it fail. I do
feel that
venom00 is committed to be
On Mon, Apr 04, 2011 at 05:45:28PM +0200, venom00 wrote:
do you remember my fear of only one man understands this
code situation in the
very beginning? :)
Well, Enrico made useful comments about the code. There were a pair of stupid
errors, Julien didn't notice them, so maybe he gave a
Enrico Forestieri wrote:
On Mon, Apr 04, 2011 at 05:45:28PM +0200, venom00 wrote:
do you remember my fear of only one man understands this
code situation in the
very beginning? :)
Well, Enrico made useful comments about the code. There were a pair of
stupid
errors, Julien
venom00 wrote:
> > Sorry I read too fast. That message about xeCJK is targeted
> > at 1.6.9, so
> > unrelated.
> >
> > I'm honestly not sure what to do for the preview. I don't
> > understand all
> > of the new code, but I also could not make it fail. I do feel that
> > venom00 is committed
On 04/04/2011 7:41 AM, Pavel Sanda wrote:
i see, Julien please put it in.
Committed at r38243
Cheers,
Julien
> venom00 wrote:
> > > Sorry I read too fast. That message about xeCJK is targeted
> > > at 1.6.9, so
> > > unrelated.
> > >
> > > I'm honestly not sure what to do for the preview. I don't
> > > understand all
> > > of the new code, but I also could not make it fail. I do
> feel that
> > >
On Mon, Apr 04, 2011 at 05:45:28PM +0200, venom00 wrote:
> > do you remember my fear of "only one man understands this
> > code" situation in the
> > very beginning? :)
>
> Well, Enrico made useful comments about the code. There were a pair of stupid
> errors, Julien didn't notice them, so
Enrico Forestieri wrote:
> On Mon, Apr 04, 2011 at 05:45:28PM +0200, venom00 wrote:
>
> > > do you remember my fear of "only one man understands this
> > > code" situation in the
> > > very beginning? :)
> >
> > Well, Enrico made useful comments about the code. There were a pair of
> > stupid
Julien Rioux wrote:
(to devs: either we go ahead on the latest patch from venom00, or we might
consider reverting to 1.6 mechanism)
whats the better solution?
pavel
On 02/04/2011 8:36 AM, Pavel Sanda wrote:
Julien Rioux wrote:
(to devs: either we go ahead on the latest patch from venom00, or we might
consider reverting to 1.6 mechanism)
whats the better solution?
pavel
Perhaps the revert, since more problems appear: problem with xeCJK,
recently on
On 02/04/2011 10:46 AM, Julien Rioux wrote:
On 02/04/2011 8:36 AM, Pavel Sanda wrote:
Julien Rioux wrote:
(to devs: either we go ahead on the latest patch from venom00, or we
might
consider reverting to 1.6 mechanism)
whats the better solution?
pavel
Perhaps the revert, since more
Sorry I read too fast. That message about xeCJK is targeted
at 1.6.9, so
unrelated.
I'm honestly not sure what to do for the preview. I don't
understand all
of the new code, but I also could not make it fail. I do feel that
venom00 is committed to be around and help in fixing
Julien Rioux wrote:
> (to devs: either we go ahead on the latest patch from venom00, or we might
> consider reverting to 1.6 mechanism)
whats the better solution?
pavel
On 02/04/2011 8:36 AM, Pavel Sanda wrote:
Julien Rioux wrote:
(to devs: either we go ahead on the latest patch from venom00, or we might
consider reverting to 1.6 mechanism)
whats the better solution?
pavel
Perhaps the revert, since more problems appear: problem with xeCJK,
recently on
On 02/04/2011 10:46 AM, Julien Rioux wrote:
On 02/04/2011 8:36 AM, Pavel Sanda wrote:
Julien Rioux wrote:
(to devs: either we go ahead on the latest patch from venom00, or we
might
consider reverting to 1.6 mechanism)
whats the better solution?
pavel
Perhaps the revert, since more
> Sorry I read too fast. That message about xeCJK is targeted
> at 1.6.9, so
> unrelated.
>
> I'm honestly not sure what to do for the preview. I don't
> understand all
> of the new code, but I also could not make it fail. I do feel that
> venom00 is committed to be around and help in fixing
on the screen and different from their appearance in the
latex result).
This does not affect the latex typesetting and the pdf files produced.
This affects both rc1 and rc2 releases.
I am longing for the solution of this problem to switch to Lyx 2.0 and
take advantage of its numerous improvements
On 01/04/2011 5:52 AM, Jean Kaplan wrote:
The problems appears to be linked with my use of a specific call to hyperref
\usepackage[colorlinks=true, pdfstartview=FitV, linkcolor=blue, citecolor=blue,
urlcolor=blue]{hyperref}
If I use the Lyx call to Hyperref in Lyx preferences instead, the
;>> Labelled equations, and only them, always stay in the editing mode
>>>> (appearing blue on the screen and different from their appearance in the
>>>> latex result).
>>>> This does not affect the latex typesetting and the pdf files produced.
>>&g
On 01/04/2011 5:52 AM, Jean Kaplan wrote:
The problems appears to be linked with my use of a specific call to hyperref
\usepackage[colorlinks=true, pdfstartview=FitV, linkcolor=blue, citecolor=blue,
urlcolor=blue]{hyperref}
If I use the Lyx call to Hyperref in Lyx preferences instead, the
Dear all
I've just compiled RC2 (from beta4) and to my surprise the 'Use
non-TeX fonts' option is always disabled, either when creating a new
document or when opening a document already configured for XeTeX.
Compiling the XeTeX document works fine, even if the relevant option
is disabled
Liviu Andronic wrote:
I've just compiled RC2 (from beta4) and to my surprise the 'Use
non-TeX fonts' option is always disabled, either when creating a new
document or when opening a document already configured for XeTeX.
Compiling the XeTeX document works fine, even if the relevant option
On Thu, Mar 31, 2011 at 1:23 PM, Jürgen Spitzmüller
spitzmuel...@ds.uzh.ch wrote:
Check if the fontspec package is installed.
liv@liv-laptop:~$ locate fontspec | grep -i texmf
/usr/share/texmf-texlive/tex/xelatex/fontspec
/usr/share/texmf-texlive/tex/xelatex/fontspec/fontspec.cfg
On Thu, Mar 31, 2011 at 3:53 PM, Jürgen Spitzmüller
spitzmuel...@ds.uzh.ch wrote:
More relevant is what
kpsewhich fontspec.sty
returns.
liv@liv-laptop:~$ kpsewhich fontspec.sty
/usr/share/texmf-texlive/tex/xelatex/fontspec/fontspec.sty
In any case XeTeX documents compile just fine, so LyX
Hi Liviu,
It's strange that you're having this problem, I am as well. In my case, though
I'm seeing it on the Windows SVN version. (I haven't updated on Linux for a
while.) My Mac build of LyX is working just fine though.
I thought that I might have accidentally flipped one of the compile
though.
I think that for RC2 there were some changes in the configure script
(the one launched by Reconfigure) that intended to check if XeTeX was
present so as to enable/disable the relevant option. My guess is that
something got mixed up.
I thought that I might have accidentally flipped one
.) My Mac build of LyX is working just fine though.
I think that for RC2 there were some changes in the configure script
(the one launched by Reconfigure) that intended to check if XeTeX was
present so as to enable/disable the relevant option. My guess is that
something got mixed up.
I thought
.
Both of you are on the same platform?
Probably. I'm on Xubuntu Lucid 64bit.
Liviu
lyx-rc2-configure.log
Description: Binary data
On 31/03/2011 11:55 AM, Liviu Andronic wrote:
On Thu, Mar 31, 2011 at 5:50 PM, Julien Rioux
jri...@physics.utoronto.ca wrote:
Since you can compile the documents using xelatex it seems that xelatex is
properly found by configure.py, but nevertheless you may attach here a log
of your configure
On 31/03/2011 7:23 AM, Jürgen Spitzmüller wrote:
Liviu Andronic wrote:
I've just compiled RC2 (from beta4) and to my surprise the 'Use
non-TeX fonts' option is always disabled, either when creating a new
document or when opening a document already configured for XeTeX.
Compiling the XeTeX
On Thu, Mar 31, 2011 at 5:59 PM, Julien Rioux
jri...@physics.utoronto.ca wrote:
configure.log looks fine. Can you please try with an empty user directory?
Yes, with a clean profile the non-TeX option is activated and can be
enabled. So I guess that the upgrade could not properly deal with the
Dear all
I've just compiled RC2 (from beta4) and to my surprise the 'Use
non-TeX fonts' option is always disabled, either when creating a new
document or when opening a document already configured for XeTeX.
Compiling the XeTeX document works fine, even if the relevant option
is disabled
Liviu Andronic wrote:
I've just compiled RC2 (from beta4) and to my surprise the 'Use
non-TeX fonts' option is always disabled, either when creating a new
document or when opening a document already configured for XeTeX.
Compiling the XeTeX document works fine, even if the relevant option
On Thu, Mar 31, 2011 at 1:23 PM, Jürgen Spitzmüller
wrote:
> Check if the fontspec package is installed.
>
liv@liv-laptop:~$ locate fontspec | grep -i texmf
/usr/share/texmf-texlive/tex/xelatex/fontspec
/usr/share/texmf-texlive/tex/xelatex/fontspec/fontspec.cfg
On Thu, Mar 31, 2011 at 3:53 PM, Jürgen Spitzmüller
wrote:
> More relevant is what
> kpsewhich fontspec.sty
> returns.
>
liv@liv-laptop:~$ kpsewhich fontspec.sty
/usr/share/texmf-texlive/tex/xelatex/fontspec/fontspec.sty
In any case XeTeX documents compile just fine, so
Hi Liviu,
It's strange that you're having this problem, I am as well. In my case, though
I'm seeing it on the Windows SVN version. (I haven't updated on Linux for a
while.) My Mac build of LyX is working just fine though.
I thought that I might have accidentally flipped one of the compile
f LyX is working just fine though.
>
I think that for RC2 there were some changes in the configure script
(the one launched by Reconfigure) that intended to check if XeTeX was
present so as to enable/disable the relevant option. My guess is that
something got mixed up.
> I thought that I migh
while.) My Mac build of LyX is working just fine though.
I think that for RC2 there were some changes in the configure script
(the one launched by Reconfigure) that intended to check if XeTeX was
present so as to enable/disable the relevant option. My guess is that
something got mixed up.
I t
k.
>
Please see attached.
> Both of you are on the same platform?
>
Probably. I'm on Xubuntu Lucid 64bit.
Liviu
lyx-rc2-configure.log
Description: Binary data
On 31/03/2011 11:55 AM, Liviu Andronic wrote:
On Thu, Mar 31, 2011 at 5:50 PM, Julien Rioux
wrote:
Since you can compile the documents using xelatex it seems that xelatex is
properly found by configure.py, but nevertheless you may attach here a log
of your
1 - 100 of 646 matches
Mail list logo