caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Martin Sandin <om_sandin@yahoo.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Still problems with the main ocaml web page
Date: Wed, 30 Mar 2005 17:29:01 +0200	[thread overview]
Message-ID: <20050330152901.GC18175@yquem.inria.fr> (raw)
In-Reply-To: <20050330141949.67864.qmail@web50904.mail.yahoo.com>

> The site works fine in Opera and Mozilla, and is a lot
> nicer than the old, but it doesn't work in IE. The
> fact that Windows isn't the no 1 priority of the OCaml
> team, or the community, is both obvious (witness the
> lack of 3.08.3 binaries for Windows) and
> understandable. But I am still surprised that it was
> even considered acceptable to release a site which
> entierly excludes the 80+% majority browser (figure is
> likely to be lower in the dev community, but no way
> less than 50%).

Of course the new site was tested with IE, and it works just fine on
my Windows installation.  Something is happening that 1- we don't
understand, and 2- we can't reproduce.  Another user suggested this
might have to do with language preferences in the browser, which could
expose a problem in content (language) negociation between the browser
and server.  Any constructive advice on how to attack this problem is
most welcome.

Concerning 3.08.3 binaries for Windows, please keep the following in
mind.  We have volunteers who do a great job of packaging binaries for
various flavors of Linux.  Other Unix users just compile from sources
and don't complain.  Doligez does the MacOS X binaries, but that's
because he uses MacOS X for all his computing.  It's only for Windows
that I haven't found anyone to prepare the binary packages in my
place.  So, yes, you'll have to wait till I don't have anything more
urgent to do, and that will probably take several weeks.  If you're
unhappy about that, why don't you build a binary distribution
yourself?  I'll be extremely grateful.

- Xavier Leroy


  parent reply	other threads:[~2005-03-30 15:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 14:19 Martin Sandin
2005-03-30 15:01 ` [Caml-list] " Yaron Minsky
2005-03-30 15:11 ` Christopher Campbell
2005-03-30 15:29 ` Xavier Leroy [this message]
2005-03-30 19:24   ` Dimitri Timofeev
2005-03-30 23:48     ` Marc Herbert
2005-03-30 20:30   ` Eijiro Sumii
2005-03-30 20:38     ` webmaster@caml.inria.fr is not a "legal" mail address (Re: [Caml-list] Re: Still problems with the main ocaml web page) Eijiro Sumii
2005-03-31 12:21       ` Francis Dupont
2005-03-31 13:05         ` webmaster@caml.inria.fr is not a "legal" mail address Eijiro Sumii
2005-03-31 13:35           ` Francis Dupont
2005-03-31 18:37             ` [OT] " Eijiro Sumii
2005-03-31 20:08               ` Eijiro Sumii
2005-03-31 10:35 [Caml-list] Re: Still problems with the main ocaml web page Martin Sandin
2005-03-31 12:14 ` Maxence Guesdon
2005-03-31 18:58   ` Eijiro Sumii
2005-03-31 19:28 Martin Sandin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050330152901.GC18175@yquem.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=om_sandin@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).