Re: [LyX/2.3.2-staging] Oops, asInsetGrpahics is new to master.
On 02/15/2018 03:48 PM, Pavel Sanda wrote: > commit 25741ca5bd2ff4c7eb55de0fabfa41bbf476c77e > Author: Pavel Sanda > Date: Thu Feb 15 21:48:23 2018 +0100 > > Oops, asInsetGrpahics is new to master. It would be fine to copy that into 2.3.2-staging. Richard
Re: [LyX/master] oops, git is playing games with me.
Christian Ridderström wrote: > There's an FTP on the LyX server... I sent out details earlier today. > So perhaps 'sshfs' is an option for uploading things. Maybe we could have separate account just for manuals and possibility to directly link to that folder from web/wiki. That way Tommaso can directly upload his exports to web without relying on me. That would be good. > - From where are the files uploaded? A developer's computer? A CI job? >From local machine where someone runs the committed script for building >manuals. > - Are uploads to be triggered automatically? Unlikely. > - How often would we do new uploads? Once per release, a few times per > release? At most once per release, maybe even once per major relase. > - To where should the files be uploaded? Internally does not matter, we just need bash-like access for rm/cp -r commands (ftp through curl-ftps is just fine for that) and ability to directly link it through URL. > As I wrote in some other post I also thinks it's good to have a separate > staging area for review, and a separate deployment area to which users > are referred. I do not see that we have enough manpower to manage such complications. At this moment, even after one decade, we were not able to publish in html form *anything*. So keep it as simple as possible... Pavel
Re: [LyX/master] oops, git is playing games with me.
Pavel Sanda writes: > The way I can comfortably push this tree onto web server will make > it pages of it's own so pmwiki format is of no help. > > If you want to make part of wiki the only reasonable way I see is > to cooperate with Christian to create some sort of ftp/scp uploading > tunnel. I have no problem with such solution, but it's in your hands > then :) There's an FTP on the LyX server... I sent out details earlier today. So perhaps 'sshfs' is an option for uploading things. I'm not really sure what you're trying to achieve, e.g. - From where are the files uploaded? A developer's computer? A CI job? - Are uploads to be triggered automatically? - How often would we do new uploads? Once per release, a few times per release? - To where should the files be uploaded? As I wrote in some other post I also thinks it's good to have a separate staging area for review, and a separate deployment area to which users are referred. /Christian PS. A long time ago I wrote some PmWiki markup that lists files in a folder. It might be possible to use this markup to automatically generate lists/tables.
Re: [LyX/master] oops, git is playing games with me.
On 18/08/2017 02:09, Tommaso Cucinotta wrote: no more time for today... but perhaps the cache wipe-out work-around is already good enough. pushed, seems acceptable (except for 0_tmp_tmp_*, 1_tmp_tmp_*, etc...) T.
Re: [LyX/master] oops, git is playing games with me.
On 17/08/2017 21:49, Pavel Sanda wrote:
To recap the current problems from my POV:
1. en/ should have it's own directory as a normal language
because xhtml output target produces lot of images which clutter
root dir (please use xhtml, not html).
sure, easy.
2. exported icons still contain original path in the filename.
ideally we want fixed filenames for images so when you regenerate
documentation only real changes need to be committed.
tracked down somewhat, 2 problems:
1) conversion cache: if the image (footnote.png) is found in the cache, then
its associated absolute path is pulled in;
workaround: wipe out ~/.lyx-trunk/cache, or equivalently run with a custom
temporary userdir when converting manuals
still, the image is converted with the full pathname of the temporary folder where
the conversion is being done (no conversion in this case, as it's a .png ->
.png, but still a lot of code is executed, the file is copied, etc.), being smth.
like /tmp/tmp.X/orig_filename.png, resulting in an exported image filename
like: 0_tmp_tmp_X_orig_filename.png which seems still sub-optimal; this comes
from:
2) when loading a graphics inset, LyX stores into the inset params().filename
the absolute file path of the references image file, not the relative path;
this can be avoided with [1], but it's not sufficient, because still LyX
references the 0_tmp_tmp_* filename instead.
no more time for today... but perhaps the cache wipe-out work-around is already
good enough.
T.
[1]
diff --git a/src/insets/InsetGraphics.cpp b/src/insets/InsetGraphics.cpp
index 3cc550b5..2aa1b8ff 100644
--- a/src/insets/InsetGraphics.cpp
+++ b/src/insets/InsetGraphics.cpp
@@ -299,7 +299,7 @@ void InsetGraphics::read(Lexer & lex)
{
lex.setContext("InsetGraphics::read");
//lex >> "Graphics";
- readInsetGraphics(lex, buffer(), true, params_);
+ readInsetGraphics(lex, buffer(), false, params_);
graphic_->update(params().as_grfxParams());
}
@@ -568,7 +568,7 @@ string InsetGraphics::prepareFile(OutputParams const & runparams) const
if (params().filename.empty())
return string();
- string const orig_file = params().filename.absFileName();
+ string const orig_file =
params().filename.relFileName(buffer().filePath());
// this is for dryrun and display purposes, do not use latexFilename
string const rel_file =
params().filename.relFileName(buffer().filePath());
@@ -902,7 +902,7 @@ string InsetGraphics::prepareHTMLFile(OutputParams const & runparams) const
string const to = findTargetFormat(from, runparams);
string const ext = theFormats().extension(to);
- string const orig_file = params().filename.absFileName();
+ string const orig_file =
params().filename.relFileName(buffer().filePath());
string output_file = onlyFileName(temp_file.absFileName());
LYXERR(Debug::GRAPHICS, "\t we have: from " << from << " to " << to);
LYXERR(Debug::GRAPHICS, "\tthe orig file is: " << orig_file);
Re: [LyX/master] oops, git is playing games with me.
Tommaso Cucinotta wrote: > Thx Pavel for pushing this. I'd like to add to the script the capability to > generate the index in PmWiki format, so that its output can be > copy'n'pasted straight to At this moment I do not consider the script at production stage so feel free to develop it in any way you want. To recap the current problems from my POV: 1. en/ should have it's own directory as a normal language because xhtml output target produces lot of images which clutter root dir (please use xhtml, not html). 2. exported icons still contain original path in the filename. ideally we want fixed filenames for images so when you regenerate documentation only real changes need to be committed. 3. some manuals have difficulties (i know that for sure with math manual others I did not try). The way I can comfortably push this tree onto web server will make it pages of it's own so pmwiki format is of no help. If you want to make part of wiki the only reasonable way I see is to cooperate with Christian to create some sort of ftp/scp uploading tunnel. I have no problem with such solution, but it's in your hands then :) Pavel
Re: [LyX/master] oops, git is playing games with me.
Thx Pavel for pushing this. I'd like to add to the script the capability to
generate the index in PmWiki format, so that its output can be copy'n'pasted
straight to
http://wiki.lyx.org/LyX/Manuals2
What'd'u think?
T.
On 17/08/2017 01:25, Pavel Sanda wrote:
commit e8b324a984e6cbbeb4ea02ba553bd5da520eb3f8
Author: Pavel Sanda
Date: Thu Aug 17 01:24:44 2017 +0200
oops, git is playing games with me.
---
development/tools/generate_manuals_for_web.sh |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/development/tools/generate_manuals_for_web.sh
b/development/tools/generate_manuals_for_web.sh
index 2ae337c..b28a638 100755
--- a/development/tools/generate_manuals_for_web.sh
+++ b/development/tools/generate_manuals_for_web.sh
@@ -18,8 +18,7 @@
# $TOC - final index.html that links all converted manuals
# $TMP - temporary folder where all the conversion is done
-#MAIN_DOCS=${MAIN_DOCS:-"Intro Tutorial UserGuide Math Additional Customization Shortcuts LFUNs"}
-MAIN_DOCS=${MAIN_DOCS:-"Math"}
+MAIN_DOCS=${MAIN_DOCS:-"Intro Tutorial UserGuide Math Additional Customization
Shortcuts LFUNs"}
LYX=${LYX:-${PWD}/src/lyx}
OUT=${OUT:-$HOME/web/lyxdoc}
TOC=${TOC:-lyxdoc/index.html}
Re: Oops... (Re: [Cvslog] r13617 - /lyx-devel/trunk/src/mathed/math_nestinset.C)
On Mon, 2006-04-10 at 13:55 +0300, Martin Vermeer wrote: > ...wrong tree, wrong patch (right log entry :-( ) > > I'll try and revert this. Done. Sorry for the noise (using esvn for the first time to commit, and not concentrating) - Martin signature.asc Description: This is a digitally signed message part
Re: Oops... (Re: [Cvslog] r13617 - /lyx-devel/trunk/src/mathed/math_nestinset.C)
Martin Vermeer <[EMAIL PROTECTED]> writes: | ...wrong tree, wrong patch (right log entry :-( ) | | I'll try and revert this. | | - Martin | | On Mon, 2006-04-10 at 10:48 +, [EMAIL PROTECTED] wrote: | > Author: vermeer | > Date: Mon Apr 10 12:47:59 2006 | > New Revision: 13617 Reverting is done by having a clean tree, merging in the reverse commitset and committing. svn co lyx-devel svn merge -r13617:13616 svn commit -m 'Reverted r13617' (With some checking in between of course.) -- Lgb
Oops... (Re: [Cvslog] r13617 - /lyx-devel/trunk/src/mathed/math_nestinset.C)
...wrong tree, wrong patch (right log entry :-( ) I'll try and revert this. - Martin On Mon, 2006-04-10 at 10:48 +, [EMAIL PROTECTED] wrote: > Author: vermeer > Date: Mon Apr 10 12:47:59 2006 > New Revision: 13617 > > Log: > Fix bug 2485 and crash on middle-mouse paste into math. > Also move reponse to middle mouse from Release to Press > > * math_nestinset.C > (MathNestInset::lfunMousePress): Add and convert to editXY > (MathNestInset::lfunMouseRelease): Remove > > Modified: > lyx-devel/trunk/src/mathed/math_nestinset.C > > > ___ > Cvslog mailing list > [EMAIL PROTECTED] > http://www.lyx.org/mailman/listinfo/cvslog > signature.asc Description: This is a digitally signed message part
oops [Re: finding a tarball on a fat-less fat partition--disk editor?
ack, wrong list . . . --
Re: Oops - missing de_TOC.lyx
> "Peter" == Peter Suetterlin <[EMAIL PROTECTED]> writes: Peter> Jean-Marc Lasgouttes wrote: >> BTW, Amir, hasn't there been some discussions about creating >> automatically the xx_TOC.lyx files? Peter> you mean on-the-fly? A perl script to do it is there, that's Peter> what I used (in a slightly changed version)... Yes, the idea was to expand the perl script to do all the languages, so that translators would not have to do it themselves. JMarc
Re: Oops - missing de_TOC.lyx
Jean-Marc Lasgouttes wrote: > BTW, Amir, hasn't there been some discussions about creating > automatically the xx_TOC.lyx files? you mean on-the-fly? A perl script to do it is there, that's what I used (in a slightly changed version)... Pit
Re: Oops! gcc 2.8.x _does_ support std:: namespace
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Aaarggghhh!!! (do...redo...reredo...) Somehow I knew you would not like this... Lars> Ok, then I will remove all uses of "using ...;" from the .h Lars> files, I'll leave them in the .C files. That makes sense. In fact, gcc 2.8.x has the same level of C++ support as egcs 1.0.x, except possibly for some bugs. JMarc
Re: Oops! gcc 2.8.x _does_ support std:: namespace
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Lars, | | Sorry about what I wrote a few days ago: gcc 2.8.x happily compiles | stuff like std::vector (and simply ignores them). It was gcc 2.7.x | which did not. Aaarggghhh!!! (do...redo...reredo...) Ok, then I will remove all uses of "using ...;" from the .h files, I'll leave them in the .C files. Lgb
Oops! gcc 2.8.x _does_ support std:: namespace
Lars, Sorry about what I wrote a few days ago: gcc 2.8.x happily compiles stuff like std::vector (and simply ignores them). It was gcc 2.7.x which did not. So you can do what you want with 'using' directive, since it seems clear that gcc 2.7.x is not going to be supported again... JMarc
Re: oops!
Guys
> I have been looking into this although I haven't much time to do the
> implementation. So far I've found at least twenty different variations of
> cite ranging from "cite" to "citeauthor" to "astrocite" and the much
> requested "cite[ntp]" etc. Unfortunately, my best plan at present
> involves a change in the lyx file format which is not backwards
> compatible. So sharing files with others would require everyone to
> upgrade.
>
> Anyway, I'm looking at adding a drop-list of citation types available for
> particular citation packages or classes to the Insert->Citation popup.
> The Layout->Document popup would have an entry for which extra citation
> package you wanted to use also. Thus there are also changes to the layout
> files or at least extra layout files to be included on demand.
I don't think it is really an issue which one we (well, you) implement. I now
use Natbib after previously using Harvard. Both had a similar format but
slightly different command set. I simply added the following to my preamble to
map the harvard command set to the Natbib command set. I'm sure people can
manage that.
% Use the Natbib package but keep Harvard command set
\usepackage[comma,round,sort&compress,authoryear,longnamesfirst]{natbib}
\renewcommand{\cite}{\citep}
\newcommand{\citeasnoun}{\citet}
\renewcommand{\citename}{\citeauthor}
If you wanted to make it automatic then you could check which package has
been selected then map the commands accordingly. If this is impractical then
you could have additional flags on the bibtex reference box for all the
different citation packages.
Hope the suggestions help.
Ben
Re: oops!
> "Mike" == <[EMAIL PROTECTED]> writes: Mike> The AASTeX package uses natbib.sty for it's citation mechanism Mike> (natbib is a standard part of the teTeX distribution). AASTeX Mike> itself uses only the \citep and \citet commands. A LyX Mike> implementation of an extended citation popup should probably Mike> generally support the natbib package. My impression was that Mike> natbib was supposed to replace all sort of other citation hacks. Hmm, and what about \bibitem? I guess we would have to change the bibkey inset too. JMarc
Re: oops!
> > Thus, my serious consideration to be a mercenary and taint the > > pristine waters of Open Source code with filthy lucre ... > > I don't think anyone has ever really said Free software had to be free. > (No, Stallman doesn't oppose paying for software its the not sharing > code and ideas he doesn't like) And let me remind you about the LyX Funding page: http://www.devel.lyx.org/funding.php3 Greets, Asger
Re: oops!
On Thu, 30 Sep 1999 [EMAIL PROTECTED] wrote: > On Fri, 1 Oct 1999, Allan Rae wrote: > > > Mike> Besides, I would be much more excited about it if my pet > > > Mike> \citet/\citep mechanism were implemented; I think that is a > > > > I have been looking into this although I haven't much time to do the > > implementation. So far I've found at least twenty different variations of > > cite ranging from "cite" to "citeauthor" to "astrocite" and the much > > requested "cite[ntp]" etc. Unfortunately, my best plan at present > > involves a change in the lyx file format which is not backwards > > compatible. So sharing files with others would require everyone to > > upgrade. > > The AASTeX package uses natbib.sty for it's citation mechanism (natbib is > a standard part of the teTeX distribution). AASTeX itself uses only the > \citep and \citet commands. A LyX implementation of an extended citation > popup should probably generally support the natbib package. My impression > was that natbib was supposed to replace all sort of other citation hacks. Well, I've archived the two long threads from both lyx-devel and lyx-users from about a month ago and while natbib is popular there seems to be at least 6 cite variations that people on the lists want and not all those are in natbib. > Yes, this will mean a file format change, and is thus way beyond my coding > abilities. (Now, if LyX were written in FORTH, it might be a different > story :-) Ahhh, you must be a good astronomer then if you know FORTH. > Thus, my serious consideration to be a mercenary and taint the > pristine waters of Open Source code with filthy lucre ... I don't think anyone has ever really said Free software had to be free. (No, Stallman doesn't oppose paying for software its the not sharing code and ideas he doesn't like) Allan. (ARRae)
Re: oops!
On Fri, 1 Oct 1999, Allan Rae wrote: > > Mike> Besides, I would be much more excited about it if my pet > > Mike> \citet/\citep mechanism were implemented; I think that is a > > I have been looking into this although I haven't much time to do the > implementation. So far I've found at least twenty different variations of > cite ranging from "cite" to "citeauthor" to "astrocite" and the much > requested "cite[ntp]" etc. Unfortunately, my best plan at present > involves a change in the lyx file format which is not backwards > compatible. So sharing files with others would require everyone to > upgrade. The AASTeX package uses natbib.sty for it's citation mechanism (natbib is a standard part of the teTeX distribution). AASTeX itself uses only the \citep and \citet commands. A LyX implementation of an extended citation popup should probably generally support the natbib package. My impression was that natbib was supposed to replace all sort of other citation hacks. Yes, this will mean a file format change, and is thus way beyond my coding abilities. (Now, if LyX were written in FORTH, it might be a different story :-) Thus, my serious consideration to be a mercenary and taint the pristine waters of Open Source code with filthy lucre ... (That's offering money for code for all you non-King-James-English speakers out there.) Mike [EMAIL PROTECTED]
Re: oops!
On 30 Sep 1999, Jean-Marc Lasgouttes wrote: > > "Mike" == <[EMAIL PROTECTED]> writes: > > Mike> I submitted AASTeX just after 1.0.3, so it has been forgotten. > Mike> Besides, I would be much more excited about it if my pet > Mike> \citet/\citep mechanism were implemented; I think that is a > Mike> serious deficiency in LyX for use with AASTeX, and thus the > Mike> AASTeX stuff is more of a toy than a real paper writing tool > Mike> (sorry guys). I hate telling people "Yeah, LyX is great for > Mike> writing astronomical manuscripts, but you still have to do > Mike> citations by hand because LyX only knows about \cite." If the > Mike> citation stuff were "fixed", I would be generating e-mail to the > Mike> AAS in Washington, DC, and asking them to officially sanction > Mike> LyX for use in writing papers. I just don't feel right about > Mike> doing this in its current configuration. > > This is not very difficult to add now, but somebody's got to do it. > And since most developpers use happily [1], it is not high on the todo > list. I have been looking into this although I haven't much time to do the implementation. So far I've found at least twenty different variations of cite ranging from "cite" to "citeauthor" to "astrocite" and the much requested "cite[ntp]" etc. Unfortunately, my best plan at present involves a change in the lyx file format which is not backwards compatible. So sharing files with others would require everyone to upgrade. Anyway, I'm looking at adding a drop-list of citation types available for particular citation packages or classes to the Insert->Citation popup. The Layout->Document popup would have an entry for which extra citation package you wanted to use also. Thus there are also changes to the layout files or at least extra layout files to be included on demand. > Mike> Perhaps I should play Imperious American Capitalist Pig and > Mike> offer a monetary reward for the implementation of such a feature > Mike> ... > > This might be a way to overcome the lack of interest of the core > developpers for the feature, maybe... I could certainly use the money since my PhD scholarship runs out next Thursday... Allan. (ARRae)
Re: oops!
> Besides, I > would be much more excited about it if my pet \citet/\citep mechanism were > implemented; I think that is a serious deficiency in LyX for use with > AASTeX, and thus the AASTeX stuff is more of a toy than a real paper > writing tool (sorry guys). I hate telling people "Yeah, LyX is great for > writing astronomical manuscripts, but you still have to do citations by > hand because LyX only knows about \cite." If the citation stuff were > "fixed", I would be generating e-mail to the AAS in Washington, DC, and > asking them to officially sanction LyX for use in writing papers. I just > don't feel right about doing this in its current configuration. Yes, yes, yes. I agree totally. I now feel that the only thing that Lyx really lacks is the ability to toggle between citations. The rest is (relatively) incidental. When showing people Lyx they always ask "what is that ERT"? Well, they don't actually say ERT but more like "that looks like latex". I have to concede to them that it is the only way I can get a noun type citation. Ben PS Congrats on releasing 1.0.4 and keep up the good work!!
Re: oops!
> "Mike" == <[EMAIL PROTECTED]> writes: Mike> I submitted AASTeX just after 1.0.3, so it has been forgotten. Mike> Besides, I would be much more excited about it if my pet Mike> \citet/\citep mechanism were implemented; I think that is a Mike> serious deficiency in LyX for use with AASTeX, and thus the Mike> AASTeX stuff is more of a toy than a real paper writing tool Mike> (sorry guys). I hate telling people "Yeah, LyX is great for Mike> writing astronomical manuscripts, but you still have to do Mike> citations by hand because LyX only knows about \cite." If the Mike> citation stuff were "fixed", I would be generating e-mail to the Mike> AAS in Washington, DC, and asking them to officially sanction Mike> LyX for use in writing papers. I just don't feel right about Mike> doing this in its current configuration. This is not very difficult to add now, but somebody's got to do it. And since most developpers use happily [1], it is not high on the todo list. Mike> Perhaps I should play Imperious American Capitalist Pig and Mike> offer a monetary reward for the implementation of such a feature Mike> ... This might be a way to overcome the lack of interest of the core developpers for the feature, maybe... JMarc
Re: oops!
On Thu, 30 Sep 1999, Amir Karger wrote: > How come aastex isn't mentioned though? Mike might get offended that the > physicists are considered more important than the astro-folk. I submitted AASTeX just after 1.0.3, so it has been forgotten. Besides, I would be much more excited about it if my pet \citet/\citep mechanism were implemented; I think that is a serious deficiency in LyX for use with AASTeX, and thus the AASTeX stuff is more of a toy than a real paper writing tool (sorry guys). I hate telling people "Yeah, LyX is great for writing astronomical manuscripts, but you still have to do citations by hand because LyX only knows about \cite." If the citation stuff were "fixed", I would be generating e-mail to the AAS in Washington, DC, and asking them to officially sanction LyX for use in writing papers. I just don't feel right about doing this in its current configuration. Perhaps I should play Imperious American Capitalist Pig and offer a monetary reward for the implementation of such a feature ... Mike [EMAIL PROTECTED]
Re: oops!
On Thu, Sep 30, 1999 at 04:57:53PM +0200, Jean-Marc Lasgouttes wrote: > > "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: > > Amir> We didn't update WHATSNEW! My suggestion: > > When is the last time you ran 'cvs up'? Wow. Amir gets the stupid prize twice in two weeks. How come aastex isn't mentioned though? Mike might get offended that the physicists are considered more important than the astro-folk. -Amir
Re: oops!
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> We didn't update WHATSNEW! My suggestion: When is the last time you ran 'cvs up'? JMarc
oops!
We didn't update WHATSNEW! My suggestion: What's new in 1.0.4 compared to LyX version 1.0.3? -- LyX 1.0.4 is a minor update to LyX 1.0.3. Besides fixing some bugs compared to version 1.0.3 and enhancing stability, it adds the following features: - DocBook support - new layouts: aastex, revtex4, g-brief (german letter) - better handling of custom pagesizes - more document files translated to other languages -- Did I miss anything? While we're at it, ANNOUNCE should list 1.0.4 at the top *and* in the ftp links. Would there be a way to use fancy RCS/CVS commands to automatically put the right version numbers in there? E.g. if you set the name (rcs -n) to, e.g., "1.0.4" or "1.0.4pre4" right before releasing preversions, then you would just recheck out everything and the right version numbers would be in there (e.g. you would linke to ftp.lyx.org/pub/lyx/stable/lyx-$Name$.tar.gz. Of course this wouldn't fix WHATSNEW. A weird and possibly nonworking idea would be to also give the web pages this name, so that the download pages automatically pointed to the right place. I mean, we're not going to have any other reason to name the web site versions, right? -Amir
oops, here's the attachement
I hit ^C^C in the file selection menu in exmh, and instead of a "huh?", it sent the underlying message . . . resume.ps
Re: OOPS!
> disregard the previous email. Unless you like star wars. It was supposed to > go to stefan, who missed the boat again. The boat, or the shuttle? :) Maybe he went to the dark side. He could even be using Word this very minute . . . rick, whose 7 year old daughter is anxiously awaiting the next movie. --
OOPS!
disregard the previous email. Unless you like star wars. It was supposed to go to stefan, who missed the boat again. -Amir
Re: Tutorial oops
Okay - I committed this to lyxdoc (with the patch). Mike [EMAIL PROTECTED]
Tutorial oops
OK. Patch for the tutorial. Sorry. -Amir --- zzz Tue Mar 2 14:59:53 1999 +++ Tutorial.lyxTue Mar 2 14:59:26 1999 @@ -1,4 +1,4 @@ -#This file was created by Tue Mar 2 13:46:34 1999 +#This file was created by Tue Mar 2 14:59:26 1999 #LyX 1.0 (C) 1995-1998 Matthias Ettrich and the LyX Team \lyxformat 2.15 \textclass book @@ -986,7 +986,22 @@ \begin_inset Quotes erd \end_inset - hints about how to fix things. + hints about how to fix things +\begin_float footnote +\layout Standard + +The hints are located in yellow +\begin_inset Quotes eld +\end_inset + +Notes +\begin_inset Quotes erd +\end_inset + +. + Access the text in a note by clicking on it. +\end_float +. If you want to cheat (or check what you've done), there's also a file called \family typewriter @@ -1027,9 +1042,11 @@ s \family default to save a copy in your own directory for you to work on. + As you fix parts of the raw document, check to see how those changes affect + the dvi output. \layout Standard -The +By the way, the \family typewriter examples/ \family default @@ -1431,6 +1448,23 @@ . If you hold the mouse above one of the buttons on the toolbar, a little yellow note will tell you that button's function. +\layout Description + +Minibuffer The gray line at the very bottom of the LyX window is called + the minibuffer. + This line will show all sorts of useful information. + For example, when you save, it will tell you the name of the file you just + saved. + Some error messages may show up here, too. + Note that you can +\emph on +type +\emph default + in the minibuffer too. + This gives you access to all sorts of interesting functionality, including + functionality which could break your document. + In other words, don't type in the minibuffer unless you know what you're + doing. \layout Standard Of course, you haven't yet written enough to make most of these functions
Re: Oops - here's de.po
Thanks. I just did the commit. JMarc
Oops - here's de.po
de.po.gz
oops! Here's the devel page
Forgot the attachment! Title: LyX - Developers only Navigate · LyX Home page · Developers only · CVS Web · CVS Commit log Customize · Short titles · Top navigator Developers only Welcome to the LyX developers only web-site. This site is meant to be used primarily by the developers of LyX. For general information about LyX, please visit the LyX homepage instead. This site will be expanding as we retrieve and update some of the less important pages that were lost in a crash. However, the essential resources are back on line. LyX 1.0 has been released! LyX 1.0.0 was released on February 1, 1999. For more information on its features, or to download it, please visit the LyX homepage. This release, coming after a long code freeze, allows the developers to focus on the new development branch, LyX 1.1; it features a kernel rewrite and toolkit independence, along with a bunch of smaller upgrades. Help wanted! LyX is an open source project, and we need your help! LyX is developed by volunteers from around the world. We work in our free time, and do our best, but we need your help to continuously improve! Do you have a few bucks to spare? If you want to show your support to the LyX effort, please consider making a donation to Lars Gullik Bjønnes to help us get a new machine to host these development resources. Do you know C++? If you are a programmer and can program in C++, please consider contributing to the coding effort. Get the latest cvs version, have a look at the code, and see if there is something you'd like to tangle with. Contact the LyX Developer's mailing list and we'll try to set you up. Are you a LyX power user? If you are a skilled LyX user, you might want to help out with the documentation effort. The LyX documentation is considered to be very good, but the development of LyX is moving faster than the DocTeam can keep up! So, if you know how to use LyX, or want to learn, get the latest docs from cvs and read the introduction which contains information on how to contribute to the documentation effort. I understand English, but I write ... The LyX program and its documentation are developed in English. However, many LyX developers and users write or speak other languages. Contributions for LyX internationalization are always welcome. There are three sorts of contributions you could make: Key bindings Allow users with US keyboards to type in various languages Menus and commands Translate LyX menus into other languages with .po files Documentation Translate the documentation into other languages. A German translation has already been mostly finished. If you have the time, please read the User Guide chapter on Internationalization, and start translating! I have an idea! If you have a cool idea for a new feature, or comments in general about LyX, please share them with us. The more feedback we get from the users, the better we know what we should prioritize in the development effort. Questions? If you have a question regarding the development of LyX, please write us at the LyX developer's mailing list. Thanks for your help. [EMAIL PROTECTED]
oops!
forgot the file!
#This file was created by Tue Jan 26 17:48:36 1999
#LyX 1.0 (C) 1995-1998 Matthias Ettrich and the LyX Team
\lyxformat 2.15
\textclass revtex
\options aps,manuscript
\layout Title
Insert your Title Here
\layout Author
Author1
\begin_float footnote
\layout Standard
Author to whom correspondence should be addressed
\end_float
and Author2
\layout Address
Insert the name of your university, company, or institute here.
\layout Standard
\begin_inset Info You don't have to write \maketitle.. LyX does this by itself.
\end_inset
\layout Abstract
Insert your abstract here.
\layout Section
Introduction
\layout Standard
Introduction goes here.
\layout Standard
By the way, any of the style options, like
\family typewriter
prl
\family default
or
\family typewriter
preprint
\family default
should go in the
\family sans
Extra
\protected_separator
Options
\family default
field in the
\family sans
Document
\protected_separator
Layout
\family default
popup (accessed from the
\family sans
Layout
\family default
menu).
\layout Section
Insert section title here
\layout Standard
Section 2 text goes here.
\layout Standard
Special REVTeX 3.1 macros must be typed in TeX mode, so typing
\family typewriter
\backslash
openone
\family default
in TeX mode yields
\latex latex
\backslash
openone{}
\latex default
.
(See the REVTeX manual for other macros.) REVTeX macros can also be used
freely in the math editor, so you can type
\begin_inset Formula \( \sqrt{\overstar {a}}>\overcirc {b} \)
\end_inset
.
\layout Standard
You can do a bibliography by hand, as shown below, or erase that, and use
BibTeX.
If you use BibTeX, don't forget to use a REVTeX bibliography style file,
such as
\family typewriter
prsty.bst
\family default
.
With either method, you can cite references with the LyX citation commands
\begin_inset LatexCommand \cite{mycitation}
\end_inset
.
\begin_inset Info If you get question marks instead of numbers in your references,
re-run LaTeX (File->update dvi)
\end_inset
\layout Bibliography
\bibitem {mycitation}
Author,
\begin_inset Quotes eld
\end_inset
Title
\begin_inset Quotes erd
\end_inset
, Journal
\series bold
Volume
\series default
, page--numbers (year).
\the_end
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 01:22:51PM -0500, Amir Karger wrote: > I'm a bit wary of sticking this inside Extended Editing. Does it really fit? > And it's kind of big Once the dialog has been perfected, it would make > somewhat more sense I suppose. OTOH, maybe this would belong in the LyX and > LaTeX chapter of UG. Is this really an extended feature? I can't tell. Depending upon its size, it probably should be a section [and a prominent one] in the LaTeX chapter of UG, called "Importing LaTeX Files." Consider this a semi-definitive edict [I haven't read reLyXdoc yet] from the former DocProject Grand-Poohbah. -- John Weiss
Re: reLyXdoc (oops)
On Mon, 25 Jan 1999, Amir Karger wrote: > Again, if we do add this doc, we'll have to mention it in the intro as well > as the UG and tutorial. Is Mike unreachable in Hawaii? I'm actually more reachable than usual right now. After I get our instrument up and running tomorrow, I'll actually have quite a bit of time for LyX doc tinkering since I'm only supporting the instrument, not actually observing with it. So I've been collecting doc suggestions over the last couple of weeks and intend to do a major dump on Friday or so. Just let me know what you want ... Mike [EMAIL PROTECTED]
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> I thought you had an AI that did that even if you didn't come in Amir> to the office. Yes, I have one, and he is a very nice one. From what Altavita tells me, an Aï is what you would call a ``Pale-Throated Three Sloth (Bradypus Tridactilus)''. In French we call them `lazy' too. It is exactly the kind of pet I needed in my office. We happen to share most of our way of life, although he tends to do more typing errors than I do. JMarc
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> On Mon, Jan 25, 1999 at 07:06:53PM +0100, Asger K. Alstrup Amir> Nielsen wrote: >> > (1) Call it reLyX, which can be translated as reLyX in all >> (latin-1) > languages. Unless you want to call it réLyX or >> something, to sound fancier. > (In america, accents make words >> foreign and hence exotic. Perhaps the joke > is lost on the few >> non-American readers of this list.) >> >> The joke is American readers. >> >> Oh sorry. It's not Friday. Amir> Hm. Perhaps the joke is the French and Danish readers who still Amir> can't get "reply" to send just one copy of e-mails... You are unfair. Lately I have stripped your name from at least half the messages I sent to you. Amir> Aha! Well, at least we got someone to talk. Asger, you should Amir> probably argue with Jean-Marc, who originally had this idea. I Amir> only really did this because Jean-Marc seemed quite in favor of Amir> it. I guess his point was that he liked having all the Amir> documentation within LyX. Me? I just proposed that to Amir as a challenge. I did not really though he would do it :) Now Amir, you can use this (and Jose's man textclass I have not commited yet) to edit the man page directly from inside LyX. Aren't you glad? JMarc
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 07:06:53PM +0100, Asger K. Alstrup Nielsen wrote: > > (1) Call it reLyX, which can be translated as reLyX in all (latin-1) > > languages. Unless you want to call it réLyX or something, to sound fancier. > > (In america, accents make words foreign and hence exotic. Perhaps the joke > > is lost on the few non-American readers of this list.) > > The joke is American readers. > > Oh sorry. It's not Friday. Hm. Perhaps the joke is the French and Danish readers who still can't get "reply" to send just one copy of e-mails... > I'm not sure we want to add that input field for reLyX. If > we should do anything, it would be a fancy dialog such that > the options are transparent to the user. > I'd prefer that importing of LaTeX is a non-brainer. If this > is unattainable, we should at least provide a user friendly > interface. > > Maybe a part of this interface is a generic input field, > but I think it would be wrong to let it stand alone. Hm. Interesting. For example, you could have a combobox to select the layout (which is just the same as the list in the Layout->Document popup and gets passed to -c), radio buttons for -d and -p (and have LyX check that a -c is chosen if -p is selected), and input fields for regular environments (-r). Plus an input field for extra syntax files (-s) with a browse button. I would think it would be pretty simple to build this, no? > Regarding whether to include the documentation inside LyX: > I think not. Since you have to do the work at the command > line never the less, there is really no point in having > a largish document inside LyX that basically says: > Go to a prompt and do this. A man page serves this > purpose beautifully. > > So at this point, it does not make much sense to put > the documentation as a separate item under the help > menu. What I propose is this: Insert it by hand > into one of the exisiting documents, preferably the > Extended Editing, or whatever it's called, with > a proper disclaimer attached. Later, when we get > the fancy dialog, we can then adjust the disclaimer > appropriately. > Aha! Well, at least we got someone to talk. Asger, you should probably argue with Jean-Marc, who originally had this idea. I only really did this because Jean-Marc seemed quite in favor of it. I guess his point was that he liked having all the documentation within LyX. I'm a bit wary of sticking this inside Extended Editing. Does it really fit? And it's kind of big Once the dialog has been perfected, it would make somewhat more sense I suppose. OTOH, maybe this would belong in the LyX and LaTeX chapter of UG. Is this really an extended feature? I can't tell. -Amir
Re: reLyXdoc (oops)
> OK. In that case... HELP! I don't know how to add things to menus and I > don't have lyxdoc access (or maybe I do?) Can a devvie help me out with > this? Adding something to the menu is as simple as editing menus.C appropriately. However, as I just wrote, I think the better option is to embed the information in an existing manual. Greets, Asger
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 06:59:31PM +0100, Jean-Marc Lasgouttes wrote: > > "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: > > Amir> #1 is *way* easier, so why don't we do that now. There are other > Amir> things that we need to do this week (I was hoping I could send > Amir> in a reLyX with a semi-large bugfix, fix the revtex > Amir> template... and I'm sure others have things to do too) > > Personally, I probably will not have time this week to do thing which > require a brain. I will probably manage to commit Jose's patch for man > support (did you have a look at the file, Amir?), but not much > more. So don't count on me for that. OK. In that case... HELP! I don't know how to add things to menus and I don't have lyxdoc access (or maybe I do?) Can a devvie help me out with this? > Oh, and I will probably not be able to refrain from sending random > nonsensical e-mails to the list. I thought you had an AI that did that even if you didn't come in to the office. -Amir
Re: reLyXdoc (oops)
> (1) Call it reLyX, which can be translated as reLyX in all (latin-1) > languages. Unless you want to call it réLyX or something, to sound fancier. > (In america, accents make words foreign and hence exotic. Perhaps the joke > is lost on the few non-American readers of this list.) The joke is American readers. Oh sorry. It's not Friday. > (2) Call it Importing LaTeX Documents. We would of course change the Title. > Then we'd have Section 1 be "Two Ways to Import". 1.1 would describe > importing from LyX (very simple, at least until Asger adds to the popup > the input field for adding options to the reLyX call). 1.2 would be the > current sections 1 and 2. (When Asger does add that input field, we could > have the options be section 2). Then sections 2-n would be the current > sections 3-n. They describe things like what reLyX can translate, syntax > files, etc. which is important to know whether you're using reLyX from the > command line or from LyX. Finally, we'll need to contact all the translators > and ask them to update the menu translations. I'm not sure we want to add that input field for reLyX. If we should do anything, it would be a fancy dialog such that the options are transparent to the user. I'd prefer that importing of LaTeX is a non-brainer. If this is unattainable, we should at least provide a user friendly interface. Maybe a part of this interface is a generic input field, but I think it would be wrong to let it stand alone. Regarding whether to include the documentation inside LyX: I think not. Since you have to do the work at the command line never the less, there is really no point in having a largish document inside LyX that basically says: Go to a prompt and do this. A man page serves this purpose beautifully. So at this point, it does not make much sense to put the documentation as a separate item under the help menu. What I propose is this: Insert it by hand into one of the exisiting documents, preferably the Extended Editing, or whatever it's called, with a proper disclaimer attached. Later, when we get the fancy dialog, we can then adjust the disclaimer appropriately. Greets, Asger
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> #1 is *way* easier, so why don't we do that now. There are other Amir> things that we need to do this week (I was hoping I could send Amir> in a reLyX with a semi-large bugfix, fix the revtex Amir> template... and I'm sure others have things to do too) Personally, I probably will not have time this week to do thing which require a brain. I will probably manage to commit Jose's patch for man support (did you have a look at the file, Amir?), but not much more. So don't count on me for that. Oh, and I will probably not be able to refrain from sending random nonsensical e-mails to the list. JMarc
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> The only reason I could think of that someone wouldn't want to Amir> put it in is that having too many manuals in the help menu could Amir> be confusing. But it seems to me that if it's called "Importing Amir> LaTeX Documents", it won't really increase confusion any. If it is named like this, it should make first how to import documents from LyX. A man page is not really done for this. And if we add it in Help menu, we'll have to check all the i18n files, so that the Help file comes out properly translated. Just to add to your confusion. JMarc
Re: reLyXdoc (oops)
On Mon, Jan 25, 1999 at 06:14:19PM +0100, Jean-Marc Lasgouttes wrote: > > "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: > > Amir> The only reason I could think of that someone wouldn't want to > Amir> put it in is that having too many manuals in the help menu could > Amir> be confusing. But it seems to me that if it's called "Importing > Amir> LaTeX Documents", it won't really increase confusion any. > > If it is named like this, it should make first how to import documents > from LyX. A man page is not really done for this. And if we add it in > Help menu, we'll have to check all the i18n files, so that the Help > file comes out properly translated. > > Just to add to your confusion. Hm. OK, then we've got at least two options. (1) Call it reLyX, which can be translated as reLyX in all (latin-1) languages. Unless you want to call it réLyX or something, to sound fancier. (In america, accents make words foreign and hence exotic. Perhaps the joke is lost on the few non-American readers of this list.) (2) Call it Importing LaTeX Documents. We would of course change the Title. Then we'd have Section 1 be "Two Ways to Import". 1.1 would describe importing from LyX (very simple, at least until Asger adds to the popup the input field for adding options to the reLyX call). 1.2 would be the current sections 1 and 2. (When Asger does add that input field, we could have the options be section 2). Then sections 2-n would be the current sections 3-n. They describe things like what reLyX can translate, syntax files, etc. which is important to know whether you're using reLyX from the command line or from LyX. Finally, we'll need to contact all the translators and ask them to update the menu translations. #1 is *way* easier, so why don't we do that now. There are other things that we need to do this week (I was hoping I could send in a reLyX with a semi-large bugfix, fix the revtex template... and I'm sure others have things to do too) -Amir
Re: reLyXdoc (oops)
On Wed, Jan 20, 1999 at 07:10:49PM +0100, Jean-Marc Lasgouttes wrote: > > "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: > > Amir> Forgot to attach this! -Amir > > So, what shall we do wih it? Setting apart the amazing technical feat, Next I'm going to write a perl script to make lyx documents turn cartwheels... > what is the feeling of doc people about whether this should go in > docs? Can we assume that the deafening lack of response implies that people either agree it should go in or don't care? I didn't really think most people would have a very strong opinion on this. Basically, it adds a few K to the distribution and most people will never look at it. The only reason I could think of that someone wouldn't want to put it in is that having too many manuals in the help menu could be confusing. But it seems to me that if it's called "Importing LaTeX Documents", it won't really increase confusion any. Again, if we do add this doc, we'll have to mention it in the intro as well as the UG and tutorial. Is Mike unreachable in Hawaii? -Amir
Re: reLyXdoc (oops)
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> Forgot to attach this! -Amir So, what shall we do wih it? Setting apart the amazing technical feat, what is the feeling of doc people about whether this should go in docs? JMarc
reLyXdoc (oops)
Forgot to attach this! -Amir reLyX.lyx.gz
