Re: Traditional look website
On Fri, 20 Jul 2001, Allan Rae wrote: If you want to see something with too much graphics take a peek at: http://www.elec.uq.edu.au/~rae/test.html ... This was just an experiment to see what could be done. It isn't necessarily a suggested scheme for use on www.lyx.org. I rather like it :-) Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: crash importing latex
238 if (!init_done) {
(gdb) bt
#0 {anonymous}::yylex () at math_parser.C:238
#1 0x814ea41 in mathed_parse (array=@0xbfbfe8d8, par=@0x836c21c, flags=0)
at math_parser.C:981
^^^
There are only 853 lines in current math_parser.C so debugging this one is
difficult... If you could spare the time you could try to reproduce the
crash or simply sen me the LaTeX file.
There have been major changes in this area during the last few weeks (with
exception of the current week), so this bug might have been fixed or moved
to an other place...
Andre'
--
André Pönitz . [EMAIL PROTECTED]
Re: Traditional look website
Mike Ressler wrote: On Fri, 20 Jul 2001, Allan Rae wrote: If you want to see something with too much graphics take a peek at: http://www.elec.uq.edu.au/~rae/test.html ... This was just an experiment to see what could be done. It isn't necessarily a suggested scheme for use on www.lyx.org. I rather like it :-) I checked it with Opera. Very good looking layout! When I use the scrollbar to have a look at the bottom of the text frame, also the menu is scrolling away. Can you make the scrollbar such that it only scrolls the text frame, so that the menu on the left remains in place? Regards, Rob.
Re: Traditional look website
If you want to see something with too much graphics take a peek at: http://www.elec.uq.edu.au/~rae/test.html Why this different background for the border? Whey yellow on black? [I don't ask Why blue?] This was just an experiment to see what could be done. It isn't necessarily a suggested scheme for use on www.lyx.org. What a relief... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) I still think that this was a sly way to get help, but anyway I've played further. #:O) Well you won't believe it but I know since a long time the exact spot and code which is culpable for this. It is InsetTabular::resetPos()! It's just that something with that scrolling mechanism is wrong, but I don't have a good idea to fix it. So if someone has time to spare he can do some investigation and see what we can do there to fix the cycle. A fast fix would be to have a bool so that resetPos is not entered 2 times, but probably that wouldn't do the right scroll, but who knows :) Anyway I'll save the mail so that when I have time I can do this myself if noone beats me in it. I'm still working A LOT in making Find/Replace work correctly and I only have a really small bug to fix right now, but you know small bugs are hard to spot :). Anyway my local tree has in a lot of cleanups and IMO some of the bugs on SourceForge are gone now as I took the time to fix also other stuff I've seen when testing the Find/Replace stuff. One of them is the Cursor appearing outside the inset on some ocacions :) Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Penn's aunts made great apple pies at low prices. No one else in town could compete with the pie rates of Penn's aunts.
Re: Natbib
On 19-Jul-2001 Dekel Tsur wrote: What I don't understand is why you don't want to use longtable (or other packages) if it is available ? Maybe you have to send the latex-file to someone you know and you know he has only a minimal LaTeX installation so you exclude some stuff. Could that be a reason? But the real reason is not to not use it if you have it but to use it if you don't have it! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ The program isn't debugged until the last user is dead.
Re: Traditional look website
On 20-Jul-2001 Allan Rae wrote: I managed to get the body and the main text to have different images behind them. I'm also thinking it might be fun to add different images You forgot to say that one should not complain about the background image of the text not being the whole vertical height and so it seems a bit strange seeing the text going of it's background color on the top. Otherwise it would be nice. (tested on Opera 5.0 that was the browser I had open when I read your mail) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ You will lose an important disk file.
Re: Natbib
On Fri, Jul 20, 2001 at 09:21:02AM +0200, Juergen Vigna wrote: On 19-Jul-2001 Dekel Tsur wrote: What I don't understand is why you don't want to use longtable (or other packages) if it is available ? Maybe you have to send the latex-file to someone you know and you know he has only a minimal LaTeX installation so you exclude some stuff. Could that be a reason? No. The other person should install the necessary packages (and most of the packages we use are standard). But the real reason is not to not use it if you have it but to use it if you don't have it! Can you explain this sentence?
Re: Natbib
On 20-Jul-2001 Dekel Tsur wrote: No. The other person should install the necessary packages (and most of the packages we use are standard). Well it's friday, but here is a * very ironic smiley * But the real reason is not to not use it if you have it but to use it if you don't have it! Can you explain this sentence? Sure! The real reason is, not to, not use it, if you have it, but to use it, if you don't have it! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ New Hampshire law forbids you to tap your feet, nod your head, or in any way keep time to the music in a tavern, restaurant, or cafe.
Re: Natbib announcement
On Thursday 19 July 2001 19:17, Jürgen Spitzmüller wrote: On Thursday, 19. July 2001 16:17, Angus Leeming wrote: Well, now it's in head so just update and play. Angus Thanks, I got it now ;-) Looks great! A few comments, though: - Citation Dialog size is much better now, but now a little bit too wide (about 1cm) for 800x600. Well, not really tragic but a little bit annoying ;-) Morning Jürgen. Could you fix this at your end please by playing with fdesign form_citation.fd. I've removed all the setSize rubbish, so any changes in the .fd file are immediately apparent. - Your WYSIWYG-Choice of the citestyle is not really WYSIWYG: The surnames are not cited, so don't parse Leeming, Angus (2001) but Leeming (2001) if possible This is a limitation of my hacked BibTeX parser. I plan to redo this eventually using pybliographic's extremely sophisticated parser. - In layout - document you can choose the option Author-Year or Numerical. But what about the other Natbib Options apart from numbered (e.g. sortcompress)? I guess I have to insert them into Layout Document Document Options. Wouldn't a separate Options field be better? Today there was a discussion about a dialog for all supported packages (thread Natbib). I guess one pro for this dialog would be that you could have an options-field for each of these packages (or support some Options directly via menue). Inserting all Options from the global options field to each and any package is not the ideal solution IMHO. This could really lead to trouble if two packages use the same name for an option. All very true. Surely it's not THAT hard for now to export to LaTeX and edit the usepackage command yourself. As a hardcore natbib user I really like how you implemented this from what I've seen on a first view. Thank you very much! I will try to help you by testing this feature as good as I can, Thank you. Angus
Re: Natbib
On Fri, Jul 20, 2001 at 10:32:05AM +0200, Juergen Vigna wrote: The real reason is, not to, not use it, if you have it, but to use it, if you don't have it! I still don't understand: how can you use the longtable package if you don't have it installed ?
Re: Patch: version build info added.
On Friday 20 July 2001 07:17, R. Lahaye wrote: Looks like an excellent idea. A simpler solution would probably be to generate this data in a file that would be installed along with LyX. This way the information would be available even when LyX cannot be launched. I then would opt for both: allow a version flag to the lyx executable and generate a file or script (lyx-config) with the version info. Many software handles a -version (and/or --version) flag, so I thought it'll be useful to add this to LyX as well. For software under development this flag should output all necessary info for the developers. This output added to a bug report, could be most helpful. Combine both ideas, so that the file is generated during compilation of lyx and is input when running lyx -version. No need to add unnecessarily to code bloat! Angus
A few new things to try out
Hello there, I have just commited a bunch of small things, and would like people to try them out and comment a bit. 1/ add support for hyphenation break inset. Currently, this is just drawn as a '|' character becasue I have been lazy. I can change it to a hand drawn vertical line if needed, but I am not sure it will work well with italics. I'd appreciate if our german friends could have a look at it 2/ the index commands now use last word or selection as default value. However, I use for that the selectWordWhenUnderCursor (!) method, which ignore word when cursor is at boundary (this mean you have to be in the middle of a word). I can understand this is a problem with index, but I did not use a different method it because it is IMO a problem for font change too (the other user). So would it be OK to change the behaviour of font functions to apply to a word when cursor is at its boundary? Currently this does nothing. Also, I would like to remove one of the index menu entries. Do we really need two of them? Can someone come up with something less wordy than 'Index of preceeding word'?? Finally, strange things are bound to happen when selecting several paragraphs and trying to index that. I'll have a look. 3/ the popup for creation of .lyx directory is gone (except when you use -userdir). Should we add something to splash.lyx to explain that this directory has been created, or just assume that the user will find out soon enough? 4/ I have cleaned up the support for french style quotes. No they add automatically inner space when in french language and output the right french.sty/frenchb constructs. Should it do the same for 'canadien' (aka fr_CA)? I am not sure the typographical rules are the same over there. Also, I'd appreciate if our french friends could have a look at it. That's all for today. JMarc
Re: Natbib
On 20-Jul-2001 Dekel Tsur wrote: On Fri, Jul 20, 2001 at 10:32:05AM +0200, Juergen Vigna wrote: The real reason is, not to, not use it, if you have it, but to use it, if you don't have it! I still don't understand: how can you use the longtable package if you don't have it installed ? Well what about Export as LaTeX functionality??? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ What do you do when your real life exceeds your wildest fantasies? You keep it to yourself. -- Broadcast News
Re: Natbib
On Fri, Jul 20, 2001 at 12:00:32PM +0200, Juergen Vigna wrote: On 20-Jul-2001 Dekel Tsur wrote: On Fri, Jul 20, 2001 at 10:32:05AM +0200, Juergen Vigna wrote: The real reason is, not to, not use it, if you have it, but to use it, if you don't have it! I still don't understand: how can you use the longtable package if you don't have it installed ? Well what about Export as LaTeX functionality??? So you want to use lyx on one machine, export to latex, and run latex on a second machine ? Why not do the lyx-latex conversion on the 2nd machine ? If you really need this feature, you can edit the packages.lst file. Another option is to add a lyxrc variable that controls whether the exported latex file uses uninstalled packages. I don't see why you need to implement a feature which will rarely be used.
Fast question, hopefully fast answer!
Have a look at this function:
int InsetCollapsable::width_collapsed(Painter pain, LyXFont const ) const
{
int width;
int ascent;
int descent;
pain.buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont, false,
width, ascent, descent);
return width + (2*TEXT_TO_INSET_OFFSET);
}
Could I do:
int InsetCollapsable::width_collapsed(Painter pain, LyXFont const ) const
{
int width;
int ascent;
int descent;
PainterBase::buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont,
false, width, ascent, descent);
return width + (2*TEXT_TO_INSET_OFFSET);
}
Is it the same??
Jürgen
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED]
Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
You never know what is enough until you know what is more than enough.
-- William Blake
Re: Natbib
On 20-Jul-2001 Dekel Tsur wrote: Well what about Export as LaTeX functionality??? So you want to use lyx on one machine, export to latex, and run latex on a second machine ? Why not do the lyx-latex conversion on the 2nd machine ? If you really need this feature, you can edit the packages.lst file. Another option is to add a lyxrc variable that controls whether the exported latex file uses uninstalled packages. Well what if: 1. The other person does not have LyX (maybe because of Windows, maybe because X11 is not installed!) 2. The other person does LaTeX only! I don't see why you need to implement a feature which will rarely be used. Because it's fun? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Women sometimes forgive a man who forces the opportunity, but never a man who misses one. -- Charles De Talleyrand-Perigord
Re: Fast question, hopefully fast answer!
On Friday 20 July 2001 11:19, Juergen Vigna wrote:
Have a look at this function:
int InsetCollapsable::width_collapsed(Painter pain, LyXFont const ) const
{
int width;
int ascent;
int descent;
pain.buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont, false,
width, ascent, descent);
return width + (2*TEXT_TO_INSET_OFFSET);
}
Could I do:
int InsetCollapsable::width_collapsed(Painter pain, LyXFont const ) const
{
int width;
int ascent;
int descent;
PainterBase::buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont,
false, width, ascent, descent);
return width + (2*TEXT_TO_INSET_OFFSET);
}
Is it the same??
Only if buttonText is a static method. From a quick look, it isn't. (But the
compiler will bomb out if it doesn't like it.)
Angus
Re: Fast question, hopefully fast answer!
On 20-Jul-2001 Angus Leeming wrote: Only if buttonText is a static method. From a quick look, it isn't. (But the compiler will bomb out if it doesn't like it.) Hmm, probably it will not work, but then it's just stupid IMO! I just want some metrics which surely are not dependant from anything (draw==false) and I'm not able to get them. IMO we should add this static methods to be able to call them without the need to pass a Painter() to the methods. This IS NEEDED if we want that InsetText is able to calculate/get the space it can draw in. As this is now it will never be able to do this! I also can explain why (as I just looked into the code to find a solution), but well let's say just believe me. Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ One picture is worth 128K words.
[noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
Submitted By: Nobody/Anonymous (nobody) Assigned to: Andre Poenitz (apoenitz) Summary: \land and \lor are not printed on screen Initial Comment: The math symbols \land and \lor are not printed on screen -- Comment By: Jean-Marc Lasgouttes (jmarc) Date: 2001-03-01 08:00 Message: Logged In: YES user_id=116707 As far as I know, these are equivalent to \wedge and \vee. I have implemented them as macro without arguments. This gives correct behaviour. Some day we'd probably need some kind of distinction here... What I do not know is whether mathed supports showing the same symbol for several macros. If it does, other things defined with \let in fontdefs.dtx should be aliased too. There is no such file on my harddisk. Andre'
Re: A few new things to try out
Jean-Marc Lasgouttes wrote: Hello there, 4/ I have cleaned up the support for french style quotes. No they add automatically inner space when in french language and output the right french.sty/frenchb constructs. Should it do the same for 'canadien' (aka fr_CA)? Oui. canadien I am not sure the typographical rules are the same over there. Also, I'd appreciate if our french friends could have a look at it. Georges, this has to do with the LyX document processor that I use to typeset the TWiG books. Judging from your book, Contes, légendes et chansons, the typographical rules are the same. Garst
Re: Natbib
Juergen Vigna wrote: On 20-Jul-2001 Dekel Tsur wrote: Well what about Export as LaTeX functionality??? So you want to use lyx on one machine, export to latex, and run latex on a second machine ? Why not do the lyx-latex conversion on the 2nd machine ? If you really need this feature, you can edit the packages.lst file. Another option is to add a lyxrc variable that controls whether the exported latex file uses uninstalled packages. Well what if: 1. The other person does not have LyX (maybe because of Windows, maybe because X11 is not installed!) 2. The other person does LaTeX only! I don't see why you need to implement a feature which will rarely be used. Because it's fun? all my texts have ERT, more or less. and it's the default for me that i have to export to latex and run it manually to see what's exactly going on with my text. the error-handling of lyx is sometimes not the best ... Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre I have implemented them as macro without arguments. This gives
Andre correct behaviour. Some day we'd probably need some kind of
Andre distinction here...
That's fine.
What I do not know is whether mathed supports showing the same
symbol for several macros. If it does, other things defined with
\let in fontdefs.dtx should be aliased too.
Andre There is no such file on my harddisk.
It should be possible to install sources with teTeX. I do not know
what package, though. This is pretty useful when you want to know what
a given command actually does.
Anyway, I get here (grepping for \let to get synonyms):
fantomas: grep '\\let' /usr/local/lib/tex/doc/base/dtx/fontdef.dtx
\let\lnot=\neg
\let\land=\wedge
\let\lor=\vee
\def\neq{\not=} \let\ne=\neq
\let\le=\leq
\let\ge=\geq
\let\owns=\ni
\let\gets=\leftarrow
\let\to=\rightarrow
% \let\@@sqrt\sqrtsign
\let\|=\Vert
Reading the whole file is probably interesting too.
JMarc
Re: A few new things to try out
Jean-Marc == Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: Jean-Marc 1/ add support for hyphenation break inset. Currently, this Jean-Marc is just drawn as a '|' character becasue I have been lazy. Jean-Marc I can change it to a hand drawn vertical line if needed, Jean-Marc but I am not sure it will work well with italics. I'd Jean-Marc appreciate if our german friends could have a look at it It just occured to me that hyphenation break is a stupid name. I'll change it to 'ligature break'. JMarc
Re: Natbib announcement
On Friday, 20. July 2001 10:56, Angus Leeming wrote:
Could you fix this at your end please by playing with fdesign
form_citation.fd.
Hello Angus,
I've done this in fdesign and editor. Now it fits almost perfectly into
the poor man's 800x600 screen. I've attached the diff (no, I won't
call it Patch this time) with the new sizes and positions (only
slight corrections on the width). Maybe it's of interest for you. I had
to edit FormCitation.C manually to get it visible. Don't know why.
Anyway, there's a diff from this, too.
[...]
This is a limitation of my hacked BibTeX parser. I plan to redo this
eventually using pybliographic's extremely sophisticated parser.
That's of course a very good idea! BTW: it's o.k. for me, I only
thought it *might* be confusing to users with no natbib experience. At
this point (just as an idea for the future): *If* this is somehow
possible eventually, it would be nice if the cite-labels in the text
could somehow show the citation style too.
- In layout - document you can choose the option Author-Year or
Numerical. But what about the other Natbib Options apart from
numbered (e.g. sortcompress)?
[...]
All very true. Surely it's not THAT hard for now to export to LaTeX
and edit the usepackage command yourself.
This was more a general thought at this point where LyX starts to
support more and more packages directly. Maybe it belongs to the
Supported Packages Dialog: Yes or No discussion which is currently
held under another topic.
Thanks,
Jürgen
BTW: I played a bit today with the new feature (all possible cite
combinations with and withour numbered). I really like it very much!
The only problem I encountered was a (known) Natbib bug: Upper Case
gives problems sometimes when NFSS commands are used. This does not
happen with the default natbib styles like plainnat but most likely
with selfmade (custom-bib) Styles. But I guess that is not your
business. So thanks again for this.
Thank you.
Angus
Index: src/frontends/xforms/form_citation.C
===
RCS file: /cvs/lyx/lyx-devel/src/frontends/xforms/form_citation.C,v
retrieving revision 1.23
diff -u -r1.23 form_citation.C
--- src/frontends/xforms/form_citation.C 2001/07/19 14:12:36 1.23
+++ src/frontends/xforms/form_citation.C 2001/07/20 11:16:52
@@ -22,12 +22,12 @@
FL_OBJECT *obj;
FD_form_citation *fdui = new FD_form_citation;
- fdui-form = fl_bgn_form(FL_NO_BOX, 860, 510);
+ fdui-form = fl_bgn_form(FL_NO_BOX, 800, 510);
fdui-form-u_vdata = this;
- fdui-box = obj = fl_add_box(FL_UP_BOX, 0, 0, 860, 510, );
+ fdui-box = obj = fl_add_box(FL_UP_BOX, 0, 0, 800, 510, );
{
char const * const dummy = N_(Inset keys|#I);
-fdui-browser_cite = obj = fl_add_browser(FL_HOLD_BROWSER, 10, 30, 180, 460, idex(_(dummy)));
+fdui-browser_cite = obj = fl_add_browser(FL_HOLD_BROWSER, 10, 30, 165, 460, idex(_(dummy)));
fl_set_button_shortcut(obj, scex(_(dummy)), 1);
}
fl_set_object_lalign(obj, FL_ALIGN_TOP_LEFT);
@@ -36,75 +36,75 @@
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
{
char const * const dummy = N_(Bibliography keys|#B);
-fdui-browser_bib = obj = fl_add_browser(FL_HOLD_BROWSER, 240, 30, 180, 460, idex(_(dummy)));
+fdui-browser_bib = obj = fl_add_browser(FL_HOLD_BROWSER, 225, 30, 180, 460, idex(_(dummy)));
fl_set_button_shortcut(obj, scex(_(dummy)), 1);
}
fl_set_object_lalign(obj, FL_ALIGN_TOP_LEFT);
fl_set_object_gravity(obj, FL_North, FL_SouthEast);
fl_set_object_resize(obj, FL_RESIZE_X);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui-button_add = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 30, 30, 30, _(@4-));
+ fdui-button_add = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 30, 30, 30, _(@4-));
fl_set_button_shortcut(obj, _(#D), 1);
fl_set_object_gravity(obj, FL_North, FL_North);
fl_set_object_resize(obj, FL_RESIZE_NONE);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui-button_del = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 65, 30, 30, _(@9+));
+ fdui-button_del = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 65, 30, 30, _(@9+));
fl_set_button_shortcut(obj, _(#X), 1);
fl_set_object_gravity(obj, FL_North, FL_North);
fl_set_object_resize(obj, FL_RESIZE_NONE);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui-button_up = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 100, 30, 30, _(@8-));
+ fdui-button_up = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 100, 30, 30, _(@8-));
fl_set_button_shortcut(obj, _(#A), 1);
fl_set_object_gravity(obj, FL_North, FL_North);
fl_set_object_resize(obj, FL_RESIZE_NONE);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui-button_down = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 135, 30, 30, _(@2-));
+ fdui-button_down = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 135, 30, 30, _(@2-));
fl_set_button_shortcut(obj, _(#B), 1);
compile problems
Hi, Am I the only one who has difficulties compiling today's cvs? Thanks, Ed. Configuration of LyX was successful. Type 'make' to compile the program, and then 'make install' to install it. Making all in intl make[1]: Entering directory `/tmp/initial/intl' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/tmp/initial/intl' Making all in po make[1]: Entering directory `/tmp/initial/po' make[1]: *** No rule to make target `all'. Stop. make[1]: Leaving directory `/tmp/initial/po' make: *** [all-recursive] Error 1
Re: Natbib announcement
On Friday 20 July 2001 13:54, Jürgen Spitzmüller wrote: On Friday, 20. July 2001 10:56, Angus Leeming wrote: Could you fix this at your end please by playing with fdesign form_citation.fd. Hello Angus, I've done this in fdesign and editor. Now it fits almost perfectly into the poor man's 800x600 screen. I've attached the diff (no, I won't call it Patch this time) with the new sizes and positions (only slight corrections on the width). Maybe it's of interest for you. I had to edit FormCitation.C manually to get it visible. Don't know why. Anyway, there's a diff from this, too. Many thanks. I'll commit this to the repository. For future information: to get the changes into form_citation.C, you have to type make updatesrc in the forms subdirectory. This is a limitation of my hacked BibTeX parser. I plan to redo this eventually using pybliographic's extremely sophisticated parser. That's of course a very good idea! BTW: it's o.k. for me, I only thought it *might* be confusing to users with no natbib experience. At this point (just as an idea for the future): *If* this is somehow possible eventually, it would be nice if the cite-labels in the text could somehow show the citation style too. Again, this will wait till we have a proper BibTeX class. It's in my wanted list too. - In layout - document you can choose the option Author-Year or Numerical. But what about the other Natbib Options apart from numbered (e.g. sortcompress)? [...] All very true. Surely it's not THAT hard for now to export to LaTeX and edit the usepackage command yourself. This was more a general thought at this point where LyX starts to support more and more packages directly. Maybe it belongs to the Supported Packages Dialog: Yes or No discussion which is currently held under another topic. Sure. The nice thing about coding LyX has been that it's taught me that the elegant solution is the right solution almost always. Lars has been a pretty good teacher in this regard. BTW: I played a bit today with the new feature (all possible cite combinations with and withour numbered). I really like it very much! The only problem I encountered was a (known) Natbib bug: Upper Case gives problems sometimes when NFSS commands are used. This does not happen with the default natbib styles like plainnat but most likely with selfmade (custom-bib) Styles. But I guess that is not your business. So thanks again for this. My pleasure. Angus
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
Anyway, I get here (grepping for \let to get synonyms): fantomas: grep '\\let' /usr/local/lib/tex/doc/base/dtx/fontdef.dtx \let\lnot=\neg \let\land=\wedge \let\lor=\vee Ok, I'll put that on my todo list. I don't really like the current macro hack, so I'll wait with the rest until the infrastructure is ready.. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
On Fri, Jul 20, 2001 at 01:05:06PM +0200, Andre Poenitz wrote: What I do not know is whether mathed supports showing the same symbol for several macros. If it does, other things defined with \let in fontdefs.dtx should be aliased too. There is no such file on my harddisk. That's because you don't have the unstripped source on your harddisk. All the stuff from fontdefs goes into .ltx files. I think it is probably all in fontmath.ltx and fonttext.ltx. Also I would draw your attention to my comments a month or so ago about using latex itself to work out which glyph an unknown sequence should be represented by Jules
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
Andre == Andre Poenitz [EMAIL PROTECTED] writes: Anyway, I get here (grepping for \let to get synonyms): fantomas: grep '\\let' /usr/local/lib/tex/doc/base/dtx/fontdef.dtx \let\lnot=\neg \let\land=\wedge \let\lor=\vee Andre Ok, I'll put that on my todo list. I don't really like the Andre current macro hack, so I'll wait with the rest until the Andre infrastructure is ready.. You could maybe have these macros in a lyx file which you read from disk :) JMarc
Re: compile problems
Edwin == Edwin Leuven [EMAIL PROTECTED] writes: Edwin Hi, Am I the only one who has difficulties compiling today's Edwin cvs? Edwin Thanks, Ed. Edwin Configuration of LyX was successful. Type 'make' to compile the Edwin program, and then 'make install' to install it. Making all in Edwin intl make[1]: Entering directory `/tmp/initial/intl' make[1]: Edwin Nothing to be done for `all'. make[1]: Leaving directory Edwin `/tmp/initial/intl' Making all in po make[1]: Entering Edwin directory `/tmp/initial/po' make[1]: *** No rule to make target Edwin `all'. Stop. make[1]: Leaving directory `/tmp/initial/po' make: Edwin *** [all-recursive] Error 1 It maigh be my fault. I removed the generation of po/Makefil from po/Makefile.in because the doc from gettext 0.10.38 did not say it is needed (so I thought it worked differently). Does reverting the following patch help? JMarc
Re: compile problems
Jean-Marc == Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: Edwin == Edwin Leuven [EMAIL PROTECTED] writes: Edwin Hi, Am I the only one who has difficulties compiling today's Edwin cvs? Edwin Thanks, Ed. Edwin Configuration of LyX was successful. Type 'make' to compile the Edwin program, and then 'make install' to install it. Making all in Edwin intl make[1]: Entering directory `/tmp/initial/intl' make[1]: Edwin Nothing to be done for `all'. make[1]: Leaving directory Edwin `/tmp/initial/intl' Making all in po make[1]: Entering Edwin directory `/tmp/initial/po' make[1]: *** No rule to make target Edwin `all'. Stop. make[1]: Leaving directory `/tmp/initial/po' make: Edwin *** [all-recursive] Error 1 Jean-Marc It maigh be my fault. I removed the generation of Jean-Marc po/Makefil from po/Makefile.in because the doc from gettext Jean-Marc 0.10.38 did not say it is needed (so I thought it worked Jean-Marc differently). Jean-Marc Does reverting the following patch help? OK, it seems that I do not know how to attach files with my new Gnus... Here it is JMarc Index: configure.in === RCS file: /usr/local/lyx/cvsroot/lyx-devel/configure.in,v retrieving revision 1.71 retrieving revision 1.72 diff -u -r1.71 -r1.72 --- configure.in2001/07/05 14:00:36 1.71 +++ configure.in2001/07/19 15:32:12 1.72 @@ -313,7 +313,7 @@ src/frontends/xforms/Makefile \ src/frontends/qt2/Makefile \ src/frontends/gnome/Makefile \ -], [sed -e /POTFILES =/r po/POTFILES po/Makefile.in po/Makefile]) +]) cat EOF
Re: A few new things to try out
On Friday, 20. July 2001 11:52, Jean-Marc Lasgouttes wrote: 1/ add support for hyphenation break inset. Currently, this is just drawn as a '|' character becasue I have been lazy. I can change it to a hand drawn vertical line if needed, but I am not sure it will work well with italics. I'd appreciate if our german friends could have a look at it Well... Looks good and seems to do the things it has to. The '|' character is sufficient IMO. I can live with the \textcompwordmark in the output. So: very nice!!! Thank you. It would be nice if you could bind it for the final release. BTW: - It's impossible to insert an ordinary quote into the 666-inset at the moment - Marking Text and clicking on the TeX-Button does not insert the marked text into the 666 inset. Greets, Jürgen JMarc
Re: A few new things to try out
Jürgen == Jürgen Spitzmüller [EMAIL PROTECTED] writes: Jürgen On Friday, 20. July 2001 11:52, Jean-Marc Lasgouttes wrote: 1/ add support for hyphenation break inset. Currently, this is just drawn as a '|' character becasue I have been lazy. I can change it to a hand drawn vertical line if needed, but I am not sure it will work well with italics. I'd appreciate if our german friends could have a look at it Jürgen Well... Looks good and seems to do the things it has to. The Jürgen '|' character is sufficient IMO. I can live with the Jürgen \textcompwordmark in the output. So: very nice!!! Thank you. Jürgen It would be nice if you could bind it for the final release. Propose bindings :) Jürgen BTW: - It's impossible to insert an ordinary quote into the Jürgen 666-inset at the moment ordinary quotes are somewhat broken right now. Jürgen - Marking Text and clicking on the TeX-Button does not insert Jürgen the marked text into the 666 inset. This could probably be added as a general feature of collapsable insets creation. JMarc
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
Andre Ok, I'll put that on my todo list. I don't really like the Andre current macro hack, so I'll wait with the rest until the Andre infrastructure is ready.. You could maybe have these macros in a lyx file which you read from disk :) I think I'd rather go for a proper 'symbol inset'. This wastes a few bytes in comparison to the current 'inline symbols' but simplifies overall structure and offers a multitude of opportunities (we could have latex name, X glyph, Unicode, and *ML; encoding all in one place...) Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: A few new things to try out
On Friday, 20. July 2001 15:43, Jean-Marc Lasgouttes wrote: Propose bindings :) C-S-L -- control-silly-ligatures ;-) AFAIK it's not used at the moment. Jürgen.
Re: Proposal: remove the 'create new .lyx directory?' popup
Lior == Lior Silberman [EMAIL PROTECTED] writes: Lior On 9 Jul 2001, Jean-Marc Lasgouttes wrote: Dekel == Dekel Tsur [EMAIL PROTECTED] writes: Dekel I'm not sure that this is a good idea when the -userdir flag is Dekel used. What if I just misspelled the userdir name ? Well, people using -userdir are supposed to know what they are doing :) And all you have to do is rm -r the directory. The reason why I want to remove the popup is also that it is buggy: with some window manager, it is not possible to have a modal dialog without a main window, and the buttons cannot be clicked on. JMarc Lior When you misspell the -userdir parameter, the concern is that Lior you'll get the wrong configuration, and take a while to notice Lior it. Removing the directory is just an annoyance. Lior I think we need to silently create the directory, except in the Lior case of an explicit_userdir (change the logic in lyx_main.C so Lior only a -userdir flag counts as explicit, not the environment Lior variable). In the case the user asked for a nonexistent Lior directory, we can help him and make sure everything is OK. I did that. JMarc
Re: Patch LyX 1.1.6fix3: use frenchb guillemets
Yves == Yves Bastide [EMAIL PROTECTED] writes: Yves Hi, Here's a proposed patch to use frenchb's guillemets \og and Yves \fg (which have proper spacing) when using frenchb. The current Yves code does it only when fontenc != T1 -- not frequent among Yves French writers (: Yves (This patch is for 1.1.6; I can prepare another for -devel if Yves accepted.) Yves, could you checkwhat I did for 1.2.0? If it works well, I may adapt it to 1.1.6 too. JMarc
Re: compile problems
Jean-Marc It maigh be my fault. I removed the generation of Jean-Marc po/Makefil from po/Makefile.in because the doc from gettext Jean-Marc 0.10.38 did not say it is needed (so I thought it worked Jean-Marc differently). I have 0.10.38 installed. Jean-Marc Does reverting the following patch help? OK, it seems that I do not know how to attach files with my new Gnus... Here it is Didn't arrive as nice attachment either. I inserted by hand: ], [sed -e /POTFILES =/r po/POTFILES po/Makefile.in po/Makefile]) instead of ]) still didn't work. gr.ed.
RE: CVS Update: lyx-devel
On 20-Jul-2001 [EMAIL PROTECTED] wrote: Implemented Search/Replace functionality for Insets. Cleaned up a bit. Small fixes. With this I think we implemented all the requested features which where missing since the change to insets: font-change, s+r spellchecking. I tested the last quite a bit and have small problems with insets inside insets if both are going over the screenborder and I have to readjust, but IMO this are minor glitches, the functions should work. Jürgen P.S.: I used up a lot of time implementing all this features and left my real work stack up on my table. This means that for the next time I will have to giv'em 99% of my time, so I will do only really needed bugfixes all other stuff will go into my todo folder! P.P.S.: Have a nice weekend! -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ No rock so hard but that a little wave May beat admission in a thousand years. -- Tennyson
Re: compile problems
Edwin == Edwin Leuven [EMAIL PROTECTED] writes: Edwin still didn't work. I'm not surprised now that I have re-read gettext configure script. Do you have a po/Makefile? What did configure say when creating everything (in the list of 'creating foo' in the console output). JMarc
Re: compile problems
Do you have a po/Makefile?
yes, an empty one...
What did configure say when creating everything (in the list of 'creating
foo' in the console output).
loading cache ./config.cache
configuring LyX version 1.2.0cvs
WARNING: This is a development version. Expect bugs.
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking config.cache system type... same
checking for install target ... ... lyx
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for prefix by checking for lyx... (cached) /usr/bin/lyx
checking whether make sets ${MAKE}... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking for kpsewhich... (cached) kpsewhich
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for strerror in -lcposix... (cached) no
checking how to run the C preprocessor... (cached) gcc -E
checking for AIX... no
checking for HP-UX... (cached) no
checking for SunOS 4.x... (cached) no
checking for SCO 3.2v4... (cached) no
checking for Cygwin environment... (cached) no
checking for mingw32 environment... (cached) no
checking for executable suffix... (cached) no
checking what frontend should be used as main GUI... xforms
checking for a working C++ compiler... g++
checking whether the C++ compiler (g++ ) is a cross-compiler... no
checking whether we are using GNU C++... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking how to run the C++ preprocessor... (cached) g++ -E
checking for ld used by GCC... (cached) /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
checking for /usr/bin/ld option to reload object files... (cached) -r
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
checking how to recognise dependant libraries... (cached) pass_all
checking for object suffix... (cached) o
checking command to parse /usr/bin/nm -B output... (cached) ok
checking for dlfcn.h... (cached) yes
checking for ranlib... (cached) ranlib
checking for strip... (cached) strip
checking for objdir... .libs
checking for gcc option to produce PIC... (cached) -fPIC
checking if gcc PIC flag -fPIC works... (cached) yes
checking if gcc static flag -static works... (cached) yes
checking if gcc supports -c -o file.o... (cached) no
checking if we can lock with hard links... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
creating libtool
checking whether the C++ compiler understands explicit... (cached) yes
checking whether the included std::string should be used... checking ...
(cached) no
checking whether the systems std::string is really good... (cached) no
checking for C headers wrappers... (cached) yes
checking whether C library functions are already in the global namespace...
(cached) no
checking for conforming std::count... (cached) yes
checking for ostream... (cached) no
checking for istream... (cached) no
checking for sstream... (cached) no
checking for locale... (cached) no
checking for limits... (cached) no
checking for modern STL streams... (cached) no
checking for regex.h... (cached) yes
checking for sin in -lm... (cached) yes
checking for fopen in -lc... (cached) yes
checking for extra library directory... (cached) NONE
checking for extra include directory... (cached) NONE
checking for extra lib+include directory... (cached) NONE
checking for main in -liberty... (cached) yes
checking whether the included libsigc++ should be used... yes
checking for pspell support... no
checking for ptsname in -lpt... (cached) no
checking for X... (cached) libraries /usr/X11R6/lib, headers
/usr/X11R6/include
checking for dnet_ntoa in -ldnet... (cached) no
checking for dnet_ntoa in -ldnet_stub... (cached) no
checking for gethostbyname... (cached) yes
checking for connect... (cached) yes
checking for remove... (cached) yes
checking for shmat... (cached) yes
checking for IceConnectionNumber in -lICE... (cached) yes
checking for XOpenIM... (cached) yes
checking for XpmCreateBufferFromImage in -lXpm... (cached) yes
checking for X11/xpm.h... (cached) yes
checking xpm header version... (cached)
Re: Patch: version build info added.
On Fri, Jul 20, 2001 at 03:17:41PM +0900, R. Lahaye wrote: I then would opt for both: allow a version flag to the lyx executable and generate a file or script (lyx-config) with the version info. Many software handles a -version (and/or --version) flag, so I thought it'll be useful to add this to LyX as well. For software under development this flag should output all necessary info for the developers. This output added to a bug report, could be most helpful. I think a separate file/script is a bad idea. the something-config's are useful for libraries and gcc flags, but we want --version to be useful for debugging the scenario where by accident some user has got a different version of lyx to the contents of the relevant /usr/local/share/lyx directory (or whatever). Whether this actually causes problems right now I don't know, but we should kee version info with the binary so it will be clearer if it does. john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: A few new things to try out
On Fri, Jul 20, 2001 at 11:52:15AM +0200, Jean-Marc Lasgouttes wrote: 3/ the popup for creation of .lyx directory is gone (except when you use -userdir). Should we add something to splash.lyx to explain that this directory has been created, or just assume that the user will find out soon enough? I think assume. 1) lots of applications create dotfiles and dotdirs. people are used to it 2) users are less likely to mess in .lyx now we have FormPreferences 3) .lyx contents are well documented in the lyx docs imho john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Patch: version build info added.
John == John Levon [EMAIL PROTECTED] writes: John On Fri, Jul 20, 2001 at 03:17:41PM +0900, R. Lahaye wrote: I then would opt for both: allow a version flag to the lyx executable and generate a file or script (lyx-config) with the version info. Many software handles a -version (and/or --version) flag, so I thought it'll be useful to add this to LyX as well. For software under development this flag should output all necessary info for the developers. This output added to a bug report, could be most helpful. John I think a separate file/script is a bad idea. the John something-config's are useful for libraries and gcc flags, but John we want --version to be useful for debugging the scenario where John by accident some user has got a different version of lyx to the John contents of the relevant /usr/local/share/lyx directory (or John whatever). OK, maybe you're right. Or we should do both, in case LyX does not start at all (which may very well happen). And also, the contents of this file should be what is displayed at the end of the configure run. Also, Rob, you do not need to change anything in acconfig.h. Use the optional third argument of AC_DEFINE to give the description. JMarc
Re: Fast question, hopefully fast answer!
On Fri, Jul 20, 2001 at 12:54:33PM +0200, Juergen Vigna wrote: On 20-Jul-2001 Angus Leeming wrote: Only if buttonText is a static method. From a quick look, it isn't. (But the compiler will bomb out if it doesn't like it.) Hmm, probably it will not work, but then it's just stupid IMO! I just want some metrics which surely are not dependant from anything (draw==false) as it's friday, I'd just like to say that this draw parameter thing is really ugly ... ... that's all ! john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: compile problems
Edwin == Edwin Leuven [EMAIL PROTECTED] writes: Do you have a po/Makefile? Edwin yes, an empty one... What did configure say when creating everything (in the list of 'creating foo' in the console output). I quote creating src/frontends/controllers/Makefile creating src/frontends/xforms/Makefile creating src/frontends/qt2/Makefile creating src/frontends/gnome/Makefile creating src/config.h After these lines, you should have creating po/POTFILES creating po/Makefile Is po/POTFILES created? What happens if you delete the empty file(s)? Is there something interesting in config.log? JMarc
Re: CVS Update: lyx-devel
On Fri, Jul 20, 2001 at 04:27:33PM +0200, Juergen Vigna wrote: On 20-Jul-2001 [EMAIL PROTECTED] wrote: Implemented Search/Replace functionality for Insets. Cleaned up a bit. Small fixes. With this I think we implemented all the requested features which where missing since the change to insets: font-change, s+r spellchecking. I tested the last quite a bit and have small problems with insets inside insets if both are going over the screenborder and I have to readjust, but IMO this are minor glitches, the functions should work. cool, I'll go test now and update sf where appropriate ! P.S.: I used up a lot of time implementing all this features and left my real work stack up on my table. This means that for the next time I will have to giv'em 99% of my time, so I will do only really needed bugfixes all other stuff will go into my todo folder! heh P.P.S.: Have a nice weekend! you too john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: A few new things to try out
jmarc jumbubled, 2/ the index commands now use last word or selection as default value. However, I use for that the selectWordWhenUnderCursor (!) method, which ignore word when cursor is at boundary (this mean you have to be in the middle of a word). I can understand this is a problem with index, but I did not use a different method it because it is IMO a problem for font change too (the other user). Hey, somebody's looking at something I wrote :) It's been a couple of years since I wrote or looked at that, but it seems to me that I wrote a new function to determine the last word. The logic to it is to default to the word you just typed, or one that you have clicked on. I think the typical case of inserting an index entry is immediately after typing it, so punctuation should also be allowed but not included. e.g., if i type end.insert index it should offer end If memory serves, the function works by checking to see if it is on a letter. If so, it moves right until it finds the last letter, and then travels left until whitespace. (hmm, did I ever get as far as using the selected text, if it exists, before looking at the word? It's been so long . . .) So would it be OK to change the behaviour of font functions to apply to a word when cursor is at its boundary? Currently this does nothing. I think this would be the expected behavior. Also, I would like to remove one of the index menu entries. Do we really need two of them? Can someone come up with something less wordy than 'Index of preceeding word'?? I think we do :) Index-preceding can be done entirely from the keyboard, and is designed to be right in the usual case. It's actually a descendent of one of my old word 5.1 macros. While typing, I get annoyed any time I have to use the mouse. For anything other than what the automated result would be, a dialog is necessary. Dialogs should not be imposed unless needed. So, yes, I think both are needed. hawk -- Prof. Richard E. Hawkins, Esq. /\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings Penn State until it pays my retainer. / \
Re: A few new things to try out
dochawk == dochawk [EMAIL PROTECTED] writes: dochawk Hey, somebody's looking at something I wrote :) Erm, I am sorry, but I'll have to announce you that I have just deleted your code... We now try to use the same function for all word selection stuff, for the sake of consistency. Of course, if you notice something you do not like with the new function, we can try to improve it. dochawk It's been a couple of years since I wrote or looked at that, dochawk but it seems to me that I wrote a new function to determine dochawk the last word. The logic to it is to default to the word dochawk you just typed, or one that you have clicked on. I think the dochawk typical case of inserting an index entry is immediately after dochawk typing it, so punctuation should also be allowed but not dochawk included. e.g., if i type end.insert index it should dochawk offer end Hmm, I am not sure this one works with current code. I'll have to check. dochawk I think we do :) Index-preceding can be done entirely from dochawk the keyboard, and is designed to be right in the usual case. dochawk It's actually a descendent of one of my old word 5.1 macros. dochawk While typing, I get annoyed any time I have to use the mouse. OK, so come up with a shorter name :) JMarc
Re: A few new things to try out
jmarc jmumbled, dochawk == dochawk [EMAIL PROTECTED] writes: dochawk Hey, somebody's looking at something I wrote :) Erm, I am sorry, but I'll have to announce you that I have just deleted your code... awe :( More seriously, as long as I get to keep my function, I'm happy. It was kind of a crude way of doing it, anyway. We now try to use the same function for all word selection stuff, for the sake of consistency. That's what I wanted to do in the first place :) I couldn't find anything at the time that would do what I needed--I think the closest I could come would come up with halfwords at times; it's all kind of vague. Of course, if you notice something you do not like with the new function, we can try to improve it. now I need to look at code :) dochawk It's been a couple of years since I wrote or looked at that, dochawk but it seems to me that I wrote a new function to determine dochawk the last word. The logic to it is to default to the word dochawk you just typed, or one that you have clicked on. I think the dochawk typical case of inserting an index entry is immediately after dochawk typing it, so punctuation should also be allowed but not dochawk included. e.g., if i type end.insert index it should dochawk offer end Hmm, I am not sure this one works with current code. I'll have to check. What really matters for the auto-selction is that it be finger-rememberable. I assume that having to hit it before the punctuation rather than afterwards can be habitualized (hmm, is that a word)? OTOH, having to hit an arrow first would be rough, though. dochawk I think we do :) Index-preceding can be done entirely from dochawk the keyboard, and is designed to be right in the usual case. dochawk It's actually a descendent of one of my old word 5.1 macros. dochawk While typing, I get annoyed any time I have to use the mouse. OK, so come up with a shorter name :) I think I started with index-last, didn't I? It vaguely seems to me that the name we ended up with wasn't what I started with. Is Index last or Index prior descriptive enough? Perhaps, Index, damnit! to indicate to just index without dialog?= my friday contribution. It *is* friday, this time, isn't it? hawk -- Prof. Richard E. Hawkins, Esq. /\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings Penn State until it pays my retainer. / \
Re: A few new things to try out
following up to my own reply, now that I have the current version: THe current version doesn't yield sensible results. The selection is blank if there is not a character of the word after the current word. I would assume, in general, that a current word function should grab the adjacent word. Is there a situation in whichtthis would *not* be the least surprising behavior? If so, perhaps the function can take an argument indicating strict (the current behavior), adjacent (touching a word), adjacent-left-only, and adjacent-right-only (I donh't see what the right-only would be useful for; I include it for completness. For that matter, on indexing and in general, adjacent makes more sense than adjacent-left, so maybe just strict and adjacent) hawk -- Prof. Richard E. Hawkins, Esq. /\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings Penn State until it pays my retainer. / \
Re: compile problems
Is po/POTFILES created? No What happens if you delete the empty file(s)? nothing Is there something interesting in config.log? nothing as far as i can see... gr.ed.
broken math labels (again)
I'm now up to date, but I'd have sworn that the math labels were fixed
weeks ago. (July 4 message from Andre). Insert-label from the menu is
greyed out in math insets, but \label{ works and becomes a lable on
reload. However, it seems the only way to edit them is to change the
raw file. Also,there seems to be no way to get a _ in the label, as
this causes a subscript.
hawk, off to see what else he can bereak
--
Prof. Richard E. Hawkins, Esq. /\ ASCII ribbon campaign
[EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail
These opinions will not be those of Xand postings
Penn State until it pays my retainer. / \
Small 666 insets all over the place
In my literate documents, I sprinkle the following construct all over the place: [[variable]] This should be in ERT and it is noweb's way of doing an in-lined code construct that also plugs into its indexing features. Look at .../examples/noweb2lyx.lyx for an example. Before the ERT inset, I could scan-read my documents without trouble: In the following code, [[io_str_iterator]] is going to walk down Now, I see this: In the following code, [666] - | [[io_str_iterator]] - is going to walk down If I collapse the inset, I see this: In the following code, [666] is going to walk down I know there is work being done to fix this. My fantasy would be to be able to see these short constructs as the label (instead of 666) of the inset. That would make the most sense in my opinion. -- Kayvan A. Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | crown of her husband | Robin Gregory (2/28/92)
Re: Patch LyX 1.1.6fix3: use frenchb guillemets
On Fri, Jul 20, 2001 at 03:58:39PM +0200, Jean-Marc Lasgouttes wrote:
Yves == Yves Bastide [EMAIL PROTECTED] writes:
Yves Hi, Here's a proposed patch to use frenchb's guillemets \og and
Yves \fg (which have proper spacing) when using frenchb. The current
Yves code does it only when fontenc != T1 -- not frequent among
Yves French writers (:
Yves (This patch is for 1.1.6; I can prepare another for -devel if
Yves accepted.)
Yves, could you checkwhat I did for 1.2.0? If it works well, I may
adapt it to 1.1.6 too.
There were two problems: when using a language other than french or
frenchb, no french quotes were inserted. And {} was missing after \fg,
eating a possible linebreak. The following patch cures both of them.
Note that there is still one problem with frenchb: the output of \of and
\fg depends on the language in use when they are invoked, not on the global
language; i.e.
« a » « a » « a »
^ Layout/Characters/Language American
is output as « a » ``a'' « a »
-- with the wrong quotes and one extra space. I don't know if
InsetQuotes::latex needs more tinkering around this feature, though...
JMarc
--
Yves
Index: src/insets/ChangeLog
===
RCS file: /cvs/lyx/lyx-devel/src/insets/ChangeLog,v
retrieving revision 1.142
diff -u -p -r1.142 ChangeLog
--- src/insets/ChangeLog2001/07/20 16:29:54 1.142
+++ src/insets/ChangeLog2001/07/20 23:05:53
@@ -1,3 +1,8 @@
+2001-07-21 Yves Bastide [EMAIL PROTECTED]
+
+ * insetquotes.C (latex): fix the handling of french double quotes
+ when not using the french pachage.
+
2001-07-20 Jean-Marc Lasgouttes [EMAIL PROTECTED]
* insetindex.h: shut off warning
Index: src/insets/insetquotes.C
===
RCS file: /cvs/lyx/lyx-devel/src/insets/insetquotes.C,v
retrieving revision 1.51
diff -u -p -r1.51 insetquotes.C
--- src/insets/insetquotes.C2001/07/20 09:38:18 1.51
+++ src/insets/insetquotes.C2001/07/20 23:05:53
@@ -253,18 +253,18 @@ int InsetQuotes::latex(Buffer const * bu
int quoteind = quote_index[side_][language_];
string qstr;
- if (language_ == FrenchQ times_ == DoubleQ) {
- if (doclang == frenchb) {
- if (side_ == LeftQ)
- qstr = \\og ; //the spaces are important here
- else
- qstr = \\fg ; //and here
- } else if (doclang == french) {
- if (side_ == LeftQ)
- qstr = ; //the spaces are important here
- else
- qstr = ; //and here
- }
+ if (language_ == FrenchQ times_ == DoubleQ
+doclang == frenchb) {
+ if (side_ == LeftQ)
+ qstr = \\og ; //the spaces are important here
+ else
+ qstr = \\fg{} ; //and here
+ } else if (language_ == FrenchQ times_ == DoubleQ
+ doclang == french) {
+ if (side_ == LeftQ)
+ qstr = ; //the spaces are important here
+ else
+ qstr = ; //and here
} else if (lyxrc.fontenc == T1) {
qstr = latex_quote_t1[times_][quoteind];
#ifdef DO_USE_DEFAULT_LANGUAGE
Re: Patch: version build info added.
"R. Lahaye" wrote: Jean-Marc Lasgouttes wrote: Also, Rob, you do not need to change anything in acconfig.h. Use the optional third argument of AC_DEFINE to give the description. Done; new patch attached. lyx-devel/configure.in : version output added lyx-devel/src/lyx_main.C : "-version flag" described and added lyx-devel/lyx.man: "-version" described Aah, forgot the ChangeLog patch. Added to this email! Rob. ChangeLogPatch.gz
Re: Traditional look website
It seems that some people didn't read what I wrote or maybe I didn't write enough. So here are a few reasons why what you complained about look like they do: Rob wrote: When I use the scrollbar to have a look at the bottom of the text frame, also the menu is scrolling away. Can you make the scrollbar such that it only scrolls the text frame, so that the menu on the left remains in place? Allan originally wrote: The menubar scrolls with the text because Galeon/Mozilla don't render it properly otherwise. I've done a fair bit of playing with this and it seems to be just another Mozilla bug. But I can't find a work around. The fixed menu works if you have a background image, like on the www.lyx.org site, but when I add the extra image for the background of the main text the menu is rendered with a default colour background rather than transparent. However, if I just let it float (so it scrolls) then Mozilla renders it transparent -- go figure. André Pönitz wrote: Why this different background for the border? Whey yellow on black? [I don't ask Why blue?] This was just an experiment to see what could be done. It isn't necessarily a suggested scheme for use on www.lyx.org. What a relief... The answer to your first question is included in the section of my email you quoted above. It was an experiment. What the actual image is is irrelevent. It's just an image I had lying around that I could use to see what could be done using CSS. But the following is also relevent: The images are just for testing so don't complain about them either. As for the yellow on black for the menu in Netscape: Allan originally wrote: The menu is rendered with a black background in Netscape -- the simple fixes for this we've used in the past don't seem to be working now. This is because Netscape like Mozilla above renders the menu with a default colour instead of rendering it transparent like it's supposed to be. Then Juergen chimed in with: You forgot to say that one should not complain about the background image of the text not being the whole vertical height and so it seems a bit strange seeing the text going of it's background color on the top. Otherwise it would be nice. (tested on Opera 5.0 that was the browser I had open when I read your mail) This rendering error is present in every browser I tested with (opera, NS, IE, Moz/Galeon). I tried using a setting of margin-top: -2em; but the height error varies with different browsers (some need -1em others up to -3em). Similarly they all fall short of the right page edge even though I set the margin-right: 0em;. Again this can be fixed with a negative right margin but again the distance is different for each browser. So the simplest way to get nice web pages seems to be to get everyone to use Opera. At least it does most things right. It's also the only browser I have that gets close to what the page should look like when the menu is fixed to the screen (so it doesn't scroll). BTW, it is also possible to allow the images behind the main text to scroll with the text but I thought it looked better fixed in place. But then again most browsers ignore this setting. See how tough it is to get consistent or at least acceptable page rendering across multiple browsers? Mike Ressler says: I rather like it :-) So do I. If only I could get it working across all the browsers (with the menu fixed in place again). Allan. (ARRae)
Re: Natbib
On Fri, 20 Jul 2001, Juergen Vigna wrote: On 20-Jul-2001 Dekel Tsur wrote: Well what about Export as LaTeX functionality??? So you want to use lyx on one machine, export to latex, and run latex on a second machine ? Why not do the lyx-latex conversion on the 2nd machine ? If you really need this feature, you can edit the packages.lst file. Another option is to add a lyxrc variable that controls whether the exported latex file uses uninstalled packages. Well what if: 1. The other person does not have LyX (maybe because of Windows, maybe because X11 is not installed!) 2. The other person does LaTeX only! This is exactly the situation faced by a number of LyX users in academia. Some use and love LyX but collaborate with others who insist on doing everything with a needle and thread (instead of the sewing machine sitting next to them). It was problems with this situation that caused all the rucus about getting reLyX fixed and the reason why the CCP2000 organising committee requested better import/export/reimport of LaTeX. I don't see why you need to implement a feature which will rarely be used. Because it's fun? Because people do actually need this and use it now because we assume internally that everything is available. Once proper checking is incorported into LyX then we will have a _lot_ of unhappy users (even unhappier than those annoyed with all the 666s) because they won't be able to collaborate or operate as they had been. Allan. (ARRae)
Re: Traditional look website
On Fri, 20 Jul 2001, Allan Rae wrote: > If you want to see something with too much graphics take a peek at: > http://www.elec.uq.edu.au/~rae/test.html > ... > This was just an experiment to see what could be done. It isn't > necessarily a suggested scheme for use on www.lyx.org. I rather like it :-) Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: crash importing latex
> 238 if (!init_done) {
> (gdb) bt
> #0 {anonymous}::yylex () at math_parser.C:238
> #1 0x814ea41 in mathed_parse (array=@0xbfbfe8d8, par=@0x836c21c, flags=0)
> at math_parser.C:981
^^^
There are only 853 lines in current math_parser.C so debugging this one is
difficult... If you could spare the time you could try to reproduce the
crash or simply sen me the LaTeX file.
There have been major changes in this area during the last few weeks (with
exception of the current week), so this bug might have been fixed or moved
to an other place...
Andre'
--
André Pönitz . [EMAIL PROTECTED]
Re: Traditional look website
Mike Ressler wrote: > > On Fri, 20 Jul 2001, Allan Rae wrote: > > If you want to see something with too much graphics take a peek at: > > http://www.elec.uq.edu.au/~rae/test.html > > ... > > This was just an experiment to see what could be done. It isn't > > necessarily a suggested scheme for use on www.lyx.org. > > I rather like it :-) I checked it with Opera. Very good looking layout! When I use the scrollbar to have a look at the bottom of the text frame, also the menu is scrolling away. Can you make the scrollbar such that it only scrolls the text frame, so that the menu on the left remains in place? Regards, Rob.
Re: Traditional look website
> If you want to see something with too much graphics take a peek at: > > http://www.elec.uq.edu.au/~rae/test.html Why this different background for the "border"? Whey yellow on black? [I don't ask "Why blue?"] > This was just an experiment to see what could be done. It isn't > necessarily a suggested scheme for use on www.lyx.org. What a relief... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: >> Well this is well known and as developer you should have looked at the > buglist >> on SourceForge.net ;) > > I still think that this was a sly way to get help, but anyway I've played > further. #:O) Well you won't believe it but I know since a long time the exact spot and code which is culpable for this. It is InsetTabular::resetPos()! It's just that something with that scrolling mechanism is wrong, but I don't have a good idea to fix it. So if someone has time to spare he can do some investigation and see what we can do there to fix the cycle. A fast fix would be to have a bool so that resetPos is not entered 2 times, but probably that wouldn't do the right scroll, but who knows :) Anyway I'll save the mail so that when I have time I can do this myself if noone beats me in it. I'm still working A LOT in making Find/Replace work correctly and I only have a really small bug to fix right now, but you know small bugs are hard to spot :). Anyway my local tree has in a lot of cleanups and IMO some of the bugs on SourceForge are gone now as I took the time to fix also other stuff I've seen when testing the Find/Replace stuff. One of them is the Cursor appearing outside the inset on some ocacions :) Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Penn's aunts made great apple pies at low prices. No one else in town could compete with the pie rates of Penn's aunts.
Re: Natbib
On 19-Jul-2001 Dekel Tsur wrote: > What I don't understand is why you don't want to use longtable (or other > packages) if it is available ? Maybe you have to send the latex-file to someone you know and you know he has only a minimal LaTeX installation so you exclude some stuff. Could that be a reason? But the real reason is not to not use it if you have it but to use it if you don't have it! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ The program isn't debugged until the last user is dead.
Re: Traditional look website
On 20-Jul-2001 Allan Rae wrote: > I managed to get the body and the main text to have different images > behind them. I'm also thinking it might be fun to add different images You forgot to say that one should not complain about the background image of the text not being the whole vertical height and so it seems a bit strange seeing the text going of it's background color on the top. Otherwise it would be nice. (tested on Opera 5.0 that was the browser I had open when I read your mail) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ You will lose an important disk file.
Re: Natbib
On Fri, Jul 20, 2001 at 09:21:02AM +0200, Juergen Vigna wrote: > > On 19-Jul-2001 Dekel Tsur wrote: > > > What I don't understand is why you don't want to use longtable (or other > > packages) if it is available ? > > Maybe you have to send the latex-file to someone you know and you know > he has only a minimal LaTeX installation so you exclude some stuff. Could > that be a reason? No. The other person should install the necessary packages (and most of the packages we use are standard). > But the real reason is not to not use it if you have it > but to use it if you don't have it! Can you explain this sentence?
Re: Natbib
On 20-Jul-2001 Dekel Tsur wrote: > No. The other person should install the necessary packages (and most of the > packages we use are standard). Well it's friday, but here is a * very ironic smiley * >> But the real reason is not to not use it if you have it >> but to use it if you don't have it! > > Can you explain this sentence? Sure! The real reason is, not to, not use it, if you have it, but to use it, if you don't have it! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ New Hampshire law forbids you to tap your feet, nod your head, or in any way keep time to the music in a tavern, restaurant, or cafe.
Re: Natbib announcement
On Thursday 19 July 2001 19:17, Jürgen Spitzmüller wrote: > On Thursday, 19. July 2001 16:17, Angus Leeming wrote: > > Well, now it's in head so just update and play. > > Angus > > Thanks, I got it now ;-) > > Looks great! A few comments, though: > > - Citation Dialog size is much better now, but now a little bit too > wide (about 1cm) for 800x600. Well, not really tragic but a little bit > annoying ;-) Morning Jürgen. Could you fix this at your end please by playing with fdesign form_citation.fd. I've removed all the setSize rubbish, so any changes in the .fd file are immediately apparent. > - Your WYSIWYG-Choice of the citestyle is not really WYSIWYG: The > surnames are not cited, so don't parse > Leeming, Angus (2001) > but > Leeming (2001) > if possible This is a limitation of my hacked BibTeX parser. I plan to redo this eventually using pybliographic's extremely sophisticated parser. > - In layout -> document you can choose the option Author-Year or > Numerical. But what about the other Natbib Options apart from > "numbered" (e.g. sort)? > I guess I have to insert them into Layout > Document > Document > > Options. Wouldn't a separate Options field be better? > Today there was a discussion about a dialog for all supported packages > (thread "Natbib"). I guess one pro for this dialog would be that you > could have an options-field for each of these packages (or support some > Options directly via menue). Inserting all Options from the global > options field to each and any package is not the ideal solution IMHO. > This could really lead to trouble if two packages use the same name for > an option. All very true. Surely it's not THAT hard for now to export to LaTeX and edit the usepackage command yourself. > As a "hardcore natbib user" I really like how you implemented this from > what I've seen on a first view. Thank you very much! > > I will try to help you by testing this feature as good as I can, Thank you. Angus
Re: Natbib
On Fri, Jul 20, 2001 at 10:32:05AM +0200, Juergen Vigna wrote: > > The real reason is, not to, not use it, if you have it, but to use it, > if you don't have it! I still don't understand: how can you use the longtable package if you don't have it installed ?
Re: Patch: version build info added.
On Friday 20 July 2001 07:17, R. Lahaye wrote:
> > Looks like an excellent idea. A simpler solution would probably be to
> > generate this data in a file that would be installed along with LyX.
> > This way the information would be available even when LyX cannot be
> > launched.
>
> I then would opt for both: allow a version flag to the lyx executable
> and generate a file or script ("lyx-config") with the version info.
>
> Many software handles a "-version" (and/or "--version") flag, so I
> thought it'll be useful to add this to LyX as well. For software under
> development this flag should output all necessary info for the developers.
> This output added to a bug report, could be most helpful.
Combine both ideas, so that the file is generated during compilation of lyx
and is input when running lyx -version. No need to add unnecessarily to code
bloat!
Angus
A few new things to try out
Hello there, I have just commited a bunch of small things, and would like people to try them out and comment a bit. 1/ add support for hyphenation break inset. Currently, this is just drawn as a '|' character becasue I have been lazy. I can change it to a hand drawn vertical line if needed, but I am not sure it will work well with italics. I'd appreciate if our german friends could have a look at it 2/ the index commands now use last word or selection as default value. However, I use for that the selectWordWhenUnderCursor (!) method, which ignore word when cursor is at boundary (this mean you have to be in the middle of a word). I can understand this is a problem with index, but I did not use a different method it because it is IMO a problem for font change too (the other user). So would it be OK to change the behaviour of font functions to apply to a word when cursor is at its boundary? Currently this does nothing. Also, I would like to remove one of the index menu entries. Do we really need two of them? Can someone come up with something less wordy than 'Index of preceeding word'?? Finally, strange things are bound to happen when selecting several paragraphs and trying to index that. I'll have a look. 3/ the popup for creation of .lyx directory is gone (except when you use -userdir). Should we add something to splash.lyx to explain that this directory has been created, or just assume that the user will find out soon enough? 4/ I have cleaned up the support for french style quotes. No they add automatically inner space when in french language and output the right french.sty/frenchb constructs. Should it do the same for 'canadien' (aka fr_CA)? I am not sure the typographical rules are the same over there. Also, I'd appreciate if our french friends could have a look at it. That's all for today. JMarc
Re: Natbib
On 20-Jul-2001 Dekel Tsur wrote: > On Fri, Jul 20, 2001 at 10:32:05AM +0200, Juergen Vigna wrote: >> >> The real reason is, not to, not use it, if you have it, but to use it, >> if you don't have it! > > I still don't understand: how can you use the longtable package if you > don't have it installed ? Well what about "Export as LaTeX" functionality??? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ "What do you do when your real life exceeds your wildest fantasies?" "You keep it to yourself." -- Broadcast News
Re: Natbib
On Fri, Jul 20, 2001 at 12:00:32PM +0200, Juergen Vigna wrote: > > On 20-Jul-2001 Dekel Tsur wrote: > > On Fri, Jul 20, 2001 at 10:32:05AM +0200, Juergen Vigna wrote: > >> > >> The real reason is, not to, not use it, if you have it, but to use it, > >> if you don't have it! > > > > I still don't understand: how can you use the longtable package if you > > don't have it installed ? > > Well what about "Export as LaTeX" functionality??? So you want to use lyx on one machine, export to latex, and run latex on a second machine ? Why not do the lyx->latex conversion on the 2nd machine ? If you really need this feature, you can edit the packages.lst file. Another option is to add a lyxrc variable that controls whether the exported latex file uses uninstalled packages. I don't see why you need to implement a feature which will rarely be used.
Fast question, hopefully fast answer!
Have a look at this function:
int InsetCollapsable::width_collapsed(Painter & pain, LyXFont const &) const
{
int width;
int ascent;
int descent;
pain.buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont, false,
width, ascent, descent);
return width + (2*TEXT_TO_INSET_OFFSET);
}
Could I do:
int InsetCollapsable::width_collapsed(Painter & pain, LyXFont const &) const
{
int width;
int ascent;
int descent;
PainterBase::buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont,
false, width, ascent, descent);
return width + (2*TEXT_TO_INSET_OFFSET);
}
Is it the same??
Jürgen
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED]
Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
You never know what is enough until you know what is more than enough.
-- William Blake
Re: Natbib
On 20-Jul-2001 Dekel Tsur wrote: >> Well what about "Export as LaTeX" functionality??? > > So you want to use lyx on one machine, export to latex, and run latex on a > second machine ? Why not do the lyx->latex conversion on the 2nd machine ? > If you really need this feature, you can edit the packages.lst file. > Another option is to add a lyxrc variable that controls whether the exported > latex file uses uninstalled packages. Well what if: 1. The other person does not have LyX (maybe because of Windows, maybe because X11 is not installed!) 2. The other person does LaTeX only! > I don't see why you need to implement a feature which will rarely be used. Because it's fun? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Women sometimes forgive a man who forces the opportunity, but never a man who misses one. -- Charles De Talleyrand-Perigord
Re: Fast question, hopefully fast answer!
On Friday 20 July 2001 11:19, Juergen Vigna wrote:
> Have a look at this function:
>
> int InsetCollapsable::width_collapsed(Painter & pain, LyXFont const &) const
> {
> int width;
> int ascent;
> int descent;
> pain.buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont, false,
> width, ascent, descent);
> return width + (2*TEXT_TO_INSET_OFFSET);
> }
>
> Could I do:
>
> int InsetCollapsable::width_collapsed(Painter & pain, LyXFont const &) const
> {
> int width;
> int ascent;
> int descent;
> PainterBase::buttonText(TEXT_TO_INSET_OFFSET, 0, label, labelfont,
> false, width, ascent, descent);
> return width + (2*TEXT_TO_INSET_OFFSET);
> }
>
> Is it the same??
Only if buttonText is a static method. From a quick look, it isn't. (But the
compiler will bomb out if it doesn't like it.)
Angus
Re: Fast question, hopefully fast answer!
On 20-Jul-2001 Angus Leeming wrote: > Only if buttonText is a static method. From a quick look, it isn't. (But the > compiler will bomb out if it doesn't like it.) Hmm, probably it will not work, but then it's just stupid IMO! I just want some metrics which surely are not dependant from anything (draw==false) and I'm not able to get them. IMO we should add this static methods to be able to call them without the need to pass a Painter() to the methods. This IS NEEDED if we want that InsetText is able to calculate/get the space it can draw in. As this is now it will never be able to do this! I also can explain why (as I just looked into the code to find a solution), but well let's say "just believe me". Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ One picture is worth 128K words.
[noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
> Submitted By: Nobody/Anonymous (nobody) > >Assigned to: Andre Poenitz (apoenitz) > Summary: \land and \lor are not printed on screen > > Initial Comment: > The math symbols \land and \lor are not printed on screen > > -- > > Comment By: Jean-Marc Lasgouttes (jmarc) > Date: 2001-03-01 08:00 > > Message: > Logged In: YES > user_id=116707 > > As far as I know, these are equivalent to \wedge and \vee. I have implemented them as macro without arguments. This gives correct behaviour. Some day we'd probably need some kind of distinction here... > What I do not know is whether mathed supports showing the > same symbol for several macros. If it does, other things > defined with \let in fontdefs.dtx should be aliased too. There is no such file on my harddisk. Andre'
Re: A few new things to try out
Jean-Marc Lasgouttes wrote: > > Hello there, > > 4/ I have cleaned up the support for french style quotes. No they add > automatically inner space when in french language and output the right > french.sty/frenchb constructs. Should it do the same for 'canadien' > (aka fr_CA)? Oui. << canadien >> I am not sure the typographical rules are the same over > there. Also, I'd appreciate if our french friends could have > a look at it. Georges, this has to do with the LyX document processor that I use to typeset the TWiG books. Judging from your book, Contes, légendes et chansons, the typographical rules are the same. Garst
Re: Natbib
Juergen Vigna wrote: > > On 20-Jul-2001 Dekel Tsur wrote: > > >> Well what about "Export as LaTeX" functionality??? > > > > So you want to use lyx on one machine, export to latex, and run latex on a > > second machine ? Why not do the lyx->latex conversion on the 2nd machine ? > > If you really need this feature, you can edit the packages.lst file. > > Another option is to add a lyxrc variable that controls whether the exported > > latex file uses uninstalled packages. > > Well what if: > > 1. The other person does not have LyX (maybe because of Windows, maybe because >X11 is not installed!) > > 2. The other person does LaTeX only! > > > I don't see why you need to implement a feature which will rarely be used. > > Because it's fun? all my texts have ERT, more or less. and it's the default for me that i have to export to latex and run it manually to see what's exactly going on with my text. the error-handling of lyx is sometimes not the best ... Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> I have implemented them as macro without arguments. This gives
Andre> correct behaviour. Some day we'd probably need some kind of
Andre> distinction here...
That's fine.
>> What I do not know is whether mathed supports showing the same
>> symbol for several macros. If it does, other things defined with
>> \let in fontdefs.dtx should be aliased too.
Andre> There is no such file on my harddisk.
It should be possible to install sources with teTeX. I do not know
what package, though. This is pretty useful when you want to know what
a given command actually does.
Anyway, I get here (grepping for \let to get synonyms):
fantomas: grep '\\let' /usr/local/lib/tex/doc/base/dtx/fontdef.dtx
\let\lnot=\neg
\let\land=\wedge
\let\lor=\vee
\def\neq{\not=} \let\ne=\neq
\let\le=\leq
\let\ge=\geq
\let\owns=\ni
\let\gets=\leftarrow
\let\to=\rightarrow
% \let\@@sqrt\sqrtsign
\let\|=\Vert
Reading the whole file is probably interesting too.
JMarc
Re: A few new things to try out
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: Jean-Marc> 1/ add support for hyphenation break inset. Currently, this Jean-Marc> is just drawn as a '|' character becasue I have been lazy. Jean-Marc> I can change it to a hand drawn vertical line if needed, Jean-Marc> but I am not sure it will work well with italics. I'd Jean-Marc> appreciate if our german friends could have a look at it It just occured to me that hyphenation break is a stupid name. I'll change it to 'ligature break'. JMarc
Re: Natbib announcement
On Friday, 20. July 2001 10:56, Angus Leeming wrote:
> Could you fix this at your end please by playing with fdesign
> form_citation.fd.
Hello Angus,
I've done this in fdesign and editor. Now it fits almost perfectly into
the "poor man's 800x600 screen". I've attached the diff (no, I won't
call it "Patch" this time) with the new sizes and positions (only
slight corrections on the width). Maybe it's of interest for you. I had
to edit FormCitation.C manually to get it visible. Don't know why.
Anyway, there's a diff from this, too.
[...]
> This is a limitation of my hacked BibTeX parser. I plan to redo this
> eventually using pybliographic's extremely sophisticated parser.
That's of course a very good idea! BTW: it's o.k. for me, I only
thought it *might* be confusing to users with no natbib experience. At
this point (just as an idea for the future): *If* this is somehow
possible eventually, it would be nice if the cite-labels in the text
could somehow show the citation style too.
> > - In layout -> document you can choose the option Author-Year or
> > Numerical. But what about the other Natbib Options apart from
> > "numbered" (e.g. sort)?
[...]
> All very true. Surely it's not THAT hard for now to export to LaTeX
> and edit the usepackage command yourself.
This was more a general thought at this point where LyX starts to
support more and more packages directly. Maybe it belongs to the
"Supported Packages Dialog: Yes or No" discussion which is currently
held under another topic.
Thanks,
Jürgen
BTW: I played a bit today with the new feature (all possible cite
combinations with and withour "numbered"). I really like it very much!
The only problem I encountered was a (known) Natbib bug: Upper Case
gives problems sometimes when NFSS commands are used. This does not
happen with the default natbib styles like plainnat but most likely
with selfmade (custom-bib) Styles. But I guess that is not your
business. So thanks again for this.
> Thank you.
> Angus
Index: src/frontends/xforms/form_citation.C
===
RCS file: /cvs/lyx/lyx-devel/src/frontends/xforms/form_citation.C,v
retrieving revision 1.23
diff -u -r1.23 form_citation.C
--- src/frontends/xforms/form_citation.C 2001/07/19 14:12:36 1.23
+++ src/frontends/xforms/form_citation.C 2001/07/20 11:16:52
@@ -22,12 +22,12 @@
FL_OBJECT *obj;
FD_form_citation *fdui = new FD_form_citation;
- fdui->form = fl_bgn_form(FL_NO_BOX, 860, 510);
+ fdui->form = fl_bgn_form(FL_NO_BOX, 800, 510);
fdui->form->u_vdata = this;
- fdui->box = obj = fl_add_box(FL_UP_BOX, 0, 0, 860, 510, "");
+ fdui->box = obj = fl_add_box(FL_UP_BOX, 0, 0, 800, 510, "");
{
char const * const dummy = N_("Inset keys|#I");
-fdui->browser_cite = obj = fl_add_browser(FL_HOLD_BROWSER, 10, 30, 180, 460, idex(_(dummy)));
+fdui->browser_cite = obj = fl_add_browser(FL_HOLD_BROWSER, 10, 30, 165, 460, idex(_(dummy)));
fl_set_button_shortcut(obj, scex(_(dummy)), 1);
}
fl_set_object_lalign(obj, FL_ALIGN_TOP_LEFT);
@@ -36,75 +36,75 @@
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
{
char const * const dummy = N_("Bibliography keys|#B");
-fdui->browser_bib = obj = fl_add_browser(FL_HOLD_BROWSER, 240, 30, 180, 460, idex(_(dummy)));
+fdui->browser_bib = obj = fl_add_browser(FL_HOLD_BROWSER, 225, 30, 180, 460, idex(_(dummy)));
fl_set_button_shortcut(obj, scex(_(dummy)), 1);
}
fl_set_object_lalign(obj, FL_ALIGN_TOP_LEFT);
fl_set_object_gravity(obj, FL_North, FL_SouthEast);
fl_set_object_resize(obj, FL_RESIZE_X);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui->button_add = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 30, 30, 30, _("@4->"));
+ fdui->button_add = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 30, 30, 30, _("@4->"));
fl_set_button_shortcut(obj, _("#"), 1);
fl_set_object_gravity(obj, FL_North, FL_North);
fl_set_object_resize(obj, FL_RESIZE_NONE);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui->button_del = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 65, 30, 30, _("@9+"));
+ fdui->button_del = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 65, 30, 30, _("@9+"));
fl_set_button_shortcut(obj, _("#X"), 1);
fl_set_object_gravity(obj, FL_North, FL_North);
fl_set_object_resize(obj, FL_RESIZE_NONE);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui->button_up = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 100, 30, 30, _("@8->"));
+ fdui->button_up = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 100, 30, 30, _("@8->"));
fl_set_button_shortcut(obj, _("#"), 1);
fl_set_object_gravity(obj, FL_North, FL_North);
fl_set_object_resize(obj, FL_RESIZE_NONE);
fl_set_object_callback(obj, C_FormBaseInputCB, 0);
- fdui->button_down = obj = fl_add_button(FL_NORMAL_BUTTON, 200, 135, 30, 30, _("@2->"));
+ fdui->button_down = obj = fl_add_button(FL_NORMAL_BUTTON, 185, 135,
compile problems
Hi, Am I the only one who has difficulties compiling today's cvs? Thanks, Ed. Configuration of LyX was successful. Type 'make' to compile the program, and then 'make install' to install it. Making all in intl make[1]: Entering directory `/tmp/initial/intl' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/tmp/initial/intl' Making all in po make[1]: Entering directory `/tmp/initial/po' make[1]: *** No rule to make target `all'. Stop. make[1]: Leaving directory `/tmp/initial/po' make: *** [all-recursive] Error 1
Re: Natbib announcement
On Friday 20 July 2001 13:54, Jürgen Spitzmüller wrote: > On Friday, 20. July 2001 10:56, Angus Leeming wrote: > > Could you fix this at your end please by playing with fdesign > > form_citation.fd. > > Hello Angus, > > I've done this in fdesign and editor. Now it fits almost perfectly into > the "poor man's 800x600 screen". I've attached the diff (no, I won't > call it "Patch" this time) with the new sizes and positions (only > slight corrections on the width). Maybe it's of interest for you. I had > to edit FormCitation.C manually to get it visible. Don't know why. > Anyway, there's a diff from this, too. Many thanks. I'll commit this to the repository. For future information: to get the changes into form_citation.C, you have to type "make updatesrc" in the forms subdirectory. > > This is a limitation of my hacked BibTeX parser. I plan to redo this > > eventually using pybliographic's extremely sophisticated parser. > > That's of course a very good idea! BTW: it's o.k. for me, I only > thought it *might* be confusing to users with no natbib experience. At > this point (just as an idea for the future): *If* this is somehow > possible eventually, it would be nice if the cite-labels in the text > could somehow show the citation style too. Again, this will wait till we have a proper BibTeX class. It's in my wanted list too. > > > - In layout -> document you can choose the option Author-Year or > > > Numerical. But what about the other Natbib Options apart from > > > "numbered" (e.g. sort)? > [...] > > All very true. Surely it's not THAT hard for now to export to LaTeX > > and edit the usepackage command yourself. > > This was more a general thought at this point where LyX starts to > support more and more packages directly. Maybe it belongs to the > "Supported Packages Dialog: Yes or No" discussion which is currently > held under another topic. Sure. The nice thing about coding LyX has been that it's taught me that the elegant solution is the right solution almost always. Lars has been a pretty good teacher in this regard. > BTW: I played a bit today with the new feature (all possible cite > combinations with and withour "numbered"). I really like it very much! > The only problem I encountered was a (known) Natbib bug: Upper Case > gives problems sometimes when NFSS commands are used. This does not > happen with the default natbib styles like plainnat but most likely > with selfmade (custom-bib) Styles. But I guess that is not your > business. So thanks again for this. My pleasure. Angus
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
> > Anyway, I get here (grepping for \let to get synonyms): > > fantomas: grep '\\let' /usr/local/lib/tex/doc/base/dtx/fontdef.dtx > \let\lnot=\neg >\let\land=\wedge >\let\lor=\vee Ok, I'll put that on my todo list. I don't really like the current macro hack, so I'll wait with the rest until the "infrastructure" is ready.. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
On Fri, Jul 20, 2001 at 01:05:06PM +0200, Andre Poenitz wrote: > > What I do not know is whether mathed supports showing the > > same symbol for several macros. If it does, other things > > defined with \let in fontdefs.dtx should be aliased too. > > There is no such file on my harddisk. That's because you don't have the unstripped source on your harddisk. All the stuff from fontdefs goes into .ltx files. I think it is probably all in fontmath.ltx and fonttext.ltx. Also I would draw your attention to my comments a month or so ago about using latex itself to work out which glyph an unknown sequence should be represented by Jules
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: >> Anyway, I get here (grepping for \let to get synonyms): >> >> fantomas: grep '\\let' /usr/local/lib/tex/doc/base/dtx/fontdef.dtx >> \let\lnot=\neg \let\land=\wedge \let\lor=\vee Andre> Ok, I'll put that on my todo list. I don't really like the Andre> current macro hack, so I'll wait with the rest until the Andre> "infrastructure" is ready.. You could maybe have these macros in a lyx file which you read from disk :) JMarc
Re: compile problems
> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes: Edwin> Hi, Am I the only one who has difficulties compiling today's Edwin> cvs? Edwin> Thanks, Ed. Edwin> Configuration of LyX was successful. Type 'make' to compile the Edwin> program, and then 'make install' to install it. Making all in Edwin> intl make[1]: Entering directory `/tmp/initial/intl' make[1]: Edwin> Nothing to be done for `all'. make[1]: Leaving directory Edwin> `/tmp/initial/intl' Making all in po make[1]: Entering Edwin> directory `/tmp/initial/po' make[1]: *** No rule to make target Edwin> `all'. Stop. make[1]: Leaving directory `/tmp/initial/po' make: Edwin> *** [all-recursive] Error 1 It maigh be my fault. I removed the generation of po/Makefil from po/Makefile.in because the doc from gettext 0.10.38 did not say it is needed (so I thought it worked differently). Does reverting the following patch help? JMarc
Re: compile problems
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes: Edwin> Hi, Am I the only one who has difficulties compiling today's Edwin> cvs? Edwin> Thanks, Ed. Edwin> Configuration of LyX was successful. Type 'make' to compile the Edwin> program, and then 'make install' to install it. Making all in Edwin> intl make[1]: Entering directory `/tmp/initial/intl' make[1]: Edwin> Nothing to be done for `all'. make[1]: Leaving directory Edwin> `/tmp/initial/intl' Making all in po make[1]: Entering Edwin> directory `/tmp/initial/po' make[1]: *** No rule to make target Edwin> `all'. Stop. make[1]: Leaving directory `/tmp/initial/po' make: Edwin> *** [all-recursive] Error 1 Jean-Marc> It maigh be my fault. I removed the generation of Jean-Marc> po/Makefil from po/Makefile.in because the doc from gettext Jean-Marc> 0.10.38 did not say it is needed (so I thought it worked Jean-Marc> differently). Jean-Marc> Does reverting the following patch help? OK, it seems that I do not know how to attach files with my new Gnus... Here it is JMarc Index: configure.in === RCS file: /usr/local/lyx/cvsroot/lyx-devel/configure.in,v retrieving revision 1.71 retrieving revision 1.72 diff -u -r1.71 -r1.72 --- configure.in2001/07/05 14:00:36 1.71 +++ configure.in2001/07/19 15:32:12 1.72 @@ -313,7 +313,7 @@ src/frontends/xforms/Makefile \ src/frontends/qt2/Makefile \ src/frontends/gnome/Makefile \ -], [sed -e "/POTFILES =/r po/POTFILES" po/Makefile.in > po/Makefile]) +]) cat <
Re: A few new things to try out
On Friday, 20. July 2001 11:52, Jean-Marc Lasgouttes wrote: > 1/ add support for hyphenation break inset. Currently, this is just > drawn as a '|' character becasue I have been lazy. I can change it to > a hand drawn vertical line if needed, but I am not sure it will work > well with italics. I'd appreciate if our german friends could have > a look at it Well... Looks good and seems to do the things it has to. The '|' character is sufficient IMO. I can live with the \textcompwordmark in the output. So: very nice!!! Thank you. It would be nice if you could bind it for the final release. BTW: - It's impossible to insert an ordinary quote " into the 666-inset at the moment - Marking Text and clicking on the TeX-Button does not insert the marked text into the 666 inset. Greets, Jürgen > JMarc
Re: A few new things to try out
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: Jürgen> On Friday, 20. July 2001 11:52, Jean-Marc Lasgouttes wrote: >> 1/ add support for hyphenation break inset. Currently, this is just >> drawn as a '|' character becasue I have been lazy. I can change it >> to a hand drawn vertical line if needed, but I am not sure it will >> work well with italics. I'd appreciate if our german friends could >> have a look at it Jürgen> Well... Looks good and seems to do the things it has to. The Jürgen> '|' character is sufficient IMO. I can live with the Jürgen> \textcompwordmark in the output. So: very nice!!! Thank you. Jürgen> It would be nice if you could bind it for the final release. Propose bindings :) Jürgen> BTW: - It's impossible to insert an ordinary quote " into the Jürgen> 666-inset at the moment ordinary quotes are somewhat broken right now. Jürgen> - Marking Text and clicking on the TeX-Button does not insert Jürgen> the marked text into the 666 inset. This could probably be added as a general feature of collapsable insets creation. JMarc
Re: [noreply@sourceforge.net: [ lyxbugs-Bugs-233242 ] \land and \lor are not printed on screen]
> Andre> Ok, I'll put that on my todo list. I don't really like the > Andre> current macro hack, so I'll wait with the rest until the > Andre> "infrastructure" is ready.. > > You could maybe have these macros in a lyx file which you read from > disk :) I think I'd rather go for a proper 'symbol inset'. This wastes a few bytes in comparison to the current 'inline symbols' but simplifies overall structure and offers a multitude of opportunities (we could have latex name, X glyph, Unicode, and &*ML; encoding all in one place...) Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: A few new things to try out
On Friday, 20. July 2001 15:43, Jean-Marc Lasgouttes wrote: > Propose bindings :) C-S-L -- control-silly-ligatures ;-) AFAIK it's not used at the moment. Jürgen.
Re: Proposal: remove the 'create new .lyx directory?' popup
> "Lior" == Lior Silberman <[EMAIL PROTECTED]> writes: Lior> On 9 Jul 2001, Jean-Marc Lasgouttes wrote: >> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes: >> Dekel> I'm not sure that this is a good idea when the -userdir flag is Dekel> used. What if I just misspelled the userdir name ? >> Well, people using -userdir are supposed to know what they are >> doing :) And all you have to do is "rm -r" the directory. >> >> The reason why I want to remove the popup is also that it is buggy: >> with some window manager, it is not possible to have a modal dialog >> without a main window, and the buttons cannot be clicked on. >> >> JMarc >> Lior> When you misspell the -userdir parameter, the concern is that Lior> you'll get the wrong configuration, and take a while to notice Lior> it. Removing the directory is just an annoyance. Lior> I think we need to silently create the directory, except in the Lior> case of an explicit_userdir (change the logic in lyx_main.C so Lior> only a -userdir flag counts as explicit, not the environment Lior> variable). In the case the user asked for a nonexistent Lior> directory, we can help him and make sure everything is OK. I did that. JMarc
Re: Patch LyX 1.1.6fix3: use frenchb guillemets
> "Yves" == Yves Bastide <[EMAIL PROTECTED]> writes: Yves> Hi, Here's a proposed patch to use frenchb's guillemets \og and Yves> \fg (which have proper spacing) when using frenchb. The current Yves> code does it only when fontenc != T1 -- not frequent among Yves> French writers (: Yves> (This patch is for 1.1.6; I can prepare another for -devel if Yves> accepted.) Yves, could you checkwhat I did for 1.2.0? If it works well, I may adapt it to 1.1.6 too. JMarc
Re: compile problems
> Jean-Marc> It maigh be my fault. I removed the generation of > Jean-Marc> po/Makefil from po/Makefile.in because the doc from gettext > Jean-Marc> 0.10.38 did not say it is needed (so I thought it worked > Jean-Marc> differently). I have 0.10.38 installed. > Jean-Marc> Does reverting the following patch help? > OK, it seems that I do not know how to attach files with my new > Gnus... > Here it is Didn't arrive as nice attachment either. I inserted by hand: ], [sed -e "/POTFILES =/r po/POTFILES" po/Makefile.in > po/Makefile]) instead of ]) still didn't work. gr.ed.
RE: CVS Update: lyx-devel
On 20-Jul-2001 [EMAIL PROTECTED] wrote: > Implemented Search/Replace functionality for Insets. Cleaned up a bit. > Small fixes. With this I think we implemented all the requested features which where missing since the change to insets: font-change, s+r & spellchecking. I tested the last quite a bit and have small problems with insets inside insets if both are going over the screenborder and I have to readjust, but IMO this are minor glitches, the functions should work. Jürgen P.S.: I used up a lot of time implementing all this features and left my real work stack up on my table. This means that for the next time I will have to giv'em 99% of my time, so I will do only really needed bugfixes all other stuff will go into my todo folder! P.P.S.: Have a nice weekend! -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ No rock so hard but that a little wave May beat admission in a thousand years. -- Tennyson
Re: compile problems
> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes: Edwin> still didn't work. I'm not surprised now that I have re-read gettext configure script. Do you have a po/Makefile? What did configure say when creating everything (in the list of 'creating foo' in the console output). JMarc
