Re: New file patch (was: Re: Just a Matter of Style (was: LaTeX file handling))

[Stephan Witt]

Arnd Hanses wrote:
 
 On 31 Aug 1999 17:57:55 +0200, Lars Gullik Bj°nnes wrote:
 
 Stephan Witt [EMAIL PROTECTED] writes:
 
 | LaTeX and Xdvi are children of LyX and directed by LyX to the
 | internally computed hidden tmp-directory. I'm aware of that
 | effect: If I close a file and reopen it again, then I have to
 | close my running Xdvi too, because it is useless now, when using
 | update-dvi. If I start Xdvi again it works ok. But there is no
 | mystery. LyX creates a new tmp-directory (as I can see with /bin/ls)
 | and starts working there. The update-dvi operation creates the
 | new dvi file in the new tmp-dir.
 |
 | latex doesn't delete and recreates the dvi file,
 | the contents of the dvi file will be replaced by latex/tex.
 
 Yes, and this should be now problem. Xdvi should not care (too much)
 that the file it views suddenly disappears. Ok, the xdvi is now
 defunct. Do you mean that it would be better if LyX killed the xdvi
 when it destroys teh buffer?
 
 IMHO killing before any defunct is the cleanest solution and avoids
 problems.
 
 Otherwise you'll leave behind abandoned zombie-like processes haunting
 your box (shudder :-)
 

Sorry for the late response. I was 2 days not online (travelling to customer).

I don't think it's a real problem with "zombie-like" running xdvi's.

1. You can see them.
   You can regularily quit them.
   You can decide yourself when to do so.
2. If I quit LyX, then Xdvi is left running too and I'm sure there're
   users who wants to leave this behaviour untouched.

A possible solution may be
1. to document the current behaviour and/or
2. kill (with asking the user?) the running "defunct" xdvi and start a new one
   when the user selects "View-dvi" or "Update-dvi" from menu

Greets,

Stephan Witt

---
[EMAIL PROTECTED]  | beusen unternehmensgruppe senkel
fon: +49 30 549932-62 | Landsberger Allee 392
fax: +49 30 549932-29 | 12681 Berlin, Germany
---

Some support for russian (fwd)

[Paul Seelig]

Hey,

what's wrong here?  Who is forking my email address?  I never sent this
mail to the list! :-(
   A little bit annoyed, P. *8^(
-- 
Please always reply to "Paul Seelig [EMAIL PROTECTED]"

-- Forwarded message (attachments deleted) --
Received: from trudi.zdv.Uni-Mainz.DE ([EMAIL PROTECTED]
[134.93.8.159])
by localhost.sowi.Uni-Mainz.DE (8.8.8/8.8.8/Debian/GNU) with ESMTP id
IAA18128
for [EMAIL PROTECTED]; Fri, 3 Sep 1999 08:44:50 +0200
Received: (from pseelig@localhost)
by trudi.zdv.Uni-Mainz.DE (8.8.8/8.8.8) id IAA06733
for [EMAIL PROTECTED]; Fri, 3 Sep 1999 08:39:24 +0200 (MET DST)
From: Paul Seelig [EMAIL PROTECTED]
Received: from wierdlmpc.msci.memphis.edu (wierdlmpc.msci.memphis.edu
[141.225.11.87])
by mail.Uni-Mainz.DE (8.8.8/8.8.8) with SMTP id IAA01077
for [EMAIL PROTECTED]; Fri, 3 Sep 1999 08:39:19 +0200 (MET DST)
Received: (qmail 24954 invoked by uid 514); 3 Sep 1999 06:39:27 -
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Unsubscribe:
mailto:[EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
Received: (qmail 24944 invoked from network); 3 Sep 1999 06:39:10 -
Organization: TPU
To: LyX Developers [EMAIL PROTECTED]
Subject: Some support for russian
Date: Thu, 2 Sep 1999 10:01:03 +0800
X-Mailer: KMail [version 1.0.17]
Content-Type: Multipart/Mixed;
  boundary="Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD"
MIME-Version: 1.0
Message-Id: [EMAIL PROTECTED]
Content-Transfer-Encoding: 8bit

Hello.

I'm maintaining LyX package for KSI Linux (russian/ukrainian Linux
distribution) and have to patch source to support our languages.
Maybe some parts of my patches will be acceptable for inclusion in
official source tree?...

lyx-1.0.4pre4-ru.patch description:

 * added support for cyrillic inputenc encodings
  (koi8-r, koi8-u, cp1251, cp866).
 * enabled support of cyrillic letters in math mode
  (we need that).

If cyrillic encodings will be accepted, we can also include
in distribution russian ru_splash.lyx (lyx-1.0.4pre4-rusplash.patch).
Note it uses `koi8-r' encoding.

-- 
With Best Wishes,
Const

Re: Some support for russian

[Jean-Marc Lasgouttes]

 "Const" == inria fr lyx-devel-return-6541-Jean-Marc.Lasgouttes writes:

Const I'm maintaining LyX package for KSI Linux (russian/ukrainian
Const Linux distribution) and have to patch source to support our
Const languages.  Maybe some parts of my patches will be acceptable
Const for inclusion in official source tree?...

Hello,

For some reason, your address does not appear on the message, so I'll
just answer on the list. The patch looks good and I see no reason why
we should not include it. However, it seems to me that it clashes a
bit with code submitted by Leonid Zeitlin [EMAIL PROTECTED] (in the
patch concerning the math editor), and I'd like first that you discuss
together the matter and submit us a patch acceptable to all. Since it
is difficult for us to know what works and what does not for russian,
we have to be sure of what goes in.

Note that the 'unsigned char' in math_parser.C is already in CVS.

Thanks for your input.

JMarc

Re: Some support for russian (fwd)

[Jean-Marc Lasgouttes]

 "Paul" == Paul Seelig [EMAIL PROTECTED] writes:

Paul Hey, what's wrong here?  Who is forking my email address?  I
Paul never sent this mail to the list! :-( A little bit annoyed,
Paul P. *8^( -- Please always reply to "Paul Seelig
Paul [EMAIL PROTECTED]"

The one I received had
From: [EMAIL PROTECTED]

I guess that the message did not have a from address and that ezmlm
got confused...

JMarc

Re: crash on 1.0.4pre4

[Jean-Marc Lasgouttes]

 "Harry" == Harry Westfahl Junior [EMAIL PROTECTED] writes:

Harry Yes! The problem usually happens with equation arrays that
Harry are larger (in high, not in width) than the lyx window size.

This is a bug I reported earlier to Alejandro, but I do not know
whether he plans to fix it. If the problem is important for you, you
should probably ask him.

JMarc

Re: \textdegree and teTeX 1.0

[Jean-Marc Lasgouttes]

 "Fred" == Fred Hucht [EMAIL PROTECTED] writes:

Fred On Thu, 2 Sep 1999, Jean-Marc Lasgouttes wrote:
 [...]
Fred This is the version of latex.ltx/latex.fmt.
 [...]
Fred This is the version of article.cls.
   Why are the dates different???
 
Fred See above...
  I know that. However, it is certainly not normal that your latex
 format is older than alrtcle.cls. I think you forgot to rebuild the
 format...

Fred The version is not changed when the format file is rebuilt. I
Fred have, in share/texmf/web2c a rather actual format file:

Fred -rw-r--r-- 1 inst inst 652734 Aug 23 14:12 latex.fmt

If the date shown at startup is old, then the format is old (remember
that this date is the version number of LaTeX). Your article class has
a newer version number than you latex kernel, and this should never
happen, as far as I know.

However, this is probably not the problem here...

 [...]
Fred I think lyx correctly translates ° into \textdegree, but
Fred incorrectly surrounds it by \ensuremath{}. Is this also done
Fred with other symbols?
  It does not translate into \textdegree (this is done at latex
 level). What it does (also for a bunch of other characters) is to
 add \ensuremath{} around the character when encoding is
 latin1. What I do not know is whether this is still needed, since
 it is really a hack.

Fred Sorry, but that's not true. As i wrote in my original mail, lyx
Fred translates ° into \textdegree when the encoding is set to
Fred Latin1, as then in the tex file I find
Fred \ensuremath{\textdegree}. With default encoding (which encoding
Fred is default?) lyx does not translate ° into \textdegree.

Are you sure?? I am very surprised:

fantomas: grep degree src/*
grep: src/CVS: Is a directory

Do you use some special kmap file or something?

JMarc

Re: Some support for russian (fwd)

[Const Kaplinsky]

Jean-Marc Lasgouttes wrote:

  "Paul" == Paul Seelig [EMAIL PROTECTED] writes:
 
 Paul Hey, what's wrong here?  Who is forking my email address?  I
 Paul never sent this mail to the list! :-( A little bit annoyed,
 Paul P. *8^( -- Please always reply to "Paul Seelig
 Paul [EMAIL PROTECTED]"
 
 The one I received had
 From: [EMAIL PROTECTED]
 
 I guess that the message did not have a from address and that ezmlm
 got confused...
 
 JMarc

Sorry for that message, but for now I don't understand what has actually
happened. I'm an author of that mail and I had used my usual address:
[EMAIL PROTECTED]

BTW, is *this* message looks right?

I'll try to find the source of the problem if it is somewhere on my
machines...

-- 

WBW,
Const Kaplinsky
Tomsk Polytechnic University, Tomsk, Russia

Re: Some support for russian (fwd)

[Jean-Marc Lasgouttes]

 "Const" == Const Kaplinsky [EMAIL PROTECTED] writes:

Const Sorry for that message, but for now I don't understand what has
Const actually happened. I'm an author of that mail and I had used my
Const usual address: [EMAIL PROTECTED]

Const BTW, is *this* message looks right?

Yes, your address is now correctly in the From: header.

JMarc

PS: did you get my message about contacting Leonid Zeitlin? I
forwarded him your message too.

JMarc

Re: 3026 public symbol exports in LyX global name space (wa: Re: LaTeX file handling)

[Arnd Hanses]

On 3 Sep 1999 14:09:33 +0900, [EMAIL PROTECTED] wrote:
Now uncommenting in figinset.C:

It seems you have modified Makefile and use figinset.org.C
Which is figinset.C. (Did some preliminary cleanup in figinset.mod.C).

 // assert (_heapset(9) == _HEAPOK);
 printf("The empty heap is set to 9 and checked: \n"); fflush(NULL);

to

 assert (_heapset(9) == _HEAPOK);
 printf("The empty heap is set to 9 and checked: \n"); fflush(NULL);

Why don't you continue! 

As I (and you) already said, just look at figinset.C: It's a mess. A
bit of cleanup before continuing to debug might help; else you could be
stuck fighting against leaks and corrupted pointers all around you.
Especially the declaration, shadowing and (re-)use of variables,
pointers and iterators in some functions is "creative".

 (I can do it myself later, though :) Here is how:
 - set breakpoint at figinset.org.C:780 in gdb
 - bt
 - check what's just above the stack, this must be InsetFig::Recompute

I saw just rubbish memory locations in gdb. But going up farther would
be the way...

 - Insert _heapchk() in InsetFig::Recompute
- just before getfigdata is called
- at the beginning of the method
 - If the heap is already corrupted when InsetFig::Recompute is called,
   then move upward one more step
There is a chance that you can pinpoint the place of memory corruption.

I've already inserted _heapchk() there (and elsehwere), to no avail:
This doesn't mean, the corruption happens later, though.


BTW you are using perror in a very funny way.

At least some fun while debugging this mess :-)

But the result is suggestive.

I must admit, I was surprised. At first I only wanted to extract errno
from crashing _heapchk() or the function that caused this crash, but
then I saw it's not only funny, it's multi-functional, showing (what I
suspect are:) multi-bugs.


 l. 803: heapcheck: Permission denied

Can you figure out where errno was set?

Very good question. Next one please... ;)

Greets,

Arnd

Re: New file patch (was: Re: Just a Matter of Style (was: LaTeX file handling))

[Arnd Hanses]

On Fri, 03 Sep 1999 10:29:01 +0200, Stephan Witt wrote:

I don't think it's a real problem with "zombie-like" running xdvi's.

Only minor annoyance.

1. You can see them.
   You can regularily quit them.
   You can decide yourself when to do so.

Except they decide themselves (they crash with reload and view-dvi on
my box).

2. If I quit LyX, then Xdvi is left running too and I'm sure there're
   users who wants to leave this behaviour untouched.

A possible solution may be
1. to document the current behaviour and/or

Yes

2. kill (with asking the user?) the running "defunct" xdvi and start a new one
   when the user selects "View-dvi" or "Update-dvi" from menu

I agree!

Greets,

Arnd

Re: crash on 1.0.4pre4

[Alejandro Aguilar Sierra]

On Fri, 3 Sep 1999, Jean-Marc Lasgouttes wrote:

 This is a bug I reported earlier to Alejandro, but I do not know
 whether he plans to fix it. If the problem is important for you, you
 should probably ask him.

Harry sent me already an example lyx file. I'll have a look as soon as I
have some time.

Alejandro

sample letterhead, tfm not being found (but it used to)

[Richard E. Hawkins]

I've put debian on my "new" office machine--a 16mb P120, with about a 
600 mb partition.

I can no longer get my fonts for letterhead and the like to work.  Lyx 
returns no errors, but the parkave stuff simply shows up as blank.  
When I export as latex, and run latex, I get errors for assorted sizes 
such as:

(/usr/lib/texmf/tex/latex/base/ifthen.sty)kpathsea: Running mktextfm  
parkave
mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input parkave
This is METAFONT, Version 2.7182 (Web2C 7.2)

kpathsea: Running mktexmf  parkave
! I can't find file `parkave'.
* ...=ljfour; mag:=1; nonstopmode; input parkave
  
Please type another input file name
! Emergency stop.
* ...=ljfour; mag:=1; nonstopmode; input parkave
  
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input parkave' failed.
kpathsea: Appending font creation commands to missfont.log.

! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not 
found.
to be read again 
   \relax 
l.23 \newfont {\lawoffice}{parkave at  14.0pt}
  
? 


I have PKFONTS set as :/home/hawk/fonts, and this contains 
hawkinsttyp0:fontsls parkave*
parkave.1080pkparkave.600pk parkave.pfb   parkave14.1800pk
parkave.1200pkparkave.660pk parkave.tfm   parkave14.300pk
parkave.1440pkparkave.720pk parkave10.1800pk  parkave9.1800pk
parkave.1800pkparkave.840pk parkave10.300pk
parkave.540pk parkave.afm   parkave10.600pk


This was working two weeks ago on FreeBSD, and the configuration there 
came from an older debian configuration.

Hitting return at the prompt simply gets another round of "Running 
mktextfm parkave" but no progress.

I'm stuck.

Until that happened, I was one detail away from a reference letterhead 
:(

I succeeded in making a header for the first page that overhangs both 
margins, but the same things don't work in the footer.  I'm starting to 
believe that the header and footer should be done by including an eps 
made with postscript fonts, but I really don't know how to do this.

For the moment:  help!!!  I need to get a couple of letters  resumes 
out, and I can't :(

rick

-- 

exdented paragraphs

[Richard E. Hawkins]

I think we started on this one, too.  In the latex books I've checked,
I haven't found a way to have exdented (negative indent) paragraphs
such as this one, which are the natural format for a number of
things that I do.

I would expect that there's a trivial way to do this, but I have no 
idea what to look under.

rick

-- 

Re: exdented paragraphs

[mressler]

On Fri, 3 Sep 1999, Richard E. Hawkins wrote:
 I think we started on this one, too.  In the latex books I've checked,
 I haven't found a way to have exdented (negative indent) paragraphs
 such as this one, which are the natural format for a number of
 things that I do.
 
 I would expect that there's a trivial way to do this, but I have no 
 idea what to look under.

You might have to resort to plain TeX to get what you want. The commands
\hangindent and \hangafter may be appropriate. I don't have my TeX book
handy, but \hangindent sets the amount of indentation and \hangafter sets
how many lines to indent in such a fashion. E.g. to do a dropped capital,
you set them like this to make room for your capital:

\hangindent=3.3em
\hangafter=-3

Now there was some funny business about positive and negative values, and
I think there might have been a third command needed for "exdenting". If
you've got Knuth's TeX book, look around page 100 for all this stuff. I
know he discusses it.

Mike
[EMAIL PROTECTED]

Re: sample letterhead, tfm not being found (but it used to)

[Arnd Hanses]

On Fri, 03 Sep 1999 10:04:28 -0500, Richard E. Hawkins wrote:

When I export as latex, and run latex, I get errors for assorted sizes 
such as:

(/usr/lib/texmf/tex/latex/base/ifthen.sty)kpathsea: Running mktextfm  
parkave
mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input parkave
This is METAFONT, Version 2.7182 (Web2C 7.2)

kpathsea: Running mktexmf  parkave
! I can't find file `parkave'.
* ...=ljfour; mag:=1; nonstopmode; input parkave

You need to tell metafont where to find parkave.mf etc. Locate this
with 

locate parkave

and modifiy your environment accordingly (syntax depends on your TeX
distribution). 

Here for emTeX it is:

set
mfinput=D:\XFREE86\USR\EMTEX\mfinput!!;D:\XFREE86\USR\EMTEX\data\dvips!

You'll have to change MFINPUTS, I think. Do 'echo $MFINPUTS'.

I have PKFONTS set as :/home/hawk/fonts, and this contains 

This is not the problem...

Check others, like (modify according to your TeX docs):

T1FONTS
DVIPSHEADERS
DVIDRVinput

I'm stuck.

If this doesn't help: Check for park*.tfm and modify env resp.

Greets,
Arnd

Re: exdented paragraphs

[Amir Karger]

On Fri, Sep 03, 1999 at 08:48:17AM -0700, [EMAIL PROTECTED] wrote:
 
 On Fri, 3 Sep 1999, Richard E. Hawkins wrote:
  I think we started on this one, too.  In the latex books I've checked,
  I haven't found a way to have exdented (negative indent) paragraphs
  such as this one, which are the natural format for a number of
  things that I do.
  
  I would expect that there's a trivial way to do this, but I have no 
  idea what to look under.
 
 You might have to resort to plain TeX to get what you want.

Huh?

Why not \setlength{\parindent}{-.2in}, e.g.? (You could move in the left
margin first and then exdent if you want.)

-Amir

Re: exdented paragraphs

[mressler]

On Fri, 3 Sep 1999, Amir Karger wrote:
  You might have to resort to plain TeX to get what you want.
 
 Huh?
 
 Why not \setlength{\parindent}{-.2in}, e.g.? (You could move in the left
 margin first and then exdent if you want.)

That was the third command. Anyway, make certain to put this command
inside braces if you want to affect only one paragraph. E.g.

{\parindent=-0.2in Here is my paragraph.}

Here is a normal paragraph.

If you put it outside the braces, it will be a global change.
Anyway, with those three commands, you can do just about anything you want
to a paragraph.

Mike
[EMAIL PROTECTED]

P.S. More \hangindent and \hangafter info:

\hangindent: positive values shift the left margin toward the right.
Negative values shift the right margin toward the left! This is not what
one would expect.

\hangafter: a positive value indents the last n lines, a negative value
indents the first n lines in the paragraph.

Both values are reset immediately after the current paragraph to there
default values, unlike \parindent which is global.

Re: sample letterhead, tfm not being found (but it used to)

[Richard E. Hawkins]

Arnd added,



 You need to tell metafont where to find parkave.mf etc. Locate this
 with 

   locate parkave

 and modifiy your environment accordingly (syntax depends on your TeX
 distribution). 

 Here for emTeX it is:

 set
 mfinput=D:\XFREE86\USR\EMTEX\mfinput!!;D:\XFREE86\USR\EMTEX\data\dvips!
 
 You'll have to change MFINPUTS, I think. Do 'echo $MFINPUTS'.


hawkinsttyp0:Jobslocate parkave
/usr/X11R6/lib/X11/fonts/freefont/parkave.pfb
hawkinsttyp0:Jobsecho $MFINPUT
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
hawkinsttyp0:Jobsecho $MFINPUTS
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
hawkinsttyp0:Jobsecho $T1FONTS 
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont

parkave.pfb is in both locations.  But it isn't getting found, even with all of these 
set:

hawkinsttyp0:Jobslatex teaching
This is TeX, Version 3.14159 (Web2C 7.2)
(teaching.tex
LaTeX2e 1998/06/01
Babel v3.6j and hyphenation patterns for american, french, german, ngerman, n
ohyphenation, loaded.
(/usr/lib/texmf/tex/latex/base/letter.cls
Document Class: letter 1998/05/10 v1.2y Standard LaTeX document class
(/usr/lib/texmf/tex/latex/base/size12.clo))
(/usr/lib/texmf/tex/latex/base/fontenc.sty
(/usr/lib/texmf/tex/latex/base/t1enc.def))
(/usr/lib/texmf/tex/latex/misc/geometry.sty
(/usr/lib/texmf/tex/latex/graphics/keyval.sty)
(/usr/lib/texmf/tex/latex/config/geometry.cfg))
(/usr/lib/texmf/tex/latex/fancyhdr/fancyhdr.sty)
(/usr/lib/texmf/tex/latex/graphics/graphics.sty
(/usr/lib/texmf/tex/latex/graphics/trig.sty)
(/usr/lib/texmf/tex/latex/config/graphics.cfg)
(/usr/lib/texmf/tex/latex/graphics/dvips.def))
(/usr/lib/texmf/tex/latex/base/ifthen.sty)kpathsea: Running mktextfm  parkave
mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input parkave
This is METAFONT, Version 2.7182 (Web2C 7.2)

kpathsea: Running mktexmf  parkave
! I can't find file `parkave'.
* ...=ljfour; mag:=1; nonstopmode; input parkave
  
Please type another input file name
! Emergency stop.
* ...=ljfour; mag:=1; nonstopmode; input parkave
  
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input parkave' failed.
kpathsea: Appending font creation commands to missfont.log.

! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not found.
to be read again 
   \relax 
l.23 \newfont {\lawoffice}{parkave at  14pt}
 

I'm trying to get debians documentation for tetex, but it's not cooperating.  It looks 
like it's going to take all weekend to get a working copy :(

rick

-- 

Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

[Duncan Simpson]

RTF is an excellent solution to the word to something else, inclyding LyX, 
problem. Not only does it support practically everything bar macro virii but 
it is also documented and reasonably sensible (quite a contrast with Word 
binary format, which is subject to NDAs and baroque to put it mildly).

One would imagine the purpose of word binary format is to defeat reverse 
engineering, even if it induces masses of bugs in word and trebles the code 
size. Given the only way to fix bugs in word is to upgrade, which costs money, 
conspiracy theorists would say I was right :-) IMHO they might not be entirely 
wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
dire (not worse than word 6, primarly because doing wose is virtually 
impossible).

Unofrtunately 99% of the time people need to do this the only avialable format 
is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
the authors of these beasts actually like word format, do you? I can only 
speak for word2x's author myself, of course.
-- 
Duncan (-:
"software industry, the: unique industry where selling substandard goods is
legal and you can charge extra for fixing the problems."

Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

[Richard E. Hawkins]

duncan delivered,
 
 RTF is an excellent solution to the word to something else, inclyding LyX, 
 problem. Not only does it support practically everything bar macro virii but 
 it is also documented and reasonably sensible (quite a contrast with Word 
 binary format, which is subject to NDAs and baroque to put it mildly).

But isn't Word's implementation of RTF nonstandard and incompatible with real RTF 
(nah, not from them . . .)


-- 

\title[foo]{bar} et al.

[Amir Karger]

Question for the latex gurus in the audience.

One popular complaint about lyx 1.0 is that you can't get the equivalent of
\section[short]{long section title}.

Well, perhaps this has been discussed before, but couldn't you do something
like this in the preamble (I don't know TeX, so this is sort of pseudoTeX):

\newcommand{\shortsection}[1]{\let\shortsectionname=#1}
% Initialie shortsectionname to nothing by default.
% however you set something to "" in TeX
\let\shortsectionname=

\def\mysection\section

\renewcommand{\section}[1]{%
\if\shortsectionname isn't null\let\optarg=\shortsectioname%
\else\let\optarg=#1
\mysection[\optarg]{#1}
\let\shortsectionname=}
}

And in the .layout file:

Style Shortsection
name = shortsection
EndStyle

Ignoring the probably laughable syntax  methodology, you can see that I'm
trying to say that you would write the short title for the chapter first,
in Shortsection style, and then you would write a Section title like usual.
The \shortsection command would set the variable \shortsectionname to the
short section name the user input, and then the renew'ed \section command
would print it out correctly, or print nothing. (I wanted to just say
\mysection[\shortsectionname]{#1} but that would make an empty entry in the
TOC, which is wrong.

Since this doesn't require changing LyX code, I would contend that it won't
break anything. I'm probably wrong. But please tell me why.

The actual reason I'm interested is that revtex lets you use optargs for
\title and a bunch of other fields in the title. If we want to "market" this
thing for clueless professors, we shouldnt' require them to reedit the thing
when they're done. (Of course, APS still isn't accepting submissions in
revtex4, so maybe we can just wait for 1.2.)

-Amir

Re: sample letterhead, tfm not being found (but it used to)

[Arnd Hanses]

On Fri, 03 Sep 1999 13:36:54 -0500, Richard E. Hawkins wrote:


hawkinsttyp0:Jobslocate parkave
/usr/X11R6/lib/X11/fonts/freefont/parkave.pfb

Ha! Got you. This is a type 1 (postscript) font. Handling this is all
very special. You won't survive without good docu. First of all you
need the parkave*.tfm files.

Cf.:
! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not
found.

If you don't have it installed, forget it: Creating this is for hackers
only (You'll find some docu on CTAN).

If you have it, you need to modifiy your env:

SET TEXTFM=D:\XFREE86\USR\EMTEX\fonts\tfm!!
set
TEXFONTS=D:/XFREE86/USR/EMTEX/fonts/tfm/dvips;D:/XFREE86/USR/EMTEX/fonts
/tfm/etc;;

But your env names will be slightly different

hawkinsttyp0:Jobsecho $MFINPUT
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
hawkinsttyp0:Jobsecho $MFINPUTS
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
hawkinsttyp0:Jobsecho $T1FONTS 
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont

parkave.pfb is in both locations.  But it isn't getting found, even with all of these 
set:

This is type 1 (*.pfb), you don't work with adobe type manager, do you?
LaTeX needs *.tfm. dvips will then use the *.pfb, if (and only if)
configured correctly. 

As it seems your dvips is misconfigured You must add parkave there.
Browse CTAN for docu and (perhaps) pre-configured packages with *.tfm.

Greets,
Arnd

Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

[Arnd Hanses]

On Thu, 02 Sep 1999 18:58:46 +0100, Duncan Simpson wrote:

 Given the only way to fix bugs in word is to upgrade, which costs money, 
conspiracy theorists would say I was right :-) IMHO they might not be entirely 
wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
dire (not worse than word 6, primarly because doing wose is virtually 
impossible).


As it seems, Word 8 is now de facto the international standard for
document exchange, even in the internet and within specialized academic
contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
seem to adhere more and more (see the new xyzOffice suite efforts for
Linux). So LyX has to change gears and gain speed...

Unfortunately 99% of the time people need to do this the only avialable format 
is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
the authors of these beasts actually like word format, do you? I can only 
speak for word2x's author myself, of course.

Do you plan Word 8 support?

Some time ago I compiled an old version of word2x on emx. Compiling was
relatively easy, only minor quirks. Adding something like this; I think
not all were necessary:

#ifdef __cplusplus
extern "C" {
#endif

#ifdef __EMX__

/* Compare S1 and S2, ignoring case.  */
int stricmp(__const__ char *, __const__ char *);

#ifndef strcasecmp
#define strcasecmp stricmp  // emx uses M$ fn name instead of posix
name??!
#define _strcasecmp stricmp 
#endif 

/* Compare S1 and S2, ignoring case.  */
int memicmp(__const__ void *, __const__ char *, size_t);

#ifndef memcasecmp 
#define memcasecmp memicmp  // emx uses M$ fn name
#endif

#if !defined(__STRICT_ANSI__)  !defined(_POSIX_SOURCE)

/* Compare no more than N chars of S1 and S2, ignoring case. */
int strnicmp(__const__ char *, __const__ char *, size_t);

#ifndef strncasecmp 
#define strncasecmp strnicmp  // emx uses M$ fn name
#define _strncasecmp strnicmp
#endif 

#endif /* !defined(__STRICT_ANSI__) */
#endif // __EMX__

#ifdef __cplusplus
}
#endif

Those funny fn names - despite emx' aim to facilitate Unix ports - is
always a reason for headache. 

BTW: Porting LyX we have the very same nuisance, recompiling the emx
Lib C with new aliases would help, but is non-standard.

Could you add this (as far as it is still necessary) to your code base
(to config.h or so?)?

I would like to release an updated emx version, perhaps a bit
synchronized with a LyX release for OS/2, if this hasn't already been
done (there was an old release from Russia, IIRC a bit idiosyncratic).
Would you agree?

A usability problem: Non ASCII-character handling was a major problem
for me; do you plan to add some support for the different M$-code pages
and LaTeX encodings (as used with Babel)?

Greets,

Arnd

Re: sample letterhead, tfm not being found (but it used to)

[Richard E. Hawkins]

arnd added,
 On Fri, 03 Sep 1999 13:36:54 -0500, Richard E. Hawkins wrote:

 hawkinsttyp0:Jobslocate parkave
 /usr/X11R6/lib/X11/fonts/freefont/parkave.pfb

 Ha! Got you. 

not quite :)

 This is a type 1 (postscript) font. Handling this is all
 very special. You won't survive without good docu. First of all you
 need the parkave*.tfm files.

Yep, but I did that forever ago.  parkave.tfm is sitting in 
/home/hawk/fonts.  And this configuration used to use it, but for some 
reason doesn't any more.



 Cf.:
 ! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not
 found.
 
 If you don't have it installed, forget it: Creating this is for hackers
 only (You'll find some docu on CTAN).
 
 If you have it, you need to modifiy your env:
 
 SET TEXTFM=D:\XFREE86\USR\EMTEX\fonts\tfm!!
 set
 TEXFONTS=D:/XFREE86/USR/EMTEX/fonts/tfm/dvips;D:/XFREE86/USR/EMTEX/fonts
 /tfm/etc;;

hmm, I added both of these as:/home/hawk/fonts   (that keeps the 
system defaults around under tcsh, doesn't it [I can't use bash; I 
haven't figured out why it can't find certain binaries in its path yet])

Now I seem to get a slightly different set of messages:

kpathsea: Running mktexmf  parkave
! I can't find file `parkave'.
* ...=ljfour; mag:=1; nonstopmode; input parkave
  
Please type another input file name
! Emergency stop.
* ...=ljfour; mag:=1; nonstopmode; input parkave
  
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input parkave' failed.
kpathsea: Appending font creation commands to missfont.log.

! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not 
found.
to be read again 
   \relax 
l.23 \newfont {\lawoffice}{parkave at  14pt}

? 

 

 This is type 1 (*.pfb), you don't work with adobe type manager, do you?
 LaTeX needs *.tfm. dvips will then use the *.pfb, if (and only if)
 configured correctly. 

Nope, I made the tfm files myselfe with mktexmf and the like.

 As it seems your dvips is misconfigured You must add parkave there.
 Browse CTAN for docu and (perhaps) pre-configured packages with *.tfm.

mmm, we figured out that debian's dvi was misconfigured a year or two ago.  I wish 
they'd leave it misconfigured in a consistent manner :)

*sigh*  I guess I do come in tomorrow.

thanks

rick

-- 

Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

[Garst R. Reese]

Arnd Hanses wrote:
 
 As it seems, Word 8 is now de facto the international standard for
 document exchange, even in the internet and within specialized academic
 contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
 seem to adhere more and more (see the new xyzOffice suite efforts for
 Linux). So LyX has to change gears and gain speed...
 
Hmm, why are all those folks with Word 8 asking me to publish their
books using LyX/LaTeX?
Yes, I also have to deal those lazy nits in "specialized academic
contexts," but I sure won't encourage them.
Garst

Re: sample letterhead, tfm not being found (but it used to)

[Garst R. Reese]

"Richard E. Hawkins" wrote:
 
 
  As it seems your dvips is misconfigured You must add parkave there.
  Browse CTAN for docu and (perhaps) pre-configured packages with *.tfm.
 
 mmm, we figured out that debian's dvi was misconfigured a year or two ago.  I wish 
they'd leave it misconfigured in a consistent manner :)
 
 *sigh*  I guess I do come in tomorrow.
 
 thanks
 
 rick
 
 --
Hi rick, stupid question, but... did you run texhash and then
reconfigure in LyX?

Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

[Alejandro Aguilar Sierra]

On Sat, 4 Sep 1999, Arnd Hanses wrote:

 As it seems, Word 8 is now de facto the international standard for
 document exchange, even in the internet and within specialized academic
 contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
 seem to adhere more and more (see the new xyzOffice suite efforts for
 Linux). So LyX has to change gears and gain speed...

I don't think that people used to the wysiwym comfort of LyX will be happy
with a boring wysiwyg word processor. The only reason support for import/
export is suitable is precisely to be able to interchange documents with
those unfortunates that doesn't know the joy of LyX.

Greets,

Alejandro

Re: New file patch (was: Re: Just a Matter of Style (was: LaTeX file handling))

[Stephan Witt]

Arnd Hanses wrote:
> 
> On 31 Aug 1999 17:57:55 +0200, Lars Gullik Bj°nnes wrote:
> 
> >Stephan Witt <[EMAIL PROTECTED]> writes:
> >
> >| LaTeX and Xdvi are children of LyX and directed by LyX to the
> >| internally computed hidden tmp-directory. I'm aware of that
> >| effect: If I close a file and reopen it again, then I have to
> >| close my running Xdvi too, because it is useless now, when using
> >| update->dvi. If I start Xdvi again it works ok. But there is no
> >| mystery. LyX creates a new tmp-directory (as I can see with /bin/ls)
> >| and starts working there. The update-dvi operation creates the
> >| new dvi file in the new tmp-dir.
> >|
> >| latex doesn't delete and recreates the dvi file,
> >| the contents of the dvi file will be replaced by latex/tex.
> >
> >Yes, and this should be now problem. Xdvi should not care (too much)
> >that the file it views suddenly disappears. Ok, the xdvi is now
> >defunct. Do you mean that it would be better if LyX killed the xdvi
> >when it destroys teh buffer?
> 
> IMHO killing before any defunct is the cleanest solution and avoids
> problems.
> 
> Otherwise you'll leave behind abandoned zombie-like processes haunting
> your box (shudder :-)
> 

Sorry for the late response. I was 2 days not online (travelling to customer).

I don't think it's a real problem with "zombie-like" running xdvi's.

1. You can see them.
   You can regularily quit them.
   You can decide yourself when to do so.
2. If I quit LyX, then Xdvi is left running too and I'm sure there're
   users who wants to leave this behaviour untouched.

A possible solution may be
1. to document the current behaviour and/or
2. kill (with asking the user?) the running "defunct" xdvi and start a new one
   when the user selects "View->dvi" or "Update->dvi" from menu

Greets,

Stephan Witt

---
<[EMAIL PROTECTED]>  | beusen unternehmensgruppe senkel
fon: +49 30 549932-62 | Landsberger Allee 392
fax: +49 30 549932-29 | 12681 Berlin, Germany
---

Some support for russian (fwd)

[Paul Seelig]

Hey,

what's wrong here?  Who is forking my email address?  I never sent this
mail to the list! >:-(
   A little bit annoyed, P. *8^(
-- 
Please always reply to "Paul Seelig <[EMAIL PROTECTED]>"

-- Forwarded message (attachments deleted) --
Received: from trudi.zdv.Uni-Mainz.DE ([EMAIL PROTECTED]
[134.93.8.159])
by localhost.sowi.Uni-Mainz.DE (8.8.8/8.8.8/Debian/GNU) with ESMTP id
IAA18128
for <[EMAIL PROTECTED]>; Fri, 3 Sep 1999 08:44:50 +0200
Received: (from pseelig@localhost)
by trudi.zdv.Uni-Mainz.DE (8.8.8/8.8.8) id IAA06733
for [EMAIL PROTECTED]; Fri, 3 Sep 1999 08:39:24 +0200 (MET DST)
From: Paul Seelig <[EMAIL PROTECTED]>
Received: from wierdlmpc.msci.memphis.edu (wierdlmpc.msci.memphis.edu
[141.225.11.87])
by mail.Uni-Mainz.DE (8.8.8/8.8.8) with SMTP id IAA01077
for <[EMAIL PROTECTED]>; Fri, 3 Sep 1999 08:39:19 +0200 (MET DST)
Received: (qmail 24954 invoked by uid 514); 3 Sep 1999 06:39:27 -
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Unsubscribe:

Delivered-To: mailing list [EMAIL PROTECTED]
Received: (qmail 24944 invoked from network); 3 Sep 1999 06:39:10 -
Organization: TPU
To: LyX Developers <[EMAIL PROTECTED]>
Subject: Some support for russian
Date: Thu, 2 Sep 1999 10:01:03 +0800
X-Mailer: KMail [version 1.0.17]
Content-Type: Multipart/Mixed;
  boundary="Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD"
MIME-Version: 1.0
Message-Id: <[EMAIL PROTECTED]>
Content-Transfer-Encoding: 8bit

Hello.

I'm maintaining LyX package for KSI Linux (russian/ukrainian Linux
distribution) and have to patch source to support our languages.
Maybe some parts of my patches will be acceptable for inclusion in
official source tree?...

lyx-1.0.4pre4-ru.patch description:

 * added support for cyrillic inputenc encodings
  (koi8-r, koi8-u, cp1251, cp866).
 * enabled support of cyrillic letters in math mode
  (we need that).

If cyrillic encodings will be accepted, we can also include
in distribution russian ru_splash.lyx (lyx-1.0.4pre4-rusplash.patch).
Note it uses `koi8-r' encoding.

-- 
With Best Wishes,
Const

Re: Some support for russian

[Jean-Marc Lasgouttes]

> "Const" == inria fr  writes:

Const> I'm maintaining LyX package for KSI Linux (russian/ukrainian
Const> Linux distribution) and have to patch source to support our
Const> languages.  Maybe some parts of my patches will be acceptable
Const> for inclusion in official source tree?...

Hello,

For some reason, your address does not appear on the message, so I'll
just answer on the list. The patch looks good and I see no reason why
we should not include it. However, it seems to me that it clashes a
bit with code submitted by Leonid Zeitlin <[EMAIL PROTECTED]> (in the
patch concerning the math editor), and I'd like first that you discuss
together the matter and submit us a patch acceptable to all. Since it
is difficult for us to know what works and what does not for russian,
we have to be sure of what goes in.

Note that the 'unsigned char' in math_parser.C is already in CVS.

Thanks for your input.

JMarc

Re: Some support for russian (fwd)

[Jean-Marc Lasgouttes]

> "Paul" == Paul Seelig <[EMAIL PROTECTED]> writes:

Paul> Hey, what's wrong here?  Who is forking my email address?  I
Paul> never sent this mail to the list! >:-( A little bit annoyed,
Paul> P. *8^( -- Please always reply to "Paul Seelig
Paul> <[EMAIL PROTECTED]>"

The one I received had
From: [EMAIL PROTECTED]

I guess that the message did not have a from address and that ezmlm
got confused...

JMarc

Re: crash on 1.0.4pre4

[Jean-Marc Lasgouttes]

> "Harry" == Harry Westfahl Junior <[EMAIL PROTECTED]> writes:

Harry> Yes! The problem usually happens with equation arrays that
Harry> are larger (in high, not in width) than the lyx window size.

This is a bug I reported earlier to Alejandro, but I do not know
whether he plans to fix it. If the problem is important for you, you
should probably ask him.

JMarc

Re: \textdegree and teTeX 1.0

[Jean-Marc Lasgouttes]

> "Fred" == Fred Hucht <[EMAIL PROTECTED]> writes:

Fred> On Thu, 2 Sep 1999, Jean-Marc Lasgouttes wrote:
>> [...]
Fred> This is the version of latex.ltx/latex.fmt.
>> [...]
Fred> This is the version of article.cls.
>>  >> Why are the dates different???
>> 
Fred> See above...
>>  I know that. However, it is certainly not normal that your latex
>> format is older than alrtcle.cls. I think you forgot to rebuild the
>> format...

Fred> The version is not changed when the format file is rebuilt. I
Fred> have, in share/texmf/web2c a rather actual format file:

Fred> -rw-r--r-- 1 inst inst 652734 Aug 23 14:12 latex.fmt

If the date shown at startup is old, then the format is old (remember
that this date is the version number of LaTeX). Your article class has
a newer version number than you latex kernel, and this should never
happen, as far as I know.

However, this is probably not the problem here...

>> [...]
Fred> I think lyx correctly translates ° into \textdegree, but
Fred> incorrectly surrounds it by \ensuremath{}. Is this also done
Fred> with other symbols?
>>  It does not translate into \textdegree (this is done at latex
>> level). What it does (also for a bunch of other characters) is to
>> add \ensuremath{} around the character when encoding is
>> latin1. What I do not know is whether this is still needed, since
>> it is really a hack.

Fred> Sorry, but that's not true. As i wrote in my original mail, lyx
Fred> translates ° into \textdegree when the encoding is set to
Fred> Latin1, as then in the tex file I find
Fred> \ensuremath{\textdegree}. With default encoding (which encoding
Fred> is default?) lyx does not translate ° into \textdegree.

Are you sure?? I am very surprised:

fantomas: grep degree src/*
grep: src/CVS: Is a directory

Do you use some special kmap file or something?

JMarc

Re: Some support for russian (fwd)

[Const Kaplinsky]

Jean-Marc Lasgouttes wrote:

> > "Paul" == Paul Seelig <[EMAIL PROTECTED]> writes:
> 
> Paul> Hey, what's wrong here?  Who is forking my email address?  I
> Paul> never sent this mail to the list! >:-( A little bit annoyed,
> Paul> P. *8^( -- Please always reply to "Paul Seelig
> Paul> <[EMAIL PROTECTED]>"
> 
> The one I received had
> From: [EMAIL PROTECTED]
> 
> I guess that the message did not have a from address and that ezmlm
> got confused...
> 
> JMarc

Sorry for that message, but for now I don't understand what has actually
happened. I'm an author of that mail and I had used my usual address:
[EMAIL PROTECTED]

BTW, is *this* message looks right?

I'll try to find the source of the problem if it is somewhere on my
machines...

-- 

WBW,
Const Kaplinsky
Tomsk Polytechnic University, Tomsk, Russia

Re: Some support for russian (fwd)

[Jean-Marc Lasgouttes]

> "Const" == Const Kaplinsky <[EMAIL PROTECTED]> writes:

Const> Sorry for that message, but for now I don't understand what has
Const> actually happened. I'm an author of that mail and I had used my
Const> usual address: [EMAIL PROTECTED]

Const> BTW, is *this* message looks right?

Yes, your address is now correctly in the From: header.

JMarc

PS: did you get my message about contacting Leonid Zeitlin? I
forwarded him your message too.

JMarc

Re: 3026 public symbol exports in LyX global name space (wa: Re: LaTeX file handling)

[Arnd Hanses]

On 3 Sep 1999 14:09:33 +0900, [EMAIL PROTECTED] wrote:
>>Now uncommenting in figinset.C:
>
>It seems you have modified Makefile and use figinset.org.C
Which is figinset.C. (Did some preliminary cleanup in figinset.mod.C).
>
>> // assert (_heapset(9) == _HEAPOK);
>> printf("The empty heap is set to 9 and checked: \n"); fflush(NULL);
>>
>>to
>>
>> assert (_heapset(9) == _HEAPOK);
>> printf("The empty heap is set to 9 and checked: \n"); fflush(NULL);

>Why don't you continue! 

As I (and you) already said, just look at figinset.C: It's a mess. A
bit of cleanup before continuing to debug might help; else you could be
stuck fighting against leaks and corrupted pointers all around you.
Especially the declaration, shadowing and (re-)use of variables,
pointers and iterators in some functions is "creative".

> (I can do it myself later, though :) Here is how:
> - set breakpoint at figinset.org.C:780 in gdb
> - bt
> - check what's just above the stack, this must be InsetFig::Recompute

I saw just rubbish memory locations in gdb. But going up farther would
be the way...

> - Insert _heapchk() in InsetFig::Recompute
>- just before getfigdata is called
>- at the beginning of the method
> - If the heap is already corrupted when InsetFig::Recompute is called,
>   then move upward one more step
>There is a chance that you can pinpoint the place of memory corruption.

I've already inserted _heapchk() there (and elsehwere), to no avail:
This doesn't mean, the corruption happens later, though.

>
>BTW you are using perror in a very funny way.

At least some fun while debugging this mess :-)

>But the result is suggestive.

I must admit, I was surprised. At first I only wanted to extract errno
from crashing _heapchk() or the function that caused this crash, but
then I saw it's not only funny, it's multi-functional, showing (what I
suspect are:) multi-bugs.

>
>> l. 803: heapcheck: Permission denied
>
>Can you figure out where errno was set?

Very good question. Next one please... ;)

Greets,

Arnd

Re: New file patch (was: Re: Just a Matter of Style (was: LaTeX file handling))

[Arnd Hanses]

On Fri, 03 Sep 1999 10:29:01 +0200, Stephan Witt wrote:

>I don't think it's a real problem with "zombie-like" running xdvi's.

Only minor annoyance.

>1. You can see them.
>   You can regularily quit them.
>   You can decide yourself when to do so.

Except they decide themselves (they crash with reload and view->dvi on
my box).

>2. If I quit LyX, then Xdvi is left running too and I'm sure there're
>   users who wants to leave this behaviour untouched.
>
>A possible solution may be
>1. to document the current behaviour and/or

Yes

>2. kill (with asking the user?) the running "defunct" xdvi and start a new one
>   when the user selects "View->dvi" or "Update->dvi" from menu

I agree!

Greets,

Arnd

Re: crash on 1.0.4pre4

[Alejandro Aguilar Sierra]

On Fri, 3 Sep 1999, Jean-Marc Lasgouttes wrote:

> This is a bug I reported earlier to Alejandro, but I do not know
> whether he plans to fix it. If the problem is important for you, you
> should probably ask him.

Harry sent me already an example lyx file. I'll have a look as soon as I
have some time.

Alejandro

sample letterhead, tfm not being found (but it used to)

[Richard E. Hawkins]

I've put debian on my "new" office machine--a 16mb P120, with about a 
600 mb partition.

I can no longer get my fonts for letterhead and the like to work.  Lyx 
returns no errors, but the parkave stuff simply shows up as blank.  
When I export as latex, and run latex, I get errors for assorted sizes 
such as:

(/usr/lib/texmf/tex/latex/base/ifthen.sty)kpathsea: Running mktextfm  
parkave
mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input parkave
This is METAFONT, Version 2.7182 (Web2C 7.2)

kpathsea: Running mktexmf  parkave
! I can't find file `parkave'.
<*> ...=ljfour; mag:=1; nonstopmode; input parkave
  
Please type another input file name
! Emergency stop.
<*> ...=ljfour; mag:=1; nonstopmode; input parkave
  
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input parkave' failed.
kpathsea: Appending font creation commands to missfont.log.

! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not 
found.
 
   \relax 
l.23 \newfont {\lawoffice}{parkave at  14.0pt}
  
? 


I have PKFONTS set as :/home/hawk/fonts, and this contains 
hawkinsttyp0:fonts>ls parkave*
parkave.1080pkparkave.600pk parkave.pfb   parkave14.1800pk
parkave.1200pkparkave.660pk parkave.tfm   parkave14.300pk
parkave.1440pkparkave.720pk parkave10.1800pk  parkave9.1800pk
parkave.1800pkparkave.840pk parkave10.300pk
parkave.540pk parkave.afm   parkave10.600pk


This was working two weeks ago on FreeBSD, and the configuration there 
came from an older debian configuration.

Hitting return at the prompt simply gets another round of "Running 
mktextfm parkave" but no progress.

I'm stuck.

Until that happened, I was one detail away from a reference letterhead 
:(

I succeeded in making a header for the first page that overhangs both 
margins, but the same things don't work in the footer.  I'm starting to 
believe that the header and footer should be done by including an eps 
made with postscript fonts, but I really don't know how to do this.

For the moment:  help!!!  I need to get a couple of letters & resumes 
out, and I can't :(

rick

-- 

exdented paragraphs

[Richard E. Hawkins]

I think we started on this one, too.  In the latex books I've checked,
I haven't found a way to have exdented (negative indent) paragraphs
such as this one, which are the natural format for a number of
things that I do.

I would expect that there's a trivial way to do this, but I have no 
idea what to look under.

rick

-- 

Re: exdented paragraphs

[mressler]

On Fri, 3 Sep 1999, Richard E. Hawkins wrote:
> I think we started on this one, too.  In the latex books I've checked,
> I haven't found a way to have exdented (negative indent) paragraphs
> such as this one, which are the natural format for a number of
> things that I do.
> 
> I would expect that there's a trivial way to do this, but I have no 
> idea what to look under.

You might have to resort to plain TeX to get what you want. The commands
\hangindent and \hangafter may be appropriate. I don't have my TeX book
handy, but \hangindent sets the amount of indentation and \hangafter sets
how many lines to indent in such a fashion. E.g. to do a dropped capital,
you set them like this to make room for your capital:

\hangindent=3.3em
\hangafter=-3

Now there was some funny business about positive and negative values, and
I think there might have been a third command needed for "exdenting". If
you've got Knuth's TeX book, look around page 100 for all this stuff. I
know he discusses it.

Mike
[EMAIL PROTECTED]

Re: sample letterhead, tfm not being found (but it used to)

[Arnd Hanses]

On Fri, 03 Sep 1999 10:04:28 -0500, Richard E. Hawkins wrote:

>When I export as latex, and run latex, I get errors for assorted sizes 
>such as:
>
>(/usr/lib/texmf/tex/latex/base/ifthen.sty)kpathsea: Running mktextfm  
>parkave
>mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input parkave
>This is METAFONT, Version 2.7182 (Web2C 7.2)
>
>kpathsea: Running mktexmf  parkave
>! I can't find file `parkave'.
><*> ...=ljfour; mag:=1; nonstopmode; input parkave

You need to tell metafont where to find parkave.mf etc. Locate this
with 

locate parkave

and modifiy your environment accordingly (syntax depends on your TeX
distribution). 

Here for emTeX it is:

set
mfinput=D:\XFREE86\USR\EMTEX\mfinput!!;D:\XFREE86\USR\EMTEX\data\dvips!

You'll have to change MFINPUTS, I think. Do 'echo $MFINPUTS'.

>I have PKFONTS set as :/home/hawk/fonts, and this contains 

This is not the problem...

Check others, like (modify according to your TeX docs):

T1FONTS
DVIPSHEADERS
DVIDRVinput

>I'm stuck.

If this doesn't help: Check for park*.tfm and modify env resp.

Greets,
Arnd

Re: exdented paragraphs

[Amir Karger]

On Fri, Sep 03, 1999 at 08:48:17AM -0700, [EMAIL PROTECTED] wrote:
> 
> On Fri, 3 Sep 1999, Richard E. Hawkins wrote:
> > I think we started on this one, too.  In the latex books I've checked,
> > I haven't found a way to have exdented (negative indent) paragraphs
> > such as this one, which are the natural format for a number of
> > things that I do.
> > 
> > I would expect that there's a trivial way to do this, but I have no 
> > idea what to look under.
> 
> You might have to resort to plain TeX to get what you want.

Huh?

Why not \setlength{\parindent}{-.2in}, e.g.? (You could move in the left
margin first and then exdent if you want.)

-Amir

Re: exdented paragraphs

[mressler]

On Fri, 3 Sep 1999, Amir Karger wrote:
> > You might have to resort to plain TeX to get what you want.
> 
> Huh?
> 
> Why not \setlength{\parindent}{-.2in}, e.g.? (You could move in the left
> margin first and then exdent if you want.)

That was the third command. Anyway, make certain to put this command
inside braces if you want to affect only one paragraph. E.g.

{\parindent=-0.2in Here is my paragraph.}

Here is a normal paragraph.

If you put it outside the braces, it will be a global change.
Anyway, with those three commands, you can do just about anything you want
to a paragraph.

Mike
[EMAIL PROTECTED]

P.S. More \hangindent and \hangafter info:

\hangindent: positive values shift the left margin toward the right.
Negative values shift the right margin toward the left! This is not what
one would expect.

\hangafter: a positive value indents the last n lines, a negative value
indents the first n lines in the paragraph.

Both values are reset immediately after the current paragraph to there
default values, unlike \parindent which is global.

Re: sample letterhead, tfm not being found (but it used to)

[Richard E. Hawkins]

Arnd added,



> You need to tell metafont where to find parkave.mf etc. Locate this
> with 

>   locate parkave

> and modifiy your environment accordingly (syntax depends on your TeX
> distribution). 

> Here for emTeX it is:

> set
> mfinput=D:\XFREE86\USR\EMTEX\mfinput!!;D:\XFREE86\USR\EMTEX\data\dvips!
> 
> You'll have to change MFINPUTS, I think. Do 'echo $MFINPUTS'.


hawkinsttyp0:Jobs>locate parkave
/usr/X11R6/lib/X11/fonts/freefont/parkave.pfb
hawkinsttyp0:Jobs>echo $MFINPUT
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
hawkinsttyp0:Jobs>echo $MFINPUTS
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
hawkinsttyp0:Jobs>echo $T1FONTS 
:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont

parkave.pfb is in both locations.  But it isn't getting found, even with all of these 
set:

hawkinsttyp0:Jobs>latex teaching
This is TeX, Version 3.14159 (Web2C 7.2)
(teaching.tex
LaTeX2e <1998/06/01>
Babel  and hyphenation patterns for american, french, german, ngerman, n
ohyphenation, loaded.
(/usr/lib/texmf/tex/latex/base/letter.cls
Document Class: letter 1998/05/10 v1.2y Standard LaTeX document class
(/usr/lib/texmf/tex/latex/base/size12.clo))
(/usr/lib/texmf/tex/latex/base/fontenc.sty
(/usr/lib/texmf/tex/latex/base/t1enc.def))
(/usr/lib/texmf/tex/latex/misc/geometry.sty
(/usr/lib/texmf/tex/latex/graphics/keyval.sty)
(/usr/lib/texmf/tex/latex/config/geometry.cfg))
(/usr/lib/texmf/tex/latex/fancyhdr/fancyhdr.sty)
(/usr/lib/texmf/tex/latex/graphics/graphics.sty
(/usr/lib/texmf/tex/latex/graphics/trig.sty)
(/usr/lib/texmf/tex/latex/config/graphics.cfg)
(/usr/lib/texmf/tex/latex/graphics/dvips.def))
(/usr/lib/texmf/tex/latex/base/ifthen.sty)kpathsea: Running mktextfm  parkave
mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input parkave
This is METAFONT, Version 2.7182 (Web2C 7.2)

kpathsea: Running mktexmf  parkave
! I can't find file `parkave'.
<*> ...=ljfour; mag:=1; nonstopmode; input parkave
  
Please type another input file name
! Emergency stop.
<*> ...=ljfour; mag:=1; nonstopmode; input parkave
  
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input parkave' failed.
kpathsea: Appending font creation commands to missfont.log.

! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not found.
 
   \relax 
l.23 \newfont {\lawoffice}{parkave at  14pt}
 

I'm trying to get debians documentation for tetex, but it's not cooperating.  It looks 
like it's going to take all weekend to get a working copy :(

rick

-- 

Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

[Duncan Simpson]

RTF is an excellent solution to the word to something else, inclyding LyX, 
problem. Not only does it support practically everything bar macro virii but 
it is also documented and reasonably sensible (quite a contrast with Word 
binary format, which is subject to NDAs and baroque to put it mildly).

One would imagine the purpose of word binary format is to defeat reverse 
engineering, even if it induces masses of bugs in word and trebles the code 
size. Given the only way to fix bugs in word is to upgrade, which costs money, 
conspiracy theorists would say I was right :-) IMHO they might not be entirely 
wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
dire (not worse than word 6, primarly because doing wose is virtually 
impossible).

Unofrtunately 99% of the time people need to do this the only avialable format 
is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
the authors of these beasts actually like word format, do you? I can only 
speak for word2x's author myself, of course.
-- 
Duncan (-:
"software industry, the: unique industry where selling substandard goods is
legal and you can charge extra for fixing the problems."

Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

[Richard E. Hawkins]

duncan delivered,
 
> RTF is an excellent solution to the word to something else, inclyding LyX, 
> problem. Not only does it support practically everything bar macro virii but 
> it is also documented and reasonably sensible (quite a contrast with Word 
> binary format, which is subject to NDAs and baroque to put it mildly).

But isn't Word's implementation of RTF nonstandard and incompatible with real RTF 
(nah, not from them . . .)


-- 

\title[foo]{bar} et al.

[Amir Karger]

Question for the latex gurus in the audience.

One popular complaint about lyx 1.0 is that you can't get the equivalent of
\section[short]{long section title}.

Well, perhaps this has been discussed before, but couldn't you do something
like this in the preamble (I don't know TeX, so this is sort of pseudoTeX):

\newcommand{\shortsection}[1]{\let\shortsectionname=#1}
% Initialie shortsectionname to nothing by default.
% however you set something to "" in TeX
\let\shortsectionname=

\def\mysection\section

\renewcommand{\section}[1]{%
\if\shortsectionname isn't null\let\optarg=\shortsectioname%
\else\let\optarg=#1
\mysection[\optarg]{#1}
\let\shortsectionname=}
}

And in the .layout file:

Style Shortsection
name = shortsection
EndStyle

Ignoring the probably laughable syntax & methodology, you can see that I'm
trying to say that you would write the short title for the chapter first,
in Shortsection style, and then you would write a Section title like usual.
The \shortsection command would set the variable \shortsectionname to the
short section name the user input, and then the renew'ed \section command
would print it out correctly, or print nothing. (I wanted to just say
\mysection[\shortsectionname]{#1} but that would make an empty entry in the
TOC, which is wrong.

Since this doesn't require changing LyX code, I would contend that it won't
break anything. I'm probably wrong. But please tell me why.

The actual reason I'm interested is that revtex lets you use optargs for
\title and a bunch of other fields in the title. If we want to "market" this
thing for clueless professors, we shouldnt' require them to reedit the thing
when they're done. (Of course, APS still isn't accepting submissions in
revtex4, so maybe we can just wait for 1.2.)

-Amir

Re: sample letterhead, tfm not being found (but it used to)

[Arnd Hanses]

On Fri, 03 Sep 1999 13:36:54 -0500, Richard E. Hawkins wrote:

>
>hawkinsttyp0:Jobs>locate parkave
>/usr/X11R6/lib/X11/fonts/freefont/parkave.pfb

Ha! Got you. This is a type 1 (postscript) font. Handling this is all
very special. You won't survive without good docu. First of all you
need the parkave*.tfm files.

Cf.:
! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not
found.

If you don't have it installed, forget it: Creating this is for hackers
only (You'll find some docu on CTAN).

If you have it, you need to modifiy your env:

SET TEXTFM=D:\XFREE86\USR\EMTEX\fonts\tfm!!
set
TEXFONTS=D:/XFREE86/USR/EMTEX/fonts/tfm/dvips;D:/XFREE86/USR/EMTEX/fonts
/tfm/etc;;

But your env names will be slightly different

>hawkinsttyp0:Jobs>echo $MFINPUT
>:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
>hawkinsttyp0:Jobs>echo $MFINPUTS
>:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
>hawkinsttyp0:Jobs>echo $T1FONTS 
>:/home/hawk/fonts:/usr/X11R6/lib/X11/fonts/freefont
>
>parkave.pfb is in both locations.  But it isn't getting found, even with all of these 
>set:

This is type 1 (*.pfb), you don't work with adobe type manager, do you?
LaTeX needs *.tfm. dvips will then use the *.pfb, if (and only if)
configured correctly. 

As it seems your dvips is misconfigured You must add parkave there.
Browse CTAN for docu and (perhaps) pre-configured packages with *.tfm.

Greets,
Arnd

Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

[Arnd Hanses]

On Thu, 02 Sep 1999 18:58:46 +0100, Duncan Simpson wrote:

> Given the only way to fix bugs in word is to upgrade, which costs money, 
>conspiracy theorists would say I was right :-) IMHO they might not be entirely 
>wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
>dire (not worse than word 6, primarly because doing wose is virtually 
>impossible).
>

As it seems, Word 8 is now de facto the international standard for
document exchange, even in the internet and within specialized academic
contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
seem to adhere more and more (see the new xyzOffice suite efforts for
Linux). So LyX has to change gears and gain speed...

>Unfortunately 99% of the time people need to do this the only avialable format 
>is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
>the authors of these beasts actually like word format, do you? I can only 
>speak for word2x's author myself, of course.

Do you plan Word 8 support?

Some time ago I compiled an old version of word2x on emx. Compiling was
relatively easy, only minor quirks. Adding something like this; I think
not all were necessary:

#ifdef __cplusplus
extern "C" {
#endif

#ifdef __EMX__

/* Compare S1 and S2, ignoring case.  */
int stricmp(__const__ char *, __const__ char *);

#ifndef strcasecmp
#define strcasecmp stricmp  // emx uses M$ fn name instead of posix
name??!
#define _strcasecmp stricmp 
#endif 

/* Compare S1 and S2, ignoring case.  */
int memicmp(__const__ void *, __const__ char *, size_t);

#ifndef memcasecmp 
#define memcasecmp memicmp  // emx uses M$ fn name
#endif

#if !defined(__STRICT_ANSI__) && !defined(_POSIX_SOURCE)

/* Compare no more than N chars of S1 and S2, ignoring case. */
int strnicmp(__const__ char *, __const__ char *, size_t);

#ifndef strncasecmp 
#define strncasecmp strnicmp  // emx uses M$ fn name
#define _strncasecmp strnicmp
#endif 

#endif /* !defined(__STRICT_ANSI__) */
#endif // __EMX__

#ifdef __cplusplus
}
#endif

Those funny fn names - despite emx' aim to facilitate Unix ports - is
always a reason for headache. 

BTW: Porting LyX we have the very same nuisance, recompiling the emx
Lib C with new aliases would help, but is non-standard.

Could you add this (as far as it is still necessary) to your code base
(to config.h or so?)?

I would like to release an updated emx version, perhaps a bit
synchronized with a LyX release for OS/2, if this hasn't already been
done (there was an old release from Russia, IIRC a bit idiosyncratic).
Would you agree?

A usability problem: Non ASCII-character handling was a major problem
for me; do you plan to add some support for the different M$-code pages
and LaTeX encodings (as used with Babel)?

Greets,

Arnd

Re: sample letterhead, tfm not being found (but it used to)

[Richard E. Hawkins]

arnd added,
> On Fri, 03 Sep 1999 13:36:54 -0500, Richard E. Hawkins wrote:

> >hawkinsttyp0:Jobs>locate parkave
> >/usr/X11R6/lib/X11/fonts/freefont/parkave.pfb

> Ha! Got you. 

not quite :)

> This is a type 1 (postscript) font. Handling this is all
> very special. You won't survive without good docu. First of all you
> need the parkave*.tfm files.

Yep, but I did that forever ago.  parkave.tfm is sitting in 
/home/hawk/fonts.  And this configuration used to use it, but for some 
reason doesn't any more.



> Cf.:
> ! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not
> found.
> 
> If you don't have it installed, forget it: Creating this is for hackers
> only (You'll find some docu on CTAN).
> 
> If you have it, you need to modifiy your env:
> 
> SET TEXTFM=D:\XFREE86\USR\EMTEX\fonts\tfm!!
> set
> TEXFONTS=D:/XFREE86/USR/EMTEX/fonts/tfm/dvips;D:/XFREE86/USR/EMTEX/fonts
> /tfm/etc;;

hmm, I added both of these as:/home/hawk/fonts   (that keeps the 
system defaults around under tcsh, doesn't it [I can't use bash; I 
haven't figured out why it can't find certain binaries in its path yet])

Now I seem to get a slightly different set of messages:

kpathsea: Running mktexmf  parkave
! I can't find file `parkave'.
<*> ...=ljfour; mag:=1; nonstopmode; input parkave
  
Please type another input file name
! Emergency stop.
<*> ...=ljfour; mag:=1; nonstopmode; input parkave
  
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input parkave' failed.
kpathsea: Appending font creation commands to missfont.log.

! Font \lawoffice=parkave at 14.0pt not loadable: Metric (TFM) file not 
found.
 
   \relax 
l.23 \newfont {\lawoffice}{parkave at  14pt}

? 

 

> This is type 1 (*.pfb), you don't work with adobe type manager, do you?
> LaTeX needs *.tfm. dvips will then use the *.pfb, if (and only if)
> configured correctly. 

Nope, I made the tfm files myselfe with mktexmf and the like.

> As it seems your dvips is misconfigured You must add parkave there.
> Browse CTAN for docu and (perhaps) pre-configured packages with *.tfm.

mmm, we figured out that debian's dvi was misconfigured a year or two ago.  I wish 
they'd leave it misconfigured in a consistent manner :)

*sigh*  I guess I do come in tomorrow.

thanks

rick

-- 

Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

[Garst R. Reese]

Arnd Hanses wrote:
> 
> As it seems, Word 8 is now de facto the international standard for
> document exchange, even in the internet and within specialized academic
> contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
> seem to adhere more and more (see the new xyzOffice suite efforts for
> Linux). So LyX has to change gears and gain speed...
> 
Hmm, why are all those folks with Word 8 asking me to publish their
books using LyX/LaTeX?
Yes, I also have to deal those lazy nits in "specialized academic
contexts," but I sure won't encourage them.
Garst

Re: sample letterhead, tfm not being found (but it used to)

[Garst R. Reese]

"Richard E. Hawkins" wrote:
> 
> 
> > As it seems your dvips is misconfigured You must add parkave there.
> > Browse CTAN for docu and (perhaps) pre-configured packages with *.tfm.
> 
> mmm, we figured out that debian's dvi was misconfigured a year or two ago.  I wish 
>they'd leave it misconfigured in a consistent manner :)
> 
> *sigh*  I guess I do come in tomorrow.
> 
> thanks
> 
> rick
> 
> --
Hi rick, stupid question, but... did you run texhash and then
reconfigure in LyX?

Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

[Alejandro Aguilar Sierra]

On Sat, 4 Sep 1999, Arnd Hanses wrote:

> As it seems, Word 8 is now de facto the international standard for
> document exchange, even in the internet and within specialized academic
> contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
> seem to adhere more and more (see the new xyzOffice suite efforts for
> Linux). So LyX has to change gears and gain speed...

I don't think that people used to the wysiwym comfort of LyX will be happy
with a boring wysiwyg word processor. The only reason support for import/
export is suitable is precisely to be able to interchange documents with
those unfortunates that doesn't know the joy of LyX.

Greets,

Alejandro