Am 24.03.2011 um 00:10 schrieb you...@lyx.org:
> Author: younes
> Date: Thu Mar 24 00:10:12 2011
> New Revision: 38018
> URL: http://www.lyx.org/trac/changeset/38018
>
> Log:
> Cleanup the SpellChecker dialog (fixes #7375 and #7379):
> * Transform Spellchecker.ui into a simple QWidget
> * Pimpl a
Enrico Forestieri wrote:
> > since it seems i'm the only one left who want to stick with old ones and
> > no other set was submitted i'm not going to push 2 more. it can be easily
> > added later if there is some real interest.
>
> Here is another possible set of icons to be considered.
does it h
On 23/03/2011 10:18 PM, Richard Heck wrote:
On 03/23/2011 06:27 PM, José Matos wrote:
On Wednesday 23 March 2011 21:36:54 Pavel Sanda wrote:
others, please note that we have new fellow on the developer's ship
so do not forget to give him warm welcome ;)
pavel
Oh, do you mean that a welcome gr
On 23/03/2011 10:19 PM, Richard Heck wrote:
On 03/22/2011 05:16 PM, Julien Rioux wrote:
You cannot have two modules which both redefine the output format.
This is a stupid patch. Something more clever might be done in the c++
code.
What happens if two modules do try to redefine the output form
On 03/22/2011 05:16 PM, Julien Rioux wrote:
You cannot have two modules which both redefine the output format.
This is a stupid patch. Something more clever might be done in the c++
code.
What happens if two modules do try to redefine the output format? Should
we issue a warning or something,
On 03/23/2011 06:27 PM, José Matos wrote:
On Wednesday 23 March 2011 21:36:54 Pavel Sanda wrote:
others, please note that we have new fellow on the developer's ship
so do not forget to give him warm welcome ;)
pavel
Oh, do you mean that a welcome group hug is in order? ;-)
Welcome. :-)
And
--- On Wed, 3/23/11, Liviu Andronic wrote:
> From: Liviu Andronic
> Subject: Re: LyX Promotion
> To: "Graham Smith"
> Cc: "LyX Devel" , lyx-us...@lists.lyx.org
> Received: Wednesday, March 23, 2011, 4:34 AM
> On Wed, Mar 23, 2011 at 9:12 AM,
> Graham Smith
> wrote:
> > One possible approach
On 23/03/2011 18:28, Stephan Witt wrote:
I'll try to solve the end-of-document too - but I doubt it could be done
without any state variable...
I managed to do this so I committed the patch. It seems to work fine now.
Abdel.
On 2011-03-23, Jürgen Spitzmüller wrote:
> Also sprach Jean-Marc Lasgouttes:
>>> Yes, I still have this message marked in my inbox. But you didn't yet
>>> propose a working python code, did you?
>>> OTOH JMarc's idea of using a test file strikes me not too bad.
>> In my mind this is the same idea
On Wed, Mar 23, 2011 at 10:39 PM, wrote:
> The slides will be publicly available in a short but are in Italian, I can
> translate my parts (first and fourth) if someone is interested and ask the
> other speakers to do the same! Maybe we can publish them on the Wiki if you
> think their quality
On 2011-03-23, Jürgen Spitzmüller wrote:
> Also sprach Guenter Milde:
>> The error message is clear: it says "... requires XeTeX".
> Then we can check for this message. Do you have TeXLive 2009, Günter?
Yes.
> Can you setup a minimal example file?
LyX or *.tex?
Actually, the only requirement
On Wednesday 23 March 2011 21:36:54 Pavel Sanda wrote:
> others, please note that we have new fellow on the developer's ship
> so do not forget to give him warm welcome ;)
>
> pavel
Oh, do you mean that a welcome group hug is in order? ;-)
Welcome. :-)
--
José Abílio
On 23/03/2011 18:28, Stephan Witt wrote:
Am 23.03.2011 um 15:34 schrieb Abdelrazak Younes:
On 03/23/2011 02:15 PM, Stephan Witt wrote:
Am 23.03.2011 um 13:56 schrieb Abdelrazak Younes:
On 03/23/2011 12:48 PM, Stephan Witt wrote:
Am 23.03.2011 um 10:18 schrieb Abdelrazak Younes:
On 03/22/2
On Wed, Mar 23, 2011 at 09:50:25PM +0100, Georg Baum wrote:
> BTW do we have any german speaking mathematician on the list who knows
> how we should deal with the missing 'Satz' theorem (see
> http://www.lyx.org/trac/ticket/7340)?
Depends a bit on what the actual problem is.
Usually I'd associat
Julien Rioux wrote:
> Dear list,
>
> Here's a patch which fix the inclusion of child documents for those child
> documents which have outputtype!=latex, e.g. docs which include the
> lilypond or sweave module and require a preprocessing step.
>
> this problem was reported here:
> http://www.mail-
> On Tue, Mar 22, 2011 at 4:51 PM, Rob Oakes
> wrote:
> > 4.) It seems that there are people willing to help
> promote/evangelize LyX, but I'm not sure we offer much in the
> way of promotional materials to help. Would it be worthwhile
> to create a limited number of tutorials for people, like
Julien Rioux wrote:
> You cannot have two modules which both redefine the output format. This is
> a stupid patch. Something more clever might be done in the c++ code.
ok, if there is no better patch yet.
others, please note that we have new fellow on the developer's ship
so do not forget to giv
Pavel Sanda wrote:
> Georg Baum wrote:
>>
>> I will work on the following items during the next days:
>>
>> 1) Change language code of chinese-traditional in lib/languages to zh_TW
>> (see other thread)
>>
>> 2) When generating lib/layouttranslations, read in the old file before
>> writing the
Georg Baum wrote:
> would be a normal bug IMO. Apart form that I am pretty sure that it does not
> go wrong ;-)
ok.p
Georg Baum wrote:
> from the po directory. Could you or Pavel add this step to the relevant
> release preparing notes please?
done
> The makefile target could also be added to any other target, e.g. remerge.
> Note that you need the python package polib installed. It is also not too
> fast, bu
On 23-3-2011 20:44, Georg Baum wrote:
Georg Baum wrote:
Thanks for the explanation. Meanwhile I have added special code to cover
the current situation. Anything that does not make this special code
useless is no improvement. Changing the .po files is no good idea IMHO,
since I see zh_CN and zh_
Pavel Sanda wrote:
> b...@lyx.org wrote:
>>
>> First version of separate translation machinery for strings that go into
>> exported documents.
>> To update the translations from the .po files, run
>> make ../lib/layouttranslations
>> from po.
>
> shall we bump file version number in case somewth
Georg Baum wrote:
> Thanks for the explanation. Meanwhile I have added special code to cover
> the current situation. Anything that does not make this special code
> useless is no improvement. Changing the .po files is no good idea IMHO,
> since I see zh_CN and zh_TW in my system, but neither zh_H
Jürgen Spitzmüller wrote:
> Georg Baum wrote:
>> OK, I'll do the technical part.
I did it. To update the translations, type
make ../lib/layouttranslations
from the po directory. Could you or Pavel add this step to the relevant
release preparing notes please?
The makefile target could also be
Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:
>> It seems to me that zh_TW is "more" correct for traditional Chinese,
>> although it seems to be more a convention than strictly conforming
>> (since TW and CN are not country codes).
>
> The official tags seem to be zh-Hant (traditional Chi
b...@lyx.org wrote:
> Author: baum
> Date: Wed Mar 23 20:17:15 2011
> New Revision: 38016
> URL: http://www.lyx.org/trac/changeset/38016
>
> Log:
> First version of separate translation machinery for strings that go into
> exported documents.
> To update the translations from the .po files, run
>
Julien Rioux wrote:
> On 19/03/2011 11:54 AM, Pavel Sanda wrote:
>> 1. new layout was proposed by Rob. who agrees/disagrees with this?
>>
>> 2. some people won't be happy with icons change and there was proposal
>> from me and supported by Enrico that we should allow to use older
>> icons a
Jürgen Spitzmüller wrote:
It seems to me that zh_TW is "more" correct for traditional Chinese,
although it seems to be more a convention than strictly conforming
(since TW and CN are not country codes).
The official tags seem to be zh-Hant (traditional Chinese) and zh-Hans
(simplified Chinese)
On Wed, Mar 23, 2011 at 7:45 PM, Ronen Abravanel wrote:
>> > department, and I started with very short into on LaTeX and "in what
>> > scene
>> > LyX is different from word", and then about 40 minutes of demonstration
>> > of
>> > what can I do and how can I do that.
>> >
>> > If there is nothing
Georg Baum wrote:
lib/languages has zh_CN as language code both for chinese (simplified) and
chinese (traditional), while the .po files are named zh_CN.po (simplified)
and zh_TW.po (traditional).
What is correct? Do we need to change lib/languages, or do I need a special
case in the layout trans
On Tue, Mar 22, 2011 at 11:49 PM, Liviu Andronic wrote:
> On Tue, Mar 22, 2011 at 10:23 PM, Ronen Abravanel
> wrote:
> > How long should it be? A year ago I had one hour workshop on LyX in my
> >
> I highly doubt that it would exceed an hour.
>
>
> > department, and I started with very short into
Richard Heck wrote:
> On 03/23/2011 01:41 PM, Pavel Sanda wrote:
>> Richard Heck wrote:
good idea. Richard, can you have look on the python part?
>>> I'm not sure about this. What if someone has a customized classic.ui in
>>> the
>>> userdir?
>> it will have full path then, no?
>>
> No.
On 03/23/2011 01:41 PM, Pavel Sanda wrote:
Richard Heck wrote:
good idea. Richard, can you have look on the python part?
I'm not sure about this. What if someone has a customized classic.ui in the
userdir?
it will have full path then, no?
No. We always do the same thing: Search the user dir,
Hi,
lib/languages has zh_CN as language code both for chinese (simplified) and
chinese (traditional), while the .po files are named zh_CN.po (simplified)
and zh_TW.po (traditional).
What is correct? Do we need to change lib/languages, or do I need a special
case in the layout translation machi
On 03/23/2011 06:28 PM, Stephan Witt wrote:
Am 23.03.2011 um 15:34 schrieb Abdelrazak Younes:
For end-of-document I'd call it normal when LFUN_CHAR_FORWARD does not do
anything.
That was the original goal of the stuck_ variable - to catch the case when the
last word is misspelled and you hit th
veno...@arcadiaclub.com wrote:
> > urmmm, Ale, please kill this "!"...
> > pavel
>
> Tested: works!
Ale, can you please try this patch? it may allow us
to compute crc properly even on samba...
pavel
diff --git a/src/support/FileName.cpp b/src/support/FileName.cpp
index 1650a5b..a16278f 100644
---
On 23/03/2011 4:53 AM, Jürgen Spitzmüller wrote:
Am 22.03.2011 23:41, schrieb Julien Rioux:
Once we are in the preview script, what's a good way to identify that we
use the pdflatex route?
I think the safest method is to search for \usepackage[pdftex]{preview}
in the preamble, as we do in the
Richard Heck wrote:
>> good idea. Richard, can you have look on the python part?
>>
> I'm not sure about this. What if someone has a customized classic.ui in the
> userdir?
it will have full path then, no?
pavel
On 03/23/2011 11:55 AM, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Kill classic.ui, which is for years unmaintained
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg166534.html
Deleted:
lyx-devel/trunk/lib/ui/classic.ui
Does this means that we need an action in prefs2prefs?
goo
Am 23.03.2011 um 15:34 schrieb Abdelrazak Younes:
> On 03/23/2011 02:15 PM, Stephan Witt wrote:
>> Am 23.03.2011 um 13:56 schrieb Abdelrazak Younes:
>>
>>> On 03/23/2011 12:48 PM, Stephan Witt wrote:
Am 23.03.2011 um 10:18 schrieb Abdelrazak Younes:
> On 03/22/2011 08:20 AM, Stepha
Jean-Marc Lasgouttes wrote:
>> Kill classic.ui, which is for years unmaintained
>> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg166534.html
>>
>> Deleted:
>> lyx-devel/trunk/lib/ui/classic.ui
>
> Does this means that we need an action in prefs2prefs?
good idea. Richard, can you have
Le 23/03/2011 16:30, sa...@lyx.org a écrit :
Author: sanda
Date: Wed Mar 23 16:30:10 2011
New Revision: 38008
URL: http://www.lyx.org/trac/changeset/38008
Log:
Kill classic.ui, which is for years unmaintained
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg166534.html
Deleted:
lyx-de
On Wed, Mar 23, 2011 at 3:28 PM, wrote:
> Author: sanda
> Date: Wed Mar 23 15:28:23 2011
> New Revision: 38003
> URL: http://www.lyx.org/trac/changeset/38003
> ==
> --- lyx-devel/trunk/src/support/FileName.cpp Wed Mar
On 03/23/2011 02:15 PM, Stephan Witt wrote:
Am 23.03.2011 um 13:56 schrieb Abdelrazak Younes:
On 03/23/2011 12:48 PM, Stephan Witt wrote:
Am 23.03.2011 um 10:18 schrieb Abdelrazak Younes:
On 03/22/2011 08:20 AM, Stephan Witt wrote:
Am 21.03.2011 um 18:00 schrieb Stephan Witt:
Am 21.03.201
On 23/03/2011 10:02 AM, Jean-Marc Lasgouttes wrote:
Le 23/03/2011 14:10, Julien Rioux a écrit :
On 23/03/2011 8:46 AM, Julien Rioux wrote:
I'll send you a file and the latex log soon.
here.
and when I put Ligatures=TeX in the class options it did not help:
LaTeX Warning: Unused global optio
Also sprach Jean-Marc Lasgouttes:
Yes, I still have this message marked in my inbox. But you didn't yet
propose a working python code, did you?
OTOH JMarc's idea of using a test file strikes me not too bad.
In my mind this is the same idea. Lime what is done in checkLatex().
I thought that G
Also sprach Jean-Marc Lasgouttes:
OK, my mistake.
The comment was not a model of clarity. Maybe a bit better now.
Jürgen
Le 23/03/2011 15:10, Jürgen Spitzmüller a écrit :
Also sprach Jean-Marc Lasgouttes:
Why are there comments in code about supporting luatex from texlive 2009?
Where? If you refer to the comment in BufferParams.cpp:2589 ff., I
wanted to express here that we want to support fontspec back to (at
l
Also sprach Jean-Marc Lasgouttes:
Why are there comments in code about supporting luatex from texlive 2009?
Where? If you refer to the comment in BufferParams.cpp:2589 ff., I
wanted to express here that we want to support fontspec back to (at
least) TeXLive 2009, but that fontspec only suppor
Le 23/03/2011 14:31, Jürgen Spitzmüller a écrit :
Yes, I still have this message marked in my inbox. But you didn't yet
propose a working python code, did you?
OTOH JMarc's idea of using a test file strikes me not too bad.
In my mind this is the same idea. Lime what is done in checkLatex().
J
Le 23/03/2011 14:10, Julien Rioux a écrit :
On 23/03/2011 8:46 AM, Julien Rioux wrote:
I'll send you a file and the latex log soon.
here.
and when I put Ligatures=TeX in the class options it did not help:
LaTeX Warning: Unused global option(s):
[Ligatures=TeX].
OK, but we have an error be
Le 23/03/2011 14:04, Jürgen Spitzmüller a écrit :
You'll need to update fontspec, LuaTeX and probably a bunch of other
packages (at least the latex3 packages) to some newer version than what
TeXLive 2009 provides.
Why are there comments in code about supporting luatex from texlive 2009?
JMarc
Also sprach Guenter Milde:
The error message is clear: it says "... requires XeTeX".
Then we can check for this message. Do you have TeXLive 2009, Günter?
Can you setup a minimal example file?
We had already the discussion with testing the fontspec date. IMO,
this should be done using Pytho
On 23/03/2011 4:53 AM, Jürgen Spitzmüller wrote:
Am 22.03.2011 23:41, schrieb Julien Rioux:
Once we are in the preview script, what's a good way to identify that we
use the pdflatex route?
I think the safest method is to search for \usepackage[pdftex]{preview}
in the preamble, as we do in the
On 2011-03-21, Richard Heck wrote:
> On 03/21/2011 03:44 PM, Joost Verburg wrote:
>> So there are two bugs here:
>> * The class conversion errors shouldn't happen
> This is bug #7080.
>> * The log isn't being cleared and previous errors therefore prevent
>> PDF export etc.
> This last is new,
On 23/03/2011 9:17 AM, Guenter Milde wrote:
On 2011-03-22, Julien Rioux wrote:
I run Ubuntu 10.10 with texlive 2009
This is the problem: LuaTeX is not "production ready" in TeXLive 2009
and does not work with LyX 2.
Fine.
We should really eliminate all those buggy output formats and kee
On 2011-03-23, Jürgen Spitzmüller wrote:
> Also sprach Jean-Marc Lasgouttes:
>> It turns out I have either ubuntu 9.10 (texlive 2007) or ubuntu 10.10
>> (texlive 2010?).
>> Isn't it a matter of loading fontspec package with Ligatures=TeX?
> The problem, AFAIU, is that the fontspec version back th
I added a book list here:
http://wiki.lyx.org/LyX/ProducedPublications
It requires a password to approve the link.
Could any developer approve the link for me or send me the password.
Best Regards
waluyo
Also sprach Richard Heck:
>> I thought that it could be a good idea because i'm using Lyx with
>> > Okular, and synctex doesn't works for me. I followed the wiki (
>> > http://wiki.lyx.org/LyX/SyncTeX) but nothing works.
>> >
> As I said in the bug, this is a separate issue. We should get inverse
Le 23/03/2011 13:47, Julien Rioux a écrit :
On 23/03/2011 7:47 AM, Jean-Marc Lasgouttes wrote:
It turns out I have either ubuntu 9.10 (texlive 2007) or ubuntu 10.10
(texlive 2010?).
if you use the standard repositories for ubuntu 10.10 you should have
texlive 2009
And actually I do not have
On 2011-03-22, Julien Rioux wrote:
> I run Ubuntu 10.10 with texlive 2009
This is the problem: LuaTeX is not "production ready" in TeXLive 2009
and does not work with LyX 2.
> We should really eliminate all those buggy output formats and keep only
> XeTeX. How do we go about that?
Remove the
> So this means that this stuck_ variable was useful for some dark corner case
> it seems... I removed it because I didn't see how and why it is useful.
1-0 for documentation.
Vincent
Am 23.03.2011 um 13:56 schrieb Abdelrazak Younes:
> On 03/23/2011 12:48 PM, Stephan Witt wrote:
>> Am 23.03.2011 um 10:18 schrieb Abdelrazak Younes:
>>
>>> On 03/22/2011 08:20 AM, Stephan Witt wrote:
Am 21.03.2011 um 18:00 schrieb Stephan Witt:
> Am 21.03.2011 um 09:43 schrieb Abde
On 23/03/2011 8:46 AM, Julien Rioux wrote:
I'll send you a file and the latex log soon.
here.
and when I put Ligatures=TeX in the class options it did not help:
LaTeX Warning: Unused global option(s):
[Ligatures=TeX].
--
Julien
luatex-test.lyx
Description: application/lyx
This is Lua
On 03/23/2011 09:09 AM, Michael wrote:
> I thought that it could be a good idea because i'm using Lyx with
> Okular, and synctex doesn't works for me. I followed the wiki (
> http://wiki.lyx.org/LyX/SyncTeX) but nothing works.
>
As I said in the bug, this is a separate issue. We should get inverse
I thought that it could be a good idea because i'm using Lyx with Okular,
and synctex doesn't works for me. I followed the wiki (
http://wiki.lyx.org/LyX/SyncTeX) but nothing works.
Best regards.
Michael.
On Tue, Mar 22, 2011 at 3:31 PM, Liviu Andronic wrote:
> On Mon, Mar 21, 2011 at 5:41 PM,
On 03/22/2011 10:31 AM, Liviu Andronic wrote:
> On Mon, Mar 21, 2011 at 5:41 PM, Michael wrote:
>> it's a shame. It would be a killer feature.
>>
>> On Sun, Mar 20, 2011 at 9:41 PM, LyX Ticket Tracker wrote:
>>> #7377: Built-in pdf viewer
> I would be against LyX fancying a built-in PDF viewer, m
Also sprach Julien Rioux:
Isn't it a matter of loading fontspec package with Ligatures=TeX?
I'll try this
This won't help.
You'll need to update fontspec, LuaTeX and probably a bunch of other
packages (at least the latex3 packages) to some newer version than what
TeXLive 2009 provides.
J
On 03/23/2011 12:48 PM, Stephan Witt wrote:
Am 23.03.2011 um 10:18 schrieb Abdelrazak Younes:
On 03/22/2011 08:20 AM, Stephan Witt wrote:
Am 21.03.2011 um 18:00 schrieb Stephan Witt:
Am 21.03.2011 um 09:43 schrieb Abdelrazak Younes:
On 03/21/2011 07:30 AM, Stephan Witt wrote:
Am 20.03.201
Also sprach Jean-Marc Lasgouttes:
It turns out I have either ubuntu 9.10 (texlive 2007) or ubuntu 10.10
(texlive 2010?).
Isn't it a matter of loading fontspec package with Ligatures=TeX?
The problem, AFAIU, is that the fontspec version back then did not
support LuaTeX yet, but only XeTeX. Lua
On 23/03/2011 7:47 AM, Jean-Marc Lasgouttes wrote:
It turns out I have either ubuntu 9.10 (texlive 2007) or ubuntu 10.10
(texlive 2010?).
if you use the standard repositories for ubuntu 10.10 you should have
texlive 2009
Isn't it a matter of loading fontspec package with Ligatures=TeX?
I
On 23/03/2011 4:39 AM, Jürgen Spitzmüller wrote:
The dvi output and subsequent chains (such as dvips, dvipdfm, ps2pdf)
should not be there in theory, but it's difficult to suppress them in
practice, see here:
http://marc.info/?l=lyx-devel&m=129619430428896&w=2
As it is hinted to in that threa
> urmmm, Ale, please kill this "!"...
> pavel
Tested: works!
venom00
Am 23.03.2011 um 10:18 schrieb Abdelrazak Younes:
> On 03/22/2011 08:20 AM, Stephan Witt wrote:
>> Am 21.03.2011 um 18:00 schrieb Stephan Witt:
>>
>>> Am 21.03.2011 um 09:43 schrieb Abdelrazak Younes:
>>>
On 03/21/2011 07:30 AM, Stephan Witt wrote:
> Am 20.03.2011 um 17:50 schrieb Abdel
Le 23/03/2011 11:01, Jürgen Spitzmüller a écrit :
Someone with TeXLive 2009 needs to setup a minimal example file for
testing then (without a specific OpenType font). I can't, since it
obviously works for me.
It turns out I have either ubuntu 9.10 (texlive 2007) or ubuntu 10.10
(texlive 2010?)
Am 21.03.2011 22:18, schrieb Reuben Thomas:
I remain a fan of LyX, if not a hardcore user, so rather than having
to check your web site it would be great if you'd announce all
releases, not just stable ones, on Freshmeat.
I am the one who currently is registered as project owner at fm. I try
t
On Wed, Mar 23, 2011 at 11:22 AM, Liviu Andronic wrote:
> On Wed, Mar 23, 2011 at 10:02 AM, Rainer M Krug wrote:
>> Hi
>>
>> I am using Ubuntu (maverick) and LyX, and I am wondering: would it be
>> possible to set up an official or inofficial ppa on launchpad in which
>> the newest releases will
On Wed, Mar 23, 2011 at 10:02 AM, Rainer M Krug wrote:
> Hi
>
> I am using Ubuntu (maverick) and LyX, and I am wondering: would it be
> possible to set up an official or inofficial ppa on launchpad in which
> the newest releases will be? Possibly a stable and an unstable for the
> betas?
>
There a
Hi
Sorry if this email appears twice - mailing error on my side.
I am using Ubuntu (maverick) and LyX, and I am wondering: would it be
possible to set up an official or inofficial ppa on launchpad in which
the newest releases will be? Possibly a stable and an unstable for the
betas? This would br
Am 23.03.2011 10:54, schrieb Jean-Marc Lasgouttes:
Ah, I see now that your distribution (TeXLive 2009) is too old for
proper LuaTeX support. I have tried to find a method to exclude LuaTeX
if it is not new/stable enough, but didn't succeed so far.
Just give an example of a document that will no
Le 23/03/2011 09:55, Jürgen Spitzmüller a écrit :
Ah, I see now that your distribution (TeXLive 2009) is too old for
proper LuaTeX support. I have tried to find a method to exclude LuaTeX
if it is not new/stable enough, but didn't succeed so far.
Just give an example of a document that will not
Enrico Forestieri wrote:
> On Mon, Mar 21, 2011 at 12:23:29AM +0100, Enrico Forestieri wrote:
>
> > Thinking a bit more about it, maybe the code could be arranged such that
> > to not have hardcoded the normal size. Say we look at the size of a
> > particular icon and then set normalIconSize accor
On 03/22/2011 08:20 AM, Stephan Witt wrote:
Am 21.03.2011 um 18:00 schrieb Stephan Witt:
Am 21.03.2011 um 09:43 schrieb Abdelrazak Younes:
On 03/21/2011 07:30 AM, Stephan Witt wrote:
Am 20.03.2011 um 17:50 schrieb Abdelrazak Younes:
Hi Pavel,
Here is a patch that should fixes #7375. The p
Hi
I am using Ubuntu (maverick) and LyX, and I am wondering: would it be
possible to set up an official or inofficial ppa on launchpad in which
the newest releases will be? Possibly a stable and an unstable for the
betas? This would broaden the tester basis considerably. I have never
setup a ppa o
Am 23.03.2011 09:39, schrieb Jürgen Spitzmüller:
The LuaTeX output is supposed to work, given that you have a reasonably
recent distribution. We probably need some more info from you to find
out what fails.
Ah, I see now that your distribution (TeXLive 2009) is too old for
proper LuaTeX suppor
Am 22.03.2011 23:41, schrieb Julien Rioux:
Once we are in the preview script, what's a good way to identify that we
use the pdflatex route?
I think the safest method is to search for \usepackage[pdftex]{preview}
in the preamble, as we do in the color_pdf method.
Jürgen
Am 23.03.2011 00:13, schrieb Julien Rioux:
Open splash.lyx
Set "Use non-tex fonts"
Leave everything else as default
Under the View menu I got:
DVI
not working, hangs LyX
DVI (LuaTeX)
not working, \RequireXeTeX error, font mapping not loadable errors
OpenDocument
not working, hangs LyX
PDF (dv
Rainer,
I completely agree and this would be a very usefull document - but the
> issue is not to provide an easy transition from Word to LyX, but to
> enable an easy co-operation with Word or OO / LibreOffice users, in
> the sense that:
>
Ah OK, I obviously misunderstood the basis of the thread,
On Wed, Mar 23, 2011 at 9:12 AM, Graham Smith wrote:
> One possible approach is to write an introduction to Lyx specifically aimed
> at Word users.
>
This makes a lot of sense to me. Most of all we probably need an
introduction for those coming from the world of Word (highest
priority) and, perhap
On Wed, Mar 23, 2011 at 9:12 AM, Graham Smith wrote:
> One possible approach is to write an introduction to Lyx specifically aimed
> at Word users.
>
> This has been done for R at
> http://chartsgraphs.wordpress.com/learnr-toolkit/ where the tutorials assume
> familiarity with Excel and demonstrat
One possible approach is to write an introduction to Lyx specifically aimed
at Word users.
This has been done for R at
http://chartsgraphs.wordpress.com/learnr-toolkit/ where the tutorials assume
familiarity with Excel and demonstrate how things differ (or are the same)
in R. There have also been
> 1) Compile Errors. Normal users aren't used to dealing with compile
> errors and shouldn't be expected to fix them. Even I don't like
> dealing with compile errors all that much.
> 1a) Perhaps we could do some sort of bisect to determine where the
> error is (either over the file itself or some f
92 matches
Mail list logo
