On Mon, Jul 26, 1999 at 11:54:42AM +0200, Jean-Marc Lasgouttes wrote:
> >>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
>
> It looks very good! I'll try to throw in a couple criticisms for good
> measure, however.
>
> In internet.php3, you forgot www.it.lyx.org, hosted by Juergen.
Added. Too bad I can't connect to sunsite again!
> In the platform page, the first paragraph ends with "..., and Solaris,
> and Digital Unix. " Is it just me, or is there an extraneous "and"?
> Note that Digital Unix (aka DEC OSF/1) is now Tru64 Unix :)
"and" removed. As for the Tru64 thing, am I missing a joke, or am I supposed
to replace DU with TU?
> For OS/2, you could give mailto: URLs for SMiyata and Arndt, if they
> accept to receive e-mail on this... You could maybe take the first
> long paragraph of README.OS2 intead of the e-mail from Arndt, or at
> least use cvsweb/checkout to ling to README.OS2 and
> INSTALL.OS2. Similarly, the mentions of README and INSTALL for Unices
> should be URLs.
OK. Arnd and SMiyata, what do *you* think I should put on that page? I'm
willing to use URL's, paragraphs, links to README's, whatever, but you
probably have the best ideas.
> Amir> - download.php3 still seems long to me. Should I put, e.g.,
> Amir> "stuff with relevance to lyx" on a separate page?
>
> Yes. And maybe setup the list in some sort of table, so that it is
> more readable.
I'll see what I can do.
> Amir> - news.php3 mentions v1.0.3 and links to a CVS checkout of
> Amir> CHANGES. While linking to a CVS checkout is Cool, and may even
> Amir> be Useful sometimes, here I think it's misleading, because the
> Amir> CHANGES file will reflect things that aren't in CHANGES!
>
> You should mention that CHANGES may contain things that are not yet
> released.
I don't really like that option. The link is on the page so that the user
can get information on what changes are in the distribution. Why have a link
to information that's not applicable to the user's situation? Certainly, we
should have a link to the CVS version of CHANGES (something like, "if you'd
like to know what has been done recently in CVS, here are the latest <a
href=...>CHANGES</a>") but I think it's just confusing to say "here is
version 1.0.3 and these are the changes" and then they don't actually list
the right changes.
It seems like we have releases rarely enough that---especially once the web
site is under CVS---we could just put a new copy of CHANGES up for each
version. Of course, this will only work if CHANGES is the only file we need
to change for each release.
> Amir> - Online docs would definitely be Cool. They should of course be
> Amir> HTML, not ps, so that people can look up specific things. And of
> Amir> course, now that DocBook is working so well (yay!) they should
> Amir> be easy to convert. Right?
>
> Or maybe PDF, if somebody has access to pdflatex or distiller.
I'm always willing to accept contributions. Of course, since all the docs
are included in the distribution, it doesn't seem like people will often
need to reference them, so they don't have to be pretty. HTML seems simpler
to me.
> Amir> If we did that, I think it would be easy to use PHP to create
> Amir> submenus for Download, About, etc. I know Asger said they would
> Amir> be hard to maintain, but I think with creative programming, we
> Amir> might be able to set it up so that moving files around would
> Amir> require changing information in only one place.
>
> Yes, I think each page should have its own submenus in place of the
> mailing-lists in the navbar, if possible.
In place of rather than in addition? I'm rather ambivalent about this. Does
anyone think this needs to stay?
-Amir
