Uwe Stöhr schrieb:
> Georg Baum schrieb:
>
>> If you have zipped graphics, e.g. x.eps.gz these will not be unzipped
>> on export, since LaTeX can handle them as is.
>
> Thanks for the info but when I use an eps.gz image I get lots of LaTeX
> errors that x.eps.gz could not be found and that
Uwe Stöhr schrieb:
> Herbert Voss schrieb:
>
>> did you also created a x.eps.bb file?
>
> No because I wasn't aware that this is needed. I grabbed some images
> from the net to test.
> How could I zipp an EPS-file so that I get an *.eps.gz and a *.eps.bb
> automatical
Uwe Stöhr schrieb:
> Jean-Marc Lasgouttes schrieb:
>
>> Uwe, we would indeed be delighted to have a real doc maintainer. But I
>> agree with Georg that, at least for a first cleanup phase, the work
>> should be done on the main documents. The more ambitious plan can only
>> be carried out if you
Martin Vermeer schrieb:
> On Sun, Oct 29, 2006 at 06:03:30PM +0100, Georg Baum wrote:
>> Am Sonntag, 29. Oktober 2006 12:57 schrieb Martin Vermeer:
>>> On Thu, Oct 26, 2006 at 04:12:08PM +0200, Georg Baum wrote:
My plan is to put it in for 1.4.4.
>>> Good! We should do this then.
>> What I
Andre Poenitz schrieb:
> On Fri, Oct 27, 2006 at 11:05:51AM +0200, Edwin Leuven wrote:
>> sometime ago i wrote:
>>
>> Original Message
>> Subject: export to latex
>> Date: Tue, 02 May 2006 20:53:01 +0200
>> From: Edwin Leuven <[EMAIL PROTECTED]>
>> To: LyX Developers
Georg Baum schrieb:
> Am Dienstag, 31. Oktober 2006 16:05 schrieb Enrico Forestieri:
>> On Tue, Oct 31, 2006 at 01:46:54PM +0100, Georg Baum wrote:
>>
>>> Enrico Forestieri wrote:
>>>
But I simply used the default converter chosen by LyX and the
> rotation
was actually depending on
Georg Baum schrieb:
> Am Dienstag, 31. Oktober 2006 22:23 schrieb Herbert Voss:
>> ps2pdf _and_ epstopdf uses both ghostscript ...
>> sometimes ghostscript is too clever and rotates parts of the images,
>> which shouldn't. In this case a -dAutoRotatePages=/None did the tr
Enrico Forestieri schrieb:
> On Wed, Nov 01, 2006 at 09:34:30AM +0100, Georg Baum wrote:
>
>> Am Dienstag, 31. Oktober 2006 22:09 schrieb Enrico Forestieri:
>>> I am wondering if it is worth trying such a check when deciding whether
>>> ps2pdf or epstopdf is to be used, instead of defining a
Enrico Forestieri schrieb:
>> If you are sure that there is at least one catcode greater than 128 is
>> classified as something other than catOther, I'll do the change. But
>> from what I read about TeX catcode since then, I doubt it.
>
> Maybe you are right as, from what I can see, only the
Enrico Forestieri schrieb:
>>> I think that we should leave the 256, but if you and others don't agree,
>>> then please also make the corresponding changes to texparser.C
>> only the characters 0,13,32,35-38,65-90,92,94,95,97-123,125-127
>> have a catcode other than 12. All others from the 256
Enrico Forestieri schrieb:
> On Sun, Nov 05, 2006 at 04:00:39PM +0100, Abdelrazak Younes wrote:
>
>> Enrico Forestieri wrote:
>>> On Sun, Nov 05, 2006 at 09:58:28AM +0100, Georg Baum wrote:
> I think that we should leave the 256, but if you and others don't agree,
> then please also make
Enrico Forestieri schrieb:
> On Sun, Nov 05, 2006 at 04:21:47PM +0100, Herbert Voss wrote:
>
>> Enrico Forestieri schrieb:
>>
>>>>> I think that we should leave the 256, but if you and others don't agree,
>>>>> then please also make th
Georg Baum schrieb:
> Am Sonntag, 5. November 2006 17:25 schrieb Enrico Forestieri:
>
>> Maybe tex2lyx should be updated to take into account the fact that
>> the latex file could be utf8 encoded?
>
> Yes, as I wrote: tex2lyx almost completely ignores encodings.
>
>> If I am not wrong, now LyX
Georg Baum schrieb:
> Am Sonntag, 5. November 2006 19:22 schrieb Herbert Voss:
>> I am interested in seeing how someone will parse a tex source, where
>> _every_ macro or environment can be hide after several other macros
>> or catcode changes ...
>
> Impossible IMH
Enrico Forestieri schrieb:
>> And the
>> fact that LyX will eat the other braces if you read the file, and then the
>> inner ones if you save it and read it again.
>
> Nope. That will only occur if the size of the nucleus is 1, but then it
> doesn't matter as latex macros don't need braces
Georg Baum schrieb:
> This patch adds support for the esint package:
>
> - new header flag for esint (can be off, auto, on). Since the package is
> quite new (tetex doew not have it, but texlive), and because some people
> might like the different look of wasysym integrals (or define their own)
Georg Baum schrieb:
> Am Donnerstag, 9. November 2006 15:18 schrieb Herbert Voss:
>> Georg Baum schrieb:
>>> - load the wasysym package automatically if esint gets loaded, since
> esint
>>> redefines the integrals in a consistent way
>>> (http://bugzilla.
Georg Baum schrieb:
> Am Donnerstag, 9. November 2006 14:15 schrieb Enrico Forestieri:
>> On Thu, Nov 09, 2006 at 01:26:31PM +0100, Georg Baum wrote:
>>
>>> We have unicode for document contents. We don't have unciode for
> internal
>>> keywords. This is the same as in LaTeX: You cannot define
Georg Baum schrieb:
> Am Dienstag, 21. November 2006 15:57 schrieb Ozgur Ugras BARAN:
>> As requested today, I have added \clearpage and \cleardoublepage
>> commands.
>
> As I wrote: The changes are trivial. If this should appear in a menu then
> we would also need an explanation of the
Georg Baum schrieb:
> Herbert Voss wrote:
>
>> and there is a \newpage ...
>
> I know. I always thought that it was equivalent to \clearpage. If that is
> not true, what is the difference?
\newpage has the same behaviour for a page as \newline
for a line, the "break&
Bo Peng schrieb:
>> If you back this feature as well that makes three developers and the
>> code
>> can be committed.
>
> I like this feature and read the patch briefly. I am not sure what you
> mean by 'back', but I guess I can fix problems of this feature when
> bugs are found (not tex2lyx or
Abdelrazak Younes schrieb:
> nusret wrote:
>> Hi all,
>> Painting is not just a Mac problem, I sincerely hope
>> that there is an easy way to fix it on Windows, too:
>> my documents are full of math, and the rendering is
>> extremely slow which makes Lyx essentially unusable in
>> my case. I
Gregor Gorjanc schrieb:
> Dear LyX team!
>
> I am trying to provide support for Sweave[1] (another literate programming
> idea
> based on noweb) in LyX. I have already contacted this list about Sweave [2]
> and
> got some respone from Andre. I have just responded in that thread. To have a
>
Gregor Gorjanc schrieb:
> Gregor Gorjanc <[EMAIL PROTECTED]> writes:
>
>> Herbert Voss ...> writes:
>>> you mean center, not centering ...
>>> \centering is a macro and center an environment.
>>>
>> Whatever. LyX sometimes outputs centering
Jean-Marc Lasgouttes schrieb:
I guess Herbert is balking at the use of centering as an environment.
In my view, using
\begin{centering}...\end{centering}
is equivalent to the more traditional
{\centering ...}
except that at least the first one is a proper markup. I agree
nevertheless that
Enrico Forestieri schrieb:
Herbert, the two constructs are not equivalent.
I know,
what I want to show is that it is not a good idea to
use a _command_ as an environment.
This one:
\begin{figure}
\begin{centering}
foo
\end{centering}
\caption{bar}
\end{figure}
corresponds to:
Jean-Marc Lasgouttes schrieb:
"Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
Herbert> Enrico Forestieri schrieb:
Herbert, the two constructs are not equivalent.
Herbert> I know, what I want to show is that it is not a good idea to
Herbert> use a _command_ as
Enrico Forestieri schrieb:
On Sun, Dec 03, 2006 at 09:31:45PM +0100, Herbert Voss wrote:
no, do it without a caption ... There is no _correct_ way.
A command shouldn't be used as environemtn. That's correct.
Independant from that it works sometimes ...
However, it is clearly documented
Richard Heck wrote:
> Yes. How about this. Just say, explicitly:
> [X] Use -Pprinter parameter with dvips.
> And then, for a tooltip:
> Adjusts dvips output for a particular printer. (Note: dvips must be
> pre-configured for that printer.)
dvips is not pre-configured, it uses always a config
Richard Heck wrote:
> Herbert Voss wrote:
>> Richard Heck wrote:
>>
>>
>>> Yes. How about this. Just say, explicitly:
>>> [X] Use -Pprinter parameter with dvips.
>>> And then, for a tooltip:
>>> Adjusts dvips output for a pa
Jean-Marc Lasgouttes wrote:
>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> sorry, I cannot follow here
>
> Herbert> dvips -Pabc uses a config.abc file which declares
> Herbert> resolution, font using a
Richard Heck wrote:
>>
>> "Herbert" == Herbert Voss
>> <[EMAIL PROTECTED]> writes:
>> Herbert> sorry, I cannot follow here
>>
>> Herbert> dvips -Pabc uses a config.abc file which declares
>> Herbert> resolution, font
Richard Heck wrote:
> Herbert Voss wrote:
>> Richard Heck wrote:
>>
>>> [EMAIL PROTECTED] src]$ find /usr/share/texmf/dvips/ -name 'config.*'
>>> /usr/share/texmf/dvips/tetex/config.www
>>> /usr/share/texmf/dvips/tetex/config.download35
>>> /u
Enrico Forestieri wrote:
>> config. is misleading. For example: config.pdf is a config file
>> to use always Type 1 fonts but I can print the ps file on _every_ printer
>
> Granted. But what if you have 300, 600, and 1200 dpi printers?
> The "Adapt Output" thing let you adapt (sic!) the pk fonts
Jean-Marc Lasgouttes wrote:
>> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
>
> Richard> And by the way, I think this means that "case 2"---see
> Richard> LyXFunc.cpp, line 1065 or so---is broken. This handles the
> Richard> case where no "spool command", such as lp, is provided. In
Enrico Forestieri wrote:
> On Mon, Jun 04, 2007 at 10:45:40PM +0200, Jean-Marc Lasgouttes wrote:
>
>>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>> Herbert> these are _all_ config files and not printer files.
>>
>> H
Jean-Marc Lasgouttes wrote:
>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> this is nowadays only of some historical interest ... As seen
> Herbert> is Richard's config list from Fedora, the file is used as a
> H
Jean-Marc Lasgouttes wrote:
>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> Jean-Marc Lasgouttes wrote:
>>>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
> Herbert> thi
Jean-Marc Lasgouttes wrote:
>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
>>> You should :) How do you use dvips in a linux-like setup?
>
> Herbert> pretty easy ... :-) there is a config.ps and all other
> Herbert&
Enrico Forestieri wrote:
> On Tue, Jun 05, 2007 at 01:25:43PM +0200, Herbert Voss wrote:
>> Jean-Marc Lasgouttes wrote:
>>>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
>>> Herbert> dvips is a driver and not a pri
Juergen Spitzmueller wrote:
> Richard Heck wrote:
>
>> << c.r/255.0 << ',' << c.g/255.0 << ',' << c.b/255.0
>
> An alternative would be to require xcolor instead of color (we require this
> anyway nowadays) and use \definecolor{shadecolor}{RGB}{}. Then you don't
> have to do any calculation.
Herbert Voss wrote:
> Juergen Spitzmueller wrote:
>> Richard Heck wrote:
>>
>>> << c.r/255.0 << ',' << c.g/255.0 << ',' << c.b/255.0
>> An alternative would be to require xcolor instead of color (we require this
>> anyway nowaday
Enrico Forestieri wrote:
> Both forms are equivalent, indeed \bgroup and \egroup are defined
> as \let\bgroup={ \let\egroup=} by TeX. The macro forms are useful
> because you can include them in a definition without worrying
> about how they nest. I mean that you can do something like:
>
>
Bo Peng wrote:
> It is currently non-trivial to write
>
> 1. item1
> 1. item1
> 2. item2
that's pretty easy
choose enumerate -- insert text
choose standard -- insert Ctrl-L and %
choose enumerate -- insert text
view
Herbert
Bo Peng wrote:
> I can not believe that I am hitting a second WONTFIX in two days, but
> this is likely the fate of this patch.
>
> The attached patch adds SplitLayout environment to a few layout/inc
> files that will end up in almost all layouts. This environment does
> not output anything but
Jean-Marc Lasgouttes wrote:
>> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
>>> what you need is nothing else than an empty line inside LyX and
>>> this is pretty easy with
>>>
>>> Style "Standard(Keep)" CopyStyle Standard KeepEmpty 1 End
>>>
>>> in stdclass.inc
>
> Andre> Good
Jean-Marc Lasgouttes wrote:
>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> two major facts:
>
> Herbert> 1. TeX knows no space ... it is used to split words 2. TeX
> Herbert> knows no empty lines ... it is
Martin Vermeer wrote:
>>> I would advise against that. People will use it as a word-like "put
>>> multiple cariage return to do my page layout" feature and then
>>> complain that it does not show on screen.
>> two major facts:
>>
>> 1. TeX knows no space ... it is used to split words
>> 2. TeX
Bo Peng wrote:
>> Herbert> The current behaviour is easy!
>
> But not so easy for lyx newbies. The question is: what to insert that
> do not show up in the screen output (better latex output), yet split
> the environment? I remember that it took me 10 minutes to figure that
> out a few years ago.
Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
Asger Ottar Alstrup wrote:
LaTeX can do UTF8, it seems.
http://mail.nl.linux.org/linux-utf8/2004-04/msg0.html
Just use "\usepackage[utf8]{inputenc}".
Note that there are still lots of packages that don't work with utf8.
For
Uwe Stöhr wrote:
Bo Peng writes:
What are the status of dvipost and latex-preview? They are needed for
the essential features of lyx: change-tracking and instant preview.
Last time I check, they are not part of miktex.
They are still not part of MiKTeX but instant preview is part of the
Bo Peng wrote:
\usepackage{usernames]{color}
That one is clearly wrong. I don't know whether the color package
has an option "usernames", but the brackets are clearly mismatched.
Sorry, my typo. Lyx inserts
\usepackage[usenames]{color}
this is superfluous, beamer loads by default
Bo Peng wrote:
Lyx inserts
\usepackage[usenames]{color}
this is superfluous, beamer loads by default xcolor.
Options to xcolor can be passed via the class options
Layout->Document->Layout->Options
So \usepackage{color} should not be inserted at all. I tried to add
yes, shouldn't be part
Bo Peng wrote:
options "pdftex,usenames" for beamer but still get the 'option clash
why do you need the pdftex option? It could be detected
by nearly all packages itself. And beamer itself passes it
to hyperref
use "dvipsnames,xcolor" as class options
pdftex is suggested by the error
Bo Peng wrote:
options "pdftex,usenames" for beamer but still get the 'option clash
why do you need the pdftex option? It could be detected
by nearly all packages itself. And beamer itself passes it
to hyperref
use "dvipsnames,xcolor" as class options
pdftex is suggested by the error
Jean-Marc Lasgouttes wrote:
"Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
Herbert> it cannot work, because LyX inserts by default a
Herbert> \usepackage[usenames]{color} which is
Herbert> -- wrong here
Because beamer provides it?
Herbert> -- and should
Bo Peng wrote:
My best guess, and it's just a guess, is that bibtex's being handed a
path with spaces and choking on them.
I am not quite sure why miktex/bibtex can not handle a path with
spaces, whereas miktex/latex can. Anyway, if this is a problem that
_TeX_ cannot handle spaces. I
Juergen Spitzmueller wrote:
Martin Vermeer wrote:
Perhaps this should be called an enhancement request and get its own bug
number.
perhaps.
Now convince HIM to put the #2015-fix in ;-)
Which of them? ;-)
Lars or Gullik. Jean and Marc have already expressed their principal
Bo Peng wrote:
And personally bst files should always go into c:\localtexmf\bibtex\bst\
Since the .bst file (downloaded from a Journal's website) is only
needed for a paper I am writing, it makes sense to put it along with
the paper. Also, it is troublesome, and sometimes not allowed, to put
Georg Baum wrote:
Am Dienstag, 3. Januar 2006 16:50 schrieb Uwe Stöhr:
Bo Peng asked:
2. It is not safe to put .bst files in a path with spaces. .lyx files
and all figure files are OK, as well as .bib files.
Also yes. The problem is only a problem of bibtex not of LyX. I sent a
bug report
Uwe Stöhr wrote:
> TeXLive2003 had own installer, TeXLive2004 hadn't windows installer,
> but later appear native windows installer: tlpm.exe (text mode) +
> tlpmgui.exe...
> Several edition of TeXLive have different variables: TEXMF, TEXMFMAIN
> TEXMFCNF.
just like with LyX, every
Jean-Pierre Chrétien wrote:
Uwe Stöhr <[EMAIL PROTECTED]> writes:
[...]
These problems and possibly more implies that I don't give support that
LyXWin works together with TeXLive.
I bought the official TeXLive2005 DVD and fiddled aroud for three days
after I gave up to get it to work
Uwe Stöhr wrote:
Herbert Voss schrieb:
So I would say, that MiKTeX is also powerful than a teTeX
or texlive installtion.
It is. Personally I like the automatic(on the fly) installation of
missing LaTeX-packages, so that the user isn't bothered with
LaTeX-errors that xxx.sty is missing
Angus Leeming wrote:
On Wednesday 04 January 2006 19:26, Uwe Stöhr wrote:
Angus Leeming wrote:
- I found also incompatibilities in the programs dt2dv and dv2dt,
that are used by LyX for the DVI-output.
Could you expand?
TeXLive has its own dt2dv versions, I expect old ones. The are
Angus Leeming wrote:
Thanks. But what I really meant is: I pulled the dt2dv package off CTAN.
How do I go about getting these improvements into it?
to the people listed in the header, e.g. Nelson Beebe. But I do not
know any person, who uses or needs this file ...
Herbert
Uwe Stöhr wrote:
Herbert Voss wrote:
This feature is very useful for LyX because all missing packages are
installed while LyX reconfigures.
no, this works as along as Christian has build a cab file of
such a package.
But you can build it and send it to him. I did this in the past to have
Uwe Stöhr wrote:
Herbert Voss wrote:
there is no reason to support old TeXLive versions.
I couldn't expect that users upgrade their TeXLive every year.
- TeXLive don't have the program "epstopdf" so that you have to
anwer from Staszek (texlive):
TeX Live2005 *has* epstopdf f
I just saw, that LyX has some own special (?) class and
style files in lib/tex. This is not a TeX-world-friendly
solution and makes supporting these files difficult for
the package writers. On the other hand an export to
LaTeX file won't run, because it chooses the CTAN package
and/or style file
Lars Gullik Bjønnes wrote:
LaTeX is not ours...
'In the background the legendary (La)TeX typesetting engine makes you
look good.'
the typesetting engine is _only_ TeX, LaTeX is a macro package,
or called a special format, no more no less
Herbert
Uwe Stöhr wrote:
+Notes: The package
+\family sans
+ preview
+\family default
+ is needed by LyX to preview math formulas when you select the option ``Instant
+ preview'' in
_everything_ for which preview is active, e.g. external stuff
http://tug.org/PSTricks/main.cgi?file=LyX/lyx
Jean-Marc Lasgouttes wrote:
"Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
Jose'> Lars or Jean-Marc, may I insert beamer.layout in LyX?
What kind of guarantee do we have that beamer is not a fast moving
target? Will everybody have a beamer.cls that is compatible with our
layout?
Herbert Voss wrote:
Jean-Marc Lasgouttes wrote:
"Jose'" == Jose' Matos <[EMAIL PROTECTED]>
writes:
Jose'> Lars or Jean-Marc, may I insert beamer.layout in LyX?
What kind of guarantee do we have that beamer is not a fast moving
target? Will everybody have a beamer.cls
Uwe Stöhr wrote:
Jean-Marc Lasgouttes writes:
Jose'> Lars or Jean-Marc, may I insert beamer.layout in LyX?
What kind of guarantee do we have that beamer is not a fast moving
target? Will everybody have a beamer.cls that is compatible with our
layout?
Also older beamer class files
Uwe Stöhr wrote:
Herbert Voss schrieb:
Also older beamer class files beginning with beamer 2.0 from
2004-02-18 works with the beamer.layout.
but 2.x is incompatible to 3.0 and later
Not the layout file. I've presentations created with beamer 2.x and 3.x
using the same beamer.layout
Uwe Stöhr wrote:
Herbert Voss schrieb:
What I want to say is, that _LyX itself_ should not
contain these files. They should be installed from the the local
distribution, then you'll be sure, that you have always the right
one.
But the average user don't want to copy layout files
Juergen Spitzmueller wrote:
if (isRequired("color")) {
if (params_.graphicsDriver == "default")
- packages << "\\usepackage[usenames]{color}\n";
- else
+ if (isRequired("dvipost"))
+
Juergen Spitzmueller wrote:
Isn't RequirePackage for packages and classes and usepackage for the
preamble (this is what I read in the documents)?
yes and no ...
How about the attached? Makes the code even simpler.
I forget the order of loading packages. Was ist first LyX and
then user or
Juergen Spitzmueller wrote:
> Herbert Voss wrote:
>
>>> Isn't RequirePackage for packages and classes and usepackage for the
>>> preamble (this is what I read in the documents)?
>>
>> yes and no ...
>
> Why yes, why no?
- take care of some form
Juergen Spitzmueller wrote:
> Herbert Voss wrote:
>
>> not really, because there exists some packages, which have the
>> same option name, but with a different meaning. Passing it via
>> \documentclass can cause problems.
>> \PassOptionsToPackage is the save way,
Uwe Stöhr wrote:
Georges-Etienne Legendre a écrit:
Now it seems that I'm not able to generate pdf/dvi that has graphics
into.
I have errors like this :
--
Missing \endcsname inserted.
..._Universite_svnintro_conflit\string".pdf}
Bo Peng wrote:
Just let you know that underscore.sty has a problem that causes
\includegraphics{"filename_with_underscore"} to fail. Try it by
read the documentation of underscore.sty!
Even if a latex file can be compiled directly, it will fail under lyx
because of the way lyx handles
Bo Peng wrote:
And with \usepackage[strings]{underscore}?
\newcommand\UnderscoreCommands{\do\includegraphics}
\usepackage[strings]{underscore}
Herbert
Andre Poenitz wrote:
On Wed, Feb 01, 2006 at 12:05:03PM +0100, Karsten Heymann wrote:
Looking forward to Berlin,
Aehm... what's in Berlin?
Did I miss something?
http://www.dante.de/dante2006/
Herbert
Charpentier Philippe wrote:
last week-end I wanted to try the last package pst-pdf. Then I install
the latest version of pstricks, preview and xkeyval, and begin some
tests. At a moment, I found a strange comportment of lyx (1.3.7), which
can be seen with the following example:
choose the
Charpentier Philippe wrote:
Charpentier Philippe wrote:
last week-end I wanted to try the last package pst-pdf. Then I
install the latest version of pstricks, preview and xkeyval, and begin
some tests. At a moment, I found a strange comportment of lyx (1.3.7),
which can be seen with the
Georg Baum wrote:
I got an interesting email from Henri Adriaens, a author of powerdot. He
reports me his problems with the implementation of powerdot for LyX. I
mean that they are interesting enough to talk about it to make life
easier for package authors to provide a LyX layout file.
Here is
Lars Gullik Bjønnes wrote:
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| I noticed today that bibtex-supported citations do not work (giving
| [?]) when doing the first View>DVI. The reason is simple: LyX runs
| latex, then bibtex, then latex again. Therefore, since bibliography is
| at
It makes no sense to allow ctrl-enter for a newline
in a caption without loading the package "caption".
Instead of a "\protect\\" a "\newline" seems to be the
better export. "\\" is very often redefined by other
packages.
The first line in the body of a float shouldn't be indented
in the
Enrico Forestieri wrote:
> On Wed, Apr 25, 2007 at 11:55:42AM +0200, Abdelrazak Younes wrote:
>
>> Enrico Forestieri wrote:
Modified:
lyx-devel/branches/BRANCH_1_4_X/src/frontends/qt2/QDelimiterDialog.C
URL:
Michael Gerz wrote:
> Bo Peng schrieb:
>>> In that case was a new inset, like include/input inset, with
>>> support to
>>> configure the different options from listings, like the programming
>>> language, ...
>>
>> That will be good to have I googled for 2 minutes and could not
>> find that
Bo Peng wrote:
>> It is not "treating as different paragraphs". They are different
>> paragraphs.
>>
>> Yes, different paragraphs are always separated by a blank line.
>
> Now I see why an inset is the only way to generate code with single
> newlines. Herbert, what do you have right now?
sent it
Georg Baum wrote:
> Another one is too little focus on 1.5.0 release. For example, restarting
> the work on insetlisting now is ridicolous. Sorry Bo and José, but that is
> how I see it, and believe me, this is something I have been wanting for a
> long time. I know that implementing that
Jürgen Spitzmüller wrote:
> Leuven, E. wrote:
>> so why don't we postpone this listings business until 1.6?
>
> Agreed.
curious ... :-)
we had 1.1.4, if I remember well, and this is years ago and
since this time beginning with Lars this is the default
statement, when I asked to include the
Jürgen Spitzmüller wrote:
> Jean-Marc Lasgouttes wrote:
>> This is the curse of the listing inset: people think about it only
>> after the first beta is out :)
>
> exactly. I also have things in my tree I urgently wish to have. But I hold
> them back until 1.6 development begins (hopefully
Michael Gerz wrote:
> although I spent a lot of effort in change tracking, there is still no
> way to show changes in pdflatex output :-(
>
> In the past, we discussed whether we should replace dvipost by the two
> packages "changes.sty" and "changebar.sty". At that time, some said that
>
Abdelrazak Younes wrote:
> Michael Gerz wrote:
>>
>> 3. We do nothing, because we don't care about pdflatex output.
>
> I tend to think that pdflatex is the most important output nowadays...
the machine is pdf(e)tex, latex is only a special format and the
LaTeX Companion was created as
Bo Peng wrote:
> Attached please find a much improved InsetListings patch. The
> implementation can now be reviewed...
>
> Changes:
>
> Better organized InsetListingsParams functions
> Autotools support
> InsetListings now derives from InsetERT
> Use LISTINS_CODE
> Code cleaning
> and more...
Bo Peng wrote:
>> > 130 parameters is sheer madness. :-)
>>
>> +1, sorry Bo...
>
> What are you sorry for? I am not going to validate all 130 parameters
> right now, and there will be the GUI designer's decision how to choose
> and present the most important parameters, and leave others may be
Jean-Marc Lasgouttes wrote:
>> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:
>
>>> Uwe, I do not understand why lang_opts is passed to babel in the
>>> second if() when lyxrc.language_global_options is true. What was
>>> your intention?
>
> Uwe> When lyxrc.language_global_options is true
Jean-Marc Lasgouttes wrote:
>>>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> there is a third variant to prevent an option clash if
> Herbert> another package already loads babel (same for other packages)
>
1 - 100 of 2868 matches
Mail list logo
