Tomasz == Tomasz Luczak [EMAIL PROTECTED] writes:
Tomasz Jean-Marc Lasgouttes wrote:
Tomasz == Tomasz Luczak [EMAIL PROTECTED] writes:
Tomasz Hi I send updated translation pl.po into polish for 1.4.0cvs
Tomasz version
Thanks a lot Tomasz. It is in now.
Tomasz New update of polish
Hello,
Angus Leeming wrote:
In light of all this, I'm asking whether I can have your permission to
add your names to http://www.lyx.org/blanket-permission.txt :
The following people hereby grant permission to licence their
contributions to LyX under the Gnu General Public Licence, version 2
or
JMarc It should look like C:\Desktop\UserGuide.lyx, I believe.
Really? Why? Who Says?
JMarc Probably the ~/ part of MakeDisplayPath should only
JMarc be done on Unix.On windows, I guess there is some API
JMarc to turn get those shorter file names.
Angus Mmmm, but this is not too important
On Thu, Mar 31, 2005 at 09:52:57AM +0200, Jean-Marc Lasgouttes wrote:
Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg Martin Vermeer wrote:
Looks great, except that Jean-Marc is right: you can still in three
places replace
istringstream is(cmd.argument); string s; is s;
by
John Levon wrote:
On Wed, Mar 30, 2005 at 09:01:02PM +0200, Alfredo Braunstein wrote:
On your document indeed the scrollbar resizes a lot (the reason is
obvious, we have paragraphs of very different vertical size).
OK, we need to go to Mac-style scrollbars where the widget is of a
fixed
Georg Baum wrote:
Am Mittwoch, 30. Mrz 2005 19:51 schrieb John Levon:
On Wed, Mar 30, 2005 at 04:28:11PM +0200, Alfredo Braunstein wrote:
Lots of testing needed...
Dragging the scrollbar on the Qt frontend is very broken (I tried with
small document). It constantly resizes itself,
Alfredo Braunstein wrote:
Dragging the scrollbar on the Qt frontend is very broken (I tried with
small document). It constantly resizes itself, jumps about. etc
I see this, too (also qt).
The fact that it resizes itself is normal (altough the resizing should be
smooth). It shouldn't
I believe that a fixed sized scroll bar is a significant regression in
terms of usability.
Also, I think that a very unreliable scroll bar is a problem. The scroll
bar can change a few pixels, but if it jumps much more than that, it is
confusing.
I did not test the new scrollbar, but if you
The tradition about displaying nice paths on windows does not exist: Either
you do the complicated:
C:\Documents and settings\alstrup\My documents\My file.lyx
C:\Documents and settings\alstrup\Desktop\My second file.lyx
C:\My third file.lyx
or you ignore the path and just do (like all the
On Thu, Mar 31, 2005 at 11:12:51AM +0200, Alfredo Braunstein wrote:
This is easy. OTOH, I'm a bit confused by your 'unusable'. Setting the
widget to fixed size would make no difference in useability AFAICS.
Having the widget constantly change size on you is extremely
disconcerting.
qt
On Thu, Mar 31, 2005 at 01:08:48PM +0200, Asger Alstrup wrote:
I believe that a fixed sized scroll bar is a significant regression in
terms of usability.
Asger, we lost the ability to have a properly working scrollbar after
the core rewrite. I'm sure there are reasons it's difficult to do
Asger Alstrup wrote:
The tradition about displaying nice paths on windows does not exist:
So you think that having such functionality is a bad thing for LyX/Win?
The only real problem here seems to be the ~ abbreviation.
Either you do the complicated:
C:\Documents and
Asger Alstrup wrote:
I believe that a fixed sized scroll bar is a significant regression in
terms of usability.
I'm not sure about that. Specially since there's no difference in the
scrollbar size in a mid-sized document vs a big document like UG, because
most toolkits have a minimum size for
John Levon wrote:
To improve further, consider the insets in the paragraph by having a
default size for each type and take that into account. Now, we are linear
There's no such thing as a linear size for figures, so this is
guaranteed to go wrong in the worst possible cases (very large figures).
Angus Leeming wrote:
Asger Alstrup wrote:
The tradition about displaying nice paths on windows does not exist:
So you think that having such functionality is a bad thing for LyX/Win?
The only real problem here seems to be the ~ abbreviation.
Well, it is not necessarily a bad thing, but it is not
On Thu, Mar 31, 2005 at 01:54:11PM +0200, Asger Alstrup wrote:
I believe it is monotoneously better to estimate all figures at say 200x200
pixels, rather than at 0x0 pixels like it does now.
Well, perhaps, but I doubt it significantly helps.
My point is that this estimation routine can be
Alfredo Braunstein wrote:
The fact that it resizes itself is normal (altough the resizing should be
smooth). It shouldn't jump. I don't understand if both of you are seeing
the same behaviour as I do and find it ugly or if you are seeing something
different.
I am actually not sure if it is
Asger == Asger Alstrup [EMAIL PROTECTED] writes:
Asger The tradition about displaying nice paths on windows does not
Asger exist: Either you do the complicated:
AsgerC:\Documents and settings\alstrup\My documents\My file.lyx
Asger C:\Documents and settings\alstrup\Desktop\My second file.lyx
John Levon wrote:
On Thu, Mar 31, 2005 at 01:54:11PM +0200, Asger Alstrup wrote:
I believe it is monotoneously better to estimate all figures at say
200x200 pixels, rather than at 0x0 pixels like it does now.
Well, perhaps, but I doubt it significantly helps.
My point is that this
Alfredo Braunstein wrote:
I'm not sure about that. Specially since there's no difference in the
scrollbar size in a mid-sized document vs a big document like UG, because
most toolkits have a minimum size for the widget.
Small documents are important too.
It shouldn't jump at all (otherwise is just
Hi Georg,
Georg Baum wrote:
Alfredo Braunstein wrote:
The fact that it resizes itself is normal (altough the resizing should be
smooth). It shouldn't jump. I don't understand if both of you are seeing
the same behaviour as I do and find it ugly or if you are seeing
something different.
Asger Alstrup wrote:
Alfredo Braunstein wrote:
I'm not sure about that. Specially since there's no difference in the
scrollbar size in a mid-sized document vs a big document like UG, because
most toolkits have a minimum size for the widget.
Small documents are important too.
Sure, I am
Please can you help me?
My system is Windows 2000 and when I try to run Lyx 1.3.3, for the first
time, I receive the message:
Lyx wasn´t able to find any layout description!
Check the contents of the file textclass.lst
Sorry has to exit
Thanks, Carlos H. Klein
Alfredo Braunstein wrote:
I believe it is monotoneously better to estimate all figures at say
200x200 pixels, rather than at 0x0 pixels like it does now.
Well, perhaps, but I doubt it significantly helps.
My point is that this estimation routine can be continuously refined
until it
Alfredo Braunstein wrote:
Small documents are important too.
Sure, I am only noting that it is a feature that only *exists* in small
documents. Thus, it cannot be so fundamentally important.
It serves as important feedback on the size of the document.
Well, we could just keep (maybe outdated)
Alfredo Braunstein wrote:
Georg Baum wrote:
You mean pagedown on the keyboard, or clicking on the scrollbar background
(i.e. scrollbar pgdown)
I mean the key on the keyboard.
Georg
Angus Leeming wrote:
I haven't been following this thread very closely, but isn't the problem
one of calculating the length of the document when it is first loaded?
Thereafter, the scrollbar would change size only when the document was
modified. (This could happen just by scrolling through a
Asger Alstrup wrote:
Well, we could just keep (maybe outdated) paragraphs sizes, and just
update on-screen ones when drawing. Then the scrollbar computation would
be only a loop over all outer paragraphs.
Only looking at outer paragraphs ignores the two most important ones.
I think you
Martin == Martin Vermeer [EMAIL PROTECTED] writes:
Martin Make a small text file in which you embed the attached XFig
Martin figure as an external inset. Then insert an erroneous ERT,
Martin (e.g. \crash) both in the paragraph before and the one after
Martin it; run LaTeX and see if the error
Georg Baum [EMAIL PROTECTED] writes:
Alfredo Braunstein wrote:
...
Could you describe some behaviour you find weird in a few steps? Thanks.
- Create a document with some paragraphs (~20, only text, one line each)
- resize the main window to the smallest possible height
- drag the
Georg Baum wrote:
Alfredo Braunstein wrote:
Georg Baum wrote:
You mean pagedown on the keyboard, or clicking on the scrollbar
background (i.e. scrollbar pgdown)
I mean the key on the keyboard.
Ah ok. But I think this is unrelated.
Regards, Alfredo
On 27.03.05, Uwe Stöhr wrote:
1. The last months I teached LyX to some colleagues and they all
complained that there is no button in the toolbar for view/update dvi.
Therefore I designed a new toolbar with new buttons. It looks like in
the attached file toolbar.png. I added two buttons
On Thu, Mar 31, 2005 at 02:05:38PM +0200, Alfredo Braunstein wrote:
Fair enough. I suspect the real answer is full rebreaking...
Always optimitic, huh?
Hmm, I wonder if we could rebreak in full below a certain document size.
This would fix the most apparent breakages whilst still giving us
I getStatus we set the error messages using N_(), so that we can
transmit the English version to the lyxserver. However, we do not do
the translation before displaying in the minibuffer...
The following pair of patches fixes that.
OK?
JMarc
Index: src/ChangeLog
G == G Milde [EMAIL PROTECTED] writes:
G It would be nice, if we had a lyx-function view-or-update (with
G arguments dvi, ps, or pdf) that just updates if there is an open
G viewer for the current buffers document.
G This could save us one keybinding and enable the view/update dvi
G button
Jean-Marc Lasgouttes wrote:
PS: actually I had some problems with your .fig file:
1/ I had to add \usepackage{color} in the preamble. Is this
expected?
It's pretty common, although it is possible to create XFig figures that
don't require color.
--
Angus
John Levon wrote:
Hmm, I wonder if we could rebreak in full below a certain document size.
This would fix the most apparent breakages whilst still giving us the
load time boost we need for big docs (where we use the approximation).
An idea?
Interesting...
Alfredo
Alfredo Braunstein wrote:
I think you didn't understand what I suggested.
I suggested to do a fullrebreak on start (foreground or background) and then
keep outer paragraphs sizes. Only update sizes when drawing paragraphs
on-screen, and live with outdated sizes for out-of-screen outer
On Thu, 2005-03-31 at 15:56, Jean-Marc Lasgouttes wrote:
Martin == Martin Vermeer [EMAIL PROTECTED] writes:
Martin Make a small text file in which you embed the attached XFig
Martin figure as an external inset. Then insert an erroneous ERT,
Martin (e.g. \crash) both in the paragraph before
On Wed, 2005-03-30 at 15:46, Jean-Marc Lasgouttes wrote:
Martin == Martin Vermeer [EMAIL PROTECTED] writes:
Martin Patch attached. Error positioning works now perfectly even at
Martin the end of my 300+ page production test document, containing a
Martin mix of traditional and external
Andreas Vox wrote:
Georg Baum [EMAIL PROTECTED] writes:
- Create a document with some paragraphs (~20, only text, one line each)
- resize the main window to the smallest possible height
- drag the scrollbar from top to bottom. It will not follow the cursor
immediately, and if you don't
Georg Baum wrote:
The attached patch adds a dummy comment to prevent the deletion of the
empty paragraph. I don't like this, but neither the current solution nor
the previous one handle \appendix commands as written by LyX correctly.
Unfortunately I have no idea how to do this better at the
Martin Vermeer wrote:
On Thu, Mar 31, 2005 at 09:52:57AM +0200, Jean-Marc Lasgouttes wrote:
Georg == Georg Baum
[EMAIL PROTECTED]
writes:
Georg I thought the reason for using the istringstream was to get rid
Georg of whitespace or other stuff that might be in cmd.argument
Georg after
I think that this
http://www.devel.lyx.org/~leeming/www-user/archaeology/lyx_timeline.php
is just about ready to go. However, we're missing archives for
1.1.4 fix1
1.1.4 fix2
1.1.4 fix3
1.1.5.5
and patches to enable earlier sources to be compiled against XForms 1.0.
--
Angus
In 1.3.5 I can do the following to get a 3-digit number with the middle
digit underlined in math mode (eg, 1_2_3)
1. Insert-Math-Inline Formula
2. Type a number
3. Insert-TeX
4. Type underline (without the quotes)
5. Type a number
6. Press right-arrow
7. Type a number
With the current 1.4 CVS
On Thu, Mar 31, 2005 at 02:32:23PM +0100, Angus Leeming wrote:
Jean-Marc Lasgouttes wrote:
PS: actually I had some problems with your .fig file:
1/ I had to add \usepackage{color} in the preamble. Is this
expected?
It's pretty common, although it is possible to create XFig figures
> "Tomasz" == Tomasz Luczak <[EMAIL PROTECTED]> writes:
Tomasz> Jean-Marc Lasgouttes wrote:
>>> "Tomasz" == Tomasz Luczak <[EMAIL PROTECTED]> writes:
Tomasz> Hi I send updated translation pl.po into polish for 1.4.0cvs
Tomasz> version
>> Thanks a lot Tomasz. It is in now.
>>
Tomasz> New
Hello,
Angus Leeming wrote:
In light of all this, I'm asking whether I can have your permission to
add your names to http://www.lyx.org/blanket-permission.txt :
"The following people hereby grant permission to licence their
contributions to LyX under the Gnu General Public Licence, version 2
JMarc>>> It should look like C:\Desktop\UserGuide.lyx, I believe.
Really? Why? Who Says?
JMarc>>> Probably the ~/ part of MakeDisplayPath should only
JMarc>>> be done on Unix.On windows, I guess there is some API
JMarc>>> to turn get those shorter file names.
Angus>> Mmmm, but this is not too
On Thu, Mar 31, 2005 at 09:52:57AM +0200, Jean-Marc Lasgouttes wrote:
> > "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
>
> Georg> Martin Vermeer wrote:
> >> Looks great, except that Jean-Marc is right: you can still in three
> >> places replace
> >>
> >> istringstream is(cmd.argument);
John Levon wrote:
> On Wed, Mar 30, 2005 at 09:01:02PM +0200, Alfredo Braunstein wrote:
>
>> On your document indeed the scrollbar resizes a lot (the reason is
>> obvious, we have paragraphs of very different vertical size).
>
> OK, we need to go to Mac-style scrollbars where the widget is of
Georg Baum wrote:
> Am Mittwoch, 30. MÃrz 2005 19:51 schrieb John Levon:
>> On Wed, Mar 30, 2005 at 04:28:11PM +0200, Alfredo Braunstein wrote:
>>
>> > Lots of testing needed...
>>
>> Dragging the scrollbar on the Qt frontend is very broken (I tried with
>> small document). It constantly
Alfredo Braunstein wrote:
>>> Dragging the scrollbar on the Qt frontend is very broken (I tried with
>>> small document). It constantly resizes itself, jumps about. etc
>>
>> I see this, too (also qt).
>
> The fact that it resizes itself is normal (altough the resizing should be
> smooth). It
I believe that a fixed sized scroll bar is a significant regression in
terms of usability.
Also, I think that a very unreliable scroll bar is a problem. The scroll
bar can change a few pixels, but if it jumps much more than that, it is
confusing.
I did not test the new scrollbar, but if you
The tradition about displaying nice paths on windows does not exist: Either
you do the complicated:
C:\Documents and settings\alstrup\My documents\My file.lyx
C:\Documents and settings\alstrup\Desktop\My second file.lyx
C:\My third file.lyx
or you ignore the path and just do (like all the
On Thu, Mar 31, 2005 at 11:12:51AM +0200, Alfredo Braunstein wrote:
> This is easy. OTOH, I'm a bit confused by your 'unusable'. Setting the
> widget to fixed size would make no difference in useability AFAICS.
Having the widget constantly change size on you is extremely
disconcerting.
> qt
On Thu, Mar 31, 2005 at 01:08:48PM +0200, Asger Alstrup wrote:
> I believe that a fixed sized scroll bar is a significant regression in
> terms of usability.
Asger, we lost the ability to have a properly working scrollbar after
the core rewrite. I'm sure there are reasons it's difficult to do
Asger Alstrup wrote:
> The tradition about displaying nice paths on windows does not exist:
So you think that having such functionality is a bad thing for LyX/Win?
The only real problem here seems to be the ~ abbreviation.
> Either you do the complicated:
>
>C:\Documents and
Asger Alstrup wrote:
> I believe that a fixed sized scroll bar is a significant regression in
> terms of usability.
I'm not sure about that. Specially since there's no difference in the
scrollbar size in a mid-sized document vs a big document like UG, because
most toolkits have a minimum size
John Levon wrote:
To improve further, consider the insets in the paragraph by having a
default size for each type and take that into account. Now, we are linear
There's no such thing as a linear size for figures, so this is
guaranteed to go wrong in the worst possible cases (very large figures).
Angus Leeming wrote:
Asger Alstrup wrote:
The tradition about displaying nice paths on windows does not exist:
So you think that having such functionality is a bad thing for LyX/Win?
The only real problem here seems to be the ~ abbreviation.
Well, it is not necessarily a bad thing, but it is not
On Thu, Mar 31, 2005 at 01:54:11PM +0200, Asger Alstrup wrote:
> I believe it is monotoneously better to estimate all figures at say 200x200
> pixels, rather than at 0x0 pixels like it does now.
Well, perhaps, but I doubt it significantly helps.
> My point is that this estimation routine can
Alfredo Braunstein wrote:
> The fact that it resizes itself is normal (altough the resizing should be
> smooth). It shouldn't jump. I don't understand if both of you are seeing
> the same behaviour as I do and find it ugly or if you are seeing something
> different.
I am actually not sure if it
> "Asger" == Asger Alstrup <[EMAIL PROTECTED]> writes:
Asger> The tradition about displaying nice paths on windows does not
Asger> exist: Either you do the complicated:
Asger>C:\Documents and settings\alstrup\My documents\My file.lyx
Asger> C:\Documents and settings\alstrup\Desktop\My
John Levon wrote:
> On Thu, Mar 31, 2005 at 01:54:11PM +0200, Asger Alstrup wrote:
>
>> I believe it is monotoneously better to estimate all figures at say
>> 200x200 pixels, rather than at 0x0 pixels like it does now.
>
> Well, perhaps, but I doubt it significantly helps.
>
>> My point is
Alfredo Braunstein wrote:
I'm not sure about that. Specially since there's no difference in the
scrollbar size in a mid-sized document vs a big document like UG, because
most toolkits have a minimum size for the widget.
Small documents are important too.
It shouldn't jump at all (otherwise is just
Hi Georg,
Georg Baum wrote:
> Alfredo Braunstein wrote:
>
>> The fact that it resizes itself is normal (altough the resizing should be
>> smooth). It shouldn't jump. I don't understand if both of you are seeing
>> the same behaviour as I do and find it ugly or if you are seeing
>> something
Asger Alstrup wrote:
> Alfredo Braunstein wrote:
>> I'm not sure about that. Specially since there's no difference in the
>> scrollbar size in a mid-sized document vs a big document like UG, because
>> most toolkits have a minimum size for the widget.
>
> Small documents are important too.
Please can you help me?
My system is Windows 2000 and when I try to run Lyx 1.3.3, for the first
time, I receive the message:
Lyx wasn´t able to find any layout description!
Check the contents of the file "textclass.lst"
Sorry has to exit
Thanks, Carlos H. Klein
Alfredo Braunstein wrote:
>>> I believe it is monotoneously better to estimate all figures at say
>>> 200x200 pixels, rather than at 0x0 pixels like it does now.
>>
>> Well, perhaps, but I doubt it significantly helps.
>>
>>> My point is that this estimation routine can be continuously refined
Alfredo Braunstein wrote:
Small documents are important too.
Sure, I am only noting that it is a feature that only *exists* in small
documents. Thus, it cannot be so fundamentally important.
It serves as important feedback on the size of the document.
Well, we could just keep (maybe outdated)
Alfredo Braunstein wrote:
> Georg Baum wrote:
>
> You mean pagedown on the keyboard, or clicking on the scrollbar background
> (i.e. scrollbar pgdown)
I mean the key on the keyboard.
Georg
Angus Leeming wrote:
> I haven't been following this thread very closely, but isn't the problem
> one of calculating the length of the document when it is first loaded?
> Thereafter, the scrollbar would change size only when the document was
> modified. (This could happen just by scrolling
Asger Alstrup wrote:
>> Well, we could just keep (maybe outdated) paragraphs sizes, and just
>> update on-screen ones when drawing. Then the scrollbar computation would
>> be only a loop over all outer paragraphs.
>
> Only looking at outer paragraphs ignores the two most important ones.
I think
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Make a small text file in which you embed the attached XFig
Martin> figure as an external inset. Then insert an erroneous ERT,
Martin> (e.g. \crash) both in the paragraph before and the one after
Martin> it; run LaTeX and see if
Georg Baum <[EMAIL PROTECTED]> writes:
>
> Alfredo Braunstein wrote:
...
> > Could you describe some behaviour you find weird in a few steps? Thanks.
>
> - Create a document with some paragraphs (~20, only text, one line each)
> - resize the main window to the smallest possible height
> - drag
Georg Baum wrote:
> Alfredo Braunstein wrote:
>
>> Georg Baum wrote:
>>
>> You mean pagedown on the keyboard, or clicking on the scrollbar
>> background (i.e. scrollbar pgdown)
>
> I mean the key on the keyboard.
Ah ok. But I think this is unrelated.
Regards, Alfredo
On 27.03.05, Uwe Stöhr wrote:
> 1. The last months I teached LyX to some colleagues and they all
> complained that there is no button in the toolbar for "view/update dvi".
> Therefore I designed a new toolbar with new buttons. It looks like in
> the attached file toolbar.png. I added two
On Thu, Mar 31, 2005 at 02:05:38PM +0200, Alfredo Braunstein wrote:
> > Fair enough. I suspect the real answer is full rebreaking...
>
> Always optimitic, huh?
Hmm, I wonder if we could rebreak in full below a certain document size.
This would fix the most apparent breakages whilst still giving
I getStatus we set the error messages using N_(), so that we can
transmit the English version to the lyxserver. However, we do not do
the translation before displaying in the minibuffer...
The following pair of patches fixes that.
OK?
JMarc
Index: src/ChangeLog
> "G" == G Milde <[EMAIL PROTECTED]> writes:
G> It would be nice, if we had a lyx-function "view-or-update" (with
G> arguments dvi, ps, or pdf) that just updates if there is an open
G> viewer for the current buffers document.
G> This could save us one keybinding and enable the "view/update
Jean-Marc Lasgouttes wrote:
> PS: actually I had some problems with your .fig file:
> 1/ I had to add \usepackage{color} in the preamble. Is this
> expected?
It's pretty common, although it is possible to create XFig figures that
don't require color.
--
Angus
John Levon wrote:
> Hmm, I wonder if we could rebreak in full below a certain document size.
> This would fix the most apparent breakages whilst still giving us the
> load time boost we need for big docs (where we use the approximation).
> An idea?
Interesting...
Alfredo
Alfredo Braunstein wrote:
I think you didn't understand what I suggested.
I suggested to do a fullrebreak on start (foreground or background) and then
keep outer paragraphs sizes. Only update sizes when drawing paragraphs
on-screen, and live with outdated sizes for out-of-screen outer
On Thu, 2005-03-31 at 15:56, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> Make a small text file in which you embed the attached XFig
> Martin> figure as an external inset. Then insert an erroneous ERT,
> Martin> (e.g. \crash) both in the
On Wed, 2005-03-30 at 15:46, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> Patch attached. Error positioning works now perfectly even at
> Martin> the end of my 300+ page production test document, containing a
> Martin> mix of traditional
Andreas Vox wrote:
> Georg Baum <[EMAIL PROTECTED]> writes:
>
>> - Create a document with some paragraphs (~20, only text, one line each)
>> - resize the main window to the smallest possible height
>> - drag the scrollbar from top to bottom. It will not follow the cursor
>> immediately, and if
Georg Baum wrote:
> The attached patch adds a dummy comment to prevent the deletion of the
> empty paragraph. I don't like this, but neither the current solution nor
> the previous one handle \appendix commands as written by LyX correctly.
> Unfortunately I have no idea how to do this better at
Martin Vermeer wrote:
> On Thu, Mar 31, 2005 at 09:52:57AM +0200, Jean-Marc Lasgouttes wrote:
>> > "Georg" == Georg Baum
>> > <[EMAIL PROTECTED]>
>> > writes:
>>
>> Georg> I thought the reason for using the istringstream was to get rid
>> Georg> of whitespace or other stuff that
I think that this
http://www.devel.lyx.org/~leeming/www-user/archaeology/lyx_timeline.php
is just about ready to go. However, we're missing archives for
1.1.4 fix1
1.1.4 fix2
1.1.4 fix3
1.1.5.5
and patches to enable earlier sources to be compiled against XForms 1.0.
--
Angus
In 1.3.5 I can do the following to get a 3-digit number with the middle
digit underlined in math mode (eg, 1_2_3)
1. Insert->Math->Inline Formula
2. Type a number
3. Insert->TeX
4. Type "underline" (without the quotes)
5. Type a number
6. Press right-arrow
7. Type a number
With the current 1.4
On Thu, Mar 31, 2005 at 02:32:23PM +0100, Angus Leeming wrote:
> Jean-Marc Lasgouttes wrote:
> > PS: actually I had some problems with your .fig file:
> > 1/ I had to add \usepackage{color} in the preamble. Is this
> > expected?
>
> It's pretty common, although it is possible to create XFig
92 matches
Mail list logo
