Would it be possible to make a README viewer and writer in SimPE?

I was thinking that it would be nice if a readme containing licensing info of the creator, special thanks, or just general notes could be imbedded in package files. Possibly there could be a reader/editor plugin that looks at the Text List files for one named "SIMPE - README" or something like that and read the lines out of the text list into the reader/editor.

I know this can be done in a way with TEXT Lists already, but you would have to edit it line by line in the Text List plugin which is a little cumbersome for the style of writing and reading needed for a README file.

I have also posted a similar suggestion on the PJSE board for inline BHAV comments using Text Lists to carry the information. 

This was already discussed some time ago and dismissed.

To include new (text) information into a new resource in package files would technically be possible, but would render them nonstandard, so problems could arise.

There are - however - text lists that allow multiple lines. Prepare your text in a text editor and copy'n'paste it into one of those.

I understood about the Text Lists (even mentioned using them instead of a custom file type). What the readme editor would do is simply utilize the Text Lists as you are suggesting, but format what it reads out them in a less separated fashion. For example... each "line" (which can actually have multiple lines) in the text lists might represent a paragraph in the editor/reader. No file formats would have to be messed with. The only thing that the plugin would look for is a specific filename and it would only read files with that particular filename. All other would be assumed to be Text Lists used by the mod.

If this has already been discussed and dismissed then I apologize for bringing it up again I just hoped I could bring a new idea to the table. 

As Xanathon said, we discussed this almost at the beginning. The Problem was, if we introduce a custom Textresource in the packages, and Maxis at some point decides to use that same TGI for something else in a package it would reult in a corrupted package.

That said, I thinnk since Sims 2 is in it's final stages, we might be able to risk something like it. What dou you think? 

Is it really worth the work?  You can have quite long strings in the catalogue description, and if I want my users to know anything important about the object, I use that field.  Then they can see it on their screen every time they choose to use the object.