Re:Invokation of tex2lyx and lyx2lyx

[Georg Baum]

Uwe Stöhr wrote:

   1) convert test.tex - tmp_dir/_test.lyx (format xxx) (tex2lyx)
   2) convert tmp_dir/_test.lyx (format xxx) -
   tmp_dir/_test_new.lyx (format yyy) (lyx2lyx)
   3) load tmp_dir/_test_new.lyx (format yyy) in LyX,
   when the user sves this file it is copied to the directory of
   test.tex
 
   I like 1) and 2), because it avoids overwriting the original .tex
 file  with Export-Latex, but instead of 3) I would simply keep an
 unnamed
   document.
 
 Why that and where would you keep it?

It would be kept in memory (the same what happens if you create a new file
with File-New).
Why? Because users are forced to think about a name for the converted
document. I have found myself several times in the situation where I
accidentally destroyed the original .tex file by Export-Latex.

 But anyway if you also like 1) and 2) perhaps we should implement it in
 future LyX versions.
 
   Besides that: What happens with master/child documents?
 
 I've never used master/child documents.

Ok, if you do that you will notice that tex2lyx will also convert the child
documents. This will complicate things if we implement the behaviour above.


Georg

Re: William Leeming

[Stephan Witt]

Angus Leeming wrote:

I'd like to announce the arrival of William who arrived on Tuesday 15
November, weighing in at 3.55kg (7lb 12oz in old money.)


Congratulations, especially to your wife.


It wasn't
easy getting him out (40 hours labour followed by a Cæsarian) but now
he is out both he and Emma are doing really well.


That was really hard, I hope the medicine men did it all well.


I've put together a few pictures to satisfy your curiosity:
http://www.lyx.org/~leeming/William/
It's not a very professional-looking page but, hey ho, it should give
you a flavour.


Very nice...

Stephan

Re: [announce] fourth release of the LyXWinInstaller

[Georg Baum]

Uwe Stöhr wrote:

 I understand you.
 The icons I mentioned shouldn't be a problem. They are only used for the
 installer executables itself and for the lyx-files in Windows
 file-explorer. That I added/changed some icons in LyX's menu bar is just a
 special gimmick. I've installed LyX for many people and most of them
 wanted for example an icon for search in LyX's menu bar and a shortcut
 to Export - PDF (pdflatex). So I thaught if these small bits make users
 happy, I'll add them.

[...]

 At last while talking with José about some lyx2lyx issues I asked him if
 I should use tex2lyx in my installer and he said yes to enforce the
 tex2lyx/lyx2lyx situation. So I dared to pack it in.

All valid reasons. My concern is that your LyX will diverge from mainline,
and I think that this would be very bad.
Why not feed your improvements back to mainline instead of offering them
only to the windows people?
Having said that I also need to say that I don't think that bigger changes
should be done in 1.3.x anymore. The time to integrate tex2lyx for example
is better spent in testing 1.4cvs. We should get that out as soon as
possible.


Georg

Re: [announce] fourth release of the LyXWinInstaller

[Jose' Matos]

On Tuesday 22 November 2005 08:44, Georg Baum wrote:
 Having said that I also need to say that I don't think that bigger changes
 should be done in 1.3.x anymore. The time to integrate tex2lyx for example
 is better spent in testing 1.4cvs. We should get that out as soon as
 possible.

  I agree with Georg here. Things are really improving and I think all the 
efforts are best applied in getting 1.4 out where some of the remaining 
issues are already solved.

  Any time plan for a release candidate?

  How about getting 1.4.0 before Christmas, after all we already promissed 
this 2 years ago. ;-)

 Georg

-- 
José Abílio

Re: Invokation of tex2lyx and lyx2lyx

[Jose' Matos]

On Tuesday 22 November 2005 08:23, Georg Baum wrote:
  I've never used master/child documents.

 Ok, if you do that you will notice that tex2lyx will also convert the child
 documents. This will complicate things if we implement the behaviour above.

  That is why I suggested to load the documents with same name and location of 
its counterpart tex. The file would not be saved, thus when the file is saved 
the users takes care of any possible collisions.

  LyX using by default the -f options always scared me.

 Georg

-- 
José Abílio

Bug 2136 Invalid latex generated with paragraph settings inside no inner box

[Helge Hafting]

Reproduce:
* Insert a box. Write text inside it.
* Bring up box settings, set it to:
 - rectangular frame
 - no inner box  (necessary)
 - width = 1 width
* Place cursor inside box
* edit-paragraph settings
* Set something nondefault, such as centering or doublespacing

Lyx will now generate invalid latex.
I believe the frameless box doesn't contain a paragraph (Using ENTER 
don't work in there) so it makes sense that you cannot apply paragraph 
settings there. But lyx lets me do that anyway, and then latex pukes.


Suggested fixes:
1. Disable the paragraph settings menu item when editing in a box with 
no inner box.
2. Users can put a box around anything, so when the user turns the box 
into the no inner box kind, please kill any paragraph settings 
contained within so as to avoid latex errors later.  No inner box is 
useful, but it is an environment with limited capabilities. Or possibly 
move the offending paragraph settings out into the paragraph containing 
the box. (Better, but quite possibly more work.)


I discovered this when trying to have a no inner box frame around a 
doublespaced table. This actually works fine if the doublespacing is 
applied outside the box, i.e. in the paragraph containing the box.  But 
that is not what happens if you apply a box around such a table and then 
set it to no inner box.


I guess some of the problem comes from the way lyx has a box inset for 
all kinds of boxes.  But a minipage/parbox contains paragraph(s), while 
a no inner box is just text markup similiar to bold.

Bug 2137: Box with width=1 width is way too thin on screen

[Helge Hafting]

A frame box with no inner box can be set to width=1 width meaning 
that the box will have the width of whatever it contains.  This is very 
nice for making double-border tables, or higlighting a word with a box.


Unfortunately, lyx seems to assume that such a box is a narrow column. 
Output is ok, but the content on screen is squashed into a horrible 
narrow column, whenever such a box is applied to wide content.  A boxed 
wide table looks _really_ bad this way. Try and cry.


Suggested fix: Don't let such a box limit the display. Draw the contents 
as if
the box wasn't there, and paint the box around the result.  Or a box the 
width of the lyx window if that is easier.  Anything but this . . .

Re: William Leeming

[Andreas Vox]

Angus Leeming [EMAIL PROTECTED] writes:

 
 Dear all,
 
 I'd like to announce the arrival of William ...

A little late, but also from me congratulations to you and your family.

So can we hope -- since you're awake at night anyway -- there will be 
continuing and steady input to our LyX project in the weeks to come? ;-)

/Andreas

Re: [announce] fourth release of the LyXWinInstaller

[Jean-Marc Lasgouttes]

 Michael == Michael Gerz [EMAIL PROTECTED] writes:

Michael I agree. What we could do is backporting tex2lyx to 1.3.7cvs.

I think this is too difficult and would require to fork tex2lyx.

JMarc

Re: [patch] fix bug 2126

[Jean-Marc Lasgouttes]

 Georg == Georg Baum [EMAIL PROTECTED] writes:

Georg Georg Baum wrote:
 I tested the patch and it works well for me. OK to apply?

Georg Take this one instaed, I forgot to implement
Georg LFUN_INSET_DIALOG_UPDATE.

Go ahead.

JMarc

Re: [PATCH] Re: bug 1952/1953

[Jean-Marc Lasgouttes]

 Juergen == Juergen Spitzmueller [EMAIL PROTECTED] writes:

Juergen Jean-Marc Lasgouttes wrote:
 At least, you could move your code that determines what the real
 text inset is into dociterator.C.

Juergen is attached.

Almost perfect :

1/ make textInset return an InsetText object; Assert on inTexted() 

2/ the loop in undo.C should use normal iterators instead of
const_iterators, so that the const_cast is not needed.

JMarc

Re: [patch] fix bug 2126

[Georg Baum]

Jean-Marc Lasgouttes wrote:

 Georg == Georg Baum
 [EMAIL PROTECTED]
 writes:
 
 Georg Georg Baum wrote:
 I tested the patch and it works well for me. OK to apply?
 
 Georg Take this one instaed, I forgot to implement
 Georg LFUN_INSET_DIALOG_UPDATE.
 
 Go ahead.

Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll discover
more...):
http://bugzilla.lyx.org/buglist.cgi?short_desc_type=allwordssubstrshort_desc=target_milestone=1.4.0long_desc_type=allwordssubstrlong_desc=bug_file_loc_type=allwordssubstrbug_file_loc=keywords_type=allwordskeywords=bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDemailtype1=substringemail1=emailtype2=substringemail2=bugidtype=includebug_id=votes=changedin=chfieldfrom=chfieldto=Nowchfieldvalue=cmdtype=doitnewqueryname=order=Reuse+same+sort+as+last+timefield0-0-0=nooptype0-0-0=noopvalue0-0-0=


Georg

plans for LyX, was: fourth release of the LyXWinInstaller

[Uwe Stöhr]

Georg Baum schrieb:


All valid reasons. My concern is that your LyX will diverge from mainline,
and I think that this would be very bad.
Why not feed your improvements back to mainline instead of offering them
only to the windows people?


I'll do. What special things do you mean should be ported to mainline?


Having said that I also need to say that I don't think that bigger changes
should be done in 1.3.x anymore. The time to integrate tex2lyx for example
is better spent in testing 1.4cvs. We should get that out as soon as
possible.


Don't beat me for the following proposal:

I can see no reason why tex2lyx need to be backported to LyX 1.3.x. 
tex2lyx runs fine with 1.3.x as it is.
I also think that my LyX diverges a bit from mainline, so I'd like to 
see 1.3.7 out WITH tex2lyx and perhaps with some of my minor changes to 
the menu bar.

JMarc what do you think needs to be done before LyX 1.3.7 can be published?

Why that? Because I have little luxus-problem: The heise.de people, who 
publish the computer magazine C't and host Germanys most readed 
computer-news page, wanted to mention my installer in their news because 
they are sold on the installer concept. I could avoid the news entry 
because I want the installer to be closer with mainline. The 
corresponding heise editor offered me to contact him when this is done 
and he would announce it in the news together with a small description.
I mean we should use this offered publicity better for LyX 1.4 or LyX 
1.3.7 than only for an installer.
Btw. he warned me that an entry at heise.de could be similar to a 
DoS-attack. Version 0.31 of my installer was downloaded 370 times within 
three days and I only announced it on the users-list and to some friends.


I'm not sure what we should do.
Is it OK when my installer could be downloaded directly from ftp.lyx.org?
Should we announce it together with a probable LyX 1.3.7 release.
What about the official Win-installer?
 Angus' version is ideal as it only ships LyX.
 My version includes third-party programs which increases the 
maintaining expenditure (for example while working on the installer I 
encountered 3 MiKTeX-bugs, 2 ImageMagick-bugs, and 1 Ghostscript-bug) 
but is ideal for beginners and unexperienced normal Win-users.


Any thoughts?

best regards Uwe

p.s.
 Angus, Michael, what about the efforts of compiling LyX 1.4 under Win? 
(Yes I know that I need to lift up my ass and try to compile it for myself.)


pp.s
 Jörg Zastrau has written a plugin to use RCS together with LyX on 
Windows. Is it OK when I include this to the network variant (the 
variant for experienced users) of my installer?

lyx140cvs: export to html

[Hartmut Haase]

This doesn't seem to work at the moment at all. Within LyX the html-file 
cannot be copied from the /tmp...-directory, and from the command line 
something like

latex2html -no_subdir -split 0 -show_section_numbers file.lyx

result in error messages like

*** no brace for \end , before:
_inset
*** using _ as the argument instead; is this correct?  ***

and others, and the resulting html-file looks weird. I was trying to convert a 
table.
-- 
Viele Grüße,
Hartmut 

Hungerhilfe: http://www.thehungersite.com

Das heutige Motto:
The trouble with some people who don't have very much to say 
is that you have to listen so long to find out. 

Re: [patch] fix bug 2126

[Jose' Matos]

On Tuesday 22 November 2005 13:58, Georg Baum wrote:
 Jean-Marc Lasgouttes wrote:
  Georg == Georg Baum
  [EMAIL PROTECTED]
  writes:
 
  Georg Georg Baum wrote:
  I tested the patch and it works well for me. OK to apply?
 
  Georg Take this one instaed, I forgot to implement
  Georg LFUN_INSET_DIALOG_UPDATE.
 
  Go ahead.

 Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll discover
 more...):

  One of those is http://bugzilla.lyx.org/show_bug.cgi?id=2088

  Have you applied your patch?

  One thing easy that we can do is a filter to catch those cases and fix them. 
It will not hurt and we will get rid of this type of errors once and for all.
The function bellow fixes this issues. What do you think?

def fix_empty_layout(file):
i = find_token(file.body, \\layout, 0)

if i == -1: return

# layout line is empty
if len(string.split(string.strip(file.body[i]))) == 1:
file.body[i] = \\layout Standard

 Georg

-- 
José Abílio

Re: [patch] fix bug 2126

[Georg Baum]

Jose' Matos wrote:

 On Tuesday 22 November 2005 13:58, Georg Baum wrote:
 Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll
 discover more...):
 
   One of those is http://bugzilla.lyx.org/show_bug.cgi?id=2088
 
   Have you applied your patch?

No, since Lars did not want it. It would be nice if you could convince him
that 1.2.x really created such files.

   One thing easy that we can do is a filter to catch those cases and fix
   them.
 It will not hurt and we will get rid of this type of errors once and for
 all. The function bellow fixes this issues. What do you think?
 
 def fix_empty_layout(file):
 i = find_token(file.body, \\layout, 0)
 
 if i == -1: return
 
 # layout line is empty
 if len(string.split(string.strip(file.body[i]))) == 1:
 file.body[i] = \\layout Standard

I like that, but I am not sure whether we want that now. You know, I have
had no good luck with appareantly simple lyx2lyx changes recently


Georg

Re: [patch] fix bug 2126

[Jose' Matos]

On Tuesday 22 November 2005 14:44, Georg Baum wrote:
 Jose' Matos wrote:
  On Tuesday 22 November 2005 13:58, Georg Baum wrote:
  Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll
  discover more...):
 
One of those is http://bugzilla.lyx.org/show_bug.cgi?id=2088
 
Have you applied your patch?

 No, since Lars did not want it. It would be nice if you could convince him
 that 1.2.x really created such files.

  Lars if you are reading this please concede this one. ;-)
  The test is done only for the first paragraph, so it is safe.

  Either that or we close this bug.

One thing easy that we can do is a filter to catch those cases and fix
them.
  It will not hurt and we will get rid of this type of errors once and for
  all. The function bellow fixes this issues. What do you think?
 
  def fix_empty_layout(file):
  i = find_token(file.body, \\layout, 0)
 
  if i == -1: return
 
  # layout line is empty
  if len(string.split(string.strip(file.body[i]))) == 1:
  file.body[i] = \\layout Standard

 I like that, but I am not sure whether we want that now. You know, I have
 had no good luck with appareantly simple lyx2lyx changes recently

  What are insinuating? ;-)
  This is my code. :-D

  I will commit this code tonight, it is safe, and as Martin says in bugzilla 
it makes the code more robust, that can only be a good thing. Even if we 
don't believe in the boogie man there are some cursed lyx files out 
there. :-)

 Georg

-- 
José Abílio

lyx140cvs: export to html, 2

[Hartmut Haase]

Sorry for the second part, I forgot to convert to latex first.
-- 
Viele Grüße,
Hartmut 

Hungerhilfe: http://www.thehungersite.com

Das heutige Motto:
The only rose without thorns is friendship. 

Re: [announce] fourth release of the LyXWinInstaller

[Stephen Harris]

- Original Message - 
From: Uwe Stöhr [EMAIL PROTECTED]

To: LyX-Users lyx-users@lists.lyx.org
Cc: LyX-Devel lyx-devel@lists.lyx.org
Sent: Monday, November 21, 2005 9:25 AM
Subject: [announce] fourth release of the LyXWinInstaller



Hello LyXers,

with the help from many people I'm now able to present the new version 0.4 
of the LyX installer for Windows.


I switched to LyX's new LaTeX - LyX converter tex2lyx. In contrary to 
the old reLyX tex2lyx is maintained by the LyX-developers. tex2lyx is 
currently not marked as stable but it is in most cases better than 
reLyX. tex2lyx is invoked when you use LyX's menu

File - Import - LaTeX



I tested version 4, small and network, with the Texlive2005, win32 latex 
distro.

Everything seemed to work and it found C:\Texlive2005\bin\win32; and added
it to the Lyx Path prefix.

I tested tex2lyx on sample.tex which has the author's picture which it 
displayed.
It did not display the pdf test files. error converting to loadable format 
and

something about No information for converting pdf to eps I saw ImageMagick
in both Paths (prefix). I tried adding C:\Texlive2005\bin\win32; to the 
Windows
Path and it didn't seem to help any, I imagine this is a problem with 
tex2lyx, not

the installer. The GUI looks a bit spiffier, new icons with functions?

Best regards,
Stephen

good news from the win95 front

[Luis Rivera]

Hello,

I am happy to report that LyX137cvs2 actually runs on Win95 (an old 
486, 16Mb
memory!)... however, with a few caveats,

0/ installer breaks on running configure, as it did before on Win98...

1/ the already reported problems with the fonts in menus, etc...

2/ it only works when the environment variable lyx_dir_13x or the 
-sysdir option
are set to the SHORT path of the LyX executable.

So apparently the wrapper to convert long to short paths on Win95 
is still broken...

3/ I didn't know LyX actually needed to know about latex's existence 
to filter
and convert from LyX to LaTeX.  I installed LyX with only msys and 
python, and
it can't convert because the article class is missing.  Is this 
behavior OK?

Perhaps the problem lies in my old MiKTeX installation, which I have 
to
upgrade... but anyway, why is LaTeX's presence required to run LyX as 
a console
converter?

Cheers,

Luis.

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Uwe Stöhr wrote:

That I added/changed some icons in LyX's menu bar is just a special 
gimmick. I've installed LyX for many people and most of them wanted 
for example an icon for search in LyX's menu bar and a shortcut to 
Export - PDF (pdflatex). So I thaught if these small bits make users 
happy, I'll add them.


I wonder whether we should add them for LyX 1.4 officially if people 
become happy ???


I don't understand the question. Do you mean the third-party programs 
I use for the installer?


Yes.

In version 0.4 I kicked out all perl files so that I include only 
python files needed for lyx2lyx and other scripts. My installer also 
comes with needed Unix-shell files and some that are requested by 
users to makes it possible for them to build some scripts.


Are the UNIX command line tools (in particular 'sh') needed for any 
other purpose than the configure script? If we were able to ignore the 
shell tools (MSYS), the size of the installer would shrink dramatically, 
I guess.


Michael

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Angus Leeming wrote:


I compiled 1.3.7cvs with MinGW/MSYS yesterday. I'll package it up using
my packager (the packaged version uses 7-zip compression and is *much*
smaller than even a bzip2 compressed archive and shove it on the wiki.
Tomorrow probably. Thereafter, you can unpackage and repackage as usual.
 

Great! Did you use Cutie  2005-10-30 ? (There have been no commit since 
then) This should fix our font problems on Windows.


Michael

Re: [announce] fourth release of the LyXWinInstaller

[Angus Leeming]

On Tuesday 22 November 2005 22:06, Michael Gerz wrote:
 Angus Leeming wrote:
 I compiled 1.3.7cvs with MinGW/MSYS yesterday. I'll package it up using
 my packager (the packaged version uses 7-zip compression and is *much*
 smaller than even a bzip2 compressed archive and shove it on the wiki.
 Tomorrow probably. Thereafter, you can unpackage and repackage as usual.

 Great! Did you use Cutie  2005-10-30 ? (There have been no commit since
 then)

Sure there has. They changed their repository from kde-cygwin to qtwin...

Your CVS/Root files should read:
:pserver:[EMAIL PROTECTED]:/cvsroot/qtwin

Everything else is unchanged, IIRC.

 This should fix our font problems on Windows. 

Apparently so ;-)

Angus

Re: [announce] fourth release of the LyXWinInstaller

[Bo Peng]

 Are the UNIX command line tools (in particular 'sh') needed for any
 other purpose than the configure script? If we were able to ignore the
 shell tools (MSYS), the size of the installer would shrink dramatically,
 I guess.

For configure, you can use the 'experimental configure.py' available
at cvs, which is for 1.4.0 though. (I do have a version for 1.3.6 but
it is less tested, search the list archive for it.) Mingw is also used
for four or five small scripts under the scripts directory. They are
easy to convert and I plan to do so after the release of 1.4.0.

Bo

shortcut to run arbitrary script.

[Bo Peng]

Dear list,

Since lyx will freeze when view-dvi/pdf etc is running,,

1. Can view-dvi/pdf etc be put into background so lyx will not freeze
during latex-ing?

2. Can I define a keyboard shortcut to run whatever shell script I
specify? If this can be done, question 1 is no longer a problem since
I can buffer-export latex and run whatever script I need on it.

Thanks.
Bo

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Bo Peng wrote:


For configure, you can use the 'experimental configure.py' available
at cvs, which is for 1.4.0 though. (I do have a version for 1.3.6 but
it is less tested, search the list archive for it.) Mingw is also used
for four or five small scripts under the scripts directory. They are
easy to convert and I plan to do so after the release of 1.4.0.
 


Excellent! Maybe something for 1.4.1...

Michael

Re: [announce] fourth release of the LyXWinInstaller

[Angus Leeming]

Michael Gerz wrote:
 Are the UNIX command line tools (in particular 'sh') needed for any
 other purpose than the configure script?

Yes. We currently generate small shell scripts on the fly to control the
conversion of graphics files for display.

-- 
Angus

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Angus Leeming wrote:


Great! Did you use Cutie  2005-10-30 ? (There have been no commit since
then)
   


Sure there has. They changed their repository from kde-cygwin to qtwin...

Your CVS/Root files should read:
:pserver:[EMAIL PROTECTED]:/cvsroot/qtwin

Everything else is unchanged, IIRC.
 


Oh, indeed! And Christian Ehrlicher made a lot of changes recently.

I think

 cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/qtwin checkout 
-r QT_WIN32_3_3_BRANCH qt-3


is the right way to get the sources.

Michael

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Michael Gerz]

Uwe Stöhr wrote:


p.s.
 Angus, Michael, what about the efforts of compiling LyX 1.4 under 
Win? (Yes I know that I need to lift up my ass and try to compile it 
for myself.)


I build a new LyX 1.4.0 on Windows about once a week. However, I don't 
know whether Angus has added some magic to the generic build process. I 
just run (more or less) ./autogen.sh, configure, make, and make 
install. Angus, do you have special build instructions for windows? Do 
we have to consider some additional files/scripts that are specific to 
the Windows world?


Regards, Michael

  Jörg Zastrau has written a plugin to use RCS together with LyX on 
Windows. Is it OK when I include this to the network variant (the 
variant for experienced users) of my installer?


Well, RCS isn't that sexy nowadays, is it? Why don't you ask Jörg to 
support subversion? THIS is a great tool!


Michael

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Michael Gerz]

Uwe Stöhr wrote:


Don't beat me for the following proposal:

I can see no reason why tex2lyx need to be backported to LyX 1.3.x. 
tex2lyx runs fine with 1.3.x as it is.
I also think that my LyX diverges a bit from mainline, so I'd like to 
see 1.3.7 out WITH tex2lyx and perhaps with some of my minor changes 
to the menu bar.
JMarc what do you think needs to be done before LyX 1.3.7 can be 
published?


The list of changes for 1.3.7 isn't very long but we have made a couple 
of GUI improvements since 1.3.6 that users will appreciate. If we 
replaced reLyX by tex2lyx (provided that tex2lyx is indeed better in 
most cases and there are no major bugzilla entries for it) we could ship 
1.3.7 and declare the 1.3 branch as closed.


Michael

Re: good news from the win95 front

[Angus Leeming]

Luis Rivera wrote:

Hello,

I am happy to report that LyX137cvs2 actually runs on Win95 (an old 
486, 16Mb memory!)... however, with a few caveats,


0/ installer breaks on running configure, as it did before on Win98...

1/ the already reported problems with the fonts in menus, etc...

2/ it only works when the environment variable lyx_dir_13x or the 
-sysdir option

are set to the SHORT path of the LyX executable.

So apparently the wrapper to convert long to short paths on Win95 
is still broken...


As promised, Luis, here is a standalone version of the paths thing for you 
to play with. It was just missing a few #includes...


Angus
// From os_win32.h (BRANCH_1_3_X)
/* The GetLongPathNameA function declaration in
 * winbase.h is protected by the WINVER macro which is
 * defined to a default value in windef.h under MinGW and Cygwin.
 *
 * SHGFP_TYPE_CURRENT is defined in shlobj.h for __W32API_VERSION = 3.2
 * where it is protected by _WIN32_IE, also defined to a default value
 * in windef.h under MinGW and Cygwin.
 * It is missing in earlier versions of the MinGW w32api headers.
 *
 * We need to #include windows.h now to make available the
 * DWORD, HMODULE et al. typedefs, so first define WINVER, _WIN32_IE.
 *
 * Note: __CYGWIN__ can be defined here if building in _WIN32 mode.
 */

#include cassert
#include iostream
#include string
#include vector

using std::cerr;
using std::cout;
using std::endl;
using std::string;
using std::vector;


#if defined(__MINGW32__)  || defined(__CYGWIN__) || defined(__CYGWIN32__)
# if defined(WINVER)  WINVER  0x0500
#  error WINVER must be = 0x0500
# endif
# define WINVER 0x0500
# define _WIN32_IE 0x0500
#endif

#include windows.h

// From os_win32.C (BRANCH_1_3_X)
/* The GetLongPathName macro may be defined on the compiling machine,
 * but we must use a bit of trickery if the resulting executable is
 * to run on a Win95 machine.
 * Fortunately, Microsoft provide the trickery. All we need is the
 * NewAPIs.h header file, available for download from Microsoft as
 * part of the Platform SDK.
 */
#if defined (HAVE_NEWAPIS_H)
# define WANT_GETLONGPATHNAME_WRAPPER 1
# define COMPILE_NEWAPIS_STUBS
# include NewAPIs.h
# undef COMPILE_NEWAPIS_STUBS
# undef WANT_GETLONGPATHNAME_WRAPPER
#endif

namespace {

string const get_long_path(string const  short_path)
{
std::vectorchar long_path(MAX_PATH);
DWORD result = GetLongPathName(short_path.c_str(),
   long_path[0], long_path.size());

if (result  long_path.size()) {
long_path.resize(result);
result = GetLongPathName(short_path.c_str(),
 long_path[0], long_path.size());
assert(result = long_path.size());
}

return (result == 0) ? short_path : long_path[0];
}

} // namespace anon

// From the code you attached.
int main(int argc, char * argv[])
{
if (argc != 2) {
std::cerr  Usage:   argv[0]   some_path\n;
return -1;
}

// Windows 95 has GetShortPathName even if it doesn't have
// GetLongPathName!
char short_path[MAX_PATH];
DWORD const result = GetShortPathName(argv[1], short_path, MAX_PATH);
if (result == 0 || result  MAX_PATH) {
std::cerr  Unable to ascertain ShortPath version of   
argv[1]  '\n';
return -1;
}

string const long_path = get_long_path(short_path);
std::cout  Short path name is   short_path  '\n'
   Long  path name is   long_path  std::endl;

return 0;
}

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Michael Gerz]

Michael Gerz wrote:


Uwe Stöhr wrote:


Don't beat me for the following proposal:

I can see no reason why tex2lyx need to be backported to LyX 1.3.x. 
tex2lyx runs fine with 1.3.x as it is.
I also think that my LyX diverges a bit from mainline, so I'd like to 
see 1.3.7 out WITH tex2lyx and perhaps with some of my minor changes 
to the menu bar.
JMarc what do you think needs to be done before LyX 1.3.7 can be 
published?



The list of changes for 1.3.7 isn't very long but we have made a 
couple of GUI improvements since 1.3.6 that users will appreciate. If 
we replaced reLyX by tex2lyx (provided that tex2lyx is indeed better 
in most cases and there are no major bugzilla entries for it) we could 
ship 1.3.7 and declare the 1.3 branch as closed.


I remember Jean-Marc mentioning that he will release 1.3.7 as soon as 
the 1.4.0 file format is fixed. (which has implications on lyx2lyx). So 
the question is: Is the 1.4.0 file format fixed?


Michael

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Angus Leeming]

Michael Gerz wrote:

Uwe Stöhr wrote:


p.s.
 Angus, Michael, what about the efforts of compiling LyX 1.4 under 
Win? (Yes I know that I need to lift up my ass and try to compile it 
for myself.)



I build a new LyX 1.4.0 on Windows about once a week. However, I don't 
know whether Angus has added some magic to the generic build process. I 
just run (more or less) ./autogen.sh, configure, make, and make 
install. Angus, do you have special build instructions for windows? Do 
we have to consider some additional files/scripts that are specific to 
the Windows world?


I don't build LyX 1.4 very often. When I do, I use Asgers MSVS.Net project.

To build LyX 1.3.x, see development/Win32/packaging/README. My build 
process is no more than:


$ sh build_lyxwin.sh
$ sh package_lyxwin.sh

Use ResourceHacker to add a couple of icons to the .exe, as described in 
the README


$ rm -f ../../../build/installprefix/bin/lyx_original.exe
$ cd installer
$ /c/Program\ Files/NSIS/makensis lyx_installer.nsi
$ scp lyx_setup_137.exe [EMAIL PROTECTED]:.
$ ssh [EMAIL PROTECTED]
$ cd ../lyx/www/pmwiki/uploads/Windows/LyX137pre/
$ mv ~/lyx_setup_137.exe lyx_setup_137_version3.exe

Edit the wiki page to point to the new version.

$ rm -f  lyx_setup_137_version2.exe

In fact, I've just done this ;-) Uwe, feel free to grab the updated 
binaries and libraries for your installer.


Angus

Grammar Checker for LyX.

[John C. McCabe-Dansted]

I am working on a grammar checker for LyX. It outputs the errors to LaTeX .log 
format so it can integrate itself into LyX without need for any modification 
to existing LyX binary.

Three questions. 

First, I understand that to tell LyX 1.3.6 that a converter generates errors 
in a LaTeX .log format you have to set the Extra Flag to be latex. 
However then it seems to ignore the converter option, and run latex instead. 
Why is this?

Secondly, I am currently getting around this problem by naming my grammar 
checker latex and then getting it to call the real LaTeX when it is done. 
Is there a better way?

Thirdly, is there any interest in including this in an official release (it is 
under 50KB), and if so is there some procedure I should follow? 

I have placed an experimental-yet-functional version up at:
 http://dansted.org/latexgc.tar.gz

--
John C. McCabe-Dansted
Masters Student

Re: [announce] fourth release of the LyXWinInstaller

[Uwe Stöhr]

Michael Gerz schrieb:

Are the UNIX command line tools (in particular 'sh') needed for any 
other purpose than the configure script?


Jep. We need them to list e.g. the TeX-Informations and to invoke 
ImageMagick.


If we were able to ignore the 
shell tools (MSYS), the size of the installer would shrink dramatically, 
I guess.


No, all files from MSYS have together a size of 1.21 MB.

regards Uwe

Re: [announce] fourth release of the LyXWinInstaller

[Uwe Stöhr]

Michael Gerz schrieb:

Great! Did you use Cutie  2005-10-30 ? (There have been no commit since 
then) This should fix our font problems on Windows.


Btw. I set the default screen fonts and their zoom now manually in my 
installer to avoid further problems. I use

Times New Roman
Arial
Courier
Zoom = 120%

regards Uwe

Re: [announce] fourth release of the LyXWinInstaller

[Uwe Stöhr]

Bo Peng wrote:


For configure, you can use the 'experimental configure.py' available
at cvs, which is for 1.4.0 though. (I do have a version for 1.3.6 but
it is less tested, search the list archive for it.) Mingw is also used
for four or five small scripts under the scripts directory. They are
easy to convert and I plan to do so after the release of 1.4.0.


What would be the advantage?
(Getting rid of the MSYS files saves only 1.2 MB and the scripts that 
use them are well tested.)


regards Uwe

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Uwe Stöhr]

Michael Gerz schrieb:

The list of changes for 1.3.7 isn't very long but we have made a couple 
of GUI improvements since 1.3.6 that users will appreciate. If we 
replaced reLyX by tex2lyx (provided that tex2lyx is indeed better in 
most cases and there are no major bugzilla entries for it) we could ship 
1.3.7 and declare the 1.3 branch as closed.


I've just reported three tex2lyx bugs: 2130, 2132, and 2135
But the import of the tex-files mentioned there failed also when I use 
reLyX. I don't think that tex2lyx must be perfect - LaTeX allows so many 
different constructs that it would take many releases until it works 
well with 99% of the tex-documents. When we really decide to ship it 
with LyX 1.3.7 we don't need to mention it as THE big new thing. But 
perhaps when we can do this when LyX 1.4 is out and we got feeedback 
from people who tested it out with LyX 1.3.7 ;-)


 I remember Jean-Marc mentioning that he will release 1.3.7 as soon as
 the 1.4.0 file format is fixed. (which has implications on lyx2lyx).

I wasn't aware of that issue. Of course the file format need to be at 
first set fix.


regards Uwe

Re: [announce] fourth release of the LyXWinInstaller

[Bo Peng]

 What would be the advantage?
 (Getting rid of the MSYS files saves only 1.2 MB and the scripts that
 use them are well tested.)

Using the old windows installer, getting rid of mingw means one less
website to visit and one less program to install. With the new
installer, yes, you are right, mingw is no longer a problem.

However, configure.py will (?) replace configure.m4 because more
complicated configuration such as registry manipulation can be done
more easily in Python than in shell.

Cheers,
Bo

Re: [announce] fourth release of the LyXWinInstaller

[Asger Ottar Alstrup]

Uwe Stöhr wrote:
Btw. I set the default screen fonts and their zoom now manually in my 
installer to avoid further problems. I use

Times New Roman
Arial
Courier
Zoom = 120%


Please use Courier New instead. Courier is a bitmap font that scales 
badly, while Courier New is a true-type font, which scales much better.


Regards,
Asger

Re: Grammar Checker for LyX.

[Asger Ottar Alstrup]

John C. McCabe-Dansted wrote:
I am working on a grammar checker for LyX. It outputs the errors to LaTeX .log 
format so it can integrate itself into LyX without need for any modification 
to existing LyX binary.


Very interesting. I've talken a look at the code - although it's Perl, 
it is kind of readable. I stumbled upon a misspelled hypen somewhere, 
which probably should be hyphen.


Regarding your questions: It might be easier to mimic chktex rather 
than LaTeX. LyX has support for doing semantic/typographical 
checking using chktex. This is much more like what you are doing, so 
that will be the easier road, I think.


Your checks about spaces before and after math are already covered by 
chktex, so before you go implement all kinds of checks, it will be a 
good idea to check out chktex to avoid duplicating work.


Thirdly, is there any interest in including this in an official release (it is 
under 50KB), and if so is there some procedure I should follow? 


Get it to work as you want it to, and submit a patch. You probably have 
to tie it into the configure-machinery, since it requires Perl, which I 
believe we do not require anymore (at least not in 1.4-devel, where 
reLyX is dead.) I'm sure someone can give you a few pointers for this.


Notice, however, that there is a feature freeze for 1.4, so you might 
have to hang on to your patch until general development opens again, 
probably some time next year. On the other hand, this might give you 
time to reimplement this stuff as C++, which I'm sure would increase the 
chances for the code to be included.


Regards,
Asger

The baby algorithm

[Asger Ottar Alstrup]

Dear Angus,

Congratulations to you and your family! I can only say that he really 
does look a lot like you. Normally, babies all look the same, but in 
this case, there is no doubt that you are the father!


I'm sure you are already know the algorithm by now:

while (age  3 months) {
If baby cries,
- want milk?
- change diper?
- need sleep?
if age  1 month, want to play?
}

At one point, we didn't really know how to handle the need sleep? 
step, so Elias would be crying and crying, and we would try more and 
more aggressive things to calm him down - like throwing him in the air 
and playing loud music. This did not exactly help, and since we had 
tried the first two steps, we were at a complete loss, being complete 
baby ignorants and totally exhausted from lack of sleep. We did try to 
put him in his bed and sing him a song, but he wouldn't sleep. This 
would go on for an hour or two, and we would put him in his baby 
carriage and go for a long walk. At the end of it, he sometimes fell asleep.


The same thing would happen the next day. We became so frustrated - we 
were sure something terrible was wrong, probably something with the 
stomach - so we took him to this person which gave him feet massage, 
because we were told this helps. The only effect was that he filled his 
diper with shit.


The next day, the nurse came, and she looked at him for one second and 
say that he was exhausted. All he needed was to be told to go to sleep. 
The trick was to tuck him up nicely in the bed with a lot of teddy bears 
so he basically couldn't move much, give him a pacifier, and hold it in 
his mouth to teach him to suck it and hang on to it, and in general 
clearly tell him that what he should do to sleep, and that this was 
really what he needed to do. He fell asleep that instant.


Ahem. Sorry about that.

After that, we did not have any problems, until the teething step...

But I guess the essense of what I'm trying to say is this: It is so 
important that both of you get some sleep - especially the mother since 
she has to produce all this milk! In the night, Maren would feed Elias, 
and then hand him over to me, so that I would change his diper, all of 
this in complete darkness. That meant that Maren did not really have to 
wake up, and that Elias would instantly fall asleep again. I had 
paternity leave the first month, so I could just sleep at some other 
points in the day.


After that, you just get used to the lack of sleep ;-)

Regards,
Asger

Re:Invokation of tex2lyx and lyx2lyx

[Georg Baum]

Uwe Stöhr wrote:

>  > 1) convert test.tex -> tmp_dir/_test.lyx (format xxx) (tex2lyx)
>  > 2) convert tmp_dir/_test.lyx (format xxx) ->
>  > tmp_dir/_test_new.lyx (format yyy) (lyx2lyx)
>  > 3) load tmp_dir/_test_new.lyx (format yyy) in LyX,
>  > when the user sves this file it is copied to the directory of
>  > test.tex
> 
>  > I like 1) and 2), because it avoids overwriting the original .tex
> file > with Export->Latex, but instead of 3) I would simply keep an
> unnamed
>  > document.
> 
> Why that and where would you keep it?

It would be kept in memory (the same what happens if you create a new file
with File->New).
Why? Because users are forced to think about a name for the converted
document. I have found myself several times in the situation where I
accidentally destroyed the original .tex file by Export->Latex.

> But anyway if you also like 1) and 2) perhaps we should implement it in
> future LyX versions.
> 
>  > Besides that: What happens with master/child documents?
> 
> I've never used master/child documents.

Ok, if you do that you will notice that tex2lyx will also convert the child
documents. This will complicate things if we implement the behaviour above.


Georg

Re: William Leeming

[Stephan Witt]

Angus Leeming wrote:

I'd like to announce the arrival of William who arrived on Tuesday 15
November, weighing in at 3.55kg (7lb 12oz in old money.)


Congratulations, especially to your wife.


It wasn't
easy getting him out (40 hours labour followed by a Cæsarian) but now
he is out both he and Emma are doing really well.


That was really hard, I hope the medicine men did it all well.


I've put together a few pictures to satisfy your curiosity:
http://www.lyx.org/~leeming/William/
It's not a very professional-looking page but, hey ho, it should give
you a flavour.


Very nice...

Stephan

Re: [announce] fourth release of the LyXWinInstaller

[Georg Baum]

Uwe Stöhr wrote:

> I understand you.
> The icons I mentioned shouldn't be a problem. They are only used for the
> installer executables itself and for the lyx-files in Windows
> file-explorer. That I added/changed some icons in LyX's menu bar is just a
> special gimmick. I've installed LyX for many people and most of them
> wanted for example an icon for "search" in LyX's menu bar and a shortcut
> to Export -> PDF (pdflatex). So I thaught if these small bits make users
> happy, I'll add them.

[...]

> At last while talking with José about some lyx2lyx issues I asked him if
> I should use tex2lyx in my installer and he said yes to "enforce" the
> tex2lyx/lyx2lyx situation. So I dared to pack it in.

All valid reasons. My concern is that your LyX will diverge from mainline,
and I think that this would be very bad.
Why not feed your improvements back to mainline instead of offering them
only to the windows people?
Having said that I also need to say that I don't think that bigger changes
should be done in 1.3.x anymore. The time to integrate tex2lyx for example
is better spent in testing 1.4cvs. We should get that out as soon as
possible.


Georg

Re: [announce] fourth release of the LyXWinInstaller

[Jose' Matos]

On Tuesday 22 November 2005 08:44, Georg Baum wrote:
> Having said that I also need to say that I don't think that bigger changes
> should be done in 1.3.x anymore. The time to integrate tex2lyx for example
> is better spent in testing 1.4cvs. We should get that out as soon as
> possible.

  I agree with Georg here. Things are really improving and I think all the 
efforts are best applied in getting 1.4 out where some of the remaining 
issues are already solved.

  Any time plan for a release candidate?

  How about getting 1.4.0 before Christmas, after all we already promissed 
this 2 years ago. ;-)

> Georg

-- 
José Abílio

Re: Invokation of tex2lyx and lyx2lyx

[Jose' Matos]

On Tuesday 22 November 2005 08:23, Georg Baum wrote:
> > I've never used master/child documents.
>
> Ok, if you do that you will notice that tex2lyx will also convert the child
> documents. This will complicate things if we implement the behaviour above.

  That is why I suggested to load the documents with same name and location of 
its counterpart tex. The file would not be saved, thus when the file is saved 
the users takes care of any possible collisions.

  LyX using by default the -f options always scared me.

> Georg

-- 
José Abílio

Bug 2136 Invalid latex generated with paragraph settings inside "no inner box"

[Helge Hafting]

Reproduce:
* Insert a box. Write text inside it.
* Bring up box settings, set it to:
 - rectangular frame
 - "no inner box"  (necessary)
 - width = "1 width"
* Place cursor inside box
* edit->paragraph settings
* Set something nondefault, such as centering or doublespacing

Lyx will now generate invalid latex.
I believe the frameless box doesn't contain a paragraph (Using ENTER 
don't work in there) so it makes sense that you cannot apply paragraph 
settings there. But lyx lets me do that anyway, and then latex pukes.


Suggested fixes:
1. Disable the paragraph settings menu item when editing in a box with 
"no inner box".
2. Users can put a box around anything, so when the user turns the box 
into the "no inner box" kind, please kill any paragraph settings 
contained within so as to avoid latex errors later.  "No inner box" is 
useful, but it is an environment with limited capabilities. Or possibly 
move the offending paragraph settings out into the paragraph containing 
the box. (Better, but quite possibly more work.)


I discovered this when trying to have a "no inner box" frame around a 
doublespaced table. This actually works fine if the doublespacing is 
applied outside the box, i.e. in the paragraph containing the box.  But 
that is not what happens if you apply a box around such a table and then 
set it to "no inner box".


I guess some of the problem comes from the way lyx has a box inset for 
all kinds of boxes.  But a minipage/parbox contains paragraph(s), while 
a "no inner box" is just text markup similiar to "bold".

Bug 2137: Box with width="1 width" is way too thin on screen

[Helge Hafting]

A frame box with "no inner box" can be set to width="1 width" meaning 
that the box will have the width of whatever it contains.  This is very 
nice for making double-border tables, or higlighting a word with a box.


Unfortunately, lyx seems to assume that such a box is a narrow column. 
Output is ok, but the content on screen is squashed into a horrible 
narrow column, whenever such a box is applied to wide content.  A boxed 
wide table looks _really_ bad this way. Try and cry.


Suggested fix: Don't let such a box limit the display. Draw the contents 
as if
the box wasn't there, and paint the box around the result.  Or a box the 
width of the lyx window if that is easier.  Anything but this . . .

Re: William Leeming

[Andreas Vox]

Angus Leeming <[EMAIL PROTECTED]> writes:

> 
> Dear all,
> 
> I'd like to announce the arrival of William ...

A little late, but also from me congratulations to you and your family.

So can we hope -- since you're awake at night anyway -- there will be 
continuing and steady input to our LyX project in the weeks to come? ;-)

/Andreas

Re: [announce] fourth release of the LyXWinInstaller

[Jean-Marc Lasgouttes]

> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:

Michael> I agree. What we could do is backporting tex2lyx to 1.3.7cvs.

I think this is too difficult and would require to fork tex2lyx.

JMarc

Re: [patch] fix bug 2126

[Jean-Marc Lasgouttes]

> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:

Georg> Georg Baum wrote:
>> I tested the patch and it works well for me. OK to apply?

Georg> Take this one instaed, I forgot to implement
Georg> LFUN_INSET_DIALOG_UPDATE.

Go ahead.

JMarc

Re: [PATCH] Re: bug 1952/1953

[Jean-Marc Lasgouttes]

> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:

Juergen> Jean-Marc Lasgouttes wrote:
>> At least, you could move your code that determines what the real
>> text inset is into dociterator.C.

Juergen> is attached.

Almost perfect :

1/ make textInset return an InsetText object; Assert on inTexted() 

2/ the loop in undo.C should use normal iterators instead of
const_iterators, so that the const_cast is not needed.

JMarc

Re: [patch] fix bug 2126

[Georg Baum]

Jean-Marc Lasgouttes wrote:

>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
> 
> Georg> Georg Baum wrote:
>>> I tested the patch and it works well for me. OK to apply?
> 
> Georg> Take this one instaed, I forgot to implement
> Georg> LFUN_INSET_DIALOG_UPDATE.
> 
> Go ahead.

Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll discover
more...):
http://bugzilla.lyx.org/buglist.cgi?short_desc_type=allwordssubstr_desc=_milestone=1.4.0_desc_type=allwordssubstr_desc=_file_loc_type=allwordssubstr_file_loc=_type=allwords=_status=UNCONFIRMED_status=NEW_status=ASSIGNED_status=REOPENED=substring==substring==include_id=Now==doit==Reuse+same+sort+as+last+time=noop=noop=


Georg

plans for LyX, was: fourth release of the LyXWinInstaller

[Uwe Stöhr]

Georg Baum schrieb:


All valid reasons. My concern is that your LyX will diverge from mainline,
and I think that this would be very bad.
Why not feed your improvements back to mainline instead of offering them
only to the windows people?


I'll do. What special things do you mean should be ported to mainline?


Having said that I also need to say that I don't think that bigger changes
should be done in 1.3.x anymore. The time to integrate tex2lyx for example
is better spent in testing 1.4cvs. We should get that out as soon as
possible.


Don't beat me for the following proposal:

I can see no reason why tex2lyx need to be backported to LyX 1.3.x. 
tex2lyx runs fine with 1.3.x as it is.
I also think that my LyX diverges a bit from mainline, so I'd like to 
see 1.3.7 out WITH tex2lyx and perhaps with some of my minor changes to 
the menu bar.

JMarc what do you think needs to be done before LyX 1.3.7 can be published?

Why that? Because I have little luxus-problem: The heise.de people, who 
publish the computer magazine "C't" and host Germanys most readed 
computer-news page, wanted to mention my installer in their news because 
they are sold on the installer concept. I could avoid the news entry 
because I want the installer to be closer with mainline. The 
corresponding heise editor offered me to contact him when this is done 
and he would announce it in the news together with a small description.
I mean we should use this offered publicity better for LyX 1.4 or LyX 
1.3.7 than only for an installer.
Btw. he warned me that an entry at heise.de could be similar to a 
DoS-attack. Version 0.31 of my installer was downloaded 370 times within 
three days and I only announced it on the users-list and to some friends.


I'm not sure what we should do.
Is it OK when my installer could be downloaded directly from ftp.lyx.org?
Should we announce it together with a probable LyX 1.3.7 release.
What about the official Win-installer?
 Angus' version is ideal as it only ships LyX.
 My version includes third-party programs which increases the 
maintaining expenditure (for example while working on the installer I 
encountered 3 MiKTeX-bugs, 2 ImageMagick-bugs, and 1 Ghostscript-bug) 
but is ideal for beginners and unexperienced "normal" Win-users.


Any thoughts?

best regards Uwe

p.s.
 Angus, Michael, what about the efforts of compiling LyX 1.4 under Win? 
(Yes I know that I need to lift up my ass and try to compile it for myself.)


pp.s
 Jörg Zastrau has written a plugin to use RCS together with LyX on 
Windows. Is it OK when I include this to the "network" variant (the 
variant for experienced users) of my installer?

lyx140cvs: export to html

[Hartmut Haase]

This doesn't seem to work at the moment at all. Within LyX the html-file 
cannot be copied from the /tmp...-directory, and from the command line 
something like

latex2html -no_subdir -split 0 -show_section_numbers file.lyx

result in error messages like

*** no brace for \end , before:
_inset
*** using "_" as the argument instead; is this correct?  ***

and others, and the resulting html-file looks weird. I was trying to convert a 
table.
-- 
Viele Grüße,
Hartmut 

Hungerhilfe: http://www.thehungersite.com

Das heutige Motto:
The trouble with some people who don't have very much to say 
is that you have to listen so long to find out. 

Re: [patch] fix bug 2126

[Jose' Matos]

On Tuesday 22 November 2005 13:58, Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
> >> "Georg" == Georg Baum
> >> <[EMAIL PROTECTED]>
> >> writes:
> >
> > Georg> Georg Baum wrote:
> >>> I tested the patch and it works well for me. OK to apply?
> >
> > Georg> Take this one instaed, I forgot to implement
> > Georg> LFUN_INSET_DIALOG_UPDATE.
> >
> > Go ahead.
>
> Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll discover
> more...):

  One of those is http://bugzilla.lyx.org/show_bug.cgi?id=2088

  Have you applied your patch?

  One thing easy that we can do is a filter to catch those cases and fix them. 
It will not hurt and we will get rid of this type of errors once and for all.
The function bellow fixes this issues. What do you think?

def fix_empty_layout(file):
i = find_token(file.body, "\\layout", 0)

if i == -1: return

# layout line is empty
if len(string.split(string.strip(file.body[i]))) == 1:
file.body[i] = "\\layout Standard"

> Georg

-- 
José Abílio

Re: [patch] fix bug 2126

[Georg Baum]

Jose' Matos wrote:

> On Tuesday 22 November 2005 13:58, Georg Baum wrote:
>> Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll
>> discover more...):
> 
>   One of those is http://bugzilla.lyx.org/show_bug.cgi?id=2088
> 
>   Have you applied your patch?

No, since Lars did not want it. It would be nice if you could convince him
that 1.2.x really created such files.

>   One thing easy that we can do is a filter to catch those cases and fix
>   them.
> It will not hurt and we will get rid of this type of errors once and for
> all. The function bellow fixes this issues. What do you think?
> 
> def fix_empty_layout(file):
> i = find_token(file.body, "\\layout", 0)
> 
> if i == -1: return
> 
> # layout line is empty
> if len(string.split(string.strip(file.body[i]))) == 1:
> file.body[i] = "\\layout Standard"

I like that, but I am not sure whether we want that now. You know, I have
had no good luck with appareantly simple lyx2lyx changes recently


Georg

Re: [patch] fix bug 2126

[Jose' Matos]

On Tuesday 22 November 2005 14:44, Georg Baum wrote:
> Jose' Matos wrote:
> > On Tuesday 22 November 2005 13:58, Georg Baum wrote:
> >> Done. That leaves 12 bugs to fix for 1.4.0 (but I fear that we'll
> >> discover more...):
> >
> >   One of those is http://bugzilla.lyx.org/show_bug.cgi?id=2088
> >
> >   Have you applied your patch?
>
> No, since Lars did not want it. It would be nice if you could convince him
> that 1.2.x really created such files.

  Lars if you are reading this please concede this one. ;-)
  The test is done only for the first paragraph, so it is safe.

  Either that or we close this bug.

> >   One thing easy that we can do is a filter to catch those cases and fix
> >   them.
> > It will not hurt and we will get rid of this type of errors once and for
> > all. The function bellow fixes this issues. What do you think?
> >
> > def fix_empty_layout(file):
> > i = find_token(file.body, "\\layout", 0)
> >
> > if i == -1: return
> >
> > # layout line is empty
> > if len(string.split(string.strip(file.body[i]))) == 1:
> > file.body[i] = "\\layout Standard"
>
> I like that, but I am not sure whether we want that now. You know, I have
> had no good luck with appareantly simple lyx2lyx changes recently

  What are insinuating? ;-)
  This is my code. :-D

  I will commit this code tonight, it is safe, and as Martin says in bugzilla 
it makes the code more robust, that can only be a good thing. Even if we 
don't believe in the boogie man there are some cursed lyx files out 
there. :-)

> Georg

-- 
José Abílio

lyx140cvs: export to html, 2

[Hartmut Haase]

Sorry for the second part, I forgot to convert to latex first.
-- 
Viele Grüße,
Hartmut 

Hungerhilfe: http://www.thehungersite.com

Das heutige Motto:
The only rose without thorns is friendship. 

Re: [announce] fourth release of the LyXWinInstaller

[Stephen Harris]

- Original Message - 
From: "Uwe Stöhr" <[EMAIL PROTECTED]>

To: "LyX-Users" 
Cc: "LyX-Devel" 
Sent: Monday, November 21, 2005 9:25 AM
Subject: [announce] fourth release of the LyXWinInstaller



Hello LyXers,

with the help from many people I'm now able to present the new version 0.4 
of the LyX installer for Windows.


I switched to LyX's new LaTeX -> LyX converter "tex2lyx". In contrary to 
the old "reLyX" tex2lyx is maintained by the LyX-developers. tex2lyx is 
currently not marked as "stable" but it is in most cases better than 
reLyX. tex2lyx is invoked when you use LyX's menu

File -> Import -> LaTeX



I tested version 4, small and network, with the Texlive2005, win32 latex 
distro.

Everything seemed to work and it found C:\Texlive2005\bin\win32; and added
it to the Lyx Path prefix.

I tested tex2lyx on sample.tex which has the author's picture which it 
displayed.
It did not display the pdf test files. "error converting to loadable format" 
and

something about "No information for converting pdf to eps" I saw ImageMagick
in both Paths (prefix). I tried adding C:\Texlive2005\bin\win32; to the 
Windows
Path and it didn't seem to help any, I imagine this is a problem with 
tex2lyx, not

the installer. The GUI looks a bit spiffier, new icons with functions?

Best regards,
Stephen

good news from the win95 front

[Luis Rivera]

Hello,

I am happy to report that LyX137cvs2 actually runs on Win95 (an old 
486, 16Mb
memory!)... however, with a few caveats,

0/ installer breaks on running configure, as it did before on Win98...

1/ the already reported problems with the fonts in menus, etc...

2/ it only works when the environment variable lyx_dir_13x or the 
-sysdir option
are set to the SHORT path of the LyX executable.

So apparently the wrapper to convert long to short paths on Win95 
is still broken...

3/ I didn't know LyX actually needed to know about latex's existence 
to filter
and convert from LyX to LaTeX.  I installed LyX with only msys and 
python, and
it can't convert because the article class is missing.  Is this 
behavior OK?

Perhaps the problem lies in my old MiKTeX installation, which I have 
to
upgrade... but anyway, why is LaTeX's presence required to run LyX as 
a console
converter?

Cheers,

Luis.

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Uwe Stöhr wrote:

That I added/changed some icons in LyX's menu bar is just a special 
gimmick. I've installed LyX for many people and most of them wanted 
for example an icon for "search" in LyX's menu bar and a shortcut to 
Export -> PDF (pdflatex). So I thaught if these small bits make users 
happy, I'll add them.


I wonder whether we should add them for LyX 1.4 officially if people 
become happy ???


I don't understand the question. Do you mean the third-party programs 
I use for the installer?


Yes.

In version 0.4 I kicked out all perl files so that I include only 
python files needed for lyx2lyx and other scripts. My installer also 
comes with needed Unix-shell files and some that are requested by 
users to makes it possible for them to build some scripts.


Are the UNIX command line tools (in particular 'sh') needed for any 
other purpose than the "configure" script? If we were able to ignore the 
shell tools (MSYS), the size of the installer would shrink dramatically, 
I guess.


Michael

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Angus Leeming wrote:


I compiled 1.3.7cvs with MinGW/MSYS yesterday. I'll package it up using
"my" packager (the packaged version uses 7-zip compression and is *much*
smaller than even a bzip2 compressed archive and shove it on the wiki.
Tomorrow probably. Thereafter, you can unpackage and repackage as usual.
 

Great! Did you use Cutie > 2005-10-30 ? (There have been no commit since 
then) This should fix our font problems on Windows.


Michael

Re: [announce] fourth release of the LyXWinInstaller

[Angus Leeming]

On Tuesday 22 November 2005 22:06, Michael Gerz wrote:
> Angus Leeming wrote:
> >I compiled 1.3.7cvs with MinGW/MSYS yesterday. I'll package it up using
> >"my" packager (the packaged version uses 7-zip compression and is *much*
> >smaller than even a bzip2 compressed archive and shove it on the wiki.
> >Tomorrow probably. Thereafter, you can unpackage and repackage as usual.
>
> Great! Did you use Cutie > 2005-10-30 ? (There have been no commit since
> then)

Sure there has. They changed their repository from kde-cygwin to qtwin...

Your CVS/Root files should read:
:pserver:[EMAIL PROTECTED]:/cvsroot/qtwin

Everything else is unchanged, IIRC.

> This should fix our font problems on Windows. 

Apparently so ;-)

Angus

Re: [announce] fourth release of the LyXWinInstaller

[Bo Peng]

> Are the UNIX command line tools (in particular 'sh') needed for any
> other purpose than the "configure" script? If we were able to ignore the
> shell tools (MSYS), the size of the installer would shrink dramatically,
> I guess.

For configure, you can use the 'experimental configure.py' available
at cvs, which is for 1.4.0 though. (I do have a version for 1.3.6 but
it is less tested, search the list archive for it.) Mingw is also used
for four or five small scripts under the scripts directory. They are
easy to convert and I plan to do so after the release of 1.4.0.

Bo

shortcut to run arbitrary script.

[Bo Peng]

Dear list,

Since lyx will freeze when view->dvi/pdf etc is running,,

1. Can view->dvi/pdf etc be put into background so lyx will not freeze
during latex-ing?

2. Can I define a keyboard shortcut to run whatever shell script I
specify? If this can be done, question 1 is no longer a problem since
I can buffer-export latex and run whatever script I need on it.

Thanks.
Bo

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Bo Peng wrote:


For configure, you can use the 'experimental configure.py' available
at cvs, which is for 1.4.0 though. (I do have a version for 1.3.6 but
it is less tested, search the list archive for it.) Mingw is also used
for four or five small scripts under the scripts directory. They are
easy to convert and I plan to do so after the release of 1.4.0.
 


Excellent! Maybe something for 1.4.1...

Michael

Re: [announce] fourth release of the LyXWinInstaller

[Angus Leeming]

Michael Gerz wrote:
> Are the UNIX command line tools (in particular 'sh') needed for any
> other purpose than the "configure" script?

Yes. We currently generate small shell scripts on the fly to control the
conversion of graphics files for display.

-- 
Angus

Re: [announce] fourth release of the LyXWinInstaller

[Michael Gerz]

Angus Leeming wrote:


Great! Did you use Cutie > 2005-10-30 ? (There have been no commit since
then)
   


Sure there has. They changed their repository from kde-cygwin to qtwin...

Your CVS/Root files should read:
:pserver:[EMAIL PROTECTED]:/cvsroot/qtwin

Everything else is unchanged, IIRC.
 


Oh, indeed! And Christian Ehrlicher made a lot of changes recently.

I think

 cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/qtwin checkout 
-r QT_WIN32_3_3_BRANCH qt-3


is the right way to get the sources.

Michael

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Michael Gerz]

Uwe Stöhr wrote:


p.s.
 Angus, Michael, what about the efforts of compiling LyX 1.4 under 
Win? (Yes I know that I need to lift up my ass and try to compile it 
for myself.)


I build a new LyX 1.4.0 on Windows about once a week. However, I don't 
know whether Angus has added some magic to the generic build process. I 
just run (more or less) "./autogen.sh", "configure", "make", and "make 
install". Angus, do you have special build instructions for windows? Do 
we have to consider some additional files/scripts that are specific to 
the Windows world?


Regards, Michael

  Jörg Zastrau has written a plugin to use RCS together with LyX on 
Windows. Is it OK when I include this to the "network" variant (the 
variant for experienced users) of my installer?


Well, RCS isn't that sexy nowadays, is it? Why don't you ask Jörg to 
support "subversion"? THIS is a great tool!


Michael

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Michael Gerz]

Uwe Stöhr wrote:


Don't beat me for the following proposal:

I can see no reason why tex2lyx need to be backported to LyX 1.3.x. 
tex2lyx runs fine with 1.3.x as it is.
I also think that my LyX diverges a bit from mainline, so I'd like to 
see 1.3.7 out WITH tex2lyx and perhaps with some of my minor changes 
to the menu bar.
JMarc what do you think needs to be done before LyX 1.3.7 can be 
published?


The list of changes for 1.3.7 isn't very long but we have made a couple 
of GUI improvements since 1.3.6 that users will appreciate. If we 
replaced reLyX by tex2lyx (provided that tex2lyx is indeed better in 
most cases and there are no major bugzilla entries for it) we could ship 
1.3.7 and declare the 1.3 branch as closed.


Michael

Re: good news from the win95 front

[Angus Leeming]

Luis Rivera wrote:

Hello,

I am happy to report that LyX137cvs2 actually runs on Win95 (an old 
486, 16Mb memory!)... however, with a few caveats,


0/ installer breaks on running configure, as it did before on Win98...

1/ the already reported problems with the fonts in menus, etc...

2/ it only works when the environment variable lyx_dir_13x or the 
-sysdir option

are set to the SHORT path of the LyX executable.

So apparently the wrapper to convert long to short paths on Win95 
is still broken...


As promised, Luis, here is a standalone version of the paths thing for you 
to play with. It was just missing a few #includes...


Angus
// From os_win32.h (BRANCH_1_3_X)
/* The GetLongPathNameA function declaration in
 *  is protected by the WINVER macro which is
 * defined to a default value in  under MinGW and Cygwin.
 *
 * SHGFP_TYPE_CURRENT is defined in  for __W32API_VERSION >= 3.2
 * where it is protected by _WIN32_IE, also defined to a default value
 * in  under MinGW and Cygwin.
 * It is missing in earlier versions of the MinGW w32api headers.
 *
 * We need to #include  now to make available the
 * DWORD, HMODULE et al. typedefs, so first define WINVER, _WIN32_IE.
 *
 * Note: __CYGWIN__ can be defined here if building in _WIN32 mode.
 */

#include 
#include 
#include 
#include 

using std::cerr;
using std::cout;
using std::endl;
using std::string;
using std::vector;


#if defined(__MINGW32__)  || defined(__CYGWIN__) || defined(__CYGWIN32__)
# if defined(WINVER) && WINVER < 0x0500
#  error WINVER must be >= 0x0500
# endif
# define WINVER 0x0500
# define _WIN32_IE 0x0500
#endif

#include 

// From os_win32.C (BRANCH_1_3_X)
/* The GetLongPathName macro may be defined on the compiling machine,
 * but we must use a bit of trickery if the resulting executable is
 * to run on a Win95 machine.
 * Fortunately, Microsoft provide the trickery. All we need is the
 * NewAPIs.h header file, available for download from Microsoft as
 * part of the Platform SDK.
 */
#if defined (HAVE_NEWAPIS_H)
# define WANT_GETLONGPATHNAME_WRAPPER 1
# define COMPILE_NEWAPIS_STUBS
# include 
# undef COMPILE_NEWAPIS_STUBS
# undef WANT_GETLONGPATHNAME_WRAPPER
#endif

namespace {

string const get_long_path(string const & short_path)
{
std::vector long_path(MAX_PATH);
DWORD result = GetLongPathName(short_path.c_str(),
   _path[0], long_path.size());

if (result > long_path.size()) {
long_path.resize(result);
result = GetLongPathName(short_path.c_str(),
 _path[0], long_path.size());
assert(result <= long_path.size());
}

return (result == 0) ? short_path : _path[0];
}

} // namespace anon

// From the code you attached.
int main(int argc, char * argv[])
{
if (argc != 2) {
std::cerr << "Usage: " << argv[0] << " some_path\n";
return -1;
}

// Windows 95 has GetShortPathName even if it doesn't have
// GetLongPathName!
char short_path[MAX_PATH];
DWORD const result = GetShortPathName(argv[1], short_path, MAX_PATH);
if (result == 0 || result > MAX_PATH) {
std::cerr << "Unable to ascertain ShortPath version of " << 
argv[1] << '\n';
return -1;
}

string const long_path = get_long_path(short_path);
std::cout << "Short path name is " << short_path << '\n'
  << "Long  path name is " << long_path << std::endl;

return 0;
}

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Michael Gerz]

Michael Gerz wrote:


Uwe Stöhr wrote:


Don't beat me for the following proposal:

I can see no reason why tex2lyx need to be backported to LyX 1.3.x. 
tex2lyx runs fine with 1.3.x as it is.
I also think that my LyX diverges a bit from mainline, so I'd like to 
see 1.3.7 out WITH tex2lyx and perhaps with some of my minor changes 
to the menu bar.
JMarc what do you think needs to be done before LyX 1.3.7 can be 
published?



The list of changes for 1.3.7 isn't very long but we have made a 
couple of GUI improvements since 1.3.6 that users will appreciate. If 
we replaced reLyX by tex2lyx (provided that tex2lyx is indeed better 
in most cases and there are no major bugzilla entries for it) we could 
ship 1.3.7 and declare the 1.3 branch as closed.


I remember Jean-Marc mentioning that he will release 1.3.7 as soon as 
the 1.4.0 file format is fixed. (which has implications on lyx2lyx). So 
the question is: Is the 1.4.0 file format fixed?


Michael

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Angus Leeming]

Michael Gerz wrote:

Uwe Stöhr wrote:


p.s.
 Angus, Michael, what about the efforts of compiling LyX 1.4 under 
Win? (Yes I know that I need to lift up my ass and try to compile it 
for myself.)



I build a new LyX 1.4.0 on Windows about once a week. However, I don't 
know whether Angus has added some magic to the generic build process. I 
just run (more or less) "./autogen.sh", "configure", "make", and "make 
install". Angus, do you have special build instructions for windows? Do 
we have to consider some additional files/scripts that are specific to 
the Windows world?


I don't build LyX 1.4 very often. When I do, I use Asgers MSVS.Net project.

To build LyX 1.3.x, see development/Win32/packaging/README. My build 
process is no more than:


$ sh build_lyxwin.sh
$ sh package_lyxwin.sh

Use ResourceHacker to add a couple of icons to the .exe, as described in 
the README


$ rm -f ../../../build/installprefix/bin/lyx_original.exe
$ cd installer
$ /c/Program\ Files/NSIS/makensis lyx_installer.nsi
$ scp lyx_setup_137.exe [EMAIL PROTECTED]:.
$ ssh [EMAIL PROTECTED]
$ cd ../lyx/www/pmwiki/uploads/Windows/LyX137pre/
$ mv ~/lyx_setup_137.exe lyx_setup_137_version3.exe

Edit the wiki page to point to the new version.

$ rm -f  lyx_setup_137_version2.exe

In fact, I've just done this ;-) Uwe, feel free to grab the updated 
binaries and libraries for your installer.


Angus

Grammar Checker for LyX.

[John C. McCabe-Dansted]

I am working on a grammar checker for LyX. It outputs the errors to LaTeX .log 
format so it can integrate itself into LyX without need for any modification 
to existing LyX binary.

Three questions. 

First, I understand that to tell LyX 1.3.6 that a converter generates errors 
in a LaTeX .log format you have to set the "Extra Flag" to be "latex". 
However then it seems to ignore the converter option, and run latex instead. 
Why is this?

Secondly, I am currently getting around this problem by naming my grammar 
checker "latex" and then getting it to call the real LaTeX when it is done. 
Is there a better way?

Thirdly, is there any interest in including this in an official release (it is 
under 50KB), and if so is there some procedure I should follow? 

I have placed an experimental-yet-functional version up at:
 http://dansted.org/latexgc.tar.gz

--
John C. McCabe-Dansted
Masters Student

Re: [announce] fourth release of the LyXWinInstaller

[Uwe Stöhr]

Michael Gerz schrieb:

Are the UNIX command line tools (in particular 'sh') needed for any 
other purpose than the "configure" script?


Jep. We need them to list e.g. the TeX-Informations and to invoke 
ImageMagick.


If we were able to ignore the 
shell tools (MSYS), the size of the installer would shrink dramatically, 
I guess.


No, all files from MSYS have together a size of 1.21 MB.

regards Uwe

Re: [announce] fourth release of the LyXWinInstaller

[Uwe Stöhr]

Michael Gerz schrieb:

Great! Did you use Cutie > 2005-10-30 ? (There have been no commit since 
then) This should fix our font problems on Windows.


Btw. I set the default screen fonts and their zoom now manually in my 
installer to avoid further problems. I use

Times New Roman
Arial
Courier
Zoom = 120%

regards Uwe

Re: [announce] fourth release of the LyXWinInstaller

[Uwe Stöhr]

Bo Peng wrote:


For configure, you can use the 'experimental configure.py' available
at cvs, which is for 1.4.0 though. (I do have a version for 1.3.6 but
it is less tested, search the list archive for it.) Mingw is also used
for four or five small scripts under the scripts directory. They are
easy to convert and I plan to do so after the release of 1.4.0.


What would be the advantage?
(Getting rid of the MSYS files saves only 1.2 MB and the scripts that 
use them are well tested.)


regards Uwe

Re: plans for LyX, was: fourth release of the LyXWinInstaller

[Uwe Stöhr]

Michael Gerz schrieb:

The list of changes for 1.3.7 isn't very long but we have made a couple 
of GUI improvements since 1.3.6 that users will appreciate. If we 
replaced reLyX by tex2lyx (provided that tex2lyx is indeed better in 
most cases and there are no major bugzilla entries for it) we could ship 
1.3.7 and declare the 1.3 branch as closed.


I've just reported three tex2lyx bugs: 2130, 2132, and 2135
But the import of the tex-files mentioned there failed also when I use 
reLyX. I don't think that tex2lyx must be perfect - LaTeX allows so many 
different constructs that it would take many releases until it works 
well with 99% of the tex-documents. When we really decide to ship it 
with LyX 1.3.7 we don't need to mention it as THE big new thing. But 
perhaps when we can do this when LyX 1.4 is out and we got feeedback 
from people who tested it out with LyX 1.3.7 ;-)


> I remember Jean-Marc mentioning that he will release 1.3.7 as soon as
> the 1.4.0 file format is fixed. (which has implications on lyx2lyx).

I wasn't aware of that issue. Of course the file format need to be at 
first set fix.


regards Uwe

Re: [announce] fourth release of the LyXWinInstaller

[Bo Peng]

> What would be the advantage?
> (Getting rid of the MSYS files saves only 1.2 MB and the scripts that
> use them are well tested.)

Using the old windows installer, getting rid of mingw means one less
website to visit and one less program to install. With the new
installer, yes, you are right, mingw is no longer a problem.

However, configure.py will (?) replace configure.m4 because more
complicated configuration such as registry manipulation can be done
more easily in Python than in shell.

Cheers,
Bo

Re: [announce] fourth release of the LyXWinInstaller

[Asger Ottar Alstrup]

Uwe Stöhr wrote:
Btw. I set the default screen fonts and their zoom now manually in my 
installer to avoid further problems. I use

Times New Roman
Arial
Courier
Zoom = 120%


Please use "Courier New" instead. "Courier" is a bitmap font that scales 
badly, while Courier New is a true-type font, which scales much better.


Regards,
Asger

Re: Grammar Checker for LyX.

[Asger Ottar Alstrup]

John C. McCabe-Dansted wrote:
I am working on a grammar checker for LyX. It outputs the errors to LaTeX .log 
format so it can integrate itself into LyX without need for any modification 
to existing LyX binary.


Very interesting. I've talken a look at the code - although it's Perl, 
it is kind of readable. I stumbled upon a misspelled "hypen" somewhere, 
which probably should be "hyphen".


Regarding your questions: It might be easier to mimic "chktex" rather 
than LaTeX. LyX has support for doing "semantic"/"typographical" 
checking using chktex. This is much more like what you are doing, so 
that will be the easier road, I think.


Your checks about spaces before and after math are already covered by 
chktex, so before you go implement all kinds of checks, it will be a 
good idea to check out chktex to avoid duplicating work.


Thirdly, is there any interest in including this in an official release (it is 
under 50KB), and if so is there some procedure I should follow? 


Get it to work as you want it to, and submit a patch. You probably have 
to tie it into the configure-machinery, since it requires Perl, which I 
believe we do not require anymore (at least not in 1.4-devel, where 
reLyX is dead.) I'm sure someone can give you a few pointers for this.


Notice, however, that there is a feature freeze for 1.4, so you might 
have to hang on to your patch until general development opens again, 
probably some time next year. On the other hand, this might give you 
time to reimplement this stuff as C++, which I'm sure would increase the 
chances for the code to be included.


Regards,
Asger

The baby algorithm

[Asger Ottar Alstrup]

Dear Angus,

Congratulations to you and your family! I can only say that he really 
does look a lot like you. Normally, babies all look the same, but in 
this case, there is no doubt that you are the father!


I'm sure you are already know the algorithm by now:

while (age < 3 months) {
If baby cries,
- want milk?
- change diper?
- need sleep?
if age > 1 month, want to play?
}

At one point, we didn't really know how to handle the "need sleep?" 
step, so Elias would be crying and crying, and we would try more and 
more aggressive things to calm him down - like throwing him in the air 
and playing loud music. This did not exactly help, and since we had 
tried the first two steps, we were at a complete loss, being complete 
baby ignorants and totally exhausted from lack of sleep. We did try to 
put him in his bed and sing him a song, but he wouldn't sleep. This 
would go on for an hour or two, and we would put him in his baby 
carriage and go for a long walk. At the end of it, he sometimes fell asleep.


The same thing would happen the next day. We became so frustrated - we 
were sure something terrible was wrong, probably something with the 
stomach - so we took him to this person which gave him feet massage, 
because we were told this helps. The only effect was that he filled his 
diper with shit.


The next day, the nurse came, and she looked at him for one second and 
say that he was exhausted. All he needed was to be told to go to sleep. 
The trick was to tuck him up nicely in the bed with a lot of teddy bears 
so he basically couldn't move much, give him a pacifier, and hold it in 
his mouth to teach him to suck it and hang on to it, and in general 
clearly tell him that what he should do to sleep, and that this was 
really what he needed to do. He fell asleep that instant.


Ahem. Sorry about that.

After that, we did not have any problems, until the teething step...

But I guess the essense of what I'm trying to say is this: It is so 
important that both of you get some sleep - especially the mother since 
she has to produce all this milk! In the night, Maren would feed Elias, 
and then hand him over to me, so that I would change his diper, all of 
this in complete darkness. That meant that Maren did not really have to 
wake up, and that Elias would instantly fall asleep again. I had 
paternity leave the first month, so I could just sleep at some other 
points in the day.


After that, you just get used to the lack of sleep ;-)

Regards,
Asger