Re: [PATCH] Initial support for the memoir class
On Mon, 2003-09-22 at 03:56, Angus Leeming wrote: > Just a thought, but is there any sense in the commit privileges to lyxdoc > vis-à-vis lyx-devel? > > avail|larsbj,mressler,lasgouttes,karger,rae,levon|lyxdoc > avail|larsbj,lasgouttes,jug,rae,jamatos,alstrup,poenitz,dekel,leeming,levon,abra > unst,vermeer,spitz|lyx-devel > > I say this in light of the apparent death of the documentation team. > Not dead, just quiet and busy and cursing the day Bill Gates was born. I still scan the list, but real life has intruded to the point where I don't even get to use LyX very often. Because I'm now working on an flight project with international collaboration, Word/Powerpoint has been mandated, so that is what I use formally. However, I have installed the MacOSX version of LyX on the same machine I use for MSOffice, so a few LyX-generated PDFs might start slipping into our documentation tree ;-) If people send me doc-related patches, I'd be happy to keep submitting them to CVS. Also, if there are any glaring deficiencies in the docs, let me know - I can try to fix them, just not with the speed I used to. I don't have time to keep up with all the changes on my own, though, so I need to be pointed to things. Just a fact of life ... Mike [EMAIL PROTECTED]
Patches to update AASTeX support
Hello,
It's been a long time since I've been able to contribute anything to
LyX, though I still scan through the mailing lists. I only get to use it
once in a blue moon - my project dictates M$ Office for everything.
However, I've been able to figure out how to force Word to behave a bit
more like LyX :-)
Attached are some patches to update LyX's AASTeX support to AASTeX-5.2.
There are separate patches to aastex.layout and to Extended.lyx - both
are against lyx-1.3.5; please don't beat me up.
I've been tracking some of the doc discussions. Because real life has
more than caught up with me, my name should be removed from all the docs
where I am listed as maintainer ([EMAIL PROTECTED]). My ability
to do anything isn't likely to improve any time soon. Sorry guys.
Mike
P.S. In the 2nd to last section of Extended (7.6 Non-standard Paragraph
Shapes), please put a page break immediately before the section title,
so that the funky paragraph is guaranteed to be on one page, not split
over two like it is now. Thanks.
Mike Ressler
[EMAIL PROTECTED]
*** /usr/share/lyx/layouts/aastex.layout 2004-11-16 00:43:27.0 -0800
--- aastex.layout 2004-05-06 23:40:56.0 -0700
***
*** 27,32
--- 27,33
# example files are available.
# Version 1.1 7/25/99 - Changed \url to take advantage of new layout option.
# Version 1.2 4/18/02 - Updated for natbib in 1.2.0
+ # Version 1.3 5/7/04 - Updated for AASTeX 5.2
# General textclass parameters
Columns 1
***
*** 117,122
--- 118,129
End
Style NoteToEditor
End
+ Style Facility
+ End
+ Style Objectname
+ End
+ Style Dataset
+ End
# OK, now we have a more or less consistent Ordering. Now fill the
# definitions.
***
*** 520,526
MarginFirst_Dynamic
LatexType Command
LatexName figcaption
- LatexParam [FileName]
LabelSep xx
ParSkip 0.4
TopSep0.5
--- 527,532
***
*** 528,531
--- 534,619
AlignPossible Block, Left
LabelType Static
LabelString "Fig. --- "
+ OptionalArgs 1
+ End
+
+ # Facility style definition
+ Style Facility
+ LeftMargin MMM
+ Margin Dynamic
+ LatexType Command
+ InTitle 0
+ LatexName facility
+ ParSkip 0.4
+ BottomSep 0.4
+ Align Block
+ AlignPossible Block, Left, Right, Center
+ LabelType Static
+ LabelSep M
+ LabelString "Facility:"
+ Font
+ Family Roman
+ Shape Up
+ Size Normal
+ EndFont
+ LabelFont
+ Family Roman
+ Shape Italic
+ Size Normal
+ EndFont
+ End
+
+ # Objectname style definition
+ Style Objectname
+ LeftMargin MMM
+ Margin Dynamic
+ LatexType Command
+ InTitle 0
+ LatexName objectname
+ ParSkip 0.4
+ BottomSep 0.4
+ Align Block
+ AlignPossible Block, Left, Right, Center
+ LabelType Static
+ LabelSep M
+ LabelString "Obj:"
+ OptionalArgs 1
+ Font
+ Family Roman
+ Shape Up
+ Size Normal
+ EndFont
+ LabelFont
+ Family Roman
+ Shape Italic
+ Size Normal
+ EndFont
End
+
+ # Dataset style definition
+ Style Dataset
+ LeftMargin MMM
+ Margin Dynamic
+ LatexType Command
+ InTitle 0
+ LatexName dataset
+ ParSkip 0.4
+ BottomSep 0.4
+ Align Block
+ AlignPossible Block, Left, Right, Center
+ LabelType Static
+ LabelSep M
+ LabelString "Dataset:"
+ OptionalArgs 1
+ Font
+ Family Roman
+ Shape Up
+ Size Normal
+ EndFont
+ LabelFont
+ Family Roman
+ Shape Italic
+ Size Normal
+ EndFont
+ End
+
*** /usr/share/lyx/doc/Extended.lyx 2004-11-16 00:43:21.0 -0800
--- Extended.lyx 2005-02-03 16:12:18.805945592 -0800
***
*** 5059,5072
publish: the Astrophysical Journal (including the Letters and Supplement),
the Astronomical Journal, and the Publications of the Astronomical Society
of the Pacific.
! LyX requires version 5.0 (or higher) of these macros.
Versions prior to 5.0 are intended for use with LaTeX2.09 and are fundamentally
incompatible with LyX.
! The AASTeX package may be downloaded from the AAS's ftp site
\layout Standard
\added_space_top medskip \added_space_bottom medskip \align center
! \begin_inset LatexCommand \url{ftp://ftp.aas.org/pubs}
\end_inset
--- 5059,5075
publish: the Astrophysical Journal (including the Letters and Supplement),
the Astronomical Journal, and the Publications of the Astronomical Society
of the Pacific.
! LyX has proven to be an excellent tool for generating these documents,
! especially given its equation, citation, and figure handling capabilities.
! LyX requires version 5.0 (or higher) of these macros; preferably 5.2, which
! is the versi
Re: Patches to update AASTeX support
On Tue, 2005-02-08 at 17:11 +0100, Jean-Marc Lasgouttes wrote: > >>>>> "Mike" == Mike Ressler <[EMAIL PROTECTED]> writes: > Mike> P.S. In the 2nd to last section of Extended (7.6 Non-standard > Mike> Paragraph Shapes), please put a page break immediately before > Mike> the section title, so that the funky paragraph is guaranteed to > Mike> be on one page, not split over two like it is now. Thanks. > > Hmm, is it really a problem to have it on several pages? Yes, because you lose the "flying wing" shape effect. Look at the DVI preview - I'll think you'll appreciate my point :-) Thanks for checking in the patches. Mike -- Mike Ressler [EMAIL PROTECTED]
Re: The LyX licence
Angus et al., I hereby grant permission to licence my contributions to LyX under the GNU General Public Licence, version 2 or later. -- Mike Ressler [EMAIL PROTECTED]
Re: Command line .lyx to .tex converter?
On Wed, 3 May 2000, Andre Poenitz wrote: > > Well the black magic is easy (the following with bash): > > > (Xvfb :1 -once -terminate &);rm myfile.tex; lyx -display :1 --export latex >myfile.lyx > > > This works everywhere (obviously you have to have the Xvfb command), xterminal > > on a text-console an xterminal, ... > > Could this go in the recently revived FAQ? It will - give me a couple of days though ... Mike Ressler [EMAIL PROTECTED]
Please commit attached file to examples directory
Hi,
I added a discussion of dcolumn to Extended as suggested some time ago. I
need someone with main CVS access to commit the attached decimal.lyx file
to the .../examples directory. Thanks.
Mike
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 2.16
\textclass article
\begin_preamble
\usepackage{dcolumn}
\newcolumntype{d}[1]{D{.}{.}{#1}}
\end_preamble
\language default
\inputencoding latin1
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Title
A Better Decimal-Alignment Solution
\layout Standard
An alternative way to have decimal alignment in tables is through the dcolumn
package.
Add the following to the LateX preamble:
\layout LyX-Code
\backslash
usepackage{dcolumn}
\layout LyX-Code
\backslash
newcolumntype{d}[1]{D{.}{.}{#1}}
\layout Standard
To have a column decimally aligned, enter in the
\family sans
Special Column Alignment
\family default
box of the
\family sans
Table extra
\family default
form the following:
\layout LyX-Code
d{number of decimals of the data}
\layout Standard
In the following table we entered
\family typewriter
d{4}
\family default
:
\layout Standard
\added_space_top 0.3cm \added_space_bottom 0.3cm \align center \LyXTable
multicol5
5 2 0 0 -1 -1 -1 -1
0 1 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
8 0 0 "" ""
4 1 0 "" "d{4}"
0 8 1 0 0 0 0 "" ""
1 8 0 1 0 0 0 "" ""
0 8 1 0 0 0 0 "" ""
1 4 0 0 0 0 0 "" ""
0 8 1 0 0 0 0 "" ""
0 8 1 0 0 0 0 "" ""
0 8 1 0 0 0 0 "" ""
0 8 1 0 0 0 0 "" ""
0 8 1 0 0 0 0 "" ""
0 8 1 0 0 0 0 "" ""
Expression
\newline
Value
\newline
\begin_inset Formula \( \pi \)
\end_inset
\newline
3.1416
\newline
\begin_inset Formula \( \pi ^{\pi } \)
\end_inset
\newline
36.462
\newline
\begin_inset Formula \( (\pi ^{\pi })^{\pi } \)
\end_inset
\newline
80663.
\newline
\begin_inset Formula \( \pi ^{\pi ^{\pi }} \)
\end_inset
\newline
1.3402e18
\layout Standard
To create extra column space just increase the number of decimals in
\family typewriter
d{}
\family default
.
Setting the multicolumn attribute for a single cell makes it insensitive
to the decimal alignment which comes in handy as well.
A drawback of this method is that math mode is not allowed in a column
with decimal alignment except if the multicolumn attribute is set.
\layout Standard
This method offers the same flexibility as the
\family typewriter
dcolumn
\family default
package.
One could, for example, change the alignment separator, and have different
alignment separators for different columns by defining multiple column
types in the preamble.
The syntax is as follows:
\layout LyX-Code
D{inputsep}{outputsep}{decimal places}
\layout Standard
The interested reader is directed towards the
\family typewriter
dcolumn
\family default
package documentation for more details.
\the_end
New FAQ committed
Hi, I've committed a new version of the FAQ. It's probably about time to make this available on the Web site as an HTML page. The tth conversion I tinkered with looked okay except for a few math mistakes. How should we do this? Can a link be made so that a FAQ pointer in the "Navigate" table points to an HTML file in the lyxdoc CVS repository? I can do the conversion, but I don't have (or really want) CVS access the web site. Thoughts? Changes since last version are extensive: spellchecked (ahem!) added book and journal references to 1.2 added precompiled binaries info reorganized question sections answers added: word counting horizontal space command line LyX->LaTeX conversions other minor rewording improvements Expect lots more changes over the next week. This is just my way of backing up my work. :-) Mike
Re: Report from the beer-festivitiesch [burp]
On Sat, 10 Jun 2000, Asger K. Alstrup Nielsen wrote: > you are All WAITING for the FirSt report from the FILM festitifvities > from Norawy. Her goes: [ ... ] Good thing FILM is a coding meeting, not a documentation meeting. You don't have to spell anything correctly, just consistently. I expect to see some rather interesting looking code based on the obvious influence of the first day's festivities! ;-) Mike
Another new Extended and FAQ
Just some minor FAQ twiddling, but many Extended additions. A bit of reorganizing, plus the following additions: Cross-referencing in multiple documents Importing/Export various formats Non-traditional paragraph shapes (all ERT) Mike
Updated FAQ again
Just a few minor twiddles and the answer to the multiple cite question. I would still like to make an HTML-ized version of this available on the Web site. How should this be accomplished? -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Ghostscript not rendering again
Hi, Okay, I'm annoyed again. Ghostscript rendering seems to hang up again in 1.1.5; the last several versions didn't seem to have this problem. I'm working on a simple talk (FoilTeX based) with 5 PostScript figures, all in the 1-2 MB range. Doing a "ps" yields three gs processes, all of which are identified as . Once in a blue moon, quiting lyx and restarting it will work, but the failures are usually pretty consistent. Any suggestions? LyX-1.1.5, gs-6.01, linux-2.2.14 (Mandrake 7.0), etc. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Addendum: Ghostscript not rendering again
On Fri, 23 Jun 2000 [EMAIL PROTECTED] wrote: > Okay, I'm annoyed again. Ghostscript rendering seems to hang up again in > 1.1.5; the last several versions didn't seem to have this problem. I'm I just discovered that starting lyx by itself, then loading the file with File->Open or the last file list works just fine. It's only when I start LyX with the filename on the command line that things fail, e.g. "lyx qwips.lyx" fails. I did this numerous times to make sure I wasn't imagining things, but I had 5 for 5 failures with the command line, and 5 for 5 successes loading the file after LyX had been started. Happy debugging. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Addendum: Ghostscript not rendering again
On Fri, 23 Jun 2000 [EMAIL PROTECTED] wrote: > I just discovered that starting lyx by itself, then loading the file with > File->Open or the last file list works just fine. It's only when I start This may be a red herring. After changing a few parameters, it fails all the time again ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Patch: better multi-lingual support
On 5 Jul 2000, Jean-Marc Lasgouttes wrote: > If using language "default" (i.e. no babel) causes too many problems > (it seems that babel does not allow to return to the state before its > loading) what is sure is that default language shold not be american > english nor british english, but simply _english_. This should > certainly have been fixed before releasing 1.1.5, since now people > have files referring to this nonsensical "american". Aren't "nonsensical" and "american" usually used together when describing my countrymen? :-) Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Some questions
Hello, I'm copying your message and my response to the LyX developer list for comment. I am just a humble document writer; I leave coding to people who know what they're doing. However, I do want to comment on a few things before I let them have at it ... LyX is not the tool you are looking for. LyX excels at creating publishable textual and mathematical documents (which may include figures, of course) by serving as the front end for a markup language known as LaTeX. LyX is not a page design tool; the page layout is done by LaTeX which in turns calls TeX. If LaTeX cannot handle what you want to do, LyX will not be able to do it at all. #1: Again, LyX is WYSIWYM - What You See Is What You Mean - not WYSIWYG. LyX gives you visual clues as to what the document will look like, not actually laying it out that way. #3: This may be doable with PSTricks, but certainly not "natively". #10 and #12: These two points show exactly why LyX is not the right tool. Guides, rules, and layers are completely antithetical to the markup language approach that LyX (because of LaTeX) chooses to use. One marks something as a "section" in LyX - you don't tell LyX how or where to place that on the page. #14: These are called Layouts and are fundamental to LyX. There are a few good ideas here which is why I'm forwarding to the LyX Developer list. However, if you are doing magazine page layout, LyX is simply not the right tool for the job. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ... On Thu, 27 Jul 2000, Bodvar Bjorgvinsson wrote: > Dear all of you fine people, who are doing such a good job and working so > hard at the LyX project, > > I have been testing LyX from time to time since mid-winter and I like it a > lot and even think it may become a real breakthrough, but I think it needs > much more flexibility and new tools. > > What I have been looking for is a Linux replacement for Adobe PageMaker6.5 > (which I use a lot) or even QuarkXpress (maybe too much to ask for ;-) ). > > What I would see in LyX (or Klyx) and cannot see that you got, is: > > 1) Better WYSIWYG. > > 2) More scaling of fonts (e.g., above 72 points). > > 3) Slanting of a selection in various degrees (like if you have a 60 pt. > text and select a word out of it, or even one letter and slant it some 30 > degrees back or forth). > > 4) Text boxes and/or text frames that can be linked so that the text flows > from one box to another. The boxes need to be able to be set to accurate > measure. > > 5) Object/picture boxes that can be set to accurate measures and where the > object can be easily resized, slanted, cropped (read: partly hidden) etc. > > 6) Maybe some automatic linking to Gimp in order to work with objects. > > 7) Import of tables from Siag or some other spread sheet application > (StarCalc, Quattro), either linked or direct if not both. > > 8) Color management (create color for filling etc). > > 9) Multiple master pages (to create different page formats within the > publication). > > 10) Layers. 3-4 layers would be very handy to work with when you have to > make a nice looking magazine page. :-) Or when you are working with > complicated forms that need to be revised frequently: Lines and boxes in one > layer, main text in another, and some other thing in the third. You really > need this when you have a lot of text boxes, lines and other stuff that can > be grouped and/or selected together and moved around. > > 11) Better line/box editor (or maybe there was none at all?) > > 12) Guides and Rulers (adjustable and possible to use from Master Page(s). > > 13) Insert pages at a given point. (Why should we need the M$Word approach: > to fill in text and spaces or use hard brake for a new page?) > > 14) Possibility to make (easily) your own styles (style sheets). > > It seems to me that WP8 comes in some ways closer to the above requests than > LyX does. However, I think it is wonderful to see a tool that is built from > ground up as a professional tool sticking to strict rules. I am not familiar > with LaTeX, but from what I have seen, LaTeX should not have much problem > with most of these requests, that is, if it is as professional as stated. I > have worked with the QuarkXpress and PageMaker (several verisions) as well > as some specific typesetting machines (like the _old_ CompuGraphic > PowerView10, which was a great breakthrough). > > I know what I would like to see here, but I am not enough acquainted with > LaTeX or programming languages, to be able to imagine whether it is possible > to make all these changes to LyX. > > 15) One more thing I would like to see, that PM does not have: ability to > open (import or place) a ready made Pos
Re: lyx graphical tour
On Wed, 5 Feb 2003, Juergen Spitzmueller wrote: > Angus Leeming wrote: > > 'I strongly suggest you use the middle mouse button (in Netscape) to open > > the image in a new browser window to avoid losing your place' > > Well, this is the original "historical" text. I guess the 1999 unix browsers > were slightly less comfortable. Wow! People are arguing about my old Graphical Tour. Cool! When I wrote the original LGT, I was using a Sun Sparc 5 with some old Netscape browser, and it took _forever_ to load one of those pages. In these days with 2 GHz processors, pop-ups (and blockers), PHP, and whatever else, I'm sure one of you kids can come up with something a lot spiffier. I suggest that you use the old LGT only as a guiding philosophy for the new one. Rewrite the whole thing (and grab all new screenshots) as necessary in order to show off LyX in the best light. My old xdvi shots with your new LyX shots look a bit funny. I might even be able to help a little bit if you want, though my time available to tinker with LyX over that last year has dropped to near zero :-( The hazards of real life intruding ... But I'm definitely glad to hear the LGT lives on! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Documentation is going to be way out of date for 1.1.6 ...
Hi guys, (Yes, I'm still alive.) I had a chance to compile 1.1.6pre1 after having ignored the blizzard of CVS changes recently. I really like what I see, but as the erstwhile documentation person, I foresee the need for huge documentation updates - more than I can possibly do by myself if the documentation for 1.1.6 proper is to be up-to-date. If you would like to contribute to the documentation, now is the time to raise your hand. Read DocStyle.lyx in .../lyx-1.1.x/lib/doc and let me know what you'd like to do. Developers - you are not off the hook either; I need you to let us know what has changed in the human interface (I don't care about all the internal guts changes) so that we catch everything. Remember that at least a small part of what makes LyX so good is that it is well documented ... Mike - speaking for the Doc Team -- Mike Ressler [EMAIL PROTECTED]
CVS compile failure
Trying to compile CVS (for better or worse - bumped into the following: (Mandrake 7.0, gcc 2.95.2, xforms-0.88, etc.) g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost-isystem /usr/X11R6/include -O2 -W -Wall -Wconversion -Winline -c trans.C In file included from /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2/../../../../include/g++-3/map:31, from language.h:19, from lyxfont.h:22, from layout.h:22, from LyXView.h:25, from trans.C:7: /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2/../../../../include/g++-3/stl_tree.h: In function `int __black_count(_Rb_tree_node_base *, _Rb_tree_node_base *)': /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2/../../../../include/g++-3/stl_tree.h:1258: warning: can't inline call to `int __black_count(_Rb_tree_node_base *, _Rb_tree_node_base *)' /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2/../../../../include/g++-3/stl_tree.h:1266: warning: called from here trans.C: In method `void Trans::AddDeadkey(tex_accent, const string &, const string &)': trans.C:175: no matching function for call to `basic_string,__default_alloc_template >::push_back (char)' trans.C:176: no matching function for call to `basic_string,__default_alloc_template >::push_back (char &)' make[3]: *** [trans.o] Error 1 I see the "can't inline" error frequently, but the "no matching function" occurs only for this file. -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: docs for 1.1.6: What strategy?
On Sat, 11 Nov 2000, R. Lahaye wrote: > I believe 1.1.6 will have a big impact on the docs. > So many things have changed (dialogs, menus, bug-fixes etc.). > > The docs in cvs are according to the current official release > of 1.1.5, but they can't be modified to 1.1.6 overnight after > its official release!! Greetings, This snippet appeared in the lyx-docs list a week or so ago, and echoes the concerns I expressed in the devel group a few weeks back. Since I have actually received at least one doc patch from a developer specific to 1.1.6 (name withheld to protect his developer reputation :-), I would like to formally request that a new CVS branch be made for lyxdoc - probably with "lyxdoc" for the new documentation and "lyxdoc_1.1.5" for the 1.1.5 stuff, similar to the source code branches, and with the same user access as now. Lars, (and/or whoever else controls this stuff), can this be done soon? (Is this something that I could in principle do? I'm pretty ignorant of the magic of CVS ...) Any arguments to the contrary? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: External Material and the menubar
> > On Tue, Nov 21, 2000 at 04:49:41PM +, Angus Leeming wrote: > > > You tell me. It's in lib/doc/ of CVS. It's also in my LyXDir/doc > > > directory, but that may be because I put it there by hand. SOMEBODY wrote > > > it and it should be installed IMO. > > > > > > Of course, I know absolutely nothing... > > > > Ah! I forgot all about this. > > > > I think it's probably supposed to be included as a chapter/section in > > Extended, no? Why make it a separate doc? I'll have a look at it and merge it if it all makes sense. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Section number depth weirdness
Hi, I'm preparing a number of corrections to the User Guide sent to me some time ago by Giacomo Comes. He notes that in section 3.3.4.3 of the User Guide, it describes depths ranging from -1 to 5, yet the Layout->Document popup allows it to range from -2 to 5 (the TOC range is -1 to 5). Bug or feature? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Another doc/feature discrepancy
Hi again, Still working on my lengthy list of changes to UserGuide (for 1.1.5fix2). The font size changing shortcuts don't seem to be working, e.g. M-s t for tiny-font. Apparently, some message is being written to the lyx-buffer, but it is immediately overwritten by "Font: Default", so that I get only the slightest glimpse of it. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Two more documentation issues
Hi, Sorry to keep pestering, but I'd like to finish this up correctly. Does anyone know what exactly the language setting does in the Layout->Character popup? (Beyond the obvious "it underlines the word".) Also, for Insert->Cross Reference, can someone send me a description of what vReference, vPage Number, and Pretty Ref do, that regular references and page numbers don't? Thanks. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Doc updates for 1.1.6
Greetings, I have followed Lars' instructions and created a branch off of the lyxdoc CVS module called lyxdoc-1_1_5-updates. Any changes relevant to LyX-1.1.5fixN should go there and should be edited only with lyx-1.1.5fixN! The main branch of lyxdoc is being changed to be relevant to 1.1.6 and should be edited only with 1.1.6pre2 or later. I have patched in Angus' modifications of Customization and UserGuide and added an appropriate caveat to UserGuide about the updating process. I have also appended the infamous ExternalMaterial.lyx to Customization as Chapter 8. I will work it into the text more properly as time permits. Correspondingly, lyx-devel/lib/doc/ExternalMaterial.lyx should be nuked. It was a productive lunch break today ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Doc updates for 1.1.6
On 28 Nov 2000, Lars Gullik Bjønnes wrote: > I not sure if I have the time to help a lot, but I will at least read > through the 1.1.6 documentation and comment on sections that are > wrong/missing or in need of a touch up. I'll send you a text snippet > when I see these. There have not been many changes yet beyond Angus' work (which is substantial, however!), so you might want to wait a bit longer before reading too much. I definitely need to cull through the User Guide for the obvious menu changes first. One question: is the user interface (e.g. location of items on the pulldown menus, etc.) likely to be stable now, or will there be more changes in the relatively near future? This will affect my enthusiasm to do the changes sooner rather than later. > | It was a productive lunch break today ... > > don't forget to eat... :-) Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Key-binding documentation dilemma
Hi, I'm working on updating the keyboard shortcuts in the docs (starting with the User Guide). It's immediately obvious that I'm going to get myself into a CUA vs Emacs binding battle. Having used Emacs for about 16 years, guess which one I prefer ... Given that CUA is the default, and assuming that an overwhelming majority use that, the question is how to I document such things without being ridiculous? Do I just document CUA and tell Emacs users to go figure it out themselves? (e.g. "to cut highlighted text, use C-x") Do I put the Emacs equivalent in parentheses? (e.g. "to cut highlighted text, use C-x (C-w)") Or do I annoy everyone and spell it out? (e.g. "to cut highlighted text, use C-x in CUA or C-w in Emacs") The current style is closer to the first (ignore Emacs users), but it's not spelled out anywhere, and there are a few Emacs-style commands sprinked about. I would like to hear a few opinions - I intend to do this only once ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Key-binding documentation dilemma
On Thu, 30 Nov 2000, Amir Karger wrote: > I think the docs have to be written assuming you've got the default binding. > Otherwise, you'd have to write it so that it automatically displayed what > the person's personal bindings were at that time, or something. That would actually be really cool! > IMO, both of these are verbose and annoying. (Admittedly I use CUA.) Yes, > the docs should have all the necessary information, but they also need to be > *readable*. Every time you have one of those parentheses (or worse, an extra > phrase) will break the train of thought of the text. Agreed - this is why I thought I'd ask. If no one feels strongly about the emacs bindings (other than me), then it's appropriate to leave them out. > I would instead suggest that you prominently note that all the given > bindings are CUA and if you want Emacs bindings, they are listed at [Ref]. This is my current leaning. Guess I'll have to resurrect the Reference manual ... > If you think this isn't good enough, maybe you could try footnotes. (I'm not Yuck! > sure how many bindings you're talking about. If there are hundreds, the > footnotes could get burdensome, although you could also put several bindings > into one footnote.) Not as many as I thought, but I'd still like to get the style "right". Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Key-binding documentation dilemma - what I will try
Hello all, I seem to have generated some discussion - good. On 1 Dec 2000, Lars Gullik Bjønnes wrote: > "Garst R. Reese" <[EMAIL PROTECTED]> writes: > | Allan Rae wrote: > | > On Thu, 30 Nov 2000, Mike Ressler wrote: > | > > Given that CUA is the default, and assuming that an overwhelming majority [ ...] > | > > | > I'd rather see you use minibuffer commands in the text and provide > | > keyboard shortcuts in a footnote. Or just refer people to the tables of > | > shortcuts in References. > | > > | > Allan. (ARRae) > | How about chapters or separate docs > > Appendix in the userguide? I will modify the docs so that only the menu bindings (minibuffer commands) are listed in the text. Appropriate verbiage will be added to the UG and perhaps the Introduction to explain the situation. Then I will update the bindings section of the Reference Guide to reflect the latest CUA and Emacs binding maps. If this updated section doesn't look like a complete mess, I will then add it as an appedix to the User Guide. Fair enough? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Key-binding documentation dilemma - what I will try
On Fri, 1 Dec 2000, Amir Karger wrote: > On Fri, Dec 01, 2000 at 08:49:42AM -0800, [EMAIL PROTECTED] wrote: > > I will modify the docs so that only the menu bindings (minibuffer > > commands) are listed in the text. Appropriate verbiage will be added to [ ...] > > > > Fair enough? > > No! > > It's Friday, so I can't agree with you so easily. Whiner ;-) > Anyway, my only concern is the tutorial, which is being read by newbies (who > are most likely to have the default bindings, although a sysadmin might've I tend not to think of the Tutorial as part of the docs I'm responsible for, so I hadn't intended to change that. I agree that the tutorial should stay as simple as possible and reference the default shortcuts. But is does make the dilemma a bit stronger if we use the shortcuts there but not in the other docs. And thus my hesitation ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: A few things to do for 1.1.6
On 7 Dec 2000, Lars Gullik Bjønnes wrote: > | - update documentation (this can be done after pre1 is out) > > Has most of this been done now? Are you thinking about doing a real 1.1.6 or just another pre? I would definitely like to update a few more things before 1.1.6 proper, and will accelerate my efforts if 1.1.6 is imminent. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Key-binding documentation dilemma
On 12 Dec 2000, Lars Gullik Bjønnes wrote: > John Weiss <[EMAIL PROTECTED]> writes: > | Plus, it excludes one set of default bindings (e.g. Emacs) in favor of > | another (e.g. CUA). We need to document *all* bindings, and the place > | for that is in the Reference Manual. > > I must admit that I'd like an apendix a lot better. Give me a chance to get everything written up. When I'm finished, we can play the appendix vs no appendix game and see how things look. I'm actually beginning to agree more with John on this one, but I'd like to see them in action first. My worry about the Reference Manual is that the keybinding section is likely to be the ONLY section that isn't completely out of date. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Trivial typo.
On Sat, 23 Dec 2000, Syam Pannala wrote: > the file "Top N things to know .." (lib/examples/splash.lyx in > lyx-devel cvs branch). > > 3. The output from LyX looks great! Select File->View dvi now to see > for yourself. > > I think this should be View->Dvi (and not file->view dvi). > > PS: If this is not the right mailing list, please redirect me to the > correct one. It's the right list, more or less, though I copied the lyx-devel list since I don't have CVS access to that particular file. The "view dvi" instruction recently moved from the "file" menu to the new "view" menu, so splash.lyx should, in fact, be updated. Just one of the many things to drive me nuts while trying to have the documentation catch up to 1.1.6 ... Thanks for your report. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
New lyxdoc CVS branch
I think I just created a new branch lyxdoc-1_1_6-updates for 1.1.6 specific documentation updates. The main branch will start having 1.2.0 specific features. I got some funny error messages, so people who know what they are doing should check it to make sure it is okay. I committed a few minor updates to several of the docs just before I created the branch, BTW. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Hartmut has created updated screenshots for the LyX Graphical Tour
Hi all, On Thu, May 28, 2009 at 9:46 AM, Pavel Sanda wrote: > Christian Ridderström wrote: >> the graphical tour, so for now I've place the new images in the >> subdirectory >> images/LGT/En >> >> If anyone (perhaps the original authors) > > original authors are not here anymore i guess The original author (that would be me) is still lurking in the background. > note that images there are _not_ localised. i would encourage Hartmut > to update the english version ot the text. If you believe the dates on some of the xdvi screenshots, I did the original 10 1/2 years ago! So it really is time to update the whole thing, including the page previews. Is Hartmunt up to doing that? I can volunteer to help proofread, but I don't have the opportunity to do much more than that. Mike -- mike.ress...@alum.mit.edu
Re: TEXmacs
On Thu, 12 Jul 2001, Herbert Voss wrote: > Zvezdan Petkovic wrote: > > > Zvezdan> That's exactly what I meant. CM family is ugly. Notice what I > > > Zvezdan> say above about Euler. Metafont itself is not an issue. It's > > > Zvezdan> a design. CM was designed by one of the greatest computer > > > Zvezdan> scientist off all time, but only a would-be artist. Euler is > > > Zvezdan> designed by one of the greatest designers of all time -- > > > Zvezdan> Herman Zapf. That's what makes a difference. As I recall, Zapf was involved in CM to some extent (at least giving advice), but the real "problem" is that CM is modeled after Monotype Modern #8. If you like that font, then you will like CM; if not, ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Wed, 18 Jul 2001, Angus Leeming wrote: > I believe that the NATBIB branch is now in a fit state to merge back into > head. This is now your final chance to try it out before I completely screw > up the CVS head by rolling the branch back in ;-) Woo hoo!!! Yes! Grabbed it, compiled it, already playing with it - even though I should go to bed since I just finished observing all night and need to get up in 6 hours to start all over again. The natbib stuff is working great. Great job, Angus! That said, I want to gripe about the 666 insets, since this is the first I've seen them. I don't care what goes on under the hood, but I want them to look and behave like the old ERT. I was playing around with converting a paper I had written. If a bit of ERT appeared midsentence (e.g. I often insert \microns, rather than doing the $\mu$m equivalent), the line before it was justified fully left to right: if there were only 3 words on the line, one would be on the left, one dead center, the third on the right margin. It looks TERRIBLE! Furthermore, instead of aiding reading, a sentence like We observed the source at 10 \microns, whenever the weather was good shows up as We observed the source at 10 666 \microns , whenever the weather was good This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I still like the natbib though!!! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: > On 18-Jul-2001 Mike Ressler wrote: > > This is not a stunning example of WYSIWYM. Please, please, (Lars?) change > > the appearance back to the old behavior!!! > > I don't think this will happen. What will happen is that we will change > the InsetERT to be inlined. What will NOT happen is that a inlined ERT > inset breaks row, so this is really thought only for short stuff! I don't care what the underlying mechanism is (insets, fonts, etc.). I would like the _appearance_ to resemble the old style. Having it appear like a math inset would be fine. Maybe that is the model: an inlined ERT box and a "display" ERT box, for longer chunks of LaTeX code. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: > On 19-Jul-2001 Mike Ressler wrote: > > > like a math inset would be fine. Maybe that is the model: an inlined ERT > > box and a "display" ERT box, for longer chunks of LaTeX code. > > That's exactly what we plan to do :) Excellent! Why didn't you just say so :-) Sorry if I sounded overly loud - I was just shocked by the appearance of those 666 boxes, and hadn't really followed the previous discussion closely enough to realize what was going on. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
View->TOC buglet
The "Close" button in the TOC panel changes to "Cancel" after you use the window to jump around. Why? Shouldn't it just stay "Close". This is with the lyx-1.1.6fix3 CVS branch. Haven't tried 1.2.0 CVS ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
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 ...
Plea from LyX Doc team
Hello all, We are trying very hard to get at least the Tutorial and User Guide completely up to date before the release of 1.1.6fix3. If you should have a few spare minutes, please glance at your favorite part of the documentation and let me know if there are any errors to be found. The latest versions of the docs can be found in the lyxdoc CVS repository, but I will accept corrections to the plain 1.1.6fix2 documentation, even though I hope to have already correctly most of those errors. Send your corrections either directly to me or to [EMAIL PROTECTED] Thanks for your time. Mike - speaking for the doc team (though mostly myself) -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
666 insets looking much better
I've just compiled the current CVS and like the "666 inset" behavior much better - collapsing them looks good. However, could the maximum size of the box be made settable somewhere? From my previous example, "\micron" shows up very nicely, as does "\farcs"; both these have a box size which matches their length (very nice!). However, "\citep(dantona)" shows up as "\citep(dan...". (Yes, I know I can now fix this with natbib, which is in fact what I was doing.) 15 characters doesn't seem to be overlong to me, so I was wondering if a settable length could be placed somewhere, perhaps in Edit->Preferences->Look & Feel->Misc? Anyway, nice job! I'll stop having a cow now ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Bug #2
On Mon, 23 Jul 2001, Michael Schmitt wrote: > I cannot export file "Extended.lyx" of LyX 1.1.6 to "dvi" format. It > seems like there is a problem with these new "ERT" insets. Could somebody > please check whether this is a real bug or just a problem with my > configuration? I had this very problem about an hour ago and the general problem is that the "floatflt" paragraph option is not honored. The first sign of trouble is that when I load Extended into 1.2.0cvs I get a textclass loading error which says "Couldn't set the layout for 7 paragraphs". Then going to Section 1.8.3, the mobius figure is displayed, but if I pop up Layout->Paragraph, there is no "Extra" page to be seen, and this is where the floatflt option is supposed to be set. Now this wouldn't be noticeable by itself, but later on, in Section 5.3, I use some ERT to call some floatflt commands, but since it wasn't loaded automatically in 1.8.3, it is not available for the ERT in 5.3. The real problem, I believe, is that the Extra Paragraph Options page has disappeared. (Only "General" appears when Layout->Paragraph is called.) This all works correctly in 1.1.6fix3cvs, but not in today's CVS. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Bug #2
On Mon, 23 Jul 2001, Herbert Voss wrote:
> > On Mon, 23 Jul 2001, Mike Ressler wrote:
> >
> > > I had this very problem about an hour ago and the general problem is
> > > that the "floatflt" paragraph option is not honored.
>
> write in preamble \usepackage{floatflt} and all should work
This is a band-aid for a much more serious problem. Yes, it will work, but
the problem is that the extra paragraph options disappeared since 1.1.6!
They don't even show up in the GUI. Some big chunk of code was deleted,
#ifdef'ed out, or something. The current CVS is just plain broken and
needs to be fixed!
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
Re: Bug #2
On Mon, 23 Jul 2001, Herbert Voss wrote: > Mike Ressler wrote: > > This is a band-aid for a much more serious problem. Yes, it will work, but > > this was only for Michael's PhD! nothing else ... ;-) Of course. Sorry if it sounded like I jumped on you. I was just rather shocked to find that a whole GUI panel, and it's functionality, seems to have disappeared. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Bug #2 (new: minipage bug report)
On Mon, 23 Jul 2001, Mike Ressler wrote: > Oh, cool. The minipage thing is definitely better. A quick bug report: if > I do side-by-side minifloats and try to put an hfill in between them, the ^^ <- minipages, of course ... > insets overlap and the hfill is squashed in the middle of them. The DVI > output is correct, but the LyX display is messed up. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: 666 insets looking much better
On Tue, 24 Jul 2001, Juergen Vigna wrote: > Well we could, but I really don't know if this is needed. I made this more > for longer paragraphs with LaTeX code as for shorter one I'll make the > inlined version so that it doesn't collapse, but it will show it's contents ^^^ Ah, yes ... if there will be a new inlined version, then I withdraw my proposal. Thanks! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Bug #2
In the docs for version 1.2.0, I shall simply remove the floatflt discussion unless it is reimplemented in time. And maybe add a note to that effect in the FAQ ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Updating NEWS for 1.2.0
On Wed, 25 Jul 2001, Herbert Voss wrote: > yes, because footnotes in table-floats make no sense! > and where shall they appear? under the table, inside a float? > on the bottom of the page, like others? ... I disagree somewhat strongly - footnotes to table-floats (or endnotes as they are more properly called) are used all the time (in astronomical journals, at least), and they appear under the table, inside the float :-) The AASTeX package (for which I created a LyX layout) actually defines \tablenotemark and \tablenotetext commands to deal with this in a sane fashion. I expect LyX could create a similar functionality. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Updating NEWS for 1.2.0
On Wed, 25 Jul 2001, [iso-8859-1] Jürgen Spitzmüller wrote: > Am Mittwoch, 25. Juli 2001 18:44 schrieb Mike Ressler: > > I disagree somewhat strongly - footnotes to table-floats (or endnotes > > as they are more properly called) are used all the time (in > ... > > Isn't the best way to get this behaviour inserting the table inside a > minipage, now that there is this new minipage support? > I think that's the way it is done in the LaTeX world. > But I think LyX should only allow footnotes in table- (and > graphic-)*floats* when a minipage is used and this is surely something > which has to be documented (so I guess I'm speaking to the right person > ;-) Ouch! Beautiful touché! :-) Your minipage suggestion is indeed correct (though AASTeX uses some funky \parbox magic). I can live with minipages, though it would be cool if LyX would do this automatically with a "table endnote" layout or something. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
"\lang ignore" in ERT insets
I'm converting the docs from 1.1.6 to 1.2.0. When trying to translate the UG, the conversion of the LaTeX code in Chapter 7 to an inset failed (or at least complained) as expected. What I didn't expect was that all the text in the inset was underlined blue, indicating a language change. Indeed, when I opened UG with emacs, I found that all ERT insets had a "\lang ignore" directive, which Lyx complains about when opening the file, as it is an unknown language. I've stripped out those \lang directives in emacs, and now the file loads fine in today's CVS. What's the deal? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: UserGuide.lyx LaTeX-ing problems
On Thu, 26 Jul 2001, Kayvan A. Sylvan wrote:
> On Thu, Jul 26, 2001 at 05:13:54PM +0200, Herbert Voss wrote:
> > Juergen Vigna wrote:
> > > I'm now able to load the UserGuide in lyx-cvs. But when I want to LaTeX
> > > it I get errors because some subsection have an underscore for the first
> > > character in their text. I tracked that down to the \usepackage{colors}
> > > if I remove that package from the produced LaTeX file I have no problems
> > > latexing the exported UserGuide.
> > >
> > > Is this a known problem for the "color"-package???
> >
> > i have no \usepackage{color} in the preamble of my
> > UserGuide.lyx
>
> I have reproduced this problem. Also, Tutorial.lyx produces the
> same type of problem (with a much smaller input file).
I have been laboring mightily to convert all the docs to 1.2.0 and have
not yet succeeded in getting the UG, Tutorial, and Customization to
convert for all of the above reasons. Keep an eye on lyxdoc CVS; I will
keep banging on them for the next couple of days ...
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
Re: Rename 666 to TEX
On 30 Jul 2001, Lars Gullik [iso-8859-1] Bjønnes wrote: > "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: > > | I think it was the brain-fart from Lars(?) who proposed re-defining > | the ERT acronym to mean Embedded Raw Text. > > Nope... I just come to the conclusion that "ERT" would be the best > acronym for us to use. I will happily update the docs accordingly :-) Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: CVS Update: lyx-devel
On Wed, 1 Aug 2001, Juergen Vigna wrote: > I already told you that we will put a small button on the left side of the > "inlined" inset so you can click on that so the above is a non valid comment! I don't like the "small button" idea for inlined ERT. It affects readability. I would like to be able to write things like "Atmospheric transmission is terrible at 20 \microns because of water vapor" with the minimal amount of decoration around the inlined "\microns". "\microns" is a very definite markup concept (used by several journal packages) and is distinct from "$\mu$m", even though that is what TeX eventually operates on. I would like to be able to read it with only the distraction of the "\" and maybe the color red. I don't understand the great desire for a toggleable ERT inset anyway. Force the user from the beginning to decide whether it will be inlined or not. The author should know right away which is appropriate. Then have two GUI operations which feed the ERT inset: one which is inlined with as little decoration as possible - like inline math mode, and one which is an ERT box (which is also collapsable). Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: TeX's parser.
On Tue, 21 Aug 2001, Andre Poenitz wrote: > I wonder at what time TeX's input routeine transforms "incoming chars" into > tokens. This obviously is not something like a preprocessing phase, since > this would not allow for catcode changes. I don't remember the answer off the top of my head, but I know it's convered in gruesome detail in the Knuth's TeX book. Poke around if you've got a copy ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: What's wrong here? [w/ PATCH] (+ Reference manual comment)
Mike weighs in :-) On Fri, 21 Sep 2001, Juergen Spitzmueller wrote: > Am Freitag, 21. September 2001 09:14 schrieb Allan Rae: > > Document it. In NEWS and in whichever user manual Mike thinks fits > > best (User Guide? but certainly in the Reference manual). > > Good idea. I will do (after it is decided that this approach will go in > and how). Maybe Mike can tell me where I have to document it... It should go in the User Guide where File->Open... stuff is discussed. If you like, write up a short description of exactly how it works and what the issues are, and send it to me. I can polish it and insert it appropriately. Note that the Reference manual is officially obsolete, at least in the sense that it is no longer maintained by the documentation team and it no longer appears in the Help menu in LyX. Information useful to a typical user was copied over to other docs; the rest of it was deemed too out of date for redemption. Since it is a document primarily for the developers, the doc team voted unanimously (1-0, with several other concurrences) :-) to leave it to the developers to update it and use it as they see fit. Ideally, it will morph into the document that enthusiastic newbies on the dev team would read to get up to speed. By its nature, though, it has to be maintained by the people who actually write the code, not merely hardcore users like me (who have no clue what "#pragma" means). I suggest, in fact, that it be moved from lyxdoc to perhaps lyx-devel/development or to the Code_rules subdirectory under that. Either way, it will be up to you guys to make something of it, or bury it once and for all. Mike P.S. Note that I committed "final" copies of the Intro and Tutorial a few days ago. Translators should start thinking about gearing up ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
ERT in right justified text buglet (CVS)
I'm not sure of the specific condition that causes this display problem, but it is easy to reproduce. 1) File->New from Template 2) Select letter.lyx 3) Put the cursor anywhere in the "My Name" area 4) Click the "TeX" button An ERT box is created that hangs way off the left side of the screen, so that the tab and the first few characters are not visible. One can right click on the box and collapse it; everything is fine. If you right click and inline it, however, the box shrinks to the _left_ edge of the screen and drags the rest of the "From" block with it. Most peculiar (and irritating). This is true of today's CVS as well as a CVS that is about two weeks old. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Lyx Server
Jiri, I have forwarded this to the LyX developers' list. Hopefully, someone there who is much more knowledgable than I can explain the current workings. (I'm just a humble documentor.) Mike On Mon, 15 Oct 2001, [iso-8859-1] Jiri Mares wrote: > Hi Mike, > I would like to ask you for more information about Lyx > Server. I am developing Perl program, that read *.lyx > file containing Mathed equations. The equation > is translated via regular expression to Perl, then > appropriate values are substituted and equation is > calculated. > The purpose of this program is to create and maintain > documents, where the mathematical expressions are > calculated. I have configured my Lyx, so I have in my > home directory lyxrc file with > > \serverpipe "/home/jiri/.lyx/.lyxpipe" > > When I write output of my program to .lyxpipe.in, Lyx > does not react. What > is the problem? Probably I did not understand the > princip of Lyx server. Could you give me advice, where > can I find more information? I tried to find more > information on some links, they are on oficial Lyx > page, but without succes. -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: LyX Review
On Sat, 27 Oct 2001, Brian Proffitt wrote: > Regarding LyX overall, what are some of the features you think users will > appreciate the most when they use this application? In addition to all the previously mentioned stuff, it is well documented. We on the doc team have tried hard to provide help files which are complete, up-to-date, and readable. Between the written docs, Herbert Voss's incredible LyX/LaTeX tips website (http://www.educat.hu-berlin.de/~voss/lyx), and the lyx-users mailing list, there's no excuse for anyone to struggle with learning LyX. Mike Ressler - doc team member (and thus biased). Current maintainer of most of the English docs. Added support for American Astronomical Society's AASTeX while documenting how to add new classes to LyX :-) -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Graphical Tour-o-Matic (i.e. lyxserver help needed)
Hi, I've decided to try updating the LyX Graphical Tour, and would like to come up with an automatic way of generating it. My idea is to have a script which dumps a few line of text into the LGT file, does a frame grab, dumps a few more, etc. I've figured out how to do most of the input through the lyxserver, but one issue has me stumped. Some commands pop up an xform window; e.g. "LYXCMD::label-insert:". The label dialog appears, but there doesn't appear to be any way to enter the label name and "hit" return. This is also true of things like buffer-new, figure-insert, etc. If there is no way to do this, the auto-LGT idea is worthless. Is there a way to automate this? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Graphical Tour-o-Matic (i.e. lyxserver help needed)
On Fri, 18 Jan 2002, Allan Rae wrote: > On Thu, 17 Jan 2002, Mike Ressler wrote: > > I've decided to try updating the LyX Graphical Tour, and would like to > > come up with an automatic way of generating it. My idea is to have a > > script which dumps a few line of text into the LGT file, > > A LyX Hand-Held Tour is what I thought you were about to introduce. > Maybe? That would be one possibility, if I can make all this work. For now, I just want to script the LGT, but the framework would be in place for a hand-held tour. > We need lots of new LyXFuncs to handle each and every little thing you > want to set that instead of popping up a dialog the values can just be > plugged straight in -- one at a time. I was hoping there might be some hidden technique to send virtual keystrokes to the xforms popups. I think I recall seeing something about going the other way - the lyxserver will output keystrokes going into LyX; I suppose the reverse isn't true? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: graphix inset
On Thu, 31 Jan 2002, Herbert Voss wrote: > Garst R. Reese wrote: > > %%Pages: (atend) > > blah blah > > %%Trailer > > %%Pages: 5 > > I did not find anything with %%BoundingBox (atend) or the like. > > Note: atend is one word. >From a figure I have: %!PS-Adobe-3.0 EPSF-3.0 %%For: brucew %%Title: PGPLOT PostScript plot %%Creator: PGPLOT %%CreationDate: 13-Jun-2000 14:59 %%BoundingBox: (atend) %%DocumentFonts: (atend) %%LanguageLevel: 1 %%Orientation: Portrait %%Pages: (atend) %%EndComments %%BeginProlog blah blah PGPLOT restore showpage %%PageTrailer %%PageBoundingBox: 40 28 535 757 %%Trailer %%BoundingBox: 40 28 535 757 %%DocumentFonts: %%Pages: 1 %%EOF Note the use of PageBoundingBox as well ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
EPS conversion failure (still)
Is this behavior from the stupid "can't mv from /tmp" bug or is it some new devilry? try to convert image file: /home/ressler/WL20/LyXCVSPaper/siess.ps GetExtension: ps GetExtFromContents: eps from: eps -> xpm imageConverted, conversion succeeded. Loading XPM Image... Error reading XPM file 'XpmColorFailed' Loading /tmp/lyx_tmpdir23889EyC1vo/siess23889YAlK3E.xpmFailed CVS from half an hour ago. Mandrake 8.0, gcc-2.96, etc. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: EPS conversion failure (still)
On Fri, 8 Feb 2002, Angus Leeming wrote: > On Friday 08 February 2002 5:36 pm, you wrote: > > Is this behavior from the stupid "can't mv from /tmp" bug or is it some > > new devilry? > > from: eps -> xpm > > imageConverted, conversion succeeded. > > Loading XPM Image... Error reading XPM file 'XpmColorFailed' > > Loading /tmp/lyx_tmpdir23889EyC1vo/siess23889YAlK3E.xpmFailed > > Try it by hand. Can you load the converted file in (say) xv? > My version of ImageMagick's convert has a bug that produces invalid XPM > files. Dunno what you use. Bingo - xv complains about a lot of invalid 8 byte long color specifications. > Here I use convert to convert everything to PPM format and then use ppmtoxpm > to go the rest of the way. Works for me, too. I had originally tried pstopnm -> ppmtoxpm, but stupid Mandrake forgot that pstopnm is a shell script which depends on "bc", which of course, isn't installed on my system. Anyway, convert -> ppmtoxpm works just fine. Thanks. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
RGB -> grayscale (was Re: Remarks about graphics in lyx1.2.0cvs)
On Thu, 21 Feb 2002, Asger K. Alstrup Nielsen wrote: > On Thu, 21 Feb 2002, Angus Leeming wrote: > > and the problem is now defining an appropriate mapping from the colour > > colourmap to a grayscale or monochrome one. > > I'm not sure what the problem is, but if you want to convert from > color to grayscale, just do this: > > int gray = (red + blue + green) / 3; Actually, the better way to do this is (xv Postscript code) gray = 0.32 * red + 0.5 * green + 0.18 * blue or perhaps (NTSC) gray = 0.30 * red + 0.59 * green + 0.11 * blue Either gives a better match to a human's RGB to luminance conversion. Definitely not (R+G+B)/3! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Graphics loading delays text display (CVS)
The new graphics loading mechanism delays the display of any text in the LyX window until all graphics have been converted. This is a problem when there are 20 images in the document :-) Because these are largish images, it took about 3 minutes until the splash screen disappeared and the text showed up. Is this normal behavior? I'm testing the CVS version as of 5 minutes ago, and I use the following eps conversion chain: \converter "eps" "xpm" "convert EPS:$$i PPM:$$i.ppm ; ppmtoxpm $$i.ppm > $$o" "" Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Graphics loading delays text display (CVS)
On Thu, 21 Feb 2002, John Levon wrote: > On Thu, Feb 21, 2002 at 10:11:49AM -0800, Mike Ressler wrote: > > The new graphics loading mechanism delays the display of any text in the > > LyX window until all graphics have been converted. This is a problem when > > I imagine you've not been reading lyx-devel for a while ? Angus is fixing it. I actually have been :-O --- I guess I just missed the synchronism thing. Angus helped me work around a stupid converter bug (ImageMagick's xpm converter is broken in my version, and Mandrake 8.0 forgot to include the "bc" dependency for netpbm), so all that seems to work beautifully. The preloading just caught me off guard, so I wanted to make sure Angus knew that I noticed :-) Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: RGB -> grayscale (was Re: Remarks about graphics in lyx1.2.0cvs)
On Fri, 22 Feb 2002, Asger K. Alstrup Nielsen wrote: > On Thu, 21 Feb 2002, Mike Ressler wrote: > > Actually, the better way to do this is (xv Postscript code) ... > > Either gives a better match to a human's RGB to luminance conversion. > > Definitely not (R+G+B)/3! > > This is true. I just couldn't remember the coefficients in my head, > so I just gave you an approximation that should be good enough for > starters. Amateur. > Just for background, you can actually do it better than the > weighted-average. However, it's a pretty big job: ... > In general, a complete color-proof system is very expensive and > difficult to achieve. Ouch! Talk about swatting a fly with a sledge hammer. But it is a very good procedure. When can we expect a patch? Mike (ducking for cover, and escaping to do some real work ...) -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Is .../lib/doc/ExternalMaterial.lyx still relevant
I've been thinking about starting to update the docs in anticipation of 1.2.0, now that the interface appears to be stabilizing a bit. While rooting around the CVS, I discovered the above file. Is it still relevant? If so, I'll paste it into Extended. Whether it is or isn't, it should probably be deleted from this directory. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
CVS make install error
When building recent CVS's (last few days, including 5 minutes ago),
everything goes fine until the end of the install. The following gets
burped at me:
[...]
/usr/bin/install -c -m 644 ../../lyx-devel/lib/symbols
/scr/ressler/lyx-cvs/share/lyx/symbols
files=`sed -e 's/^\([^ ]*\) .*$/\1/' xfonts/fonts.dir` ; \
for i in ${files} ; do \
ln -s `kpsewhich $i` /scr/ressler/lyx-cvs/share/lyx/xfonts/$i ; \
done
ln: /scr/ressler/lyx-cvs/share/lyx/xfonts/cmex10.pfb: File exists
ln: /scr/ressler/lyx-cvs/share/lyx/xfonts/cmmi10.pfb: File exists
[ ... more deleted ...]
ln: /scr/ressler/lyx-cvs/share/lyx/xfonts/msbm10.pfb: File exists
make[3]: *** [install-xfonts] Error 1
make[3]: Leaving directory `/home/mressler/LyX/lyx-build/lib'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/mressler/LyX/lyx-build/lib'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/mressler/LyX/lyx-build/lib'
make: *** [install-recursive] Error 1
No big deal, but it does abort the install early. While poking at
lib/Makefile, I found that the relevant install code is hardwired for
"ln -s `kpsewhich ...", which ignores the Makefile variables LN and
KPSEWHICH. Summary:
1) Old links need to be dealt with by "ln -sf" or deleting the old links
2) The Makefile needs to be patched to use the appropriate variables
3) I really don't know what the heck I'm doing in terms of fixing
Makefile.am or Makefile.in, so I hope this is enough info for people who
do know what they are doing to solve this.
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
Re: Underfull boxes
On Fri, 29 Mar 2002, John Levon wrote: > On Fri, Mar 29, 2002 at 03:40:58AM +0300, Gady Kozma wrote: > > I threw together a little document which explains how to deal with > ... > I think we should include this as part of the main LyX docs in fact, it > plugs a big hole in the current documentation. It needs a couple of > minor doc style fixes though. > > Anyone else agree ? Where should it go ? I do. For now, I would say into Extended with the other LaTeX stuff (Warning, I haven't had a chance to actually read Gady's doc yet), but we might want to create a section in the UserGuide, or even a new document "What to do when things go wrong". It should definitely not remain an isolated document abandoned in the frozen wasteland of the Web ... Your overbusy and still-paying-attention-but-waiting-for-1.2.0pre1 document maintainer, Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: eps preview problems in 1.2pre1
On Thu, 4 Apr 2002, Ulrich [iso-8859-15] Günther wrote: > Eps figures cannot be shown in 1.2pre1. > Every single figure creates an alert once I get on the page with the figure. > Afterwards the figs show 'error converting to loadable format'. > I am using SuSE 7.3 but not the ghostscript that comes with the distribution, > but rather ghostscript-7.04-1 with ghostscript-fonts-6.0-2. This smells like the bad Imagemagick convert problem to me. In your preferences, try the following for the EPS->XPM converter: convert EPS:$$i PPM:$$i.ppm ; ppmtoxpm $$i.ppm > $$o It uses Imagemagick convert to go from EPS to PPM, then the netpbm tools to go from PPM to XPM. Some versions of convert (like mine in Mandrake 8.0) produce bad XPM files. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Math character bug in pre3
This bug was around a long time ago; I don't remember if it was fixed and got broken again, or if it was ignored and declared correct behavior. I use "Alt-m g m m" in text mode in 1.1.5fix2 all the time to make the micrometer abbreviation - in TeX it is "$\mu$m". In 1.2.0pre3, the above sequence generates a math box with the greek letter mu, then leaves the cursor just of the left of the box and inserts the m before it - I get "m$\mu$". If I am already in mathed, the "Alt-m g m m" works as expected: a "mu" followed by an "m". Can this be fixed? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
ProvidesNatbib needed in layouts
Hi,
I've started updating the AASTeX layout for 1.2.0. It actually doesn't
need much work, but there is a natbib issue which needs to be straightened
out. AASTeX (the American Astronomical Society's journal class) "provides"
natbib in the sense that you don't put a \usepackage{natbib} in your file.
It would be nice to have a ProvidesNatbib keyword for layout files similar
to ProvidesAmsmath and ProvidesUrl so that 1) the user doesn't have to
check the "Use Natbib" button seperately (choosing the AASTeX layout
should do this automatically) and 2) the \usepackage line doesn't have to
be removed manually from the exported LaTeX file. Is this doable without
too much pain?
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
provides_ buglet
While trying to answer my own ProvidesNatbib question, I came across the following snippet of code in lyxtextclass.C (line 282 and following): case TC_PROVIDESAMSMATH: if (lexrc.next() && lexrc.getInteger()) provides_ |= amsmath; break; case TC_PROVIDESMAKEIDX: if (lexrc.next() && lexrc.getInteger()) provides_ |= makeidx; break; case TC_PROVIDESURL: if (lexrc.next() && lexrc.getInteger()) provides_ = url; break; I'm no C++ guru, but shouldn't that last provides_ line be provides_ |= url; Having ProvidesUrl would appear to stomp on any prior Amsmath and Makeidx directives. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: provides_ buglet
> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> >>>>>> "Mike" == Mike Ressler <[EMAIL PROTECTED]> writes:
> >
> | Mike> Having ProvidesUrl would appear to stomp on any prior Amsmath
> | Mike> and Makeidx directives.
> >
> | Indeed. Lars fixed it. Am I right to undertand you are having a go at
> | ProvidesNatbib?
I've decided to attempt it: I'm a terrible programmer, but I found a fatal
flaw (from the perspective of AASTeX support) with the current approach.
AASTeX, as I mentioned, "provides" natbib. In order to get LyX to turn on
the natbib support, one must click the "use natbib" radio button (not
surprising). The problem is, turning on the button inserts a
\usepackage[author-year]{natbib} line in the temporary latex file. This
clashes with what AASTeX uses internally and borks the latex run.
Thus, the one feature I was really looking forward to in 1.2.0 (full
natbib support for AASTeX) doesn't work. Knowing that Lars is holding an
ax over the head of all the regular developers to only fix bugs (savage
Viking! :-), I thought I might coerce someone to fix this by submitting a
really awful patch, offending the sensibilities of all True Programmers,
and having someone submit a Pure Version.
But if someone would like to fix this before I submit my disaster, please
do. Maybe I can get it decreed a bug - since Lars thinks it is only 10
lines of code, it should be easy, right ;-). I should say, I had planned
to email bomb the American Astronomical Society publication department
with news of 1.2.0 when it is released to brag about the awesome AASTeX
support. LyX's current natbib trouble will mute that a bit.
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
ProvidesNatbib: patch attached
I've carried through on my threat and created a ProvidesNatbib layout
keyword. It's attached as diff_natbib (diff -ru format). I've also
attached the updated AASTeX stuff as diff_aastex. Only if the natbib patch
is accepted should the aastex patch be applied. The changes are trivial,
but get done what I need. There is one thing I'd like to do, but haven't
figured out how: the patch currently does not turn on the GUI natbib
support automatically; you still need to click the radio button. Is there
some way to tell the GUI to turn on without clicking anything else?
The Changelog entry, which I didn't apply, should look like
LaTeXFeatures.C, lyxtextclass.C lyxtextclass.h: Add layout keyword
ProvidesNatbib. Do not add \usepackage{natbib} to tex file if natbib is
provided by the LaTeX class.
I'd like the patch to be applied now since I consider the lack of
ProvidesNatbib to be a bug in the sense that it breaks the new natbib
support for AASTeX.
Be gentle - there's a reason I write documentation, not code ...
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
diff -ru lyx-1.2.0pre3/src/LaTeXFeatures.C lyx-1.2.0pre3a/src/LaTeXFeatures.C
--- lyx-1.2.0pre3/src/LaTeXFeatures.C Thu Mar 21 09:25:07 2002
+++ lyx-1.2.0pre3a/src/LaTeXFeatures.C Thu Apr 18 21:13:48 2002
@@ -245,7 +245,7 @@
// float.sty
// natbib.sty
- if (isRequired("natbib")) {
+ if (isRequired("natbib") && ! tclass.provides(LyXTextClass::natbib)) {
packages << "\\usepackage[";
if (params.use_numerical_citations) {
packages << "numbers";
diff -ru lyx-1.2.0pre3/src/lyxtextclass.C lyx-1.2.0pre3a/src/lyxtextclass.C
--- lyx-1.2.0pre3/src/lyxtextclass.CThu Mar 21 09:25:15 2002
+++ lyx-1.2.0pre3a/src/lyxtextclass.C Thu Apr 18 23:18:01 2002
@@ -91,6 +91,7 @@
TC_CLASSOPTIONS,
TC_PREAMBLE,
TC_PROVIDESAMSMATH,
+ TC_PROVIDESNATBIB,
TC_PROVIDESMAKEIDX,
TC_PROVIDESURL,
TC_LEFTMARGIN,
@@ -114,6 +115,7 @@
{ "pagestyle", TC_PAGESTYLE },
{ "preamble",TC_PREAMBLE },
{ "providesamsmath", TC_PROVIDESAMSMATH },
+ { "providesnatbib", TC_PROVIDESNATBIB },
{ "providesmakeidx", TC_PROVIDESMAKEIDX },
{ "providesurl", TC_PROVIDESURL },
{ "rightmargin", TC_RIGHTMARGIN },
@@ -284,6 +286,11 @@
provides_ |= amsmath;
break;
+ case TC_PROVIDESNATBIB:
+ if (lexrc.next() && lexrc.getInteger())
+ provides_ |= natbib;
+ break;
+
case TC_PROVIDESMAKEIDX:
if (lexrc.next() && lexrc.getInteger())
provides_ |= makeidx;
diff -ru lyx-1.2.0pre3/src/lyxtextclass.h lyx-1.2.0pre3a/src/lyxtextclass.h
--- lyx-1.2.0pre3/src/lyxtextclass.hThu Mar 21 09:25:15 2002
+++ lyx-1.2.0pre3a/src/lyxtextclass.h Thu Apr 18 21:18:40 2002
@@ -93,7 +93,9 @@
///
makeidx = 2,
///
- url = 4
+ url = 4,
+ ///
+ natbib = 8
};
///
bool provides(Provides p) const;
diff -ru lyx-1.2.0pre3/lib/layouts/aastex.layout
lyx-1.2.0pre3a/lib/layouts/aastex.layout
--- lyx-1.2.0pre3/lib/layouts/aastex.layout Mon Mar 20 06:49:53 2000
+++ lyx-1.2.0pre3a/lib/layouts/aastex.layoutThu Apr 18 22:43:29 2002
@@ -26,6 +26,7 @@
#is changed. (Not by me!) Documentation, template, and
#example files are available.
# Version 1.1 7/25/99 - Changed \url to take advantage of new layout option.
+# Version 1.2 4/18/02 - Updated for natbib in 1.2.0
# General textclass parameters
Columns1
@@ -35,6 +36,7 @@
TocDepth 0
PageStyle Plain
ProvidesAmsmath1
+ProvidesNatbib 1
ProvidesUrl1
ClassOptions
PageStyle""
diff -ru lyx-1.2.0pre3/lib/templates/aastex.lyx
lyx-1.2.0pre3a/lib/templates/aastex.lyx
--- lyx-1.2.0pre3/lib/templates/aastex.lyx Fri Nov 3 03:21:37 2000
+++ lyx-1.2.0pre3a/lib/templates/aastex.lyx Fri Apr 19 00:45:49 2002
@@ -1,6 +1,5 @@
-#This file was created by Wed Jun 9 13:29:15 1999
-#LyX 1.0 (C) 1995-1999 Matthias Ettrich and the LyX Team
-\lyxformat 2.15
+#LyX 1.2 created this file. For more info see http://www.lyx.org/
+\lyxformat 220
\textclass aastex
\begin_preamble
\slugcomment{}
@@ -17,6
Re: natbib citations
On Tue, 23 Apr 2002, Angus Leeming wrote: > On Monday 22 April 2002 8:12 pm, Mike Ressler wrote: > > No problem. As a return favor, could you look at the ProvidesNatbib patch > > I sent out Friday? The patch itself is trivial, but you might be able to > > address my question about how "ProvidesNatbib 1" in the layout file might > > automatically turn on the GUI support provided by clicking on "Use > > Natbib". > > Mike, I _think_ that all you need to do is modify InsetCitation::validate I'll give this a try, perhaps tomorrow. The real world has been awfully intrusive this week ... Thanks for the hint. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: ProvidesNatbib: patch attached
On 23 Apr 2002, Jean-Marc Lasgouttes wrote: > >>>>> "Mike" == Mike Ressler <[EMAIL PROTECTED]> writes: > Please provide this changelog entry. It helps. Also, Customization.lyx > should be updated (although I am not sure that the other ProvidesXXX > are there). Now that the patch is in, I will update the docs accordingly. Hopefully tomorrow. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
What documentation needs to be updated for 1.2.0?
Greetings, documentation fans! With the imminent release of 1.2.0, the documentation surely needs one more good update. I know John Levon has done a lot of work (thanks!), so hopefully things aren't too obsolete. But I know there are still things to do - my own section for AASTeX in Extended needs to be updated for the new natbib support, for example. I'm guessing a lot of the GUI changes still need to be documented, as well. What else needs to be done? If I can put together a todo list with your inputs, I may be able to attack this (or delegate!) so we're not in too bad shape for the release. Any volunteers to help me out? Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: "Tabular"/"Tabular Material" vs. "Table"
On Fri, 21 Jun 2002, robin wrote:
> John Levon wrote:
> >JMarc suggested I ask here about this terminology. My question is, what
> >is our justificatino for exposing the user to the unusual formulation
> >"Tabular Material", or the even worse "Tabular" ?
> >
> Beats me.
This is another of those things that was argued about back when the Earth
was young and dinosaurs roamed the land. The issue was how to make a
distinction between LaTeX's tabular - the actual table material - and a
table, which is the floating thing you put a tabular into. A similar
problem was posed by "figure", but at least there we could call the actual
picture a graphic. In tabular form :-) we have
Content Float
--
graphic ---> Figure
??? ---> Table
So, the problem is how to properly label the ???. We compromised on
"tabular material" so we could go back to arguing about more important
things.
> >What are the problems with using "Table" everywhere throughout the GUI
> >and the documentation (except where specifically related to the LaTeX
> >construct) ?
> >
> None, as far as I can see. Maybe it's a LaTeX thang. In general I'm in
> favour of making the GUI and the documentation as close as possible to
> conventional word-processors, HTML editors etc.
Now that floating figures and tables have been moved off into their own
submenu (Insert->Floats->Table), this isn't so big a deal anymore, but
then people will ask "What's the difference between Insert->Table and
Insert->Floats->Table?". LaTeX chose to solve it by using the names
Tabular and Table. Just because everyone else chose the wrong thing :-)
doesn't mean we need to change. On the other hand, I've never particularly
liked "tabular material". Kinda sounds like the corroding metal encrusting
the garbage disposal in my kitchen sink ("Honey, what's this tabular
material growing out of the disposal?").
So, I'm in favor of renaming it if a consistent, non-ambiguous solution
can be found. Keep in mind the fact that if one inserts a
Insert->Floats->Table, one then needs to insert a Insert->Table into it.
That's a bit too ambiguous for my taste.
Mike
--
Mike Ressler
[EMAIL PROTECTED]
OK, I'm lame: I don't have my own website ...
