Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.postscript > #2744 > unrolled thread

DSC level 1: For comment

Started byvincent.torri@gmail.com
First post2016-08-09 12:51 -0700
Last post2016-08-11 11:45 -0700
Articles 3 — 2 participants

Back to article view | Back to comp.lang.postscript


Contents

  DSC level 1: For comment vincent.torri@gmail.com - 2016-08-09 12:51 -0700
    Re: DSC level 1: For comment Martin Leese <please@see.Web.for.e-mail.INVALID> - 2016-08-10 11:08 -0600
      Re: DSC level 1: For comment vincent.torri@gmail.com - 2016-08-11 11:45 -0700

#2744 — DSC level 1: For comment

Fromvincent.torri@gmail.com
Date2016-08-09 12:51 -0700
SubjectDSC level 1: For comment
Message-ID<d8a6b940-5a86-4ad4-802f-0a279fdad375@googlegroups.com>
Hello

DSC level 1 says that "if there is no For comment, the intended recipient is assumed to be the same as the value of Creator".

But I see no such remark in DSC 2.1 or 3.0 for the For comment. When parsing the postscript file, should I set the For comment to the value of Creator only for level 1 if For is not present? Or should I just leave it unset ?

thank you

Vincent Torri

[toc] | [next] | [standalone]


#2746

FromMartin Leese <please@see.Web.for.e-mail.INVALID>
Date2016-08-10 11:08 -0600
Message-ID<nofn2b$4mi$1@dont-email.me>
In reply to#2744
vincent.torri@gmail.com wrote:
> Hello
> 
> DSC level 1 says that "if there is no For comment, the intended recipient is assumed to be the same as the value of Creator".
> 
> But I see no such remark in DSC 2.1 or 3.0 for the For comment. When parsing the postscript file, should I set the For comment to the value of Creator only for level 1 if For is not present? Or should I just leave it unset ?

It depends *why* you are parsing the
PostScript document.

The %%For: comment can be used for a banner
page or for document routing.  If your
purpose is something similar then, for DSC
Level 1, set %%For: equal to %%Creator::.
At higher DSC levels, %%Creator: is usually
the name of the document composition
software; this is not much use for a
banner or for routing, so the %%For: comment
should be left unset.

If your purpose is simply to check
compliance with a DSC specification then
there is no point in setting anything;
either the PostScript document complies or
it does not.

-- 
Regards,
Martin Leese
E-mail: please@see.Web.for.e-mail.INVALID
Web: http://members.tripod.com/martin_leese/

[toc] | [prev] | [next] | [standalone]


#2751

Fromvincent.torri@gmail.com
Date2016-08-11 11:45 -0700
Message-ID<63c9c3c0-f74a-4fca-b230-0d6ff1cbc5ac@googlegroups.com>
In reply to#2746
Hello

Le mercredi 10 août 2016 20:08:30 UTC+3, Martin Leese a écrit :
> vincent.torri@gmail.com wrote:
> > Hello
> > 
> > DSC level 1 says that "if there is no For comment, the intended recipient is assumed to be the same as the value of Creator".
> > 
> > But I see no such remark in DSC 2.1 or 3.0 for the For comment. When parsing the postscript file, should I set the For comment to the value of Creator only for level 1 if For is not present? Or should I just leave it unset ?
> 
> It depends *why* you are parsing the
> PostScript document.

Actually for both parsing the document to retrieve values of the DSC and validating he DSC. But indeed i have forgotten to say that it was specifically for geting values of the DSC comments

> The %%For: comment can be used for a banner
> page or for document routing.  If your
> purpose is something similar then, for DSC
> Level 1, set %%For: equal to %%Creator::.
> At higher DSC levels, %%Creator: is usually
> the name of the document composition
> software; this is not much use for a
> banner or for routing, so the %%For: comment
> should be left unset.

that was the answer I wanted.

> If your purpose is simply to check
> compliance with a DSC specification then
> there is no point in setting anything;
> either the PostScript document complies or
> it does not.

indeed.

Thank you

Vincent Torri

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.postscript


csiph-web