From ping@lfw.org  Thu Jun  1 08:17:47 2000
From: ping@lfw.org (Ka-Ping Yee)
Date: Thu, 1 Jun 2000 00:17:47 -0700 (PDT)
Subject: [Doc-SIG] htmldoc.py and inspect.py
In-Reply-To: <4.3.1.0.20000531190035.00af19f0@mail.tmt.de>
Message-ID: <Pine.LNX.4.10.10006010016570.2697-100000@localhost>

On Wed, 31 May 2000, Walter Doerwald wrote:
> 
> But eventually someone has to implement some structured text docstring.
> Plain ASCII dumps just don't cut it anymore.

Hmm.  I have two answers to that:

    (a) What is the burning need to structure the text anyway?
        What information do you expect to need to automatically
        extract from within individual docstrings?  Since they
        are really for human consumption, and at the level of
        entire docstrings, not little pieces, plain ASCII really
        does get you 90% of the way.  ("man" still works pretty
        well, right?)

    (b) Sure, i grant you that a little style and formatting
        might be nice.  (But only "nice", not "essential".
        The only thing that seems close to essential might be
        marking symbol names and code fragments.)  Anyway, in
        this case, i like Paul's suggestion very much: we'll
        just provide a hook for you to do your own parsing
        and formatting, and that leaves the door open for you
        to implement structured text if you want.

Hmm.  Maybe a third answer:

    (c) Even though right now the state of existing docstrings
        makes for a minimal payoff from using structured text,
        i can see a particular structured text standard getting
        much more established by the time, say, Python 3000
        arrives -- when the document-generating tool is mature,
        and we are ready to overhaul everything, then it may
        actually be possible to declare, "This is the standard
        way to write docstrings."  Then a big payoff is possible.

> And when you use XML you can convert this to practically any format
> that is out there (PDF, TeX, ASCII, ...)

No one will bother to write XML by hand in their code.  Really.
I mean it.  To take an example from MathML, who on earth is going
to write

    <apply>
        <plus/>
        <mn>x</mn>
        <mn>y</mn>
    </apply>

instead of writing x+y?  I count a factor of at least 15.

> 50 years of computer science and I still can't type my name
> into an email. I'm really impressed! :-(

*sigh*  I know, it makes me really sad, too.


-- ?!ng

"To be human is to continually change.  Your desire to remain as you are
is what ultimately limits you."
    -- The Puppet Master, Ghost in the Shell



From ke@gnu.franken.de  Fri Jun  2 04:24:54 2000
From: ke@gnu.franken.de (Karl Eichwalder)
Date: 02 Jun 2000 05:24:54 +0200
Subject: [Doc-SIG] Re: htmldoc.py and inspect.py
In-Reply-To: Ka-Ping Yee's message of "Thu, 1 Jun 2000 00:17:47 -0700 (PDT)"
References: <Pine.LNX.4.10.10006010016570.2697-100000@localhost>
Message-ID: <shsnuwwyrd.fsf@tux.gnu.franken.de>

Ka-Ping Yee <ping@lfw.org> writes:

> On Wed, 31 May 2000, Walter Doerwald wrote:

> > 50 years of computer science and I still can't type my name
> > into an email. I'm really impressed! :-(

Really?  I can do it for you :)

BTW, my name is easily written -- but people will fail to pronounce it
correctly -- is this better?

> *sigh*  I know, it makes me really sad, too.

From time to time I receive e-mails with properly encoded eastern names.
They are looking nice -- but my eyes are untrained to remember them.

-- 
work : ke@suse.de                          |
     : http://www.suse.de/~ke/             |          ------    ,__o
home : ke@gnu.franken.de                   |         ------   _-\_<,
     : http://www.franken.de/users/gnu/ke/ |        ------   (*)/'(*)



From fdrake@beopen.com  Mon Jun  5 17:09:55 2000
From: fdrake@beopen.com (Fred L. Drake, Jr.)
Date: Mon, 5 Jun 2000 12:09:55 -0400 (EDT)
Subject: [Doc-SIG] Re: Help with SSL in 1.6
In-Reply-To: <39382a75$0$25922@personalnews.de.uu.net>
References: <Pine.LNX.4.21.0006021832560.13804-100000@lade.src.no>
 <39382a75$0$25922@personalnews.de.uu.net>
Message-ID: <14651.53459.943389.828213@cj42289-a.reston1.va.home.com>

Johannes Stezenbach writes:
 > configure doesn't seem to test for OpenSSL.
 > You must edit Modules/Setup manually (copy from Setup.in,
 > if necessary):

  And the SSL support doesn't appear to be documented anywhere.  If
anyone would like to document the socket.ssl() function and the SSL
objects, I'd love to see a patch to the documentation, or just plain
text for the new material.
  If anyone's interested, please drop me a note!


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member



From walter@livinglogic.de  Tue Jun  6 17:47:24 2000
From: walter@livinglogic.de (Walter Doerwald)
Date: Tue, 06 Jun 2000 18:47:24 +0200
Subject: [Doc-SIG] htmldoc.py and inspect.py
In-Reply-To: <Pine.LNX.4.10.10006010016570.2697-100000@localhost>
References: <4.3.1.0.20000531190035.00af19f0@mail.tmt.de>
Message-ID: <4.3.1.0.20000606183848.00ae8900@mail.tmt.de>

At 09:17 01.06.00, Ka-Ping Yee wrote:
>On Wed, 31 May 2000, Walter Doerwald wrote:
> >
> > But eventually someone has to implement some structured text docstring.
> > Plain ASCII dumps just don't cut it anymore.
>
>Hmm.  I have two answers to that:
>
>     (a) What is the burning need to structure the text anyway?

I might want to do an <ol type=3D"a">, like you tried to do here.
Or any other feature of HTML, like tables, paragraphs, <dl>s
Unicode characters, links, ...

And of course be can have any kind of markup we like.

Some day we might even generate class hierarchy diagrams in SVG.

>         What information do you expect to need to automatically
>         extract from within individual docstrings?  Since they
>         are really for human consumption, and at the level of
>         entire docstrings, not little pieces, plain ASCII really
>         does get you 90% of the way.  ("man" still works pretty
>         well, right?)

But AFAIK man *does* use syntactic markup.

>    (b) Sure, i grant you that a little style and formatting
>         might be nice.  (But only "nice", not "essential".

One mans niceties are another mans essentials. >;)

>         The only thing that seems close to essential might be
>         marking symbol names and code fragments.)  Anyway, in
>         this case, i like Paul's suggestion very much: we'll
>         just provide a hook for you to do your own parsing
>         and formatting, and that leaves the door open for you
>         to implement structured text if you want.

That doesn't solve the problem: Either I write my docstrings
in XML or I don't. A simple ASCII parser doesn't make the XML
in the docstring go away.

>Hmm.  Maybe a third answer:
>
>     (c) Even though right now the state of existing docstrings
>         makes for a minimal payoff from using structured text,
>         i can see a particular structured text standard getting
>         much more established by the time, say, Python 3000
>         arrives -- when the document-generating tool is mature,
>         and we are ready to overhaul everything, then it may
>         actually be possible to declare, "This is the standard
>         way to write docstrings."  Then a big payoff is possible.

Sounds good.

> > And when you use XML you can convert this to practically any format
> > that is out there (PDF, TeX, ASCII, ...)
>
>No one will bother to write XML by hand in their code.  Really.
>I mean it.  To take an example from MathML, who on earth is going
>to write
>
>     <apply>
>         <plus/>
>         <mn>x</mn>
>         <mn>y</mn>
>     </apply>
>
>instead of writing x+y?  I count a factor of at least 15.

You picked one of the worst examples there is.

>[...]

Bye,
         Walter D=F6rwald



From manini@ies.it  Wed Jun  7 08:12:47 2000
From: manini@ies.it (Luca Manini)
Date: Wed, 07 Jun 2000 09:12:47 +0200
Subject: [Doc-SIG] Python Docs' Translation
Message-ID: <b0trjs0gc3g5nke37cla4gbnnds2u3leej@4ax.com>

Hi,=20

I've just joined the list, I hope what follows is not off-topic.=20

I'm studing Python in my spare time and I think I can try to translate
some docs from English to Italian, may be starting with the Library
Reference and the very interesting Extending and Embedding stuff.=20

What should I do?

If I understand well, the original source is LaTeX (with some ad-hoc
macros). I'm quite fluent in LaTeX so this would be easy to work with.
The questions are: is there a coordinator for this kind of effort,
where should I get the sources from, where should I put the translated
files?

	Any hint ?
	TIA, Luca.=20




From hfoffani@sofrecom.com.ar  Wed Jun  7 14:06:21 2000
From: hfoffani@sofrecom.com.ar (Hernan Martinez Foffani)
Date: Wed, 7 Jun 2000 10:06:21 -0300
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <b0trjs0gc3g5nke37cla4gbnnds2u3leej@4ax.com>
Message-ID: <001801bfd081$2ccaa5a0$c101010a@pez-volador>

I'd suggest the Tutorial. (If it's not already translated.)
It helps a lot to reach more people.

-Hernan

> -----Original Message-----
> From: doc-sig-admin@python.org [mailto:doc-sig-admin@python.org]On
> Behalf Of Luca Manini
> Sent: Wednesday, June 07, 2000 4:13 AM
> To: doc-sig@python.org
> Subject: [Doc-SIG] Python Docs' Translation
> 
> 
> Hi, 
> 
> I've just joined the list, I hope what follows is not off-topic. 
> 
> I'm studing Python in my spare time and I think I can try to translate
> some docs from English to Italian, may be starting with the Library
> Reference and the very interesting Extending and Embedding stuff. 
> 
> What should I do?
> 
> If I understand well, the original source is LaTeX (with some ad-hoc
> macros). I'm quite fluent in LaTeX so this would be easy to work with.
> The questions are: is there a coordinator for this kind of effort,
> where should I get the sources from, where should I put the translated
> files?
> 
> 	Any hint ?
> 	TIA, Luca. 
> 
> 
> 
> _______________________________________________
> Doc-SIG maillist  -  Doc-SIG@python.org
> http://www.python.org/mailman/listinfo/doc-sig
> 



From gward@mems-exchange.org  Wed Jun  7 14:15:08 2000
From: gward@mems-exchange.org (Greg Ward)
Date: Wed, 7 Jun 2000 09:15:08 -0400
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <001801bfd081$2ccaa5a0$c101010a@pez-volador>; from hfoffani@sofrecom.com.ar on Wed, Jun 07, 2000 at 10:06:21AM -0300
References: <b0trjs0gc3g5nke37cla4gbnnds2u3leej@4ax.com> <001801bfd081$2ccaa5a0$c101010a@pez-volador>
Message-ID: <20000607091508.C5456@ludwig.cnri.reston.va.us>

[Luca]
> I'm studing Python in my spare time and I think I can try to translate
> some docs from English to Italian, may be starting with the Library
> Reference and the very interesting Extending and Embedding stuff. 

[Hernan Martinez Foffani] 
> I'd suggest the Tutorial. (If it's not already translated.)
> It helps a lot to reach more people.

You might also get in touch with Martin von Loewis
<loewis@informatik.hu-berlin.de>: he recently announced an intention to
translate docstrings in the standard library, with the intent that

>>> doc(os.path.isdir)

would give you help in your native tongue.  ('doc()' was a proposed new
built-in that would do a bit more than ".__doc__" -- it would have to
fetch language-specific text, of course).  Obviously this is quite
different technically from translating the manuals, but everyone
interested in translating Python docs should be coordinating!  Probably
the doc-sig is the right place for that.

        Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange / CNRI                           voice: +1-703-262-5376
Reston, Virginia, USA                            fax: +1-703-262-5367


From fdrake@beopen.com  Wed Jun  7 14:22:12 2000
From: fdrake@beopen.com (Fred L. Drake, Jr.)
Date: Wed, 7 Jun 2000 09:22:12 -0400 (EDT)
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <20000607091508.C5456@ludwig.cnri.reston.va.us>
References: <b0trjs0gc3g5nke37cla4gbnnds2u3leej@4ax.com>
 <001801bfd081$2ccaa5a0$c101010a@pez-volador>
 <20000607091508.C5456@ludwig.cnri.reston.va.us>
Message-ID: <14654.19588.760542.122501@cj42289-a.reston1.va.home.com>

Greg Ward writes:
 > would give you help in your native tongue.  ('doc()' was a proposed new
 > built-in that would do a bit more than ".__doc__" -- it would have to
 > fetch language-specific text, of course).  Obviously this is quite

  Gosh, I'm still falling behind!

 > different technically from translating the manuals, but everyone
 > interested in translating Python docs should be coordinating!  Probably
 > the doc-sig is the right place for that.

  Actually, there's a special list for translators; see the top of

	http://www.python.org/doc/NonEnglish.html

for more information.
  As for documentation sources, the best place to look currently is in
the Python CVS repository, in the module "python/dist/src/Doc".
  I *should* be able to catch up a little in a couple of days; I'll
try to answer further questions on this at that time.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member



From fdrake@beopen.com  Wed Jun  7 14:35:06 2000
From: fdrake@beopen.com (Fred L. Drake, Jr.)
Date: Wed, 7 Jun 2000 09:35:06 -0400 (EDT)
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <b0trjs0gc3g5nke37cla4gbnnds2u3leej@4ax.com>
References: <b0trjs0gc3g5nke37cla4gbnnds2u3leej@4ax.com>
Message-ID: <14654.20362.720224.409958@cj42289-a.reston1.va.home.com>

Luca Manini writes:
 > I'm studing Python in my spare time and I think I can try to translate
 > some docs from English to Italian, may be starting with the Library
 > Reference and the very interesting Extending and Embedding stuff. 

  Cool!
  (Please also see my response to Greg Ward's message on this thread.)

 > If I understand well, the original source is LaTeX (with some ad-hoc
 > macros). I'm quite fluent in LaTeX so this would be easy to work with.
 > The questions are: is there a coordinator for this kind of effort,
 > where should I get the sources from, where should I put the translated
 > files?

  The sources are indeed in LaTeX, and we intend to convert them to
SGML or XML later this year.  The markup largely consists of the LaTeX
sectioning and list-like environments and some inline markups, and a
large amount of specialized markup (the "ad-hoc" markup you mention).
The Python-specific markup is mostly documented in "Documenting
Python", available at:

         http://www.python.org/doc/currect/doc/doc.html

  I should have more time to answer questions in a couple of days, and
will be glad to do so.  Thanks for your interest in helping out with
the documentation efforts!


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member



From pf@artcom-gmbh.de  Wed Jun  7 14:34:04 2000
From: pf@artcom-gmbh.de (Peter Funk)
Date: Wed, 7 Jun 2000 15:34:04 +0200 (MEST)
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <20000607091508.C5456@ludwig.cnri.reston.va.us> from Greg Ward at "Jun 7, 2000  9:15: 8 am"
Message-ID: <m12zfy8-000DifC@artcom0.artcom-gmbh.de>

Hi!

> [Luca]
> > I'm studing Python in my spare time and I think I can try to translate
> > some docs from English to Italian, may be starting with the Library
> > Reference and the very interesting Extending and Embedding stuff. 
> 
> [Hernan Martinez Foffani] 
> > I'd suggest the Tutorial. (If it's not already translated.)
> > It helps a lot to reach more people.
> 
[Greg Ward]
> You might also get in touch with Martin von Loewis
> <loewis@informatik.hu-berlin.de>: he recently announced an intention to
> translate docstrings in the standard library, with the intent that
[...]
> , but everyone
> interested in translating Python docs should be coordinating!  Probably
> the doc-sig is the right place for that.

I think the i18n-sig is a better place.  Currently there are not that many
people bothering about i18n, so the traffic on that list is very low.

Regards, Peter


From pf@artcom-gmbh.de  Wed Jun  7 14:41:48 2000
From: pf@artcom-gmbh.de (Peter Funk)
Date: Wed, 7 Jun 2000 15:41:48 +0200 (MEST)
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <14654.19588.760542.122501@cj42289-a.reston1.va.home.com> from "Fred L. Drake, Jr." at "Jun 7, 2000  9:22:12 am"
Message-ID: <m12zg5c-000DifC@artcom0.artcom-gmbh.de>

Hi Fred,

>   Actually, there's a special list for translators; see the top of
> 
> 	http://www.python.org/doc/NonEnglish.html

Uopppsss!  I wasn't really aware of this list, although my netscape
believes that I've already visited this page sometime in the past.  :-(

Is there any reason, why this list resides on egroups at
	<http://www.egroups.com/list/python_doc_translation/info.html>
and is not a normal mailman list on www.python.org?

Regards, Peter


From fdrake@beopen.com  Wed Jun  7 14:49:35 2000
From: fdrake@beopen.com (Fred L. Drake, Jr.)
Date: Wed, 7 Jun 2000 09:49:35 -0400 (EDT)
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <m12zg5c-000DifC@artcom0.artcom-gmbh.de>
References: <14654.19588.760542.122501@cj42289-a.reston1.va.home.com>
 <m12zg5c-000DifC@artcom0.artcom-gmbh.de>
Message-ID: <14654.21231.592093.250595@cj42289-a.reston1.va.home.com>

Peter Funk writes:
 > Is there any reason, why this list resides on egroups at
 > 	<http://www.egroups.com/list/python_doc_translation/info.html>
 > and is not a normal mailman list on www.python.org?

  It was set up and is administered outside the python.org crew; I'm
sure someone mentioned it when it was created, but I only learned
about it more recently, at which point I added the link from
python.org.
  If the list owners would like to move it to python.org, I'm sure
we'll be able to accomodate them, but there may be some timing
delays.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member



From olivier.berger@idealx.com  Wed Jun  7 14:49:27 2000
From: olivier.berger@idealx.com (Olivier Berger)
Date: Wed, 07 Jun 2000 15:49:27 +0200
Subject: [Doc-SIG] Python Docs' Translation
References: <b0trjs0gc3g5nke37cla4gbnnds2u3leej@4ax.com>
 <001801bfd081$2ccaa5a0$c101010a@pez-volador>
 <20000607091508.C5456@ludwig.cnri.reston.va.us> <14654.19588.760542.122501@cj42289-a.reston1.va.home.com>
Message-ID: <393E52E7.2C958413@idealx.com>

"Fred L. Drake, Jr." a écrit :
> 
>  > different technically from translating the manuals, but everyone
>  > interested in translating Python docs should be coordinating!  Probably
>  > the doc-sig is the right place for that.
> 
>   Actually, there's a special list for translators; see the top of
> 
>         http://www.python.org/doc/NonEnglish.html
> 
> for more information.

Well, the project is not really alive but the list still exists
http://club.voila.fr/do/info/python_doc_translation

Note that it used to be hosted at egroups and has been transfered top
club-voila recently after conflict between those two organisations.

Anyway, any volunteer to help organize the project is welcome...

>   -Fred
> 
> --
> Fred L. Drake, Jr.  <fdrake at beopen.com>
> BeOpen PythonLabs Team Member

-- 
Olivier BERGER                          IDEALX S.A.S.
Développeur senior                      15-17, av. de Ségur
01.44.42.00.00                          F-75007 PARIS
06.81.27.86.79                          http://IDEALX.com/


From pf@artcom-gmbh.de  Wed Jun  7 15:09:59 2000
From: pf@artcom-gmbh.de (Peter Funk)
Date: Wed, 7 Jun 2000 16:09:59 +0200 (MEST)
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <14654.21231.592093.250595@cj42289-a.reston1.va.home.com> from "Fred L. Drake, Jr." at "Jun 7, 2000  9:49:35 am"
Message-ID: <m12zgWt-000DifC@artcom0.artcom-gmbh.de>

[me]:
>  > Is there any reason, why this list resides on egroups at
>  > 	<http://www.egroups.com/list/python_doc_translation/info.html>
>  > and is not a normal mailman list on www.python.org?

[Fred L. Drake, Jr.]:
>   It was set up and is administered outside the python.org crew; I'm
> sure someone mentioned it when it was created, but I only learned
> about it more recently, at which point I added the link from
> python.org.

ah...  I see, that's why I missed it.

>   If the list owners would like to move it to python.org, I'm sure
> we'll be able to accomodate them, but there may be some timing
> delays.

I just had short look at the lists archive at egroups:  There was absolutely
no traffic this year other than a single message of today by Oliver Berger,
that the list has now been moved to 
	<http://club.voila.fr/do/info/python_doc_translation>
This is page is in french, and as far as I can see, there is no
web accessable archive available.

Regards, Peter


From olivier.berger@idealx.com  Wed Jun  7 15:15:12 2000
From: olivier.berger@idealx.com (Olivier Berger)
Date: Wed, 07 Jun 2000 16:15:12 +0200
Subject: [Doc-SIG] Python Docs' Translation
References: <14654.19588.760542.122501@cj42289-a.reston1.va.home.com>
 <m12zg5c-000DifC@artcom0.artcom-gmbh.de> <14654.21231.592093.250595@cj42289-a.reston1.va.home.com>
Message-ID: <393E58F0.5981D0A5@idealx.com>

"Fred L. Drake, Jr." a écrit :
> 
> Peter Funk writes:
>  > Is there any reason, why this list resides on egroups at
>  >      <http://www.egroups.com/list/python_doc_translation/info.html>
>  > and is not a normal mailman list on www.python.org?
> 
>   It was set up and is administered outside the python.org crew; I'm
> sure someone mentioned it when it was created, but I only learned
> about it more recently, at which point I added the link from
> python.org.
>   If the list owners would like to move it to python.org, I'm sure
> we'll be able to accomodate them, but there may be some timing
> delays.
> 

I wouldn't be against that... but I doubt it is necessary, considering
that people seem to be *really* quiet on the list...

But if someone volunteers to start it again...

>   -Fred
> 
> --
> Fred L. Drake, Jr.  <fdrake at beopen.com>
> BeOpen PythonLabs Team Member
> 

-- 
Olivier BERGER                          IDEALX S.A.S.
Développeur senior                      15-17, av. de Ségur
01.44.42.00.00                          F-75007 PARIS
06.81.27.86.79                          http://IDEALX.com/


From fdrake@beopen.com  Wed Jun  7 15:21:40 2000
From: fdrake@beopen.com (Fred L. Drake, Jr.)
Date: Wed, 7 Jun 2000 10:21:40 -0400 (EDT)
Subject: [Doc-SIG] Python Docs' Translation
In-Reply-To: <m12zgWt-000DifC@artcom0.artcom-gmbh.de>
References: <14654.21231.592093.250595@cj42289-a.reston1.va.home.com>
 <m12zgWt-000DifC@artcom0.artcom-gmbh.de>
Message-ID: <14654.23156.26278.625131@cj42289-a.reston1.va.home.com>

Peter Funk writes:
 > I just had short look at the lists archive at egroups:  There was absolutely
 > no traffic this year other than a single message of today by Oliver Berger,
 > that the list has now been moved to 
 > 	<http://club.voila.fr/do/info/python_doc_translation>
 > This is page is in french, and as far as I can see, there is no
 > web accessable archive available.

Olivier,
  Has the list been active since the move?  Is there an accessible
archive?  (Or even a privately saved archive that could be made
available?)
  It sounds like moving the list to python.org or python.net might be
a good idea, if only to make sure the archives remain available.
Would the community of translators like to pursue this?


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member



From olivier.berger@idealx.com  Wed Jun  7 17:06:42 2000
From: olivier.berger@idealx.com (Olivier Berger)
Date: Wed, 07 Jun 2000 18:06:42 +0200
Subject: [Doc-SIG] Python Docs' Translation
References: <14654.21231.592093.250595@cj42289-a.reston1.va.home.com>
 <m12zgWt-000DifC@artcom0.artcom-gmbh.de> <14654.23156.26278.625131@cj42289-a.reston1.va.home.com>
Message-ID: <393E7312.8FFD6E4@idealx.com>

"Fred L. Drake, Jr." a écrit :
> 
> Peter Funk writes:
>  > I just had short look at the lists archive at egroups:  There was absolutely
>  > no traffic this year other than a single message of today by Oliver Berger,
>  > that the list has now been moved to
>  >      <http://club.voila.fr/do/info/python_doc_translation>
>  > This is page is in french, and as far as I can see, there is no
>  > web accessable archive available.
> 
> Olivier,
>   Has the list been active since the move?  Is there an accessible
> archive?  (Or even a privately saved archive that could be made
> available?)

The old archive is at
http://www.egroups.com/messages/python_doc_translation/ ... and most
messages are pretty old :(

The new one is at http://club.voila.fr/do/info/python_doc_translation
and there appears to be no message yet :((

>   It sounds like moving the list to python.org or python.net might be
> a good idea, if only to make sure the archives remain available.
> Would the community of translators like to pursue this?
> 

That's ok for me... maybe I can give you the list of subscribers if you
need it (or maybe starting again a new list of people could boost
interest ?).

>   -Fred
> 
> --
> Fred L. Drake, Jr.  <fdrake at beopen.com>
> BeOpen PythonLabs Team Member

-- 
Olivier BERGER                          IDEALX S.A.S.
Développeur senior                      15-17, av. de Ségur
01.44.42.00.00                          F-75007 PARIS
06.81.27.86.79                          http://IDEALX.com/


From laurie@eh.org  Sat Jun 10 17:43:06 2000
From: laurie@eh.org (Laurence Tratt)
Date: Sat, 10 Jun 2000 16:43:06 GMT
Subject: [Doc-SIG] Crystal 0.3
Message-ID: <57348dcc49.laurie@btinternet.com>

Sorry for the wait, but after a long typing injury and with generous
assistance Crystal 0.3 is available from:

  http://eh.org/~laurie/comp/python/crystal/

This version contains a command line interface, better HTML output and a few
bug fixes. Because of its difficult period of gestation, YMMV.

For those not in the know, Crystal is a pythondoc/javadoc type system.


Laurie
-- 
http://eh.org/~laurie/comp/python/


From gherman@darwin.in-berlin.de  Mon Jun 26 09:45:14 2000
From: gherman@darwin.in-berlin.de (Dinu C. Gherman)
Date: Mon, 26 Jun 2000 10:45:14 +0200
Subject: [Doc-SIG] Python tutorial changes for 1.6?
Message-ID: <3957181A.2A796FEF@darwin.in-berlin.de>

Hello,

on the following page:

  http://www.python.org/doc/current/download.html

I can read the this note:

  Note: The LaTeX sources are not being distributed as 
  a package for this release since the documentation 
  sources are being merged with the development version 
  of the documentation in preparation for the Python 
  1.6 release.

saying that the LaTeX files are currently not available. 

Could anybody provide some brief background information 
trying to outline what is expected to change apart from
the pure content, i.e. LaTeX/format-unspecific material,
especially for the Tutorial?

I'm asking because I'd like to provide as soon as possi-
ble an update of my German translation of Guido's 1.5.2 
tutorial. And I might get somebody working on a more exo-
tic translation of that tutorial, too, but would like to 
know if one can start confidently with 1.5.2 or should 
wait for the final 1.6 tutorial?

Regards,

Dinu

-- 
Dinu C. Gherman
................................................................
"The only possible values [for quality] are 'excellent' and 'in-
sanely excellent', depending on whether lives are at stake or 
not. Otherwise you don't enjoy your work, you don't work well, 
and the project goes down the drain." 
                    (Kent Beck, "Extreme Programming Explained")


From fdrake@beopen.com  Wed Jun 28 12:16:53 2000
From: fdrake@beopen.com (Fred L. Drake, Jr.)
Date: Wed, 28 Jun 2000 07:16:53 -0400 (EDT)
Subject: [Doc-SIG] back up & running
Message-ID: <14681.56997.50955.892954@cj42289-a.reston1.va.home.com>

  My mega-laptop got fixed faster than I'd expected, so I'm back up to
doing useful work.  My top priorities are handling patches and going
back through my email to find all the documentation patches that have
sat idle for too long.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member



From fdrake@beopen.com  Wed Jun 28 12:16:53 2000
From: fdrake@beopen.com (Fred L. Drake, Jr.)
Date: Wed, 28 Jun 2000 07:16:53 -0400 (EDT)
Subject: [Doc-SIG] [Python-Dev] back up & running
Message-ID: <14681.56997.50955.892954@cj42289-a.reston1.va.home.com>

  My mega-laptop got fixed faster than I'd expected, so I'm back up to
doing useful work.  My top priorities are handling patches and going
back through my email to find all the documentation patches that have
sat idle for too long.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member


_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://www.python.org/mailman/listinfo/python-dev