Hello Jürgen,
can you please upload my installer from
http://developer.berlios.de/projects/lyxwininstall
to ftp.lyx.org
thanks and regards
Uwe
Le 24/08/2009 16:25, rgheck a écrit :
I've thought about this before, and it's actually an important matter as
concerns HTML output, where we'd like to be able to put the right
numbers into the HTML file.
Isn't HTML/css able to autonumber things?
The problem, however, is that it is not at
all
(reviving an older discussion)
Please read below.
On 12/2/08, Paul A. Rubin wrote:
> Ernesto Jardim wrote:
>
> > Hi,
> >
> > I want to include a citation to LyX on a paper but I don't know what's the
> correct bibliographic reference for LyX. In R (r-project.org) one runs
> "citation()" and gets:
On 08/24/2009 03:54 AM, Liviu Andronic wrote:
Dear LyX developers
These days I'm working on a LyX/Sweave document and discovered how to
properly handle lables/cross-references, which are very helpful. One
eye-candy functionality that seems missing is to display in a tooltip
the exact number that
http://www.tuxradar.com/content/lyx-made-easy
Vincent
Vincent van Ravesteijn - TNW wrote:
> Would that be caused by all the eager people to get the new LyX ?
I suspect so. I noticed it began to slow down soon after the release.
Jürgen
>Public release of LyX version 1.6.4
>===
Www.LyX.org is down again.
Would that be caused by all the eager people to get the new LyX ?
Vincent
>Even if I would have preferred that you go though the
>model/view separation way,
Yes, but you already knew i wouldn't (and still got your OK ;-))
>I am glad that we at last have this separation.
It still itches..., but I think I just don't look at it anymore.
>Just in case you don't know,
Kornel Benko wrote:
Hi Abdel,
spellchecking with aspel shows big differencies between trunk and branch.
In branch is seems to work flawlessly. In trunk it seems to stop very
early, the last part of
a bigger lyx-file seems to be not checked.
If I change a word I see immediately the now underli
Kornel Benko wrote:
Hi Abdel,
hunspell does not find corect spelling for words with umlauts, while
aspell does.
(Although they both use the same dictionary here)
So e.g. the german words "über", "können" or "benötigt" are not
recognized.
I guess this has to do with utf8 encoding. I did not
v...@lyx.org wrote:
Author: vfr
Date: Sat Aug 15 00:58:57 2009
New Revision: 31042
URL: http://www.lyx.org/trac/changeset/31042
Log:
Move layout from GuiToolbar to GuiView. Now, it is possible to use the popup
also when the Toolbar has not been visible before.
Even if I would have preferred t
Joachim Osnabryg wrote:
> > If you already have the sources of the previous release, you may want to
> > apply one of the following patches instead
> > ftp://ftp.lyx.org/pub/lyx/stable/1.6.x/patch-1.6.4.gz
> > ftp://ftp.lyx.org/pub/lyx/stable/1.6.x/patch-1.6.4.bz2
>
> Is this stateme
Tommaso Cucinotta wrote:
Hello,
when clicking on a broken reference to label, the current reference is
shown as BROKEN: also in the GuiRef.cpp dialog, but when clicking on
it (i.e., confirming its value -- for example, because I'm going to
add the label just a few seconds afterward), the "BRO
>Author: tommaso
>Date: Mon Aug 24 13:41:58 2009
>New Revision: 31219
>URL: http://www.lyx.org/trac/changeset/31219
>
>Log:
>This fix suppresses the "BROKEN:" tag on references to labels,
>when the reference is within an "internal" buffer, i.e.,
>associated to an Embedded WorkArea (such as the Adva
Hello,
when clicking on a broken reference to label, the current reference is
shown as BROKEN: also in the GuiRef.cpp dialog, but when clicking on it
(i.e., confirming its value -- for example, because I'm going to add the
label just a few seconds afterward), the "BROKEN: Ref: " label is
ente
Public release of LyX version 1.6.4
===
We are pleased to announce the release of LyX 1.6.4. This is the fourth
maintenance release in the 1.6.x series. This release covers, amongst
many minor improvements, fixes to some rather severe issues, such as:
* A workaroun
Vincent van Ravesteijn - TNW wrote:
* Close All / Close View
Close all should close all visible workareas and the
buffers that were hidden in this view. Again, I wouldn't
close buffers in another view.
There is no such thing as "buffers that were hidden in this view".
Yes, that
>> > In my case they can't be accessed at all.
>>
>> I see. So I propose to either fix the issue or
>> revert the respective change and release LyX
>> 1.6.4.1. Since only the Mac seems to be concerned,
>> binary by a 1.6.4.1 binary.
>> we would just need to replace the current 1.6.4 Mac
>> Oth
>> * Close
>>
>> When you close a buffer in one view, it's everything but
>> expected thatthis buffer gets closed in the other view
>> too. I know this is 'consistent', but I'd rather stop
>> doing that.
>
> I disagree but I guess this is just a terminology problem.
> We should rename that to
> You can't do much about its size, but you could adapt the
painting.
> See the attached patch.
>
This looks perfect. Please put it in.
>>> I've put it in now although it was not my patch. I hope this is OK
>>> nevertheless in this case.
>>>
>>
>> I wa
Enrico Forestieri wrote:
No, I am not going to do that. If I was the maintainer of a doc, in
order to not scare possible contributors, I would download ldiff
from http://cs.haifa.ac.il/~dekelts/ldiff/ , then I would apply
the attached patch to it and use it as follows:
cd lib/docs
ldiff -r31213
Jürgen Spitzmüller wrote:
Vincent van Ravesteijn wrote:
So, if there is no view (that
is if no buffer is open, right ?), then no menu option that shows a
dialog would be enabled, but that would also be the case without this
change.
I'm not sure I understand your elaborations. We have
Vincent van Ravesteijn - TNW wrote:
but its maybe true that some people would like
see 'hide all' in menu...
No, I was thinking about "Close All" == "Close All Buffers in this
View"
if we call it 'close all in window', then it would ok with me.
(hide all would be consi
Vincent van Ravesteijn - TNW wrote:
You can't do much about its size, but you could adapt
the painting. See the attached patch.
This looks perfect. Please put it in.
I've put it in now although it was not my patch. I hope this
is OK nevertheless in this case.
I was s
Jürgen Spitzmüller wrote:
> > In my case they can't be accessed at all.
>
> I see. So I propose to either fix the issue or revert the respective change
> and release LyX 1.6.4.1. Since only the Mac seems to be concerned, we would
> just need to replace the current 1.6.4 Mac binary by a 1.6.4.1 bin
Dear LyX developers
These days I'm working on a LyX/Sweave document and discovered how to
properly handle lables/cross-references, which are very helpful. One
eye-candy functionality that seems missing is to display in a tooltip
the exact number that the cross-reference will generate in the .pdf
fi
Uwe Stöhr wrote:
> Hartmut pointed me today to this regression to LyX 1.6.3:
> http://www.lyx.org/trac/ticket/6175
> I think it it not that problematic to hold back LyX 1.6.4.
No, this is only a cosmetic issue.
Jürgen
27 matches
Mail list logo
