taskSavannah Administration - Tasks: task #5859, Submission of PosrScript Generator

 
 

task #5859: Submission of PosrScript Generator

Submitter:  Diedrich Vorberg <diedrich>
Submitted:  Wed 30 Aug 2006 04:40:41 PM UTC
   
 
Should Start On:  Wed 30 Aug 2006 12:00:00 AM UTC Should be Finished on:  Sat 09 Sep 2006 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 22 Sep 2006 05:09:10 AM UTC, comment #7: 

Hello and sorry for my delay. :-(

About the .ps files I got your points.

At first, for your font_utils.ps file, please write a short commend at least where are the source code from and how is the copyright owner (I think you have got these information if it's from the a2ps team).


At second, for your eps.ps file, please remove the "So I guess it's (c) Adobe" sentence.
It's a example of a book, so it is public domain or fair use - no need to investigate this.





I have approved your project.  You will receive an automated e-mail containing detailed information about the approval.

Regards.


Sebastian Wieseler <kickino>
Mon 18 Sep 2006 09:30:35 AM UTC, comment #6: 

Hi Sebastian, it's been nearly a week since I asked about how to handle the procsets from my psg project. I'm still unsure on how to handle this.... -- Diedrich

Diedrich Vorberg <diedrich>
Tue 12 Sep 2006 08:46:49 AM UTC, comment #5: 

Hi,

Your last e-Mail leaves me with a question...

About the font_utils.ps procset: I don't want to put the procsets under a license, because they will be included in PostScript code generated by psg. Putting them under GPL would mean that any document created with psg would need to be under GPL (PostScript documents are programs). This is unacceptable for most if not all users. I believe this is why the GNU (!!) a2ps team has omited licensing information from the a2ps generated PS file. How do I go about this?

Abouit eps.ps: The PostScript Language Manual states that I'm not allowed to reproduce any of its content and makes no exceptions for the examples. Asking Adobe about the rights is pointless: They will give a crap about my request and not even reply. I mean, it's about an example in a programming book. These examples are ment to be used, aren't they? So I would need to re-write the procedure and put it under my own copyright and in the public domain. Yet there are a limited number of ways to do the job the code is supposed to do. How far do I have to modify this thing to legitametly claim copyrights?

Regards
Diedrich

Diedrich Vorberg <diedrich>
Mon 11 Sep 2006 08:04:30 PM UTC, comment #4: 

Hello.

At first, contrib/* lacks copyright+license information.

At second, the file psg/procsets/eps.ps has a vague copyright. If you copied it of a webpage, ask the webmaster for copyright+license information, if you copied it out of a book - name the author and the publisher (I think it is "fair use" then).

At third, in the same directory the file font_utils.ps - this file lacks information about the license. Maybe you should contact the copyright owners about it.



Please provide us with an updated tarball.
Regards,

Sebastian Wieseler <kickino>
Sun 10 Sep 2006 07:30:57 PM UTC, comment #3: 

Hi Sebastian,

>I'm evaluating the project you submitted for approval in Savannah.


>Please include a (perhaps temporary) URL pointing to the source code.
>The description you gave when registering will not be read by the general
>public.

sorry about this. I was wondering how you'd ge the source and then forgot about it. I've ubloaded an archive here:

   http://hs0.tux4web.de/psg-savannah-0.0.tgz

Kind regards
Diedrich

Diedrich Vorberg <diedrich>
Sun 10 Sep 2006 05:32:52 PM UTC, comment #2: 

Hi,

I am waiting for an answer from you.

If within one week I still do not get a reply, I will remove your project.
You will still be able to register it again once you have the time to deal with the registration issues.

Are you still willing to host your project at Savannah?
If not, please tell us - we don't bite, and it will make us gain time.

Regards.

Sebastian Wieseler <kickino>
Sat 02 Sep 2006 05:25:57 PM UTC, comment #1: 

Hi,
I'm evaluating the project you submitted for approval in Savannah.


Please include a (perhaps temporary) URL pointing to the source code.
The description you gave when registering will not be read by the general public.
If you are still concerned with privacy, however, you can forward the code to me by email.

We wish to review your source code, even if it is not functional, to catch potential legal issues early.

For example, to release your program properly under the GPL you must include a copyright notice and
permission-to-copy statements at the beginning of every file of source code.  This is explained in
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch potential omissions such as these.



Regards,

Sebastian Wieseler <kickino>
Wed 30 Aug 2006 04:40:41 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.


REGISTRATION ADMINISTRATION


While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific "Group Administration" page, accessible only to site administrators, effectively logged as site administrators (superuser):

  <https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=8749>


REGISTRATION DETAILS


Full Name:
----------
  PosrScript Generator

System Group Name:
-----------------
  pypsg

Type:
-----
  non-GNU software &amp; documentation

License:
--------
  GNU General Public License V2 or later

Description:
------------
  Psg is a Python module to create PostScript documents which adhere to Adobe's Document Structuring Conventions from scratch or read them from complient PostScript files.

- It lets you create PostScript files by embedding EPS files, bitmaps, fonts and arbitrary subsections from DSC complient input files. This could be used to re-write the psutils package in Python. 
- I do not intend to implement drawing primitives, there are already libraries that do that very well. However, I plan to create an interface between psg and pyscript, a PostScript creation module which focuses on drawing end geometry.
- Text is a different subject, though. A rudimentary layout engine to create connected text boxes is in place and will be extended in the future. I envision a subset of XML/CSS. The text functons support Type1 fonts and dynamically re-encodes them based on unicode(!) input.
- All input/output operation goes through regular Python file objects. (This may seem an odd thing to mention as a  'feature'. But trust me, it's special).
- Though PostScript files are generally constructed in memory, all import operations are 'lazy', that is, input files are analyzed but their content is only copied over to the outfile in the last step of composition to reduce memory footprint.
- Psg contains classes to model a PostScript run time environment (namely Ghostscript). It will contain functionality to use Ghostscript to create PDF files and bitmap previews (my own use is largely www applications), but also to import PDF and those PostScript files that make use of all the DSC's liberties.
- There is no coherent documentation, yet, but the source code is richly and (I hope) usefully documented.

Every kind of feedback is strongly encouraged!

Diedrich Vorberg <diedrich@tux4web.de>


Other Software Required:
------------------------
  Python 2.3.
pyscript is going to be optional.
Ghostscript is supported through some classes, but not needed.


Other Comments:
---------------
  I've tried to follow my other nongnu.org hosted project, orm, in terms of directory and file layout. Hope that's ok...


Diedrich Vorberg <diedrich>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 6 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-09-22 kickino StatusWait reply Done
    Open/ClosedOpen Closed
2006-09-11 kickino StatusPing-ed Wait reply
2006-09-10 kickino StatusWait reply Ping-ed
2006-09-02 kickino StatusNone Wait reply
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-caa5.
Corresponding source code