Moritz Moeller-Herrmann wrote:
Hmm, life would become easier for lyx and other projects, if lyx used
standard sizes. Also most if not all of the KDE icons are available as SVG,
so you could just rerender them for the lyx size.
Hmm if you tell us the rule for standard size? As much as I know
John == John Levon [EMAIL PROTECTED] writes:
John On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein
John wrote:
1) first patch to enable Layout-Preamble
John I don't think we want this. Preamble has been moved to the
John Document dialog. We need to make the menus frontend-specific
Jean-Marc Lasgouttes wrote:
What about the idea of disabling preamble if it is not hooked to a
signal? I can do that if someone tells me how I can test for this
condition.
What about the optitem (related to frontend) idea? Then you can disable
tooltips and child processes too, and I'm shure
Juergen Spitzmueller wrote:
tooltip specific issues
frontend specific issues...
Jürgen.
Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:
Juergen Jean-Marc Lasgouttes wrote:
What about the idea of disabling preamble if it is not hooked to a
signal? I can do that if someone tells me how I can test for this
condition.
Juergen What about the optitem (related to frontend)
On Monday 09 December 2002 7:20 pm, John Levon wrote:
On Mon, Dec 09, 2002 at 11:20:15AM +, Angus Leeming wrote:
How about this as a hacked-together first-stab at an announcement. It
sort of
here's the state of the next LDN as it is :
http://compsoc.man.ac.uk/~moz/www-user/news/
On Tuesday 10 December 2002 8:45 am, Jean-Marc Lasgouttes wrote:
John == John Levon [EMAIL PROTECTED] writes:
John On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein
John wrote:
1) first patch to enable Layout-Preamble
John I don't think we want this. Preamble has been moved to
On Tue, 10 Dec 2002, Juergen Vigna wrote:
Moritz Moeller-Herrmann wrote:
Hmm, life would become easier for lyx and other projects, if lyx used
standard sizes. Also most if not all of the KDE icons are available as SVG,
so you could just rerender them for the lyx size.
Hmm if you tell us
On Mon Dec 9, 2002 21:04, Alfredo Braunstein wrote:
Hi,
1) first patch to enable Layout-Preamble
2) second patch: to
a) eliminate a crash on Layout-Preamble-Edit-Cancel (a NULL
point er was assigned to a string)
b) adds 'xterm -e ' when calling the editor from $EDITOR
Hope
On Tue Dec 10, 2002 10:16, Edwin Leuven wrote:
On Mon Dec 9, 2002 21:04, Alfredo Braunstein wrote:
Hi,
1) first patch to enable Layout-Preamble
2) second patch: to
a) eliminate a crash on Layout-Preamble-Edit-Cancel (a NULL
point er was assigned to a string)
b) adds
On Tue, Dec 10, 2002 at 02:17:10AM -0700, Bruce Sass wrote:
Sounds like it will need to be a ./configure thing (which sizes (or
styles) to generate, where to place them, ... ). In which case LyX
can choose whatever size and format it likes, but would need to manage
the conversion(s).
Sounds
On Tue, Dec 10, 2002 at 03:01:36AM +, John Levon wrote:
Unless somebody has major complaints I'm going to commit it ...
What happens when the user changes the font in the preferences dialog ?
If I'm not mistaken, the cache will not be cleared.
One solution (other than cleaning the cache)
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Angus Leeming [EMAIL PROTECTED] writes: | Ok, it's out.
Lars |
Lars | Are we going to keep support for xforms 0.88 and 0.89 in LyX
Lars 1.3?
Lars _I_ would like us to ditch support for 0.88 and 0.89 at once,
Lars especially 0.88.
So
Jean-Marc Lasgouttes wrote:
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Angus Leeming [EMAIL PROTECTED] writes: | Ok, it's out.
Lars |
Lars | Are we going to keep support for xforms 0.88 and 0.89 in LyX
Lars 1.3?
Lars _I_ would like us to ditch support for 0.88 and 0.89 at
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Jean-Marc, none of them are hooked to signals anymore. See
Angus xforms/Dialogs_impl.h, xforms/Dialogs2.C.
OK, I see.
Angus What we could do is have all these methods return a bool
Angus telling the core whether the request has been dealt
Jean-Marc Lasgouttes wrote:
So what was the final decision on this? I think we should get rid of
0.88 now, since it is the most problematic. Note however that this
will cause problems for people who use solaris and for cjk-lyx,
because of shortcomings ion xforms support for input methods. But
Stephan == Stephan Witt [EMAIL PROTECTED] writes:
Stephan Yesterday I tried to compile 1.0-release on my solaris
Stephan machine. I can't say it compiles out of the box, but the
Stephan problems where solveable. But I didn't try to install the
Stephan shared libs, because of the suspected
On Tuesday 10 December 2002 9:57 am, Jean-Marc Lasgouttes wrote:
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Angus Leeming [EMAIL PROTECTED] writes: | Ok, it's out.
Lars |
Lars | Are we going to keep support for xforms 0.88 and 0.89 in LyX
Lars 1.3?
Lars _I_ would like us
On Tue, Dec 10, 2002 at 11:07:10AM +0100, Juergen Vigna wrote:
So what was the final decision on this? I think we should get rid of
0.88 now, since it is the most problematic. Note however that this
will cause problems for people who use solaris and for cjk-lyx,
because of shortcomings ion
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus On Tuesday 10 December 2002 9:57 am, Jean-Marc Lasgouttes
Angus wrote:
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Angus Leeming [EMAIL PROTECTED] writes: | Ok, it's out.
Lars |
Lars | Are we going to keep support for
On Tuesday 10 December 2002 10:06 am, Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Jean-Marc, none of them are hooked to signals anymore. See
Angus xforms/Dialogs_impl.h, xforms/Dialogs2.C.
OK, I see.
Angus What we could do is have all these methods
On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
Well then, I see no alternative but to write a bunch of 1-line functions for
each frontend (below). If they default to true, then you'll have to overload
only a few in the respective frontends...
frontends/Dialogs.h
class
On Tuesday 10 December 2002 10:15 am, Jean-Marc Lasgouttes wrote:
But it does the compose key preprocessing first.
Not totally true. It passes all FL_KEYPRESS events to the XWorkArea handler.
It just so happens that during composition the passed key is null. That's
why this can be made to
On Tuesday 10 December 2002 10:21 am, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
Well then, I see no alternative but to write a bunch of 1-line functions
for each frontend (below). If they default to true, then you'll have to
overload only a few in
John Levon wrote:
It's not possible to have multiple target milestones.
Oh...
intend to make some final corrections this week, it might be useful to
restructure the bug list.
how ?
Decide what needs to be fixed before 1.3.0 is released. For example, bug
#576 (if it applies for
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus On Tuesday 10 December 2002 10:21 am, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 10:27:08AM +, Angus Leeming wrote:
Well then, I see no alternative but to write a bunch of 1-line
functions for each frontend (below). If they
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus On Tuesday 10 December 2002 10:15 am, Jean-Marc Lasgouttes
Angus wrote:
But it does the compose key preprocessing first.
Angus Not totally true. It passes all FL_KEYPRESS events to the
Angus XWorkArea handler. It just so happens that
On Tuesday 10 December 2002 10:51 am, Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus On Tuesday 10 December 2002 10:15 am, Jean-Marc Lasgouttes
Angus wrote:
But it does the compose key preprocessing first.
Angus Not totally true. It passes all
On Tuesday 10 December 2002 10:47 am, Jean-Marc Lasgouttes wrote:
Angus Excellent idea. It's a major pain that adding a new dialog
Angus causes the re-compilation of the whole LyX tree.
In this case, we should also have showDialog(string const name) and
a map name-dialog of some sort.
On Tue, Dec 10, 2002 at 11:09:35AM +, Angus Leeming wrote:
No. I reckon that for 1.3 you should go for the simple to code multiple
virtual bool haveXYZ() { return true; }
and overload the few cases in Qt where they decided that they don't want a
dialog.
Wouldn't it even for 1.3 be
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars Angus Leeming [EMAIL PROTECTED] writes: | Ok, it's out.
| Lars |
| Lars | Are we going to keep support for xforms 0.88 and 0.89 in LyX
| Lars 1.3?
|
| Lars _I_ would like us to
John Levon [EMAIL PROTECTED] writes:
| On Tue, Dec 10, 2002 at 12:41:26AM +, John Levon wrote:
|
| Well I'm out of ideas so here's a dumb patch that caches single widths.
|
| btw, a mappair, int based approach is at least twice as slower than
| the vector one below
|
| resize took
Edwin Leuven [EMAIL PROTECTED] writes:
| redundant now (preamble is in document settings dialog). I also think the
| show preamble entry should be removed from the (qt) menu.
Or just make the QDocument::preamble pop up...
--
Lgb
On Tuesday 10 December 2002 11:15 am, Lars Gullik Bjønnes wrote:
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars Angus Leeming [EMAIL PROTECTED] writes: | Ok, it's out.
| Lars |
| Lars | Are we going to keep support for xforms
On Tuesday 10 December 2002 11:10 am, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 11:09:35AM +, Angus Leeming wrote:
No. I reckon that for 1.3 you should go for the simple to code multiple
virtual bool haveXYZ() { return true; }
and overload the few cases in Qt where they decided
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Edwin Leuven [EMAIL PROTECTED] writes: | redundant now
Lars (preamble is in document settings dialog). I also think the |
Lars show preamble entry should be removed from the (qt) menu.
Lars Or just make the QDocument::preamble pop up...
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars IMHO we should let 0.88 go now, and wait a short while into the
Lars freeze period before we make final decision on 0.89. (currently
Lars I am inclined to keep 0.89 for 1.3.0)
Agreed. Is there special code for 0.89 vs 1.0?
JMarc
John Levon [EMAIL PROTECTED] writes:
What is the list used for?
| +typedef pairLyXFont, int MetricPair;
| +typedef vectorMetricPair MetricList;
| +typedef mapUchar, MetricList CharMetrics;
| +CharMetrics char_metrics;
| +
| +int singlewidth(Uchar val, LyXFont const f)
| +{
| +
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars Edwin Leuven [EMAIL PROTECTED] writes: | redundant now
| Lars (preamble is in document settings dialog). I also think the |
| Lars show preamble entry should be removed from the (qt)
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 11:15 am, Lars Gullik Bjønnes wrote:
| Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| | Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
| |
| | Lars Angus Leeming [EMAIL PROTECTED] writes: | Ok, it's out.
| | Lars
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars IMHO we should let 0.88 go now, and wait a short while into the
| Lars freeze period before we make final decision on 0.89. (currently
| Lars I am inclined to keep 0.89 for 1.3.0)
|
Steve, how do you see future development of xforms panning out? At present it
seems to be stagnating somewhat. That may seem churlish, given that you only
released 1.0final over the weekend, but it isn't meant to be. I'm merely
pointing out the reality of a release that occurred 6 months after
Andre Poenitz [EMAIL PROTECTED] writes:
| On Mon, Dec 09, 2002 at 07:15:23PM +, John Levon wrote:
This is a feature of the floatflt package.
When you have a floatingfigure, it will be put at the next paragraph.
But if there is no next paragraph, the floatingfigure is ignored.
Um, can
On Tue, Dec 10, 2002 at 01:20:15PM +0100, Lars Gullik Bjønnes wrote:
This is also one of the reasons why I was not so enthusiastic about
the InsetWrap in the first place. There are just to many special rules
that must be followed to make it work properly.
The rules should be enforced by lyx,
Jean-Marc Lasgouttes wrote:
Stephan == Stephan Witt [EMAIL PROTECTED] writes:
Stephan Yesterday I tried to compile 1.0-release on my solaris
Stephan machine. I can't say it compiles out of the box, but the
Stephan problems where solveable. But I didn't try to install the
Stephan shared libs,
Lars, the attached patch to xforms' forms.c cures these two bugs in xforms
handling of key events.
o xforms should swallow null keyevents. They occur during composition of
multi-byte chars. The problem was reported and a solution proposed here:
o xforms should pass FL_KEYRELEASE events to the
Angus Leeming [EMAIL PROTECTED] writes:
| Lars, the attached patch to xforms' forms.c cures these two bugs in xforms
| handling of key events.
| o xforms should swallow null keyevents. They occur during composition of
| multi-byte chars. The problem was reported and a solution proposed here:
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:19 pm, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| Lars, the attached patch to xforms' forms.c cures these two bugs in
| xforms handling of key events.
|
| o xforms should swallow null keyevents.
On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
| Why? Ie, I don't understand what you're attempting to do with this code.
Just do it
KeyRelease event, serial 27, synthetic NO, window 0x4a1,
Steve, how do you see future development of xforms panning out? At
present it seems to be stagnating somewhat. That may seem churlish,
given that you only released 1.0final over the weekend, but it isn't
meant to be. I'm merely pointing out the reality of a release that
occurred 6 months
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
| Why? Ie, I don't understand what you're attempting to do with this code.
Just do it
KeyRelease event,
Am Montag, 9. Dezember 2002 13:13 schrieb Lars Gullik Bjønnes:
Darren Freeman [EMAIL PROTECTED] writes:
| On Mon, 2002-12-09 at 21:01, Angus Leeming wrote:
Ok, it's out.
Are we going to keep support for xforms 0.88 and 0.89 in LyX 1.3?
|
| I would say that it needs to go, but maybe hold
On Tuesday 10 December 2002 2:51 pm, Steve Lamont wrote:
It may be that I am not the right person for this job, inasmuch as my
professional responsibilities continue to evolve and my collaborative
projects continue to proliferate.
Nah!
I am chastened.
Don't be. None of this was meant as a
On Tuesday 10 December 2002 3:01 pm, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
| Why? Ie, I don't understand what you're
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 3:01 pm, Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 2:29 pm, Lars Gullik Bjønnes wrote:
Look at the time difference between the KEYRELEASE and KEYPRESS
events.
|
Juergen Vigna wrote:
Moritz Moeller-Herrmann wrote:
Hmm, life would become easier for lyx and other projects, if lyx used
standard sizes. Also most if not all of the KDE icons are available as
SVG,
so you could just rerender them for the lyx size.
Hmm if you tell us the rule for
On Tuesday 10 December 2002 3:26 pm, Lars Gullik Bjønnes wrote:
What we do not want is cursors, auto-repeat chars that just continue
to go after the key has been released. so we use xsync for this.
The problem is to know when to run this xsync, we want to loose as few
xevents as possible.
|
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 3:26 pm, Lars Gullik Bjønnes wrote:
What we do not want is cursors, auto-repeat chars that just continue
to go after the key has been released. so we use xsync for this.
The problem is to know when to run this xsync, we want
On Tuesday 10 December 2002 4:18 pm, Lars Gullik Bjønnes wrote:
| Ok. I'm getting there. You want code like this:
Sorry for leading you on a leash like that...
As we progressed I began feeling a bit queasy...it might not be som
clever after all.
..but yes, something similar to this was
On Tuesday 10 December 2002 16:34, Angus Leeming wrote:
Ie, can you envisage ANY situations where one
might want to pass auto-repeat events to the widgets?
When Lars finally commit his insetgame that he has in one of the other trees
we develops. (?) ;-)
That would be uber cool. ::-)
Angus Leeming [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 4:18 pm, Lars Gullik Bjønnes wrote:
| Ok. I'm getting there. You want code like this:
Sorry for leading you on a leash like that...
As we progressed I began feeling a bit queasy...it might not be som
clever after all.
José Matos [EMAIL PROTECTED] writes:
| On Tuesday 10 December 2002 16:34, Angus Leeming wrote:
Ie, can you envisage ANY situations where one
might want to pass auto-repeat events to the widgets?
| When Lars finally commit his insetgame that he has in one of the
| other trees we develops.
On Tue, 10 Dec 2002, Steve Lamont wrote:
It may be that I am not the right person for this job, inasmuch as my
professional responsibilities continue to evolve and my collaborative
projects continue to proliferate.
If it is the group's consensus that someone else should assume these
I cannot see it -- I am really happy with your efforts, Steve.
Please, folks. I wasn't fishing for pats on the back (or kicks in the
tush, for that matter :-)), just thinking out loud.
spl
. LaTeX can handle the
+ // graphic file as is. This is true even if the
+ // orig_file is compressed. We have to return the
+ // orig_file_with_path, maybe it is a zipped one
+
+ // If the extension is not the default one (e.g. .epsi
+ // instead of .eps), then we do not remove it. (JMarc 20021210
Rob == Rob Lahaye [EMAIL PROTECTED] writes:
Rob Shouldn't you remove all extensions of each figure input file? I
Rob use Grace files (.agr extension), which goes as .agr files into
Rob the LaTeX export file. Of cource LaTeX doen't know what to do
Rob with Grace files and reports errors.
Rob You
Rod == Rod Pinna [EMAIL PROTECTED] writes:
Rod Given Rob's comment wrt .agr files, maybe a better way would be
Rod to only leave the extension if it is one of the eps formats (epsi
Rod etc) that the latex can deal with?
As I wrote a in my previous message, Rob's problem is related to
special
On Tue, Dec 10, 2002 at 11:57:08AM +0200, Dekel Tsur wrote:
What happens when the user changes the font in the preferences dialog ?
If I'm not mistaken, the cache will not be cleared.
Yes it will. Like I mentioned ...
One solution (other than cleaning the cache) is to store
On Tue, Dec 10, 2002 at 11:48:59AM +0100, Lars Gullik Bjønnes wrote:
I have a feeling that the cache is a bit more complex than it needs to
be, but I cannot quite put my finger on it...
I'm going to rework things a bit I think
How often is metrics for whole strings wanted?
Not often. the
On Tue, Dec 10, 2002 at 11:28:56AM +, Angus Leeming wrote:
Wouldn't it even for 1.3 be simpler to have the 'name' argument and an 'if'
cascade in the Qt implementation?
Whatever. It should needs implementing SOMEHOW. Two minutes to code. 10
minutes to compile on a fast machine (*). 1
On Tue, Dec 10, 2002 at 12:23:24PM +0100, Jean-Marc Lasgouttes wrote:
Another solution: add a method GUIruntime::isImplemented(kb_action)
that would return false for not implemented actions. Then these would
be ignored by MenuBackend. The advantage is simplicity, and
possibility to ignore
On Tue, Dec 10, 2002 at 11:24:00AM +0100, Michael Schmitt wrote:
Decide what needs to be fixed before 1.3.0 is released. For example, bug
We've done that, and already punted some very important bugs :(
For example, scrolling past a large tabular will be broken in 1.3.0
#576 (if it applies
On Tue, Dec 10, 2002 at 06:34:58PM +0100, Jean-Marc Lasgouttes wrote:
What I do not see is what is the practical use of removing the
extension on output... We should output without extension when there
is no extension in the graphics file name (and use the same rules to
search as
There is a long existing problem with lyx/url and was discussed in
lyx-users several times. When exporting lyx url to html format, the
links turn to normal text. Temporary solution is to use ERT and
\htmladdnormallink. Will 1.3 fix this problem? I searched bugzilla with
keyword url but I could
On Tue, Dec 10, 2002 at 12:31:58PM -0600, Bo Peng wrote:
There is a long existing problem with lyx/url and was discussed in
lyx-users several times. When exporting lyx url to html format, the
links turn to normal text. Temporary solution is to use ERT and
\htmladdnormallink. Will 1.3 fix
On Tue, Dec 10, 2002 at 06:10:46PM +, John Levon wrote:
One solution (other than cleaning the cache) is to store
(qfont_loader::font_info const *, int) pairs instead of
(LyXFont, int) pairs.
I'm going to do something similar indeed.
Another idea is to just cache the width for the
Here it is. OK ?
This is a little faster; sub-second times on userguide are now common,
so it's pretty much on a par with xforms (glacial) speed
regards
john
--
Saying that taste is just personal preference is a good way to prevent
disputes. The trouble is, it's not true.
- Paul Graham
Haloo,
I would like to insert and process text in bulgarian language in lyx. I used
to have phonetic bulgarian keyboard in other applications but in lyx I
suspect it is impossible.
1. Only bg-bds-cp1251.kmap is available in /usr/share/lyx/kbd.
2. When I tried a kmap file form another package
On Tue, Dec 10, 2002 at 08:36:45PM +0200, Dekel Tsur wrote:
Another idea is to just cache the width for the default text font.
This would reduce the speedup we get...
regards
john
--
Saying that taste is just personal preference is a good way to prevent
disputes. The trouble is, it's not
John Levon [EMAIL PROTECTED] writes:
| +#include map
| +
| +#include encoding.h
| #include lyxfont.h
|
| #include qfont.h
include order
| @@ -44,6 +47,10 @@
| QFontMetrics const metrics(LyXFont const f) {
| return getfontinfo(f)-metrics;
| }
| +
| + ///
On Tue, Dec 10, 2002 at 08:48:02PM +0100, Lars Gullik Bjønnes wrote:
| +#include map
| +
| +#include encoding.h
| #include lyxfont.h
|
| #include qfont.h
include order
I have never been able to work out what you wanted with these, and I
never understood your summary
| + ///
There is a long existing problem with lyx/url and was discussed in_
lyx-users several times. When exporting lyx url to html format, the_
links turn to normal text. Temporary solution is to use ERT and_
\htmladdnormallink. Will 1.3 fix this problem?_
There have been no changes here._
It
On Tue, Dec 10, 2002 at 02:34:50PM -0600, Bo Peng wrote:
There have been no changes here._
It seems to me that the URL boxes are meaningless if they can not be_
exported to HTML/links correctly. (I know, it helps latex use the_
correct font for links :-)
Since I use this feature a lot,
On Tue, Dec 10, 2002 at 08:38:30PM +, John Levon wrote:
Since I use this feature a lot, I would hope it can be done in_
1.3. Currently, I use a csh script to translate the URL inset of a lyx_
file to ERT/htmladdnormallink and then export it to latex.
Since you seem to know what is
On Tue, Dec 10, 2002 at 08:00:03PM +, John Levon wrote:
short makes me go: Hu! Why? Anything special going on here?
why not save some memory ?
The saving is negligible (compared to the memory already used by the map, and
the memory used to hold the font).
And why cannot these be
Since you seem to know what is needed, how about making a patch ? What
are the difficulties ... if it's really so trivial to do.
Well, good idea. I do know what to change as long as I know where to
change it. I am TOATALLY new to lyx code so can anyone tell me which
part of the lyx-devel deal
On Tue, Dec 10, 2002 at 10:59:03PM +0200, Dekel Tsur wrote:
short makes me go: Hu! Why? Anything special going on here?
why not save some memory ?
The saving is negligible (compared to the memory already used by the map, and
the memory used to hold the font).
We have to hold the font
\htmladdnormallink is latex2html specific.
The correct way is probably to use the \href command from hyperref
(though some latex-html converters might not support it).
Another problem is that some users might not want to use hyperref when
creating the DVI/PS/PDF file (as it may interfere with
On Tue, Dec 10, 2002 at 06:34:58PM +0100, Jean-Marc Lasgouttes wrote:
What I do not see is what is the practical use of removing the
extension on output... We should output without extension when there
is no extension in the graphics file name (and use the same rules to
search as
None of the contents of My Address layout appear in the dvi output
john
--
Saying that taste is just personal preference is a good way to prevent
disputes. The trouble is, it's not true.
- Paul Graham
Alfredo Braunstein wrote:
Small bugs on References Dialog. When editing a reference, the type was
not correctly updated. Patch attached.
Please look at this patch, it's very small. Thanks, Alfredo
On Tue, 10 Dec 2002, Andre Poenitz wrote:
On Tue, Dec 10, 2002 at 02:17:10AM -0700, Bruce Sass wrote:
Sounds like it will need to be a ./configure thing (which sizes (or
styles) to generate, where to place them, ... ). In which case LyX
can choose whatever size and format it likes, but
On Tue, Dec 10, 2002 at 10:37:33PM +0100, Alfredo Braunstein wrote:
Please look at this patch, it's very small. Thanks, Alfredo
I already committed it
john
--
Saying that taste is just personal preference is a good way to prevent
disputes. The trouble is, it's not true.
- Paul Graham
Edwin Leuven wrote:
And after sending this I contniued to read the thread: sorry (guess I am
still asleep).
Ed.
Don't worry... For sure you were not the only one... Thanks¸ Alfredo
John Levon wrote:
On Mon, Dec 09, 2002 at 10:04:31PM +0100, Alfredo Braunstein wrote:
1) first patch to enable Layout-Preamble
I don't think we want this. Preamble has been moved to the Document
dialog. We need to make the menus frontend-specific to remove the menu
Ah, I knew I was
Hi John,
For example, scrolling past a large tabular will be broken in 1.3.0
Argh! I have a lot of large tabulars!
#576 (if it applies for 1.3.0) is critical
critical ? hardly !
Depends on the point of view. If I cannot trust LyX that it really
replaces all occurrences of a particular
The following message is a courtesy copy of an article
that has been posted to de.comp.text.tex as well.
Herbert Voss [EMAIL PROTECTED] writes:
Ralf Zosel schrieb:
wenn man diese Level kennt, ist es eine Kleinigkeit,
sie auf ein LyX Layout zu übertragen.
Wenn das so einfach ist: Hast Du
On Tue, Dec 10, 2002 at 11:24:04PM +0100, Michael Schmitt wrote:
For example, scrolling past a large tabular will be broken in 1.3.0
Argh! I have a lot of large tabulars!
I'm afraid so. The persons unknown who broke this have yet to come
forward :(
#576 (if it applies for 1.3.0) is
[EMAIL PROTECTED] (David Kastrup) writes:
| The following message is a courtesy copy of an article
| that has been posted to de.comp.text.tex as well.
Can some one give a quick translation so that I know what to mean
about this?
--
Lgb
John Levon [EMAIL PROTECTED] writes:
| None of the contents of My Address layout appear in the dvi output
Is this a bug report? It is somewhat lacking...
--
Lgb
1 - 100 of 216 matches
Mail list logo
