Alan J. Salmoni wrote:
> I heartily agree. pdf format has never been much of a problem for me.
> Now that you have an ISSN, has it been submitted to Google Scholar or
> other academic indexes?
>
> http://scholar.google.com/intl/en/scholar/about.html for Google Scholar
> http://citeseer.ist.psu.edu
I heartily agree. pdf format has never been much of a problem for me.
Now that you have an ISSN, has it been submitted to Google Scholar or
other academic indexes?
http://scholar.google.com/intl/en/scholar/about.html for Google Scholar
http://citeseer.ist.psu.edu/submitDocument.html for Citeseer
"Noah Slater" <[EMAIL PROTECTED]> writes:
> I do not think this thread is an embarrassment to the community. I
> think it speaks volumes about people's commitment to free software.
>
> While we can applaud such contributions it is no excuse to waiver on
> one's ethics and principles.
Yes, this wa
I do not think this thread is an embarrassment to the community. I
think it speaks volumes about people's commitment to free software.
While we can applaud such contributions it is no excuse to waiver on
one's ethics and principles.
Regardless of content, or even format, if the Python Papers are
Fredrik Lundh:
> Tennessee Leeuwenburg wrote:
>
>
>> If anyone has any good ideas for how to cope as a publisher with these
>> difficulties, I'm all ears.
>>
>
> has any of the format zealots posting to this thread actually
> volunteered to produce any material for your publication? if no
On Sat, 25 Nov 2006 08:13:58 -0800, Noah Slater wrote:
>
> On Nov 22, 12:41 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>> Thanks for the comments. PDF is, to some extent, a requirement. To
>> preserve the entire journal as a single "entity" with a reasonably high
>> production quality,
Noah Slater wrote:
> Which is more important to the Python comunity...
the community definitely don't need more random usenet posters who's
only contribution is to complain whenever someone tries to do some-
thing. this thread is an embarrassment for the Python community; you
should all be ash
On Nov 22, 12:41 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Thanks for the comments. PDF is, to some extent, a requirement. To
> preserve the entire journal as a single "entity" with a reasonably high
> production quality, there seems to be no way around it. I could not
> find a sufficie
Jerry Hill wrote:
> > MontyLingua is GPL software and thus has its own licensing issues for
> > commercial software.
MontyLingua might appear to be GPL-licensed, but then the author puts
some kind of non-commercial clause on top, either thinking that's what
the GPL is all about (out of confusion,
Paul Rubin wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> > Your email indicates a possible concern that we are doing something
> > untoward -- this was not at all intended, nor is it true.
>
> Although you might not have intended it, I feel it is still true. You
> are misappropriatin
Maurice LING wrote:
[snip..]
> As Steven mentioned -- anything you can read is copyrighted. The
> difference is whether is the copyright effective or enforceable. What do
> I mean by this? Without copyright, there will not be plagarism. Ask
> yourself this question, can you copy William Shakespear
Fredrik Lundh wrote:
> Tennessee Leeuwenburg wrote:
>
> > If anyone has any good ideas for how to cope as a publisher with these
> > difficulties, I'm all ears.
>
> has any of the format zealots posting to this thread actually
> volunteered to produce any material for your publication? if not, I
On 11/25/06, Steven D'Aprano <[EMAIL PROTECTED]> wrote:
> And how do you think this is different from any other publication? That
> Python Papers is under a CC licence is a red-herring.
Well, the CC license is viral. According to the CC explanation of the
Attribution-NonCommercial-ShareAlike lice
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> I thought I just had. In what way does the statement "Yes, it's true
> that you can't resell copies of The Python Papers for personal profits,
> but you may derive from it, reproduce and propagate it" not provide
> such a revision and clarification?
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Your email indicates a possible concern that we are doing something
> untoward -- this was not at all intended, nor is it true.
Although you might not have intended it, I feel it is still true. You
are misappropriating terminology ("free as in fre
Tennessee Leeuwenburg wrote:
> If anyone has any good ideas for how to cope as a publisher with these
> difficulties, I'm all ears.
has any of the format zealots posting to this thread actually
volunteered to produce any material for your publication? if not, I
suggest ignoring them. any bozo
Maurice LING wrote:
> As Steven mentioned -- anything you can read is copyrighted. The
> difference is whether is the copyright effective or enforceable. What do
> I mean by this? Without copyright, there will not be plagarism. Ask
> yourself this question, can you copy William Shakespeare's Mac
Jerry Hill wrote:
> On 11/25/06, Jerry Hill <[EMAIL PROTECTED]> wrote:
>
>> On 23 Nov 2006 15:09:11 -0800, [EMAIL PROTECTED]
>> <[EMAIL PROTECTED]> wrote:
>> > Yes, it's true that you can't resell copies of The Python Papers for
>> > personal profits, but you may derive from it, reproduce and prop
On Sat, 25 Nov 2006 00:27:24 -0500, Jerry Hill wrote:
> On 11/25/06, Jerry Hill <[EMAIL PROTECTED]> wrote:
>> On 23 Nov 2006 15:09:11 -0800, [EMAIL PROTECTED]
>> <[EMAIL PROTECTED]> wrote:
>> > Yes, it's true that you can't resell copies of The Python Papers for
>> > personal profits, but you may
On 11/25/06, Jerry Hill <[EMAIL PROTECTED]> wrote:
> On 23 Nov 2006 15:09:11 -0800, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > Yes, it's true that you can't resell copies of The Python Papers for
> > personal profits, but you may derive from it, reproduce and propagate
> > it. You're quite
Shane Hathaway wrote:
> Just avoid the term "free as in freedom", since the Free
> Software Foundation has assigned that phrase a very specific meaning.
Bah. FSF is not an arbiter of the language. People whose idea of
"free" differs from FSF's still need to differentiate it from the
monetary sen
Shane Hathaway wrote:
>
> IMHO your licensing terms are fine; you don't need to switch from the CC
> license. Just avoid the term "free as in freedom", since the Free
> Software Foundation has assigned that phrase a very specific meaning.
Agreed. It should also be noted that Debian - amongst the
[EMAIL PROTECTED] wrote:
> Ben Finney wrote:
>> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>>
>>> Yes, it's true that you can't resell copies of The Python Papers for
>>> personal profits, but you may derive from it, reproduce and
>>> propagate it. You're quite right to point it out.
>> Then p
kilnhead wrote:
> I for one like the pdf format. Nothing irks me more than help files in
> multipage HTML. I want a document I can easily download and save.
> Thanks for your efforts.
>
>
> [EMAIL PROTECTED] wrote:
>> Greetings all,
>>
>> Some of you may have noticed the launch of the Python Jour
> I thought I just had. In what way does the statement "Yes, it's true
> that you can't resell copies of The Python Papers for personal profits,
> but you may derive from it, reproduce and propagate it" not provide
> such a revision and clarification? Seriously, let me know what exact
> statement
Ben Finney wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>
> > Yes, it's true that you can't resell copies of The Python Papers for
> > personal profits, but you may derive from it, reproduce and
> > propagate it. You're quite right to point it out.
>
> Then please revise the false stat
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Yes, it's true that you can't resell copies of The Python Papers for
> personal profits, but you may derive from it, reproduce and
> propagate it. You're quite right to point it out.
Then please revise the false statement that the publication is "
Klaas wrote:
> Tennessee writes:
> >* If you say LaTex, I'll eat your brain. Or my hat. Unless I'm
> > seriously underrating it, but I don't think so.
>
> Why? It is a suitable solution to this problem. You can produce
> unformatted content, then produce pdf and html pages from it.
Sure, LaT
Perhaps people could comment on the following proposition -- if an
organisation is Not for Profit, its dealings are therefore
Noncommercial?
I think the problem is Python has historically been so very free-- It has
always been *extremely* Business-Friendly, and totally lacks ... ah, the
moral o
Yes, it's true that you can't resell copies of The Python Papers for
personal profits, but you may derive from it, reproduce and propagate
it. You're quite right to point it out.
Licenses are too complicated. I don't believe a license exists which
meets the demands of all clients, however should I
Tennessee writes:
>* If you say LaTex, I'll eat your brain. Or my hat. Unless I'm
> seriously underrating it, but I don't think so.
Why? It is a suitable solution to this problem. You can produce
unformatted content, then produce pdf and html pages from it.
-Mike
--
http://mail.python.org
[EMAIL PROTECTED] wrote:
> 1.) It takes too many clicks to download.
> A) We know, but it's like that to save our server. We will be
> publishing to a number of online archives, back-issues may be
> back-linkable from those.
Please consider using S3, coral cache, or similar to distribute, if the
I for one like the pdf format. Nothing irks me more than help files in
multipage HTML. I want a document I can easily download and save.
Thanks for your efforts.
[EMAIL PROTECTED] wrote:
> Greetings all,
>
> Some of you may have noticed the launch of the Python Journal a while
> back. Due to arti
I've recently tried the docutils's reST module with Pygments ( to
highlight Python sources), so you can have LaTeX + HTML + PDF output
(You can see what it renders here :
h**p://kib2.free.fr/geoPyX/geoPyX.html ). It worked fine, but needs a
little work to suit your needs (you'll have to write your
On 11/23/06, Stephen Hansen <[EMAIL PROTECTED]> wrote:
>
>
>
> > 3.) Can I have an HTML version?
> > A) No, we like it pretty.
>
>
> The interesting thing is, there's nothing in your layout or format that you
> can't do with some nice standards-compliant HTML and CSS. It could look
> identical as
3.) Can I have an HTML version?
A) No, we like it pretty.
The interesting thing is, there's nothing in your layout or format that you
can't do with some nice standards-compliant HTML and CSS. It could look
identical as HTML-- and be significantly more "reachable" by people, easier
for them to u
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Some of you may have noticed the launch of the Python Journal a while
> back. Due to artistic differences, the journal has now been re-launched
> as The Python Papers. It is available under a Creative Commons License,
> something we felt was appropr
The adobe people have online conversion
http://www.adobe.com/products/acrobat/access_onlinetools.html
google seems to convert them when they end up in the engines
http://www.google.com/search?hl=en&q=pdf+to+html
has a list of converters
http://www.dexrow.com
[EMAIL PROTECTED] wrote:
> Tell u
Tell us about it again when it is available as html. We will be glad to
read it. I am sorry but I almost never find a pdf worth the bother of
clicking on it.
Sorry
--
http://mail.python.org/mailman/listinfo/python-list
39 matches
Mail list logo
