numpy-discussion

[Numpy-discussion] draft numarray manual available

[Perry G. <pe...@st...>]

We have begun adapting the Numeric manual for numarray. An early 
draft of such a manual (in PDF format) is available from the
numarray home page: http://stsdas.stsci.edu/numarray

Comments and corrections are welcome. Over the next few months
we will be adding chapters on how to interface C code to numarray
as well as how to use non-numeric arrays.

Perry Greenfield

[Numpy-discussion] Re: draft numarray manual available

[Jochen <jo...@un...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 27 Feb 2002 10:22:48 -0500 Perry Greenfield wrote:

Perry> We have begun adapting the Numeric manual for numarray. An
Perry> early draft of such a manual (in PDF format) is available from
Perry> the numarray home page: http://stsdas.stsci.edu/numarray

Would it be possible to use the python doc format?  That would allow
to create the nice HTML as Python has and dvi/ps/pdf as well as info.

I am willing to help with the transition.  What is the current
original format?

Greetings,
Jochen
- -- 
University of North Carolina                       phone: +1-919-962-4403
Department of Chemistry                            phone: +1-919-962-1579
Venable Hall CB#3290 (Kenan C148)                    fax: +1-919-843-6041
Chapel Hill, NC 27599, USA                            GnuPG key: 44BCCD8E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6-cygwin-fcn-1 (Cygwin)
Comment: Processed by Mailcrypt and GnuPG <http://www.gnupg.org/>

iD8DBQE8fQAaiJ/aUUS8zY4RAro0AJ0UQoyvvHHwgjJ+4tJXmwWyx18jRQCfY6v/
1BBZoSU5KrzZ+4toNcYt7hk=
=IOF2
-----END PGP SIGNATURE-----

RE: [Numpy-discussion] Re: draft numarray manual available

[Perry G. <pe...@st...>]

Hi Jochen,

Indeed, we are considering converting the format at some time
to the Python doc format (it would be a requirement in order to
get it into the standard library).

If you would do that it would be a great help (presuming
you can access the current format...other than retyping it!)
It is currently in Framemaker format (that's what the original
Numeric manual was in).

I was just beginning to mull over how best to convert formats.
There is a Framemaker Interchange Format (SGML-based) that might
be the easiest way to deal with it. Or perhaps the brute force
method of converting it to ascii and adding Python doc markup
would be the fastest. Any other ideas?

Thanks, Perry Greenfield

Re: [Numpy-discussion] Re: draft numarray manual available

[Janko <jh...@co...>]

On Wed, 27 Feb 2002 11:05:59 -0500
"Perry Greenfield" <pe...@st...> wrote:

> Hi Jochen,
> 
> Indeed, we are considering converting the format at some time
> to the Python doc format (it would be a requirement in order to
> get it into the standard library).
> 
> If you would do that it would be a great help (presuming
> you can access the current format...other than retyping it!)
> It is currently in Framemaker format (that's what the original
> Numeric manual was in).
> 
> I was just beginning to mull over how best to convert formats.
> There is a Framemaker Interchange Format (SGML-based) that might
> be the easiest way to deal with it. Or perhaps the brute force
> method of converting it to ascii and adding Python doc markup
> would be the fastest. Any other ideas?
> 
I have done exactly this, there are tools like pdf2text or so, which do help with this.

Jochen I'm doing the same effort for the scipy docs at the moment, the first step is nearly done. So if you want to collaborate send me a note privatly.

__Janko

Re: [Numpy-discussion] draft numarray manual available

[Jochen <jo...@un...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 27 Feb 2002 11:05:59 -0500 Perry Greenfield wrote:

Perry> If you would do that it would be a great help (presuming you
Perry> can access the current format...other than retyping it!)  It is
Perry> currently in Framemaker format (that's what the original
Perry> Numeric manual was in).

Framemake, huh:) Never used that...  It shouldn't be too bad to put
the raw ASCII into python-style LaTeX.  But if you can create SGML one
could try to use sgml2tex or similar to preserve the basic formatting.

I am a little busy right now and will be out of town next week, but
propose to do the work to get the doc converted after that
(mid-March). If you could send me the sgml I could try out whether it
actually helps or we have to go the raw-ASCII route.

Greetings,
Jochen
- -- 
University of North Carolina                       phone: +1-919-962-4403
Department of Chemistry                            phone: +1-919-962-1579
Venable Hall CB#3290 (Kenan C148)                    fax: +1-919-843-6041
Chapel Hill, NC 27599, USA                            GnuPG key: 44BCCD8E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6-cygwin-fcn-1 (Cygwin)
Comment: Processed by Mailcrypt and GnuPG <http://www.gnupg.org/>

iD8DBQE8fRIDiJ/aUUS8zY4RAhh+AJ9ZP0H4szek5W13makOEVSQnKYhngCglzzU
T1zJa2gKx6uYn4VCnOXlsJQ=
=AzS3
-----END PGP SIGNATURE-----

RE: [Numpy-discussion] draft numarray manual available

[Perry G. <pe...@st...>]

> Perry> If you would do that it would be a great help (presuming you
> Perry> can access the current format...other than retyping it!)  It is
> Perry> currently in Framemaker format (that's what the original
> Perry> Numeric manual was in).
> 
> Framemake, huh:) Never used that...  It shouldn't be too bad to put
> the raw ASCII into python-style LaTeX.  But if you can create SGML one
> could try to use sgml2tex or similar to preserve the basic formatting.
> 
> I am a little busy right now and will be out of town next week, but
> propose to do the work to get the doc converted after that
> (mid-March). If you could send me the sgml I could try out whether it
> actually helps or we have to go the raw-ASCII route.
> 
> Greetings,
> Jochen
> 
That would be great. I'd check with Janko to see if either his tools or
experience could be used to make it easier. But I'll send you the MIF
format (and perhaps some documentation on what it means).

Thanks, Perry