<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>comp.lang.postscript Google Group</title>
  <link>http://groups.google.com/group/comp.lang.postscript</link>
  <description>The PostScript Page Description Language.</description>
  <language>en</language>
  <item>
  <title>Re: Throwing a custom error</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/56997f5d76b1f300?show_docid=56997f5d76b1f300</link>
  <description>
  Hi Ken, &lt;br&gt; &lt;p&gt;Thanks for the information. After continuing my experiments I have concluded that I do not require a non-zero exit code, so I&#39;m not requesting the GS be modified to act in a non-standard way. &lt;br&gt; &lt;p&gt;For anybody who is interested my approach, BWIPP has been modified to include a raiseerror procedure (&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://goo.gl/SjoSZ&quot;&gt;[link]&lt;/a&gt;) that is invoked from the code to generate custom errors with names such as bwipp.someErrorName.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/56997f5d76b1f300?show_docid=56997f5d76b1f300</guid>
  <author>
  terry.bur...@gmail.com
  (Terry Burton)
  </author>
  <pubDate>Tue, 21 May 2013 14:01:08 UT
</pubDate>
  </item>
  <item>
  <title>Re: Throwing a custom error</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/0d511b21dfa10134?show_docid=0d511b21dfa10134</link>
  <description>
  In article &amp;lt;e4d4fc8b-af38-46db-a95e-86a88 9a0b9d1@googlegroups.com&amp;gt;, &lt;br&gt; terry.bur...@gmail.com says... &lt;br&gt; &lt;p&gt;Essentially, you can&#39;t. By processing the error you prevent the &lt;br&gt; interpreter from &#39;seeing&#39; it. So as far as the interpreter is &lt;br&gt; concerened, there is no error. &lt;br&gt; &lt;p&gt;Technically this is correct, the input was fully processed in accordance
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/0d511b21dfa10134?show_docid=0d511b21dfa10134</guid>
  <author>
  k...@spamcop.net
  (ken)
  </author>
  <pubDate>Mon, 20 May 2013 06:52:19 UT
</pubDate>
  </item>
  <item>
  <title>Re: Throwing a custom error</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/81f4661613904b28?show_docid=81f4661613904b28</link>
  <description>
  [...] &lt;br&gt; &lt;p&gt;Hopefully the ghostscript gurus will have something better, &lt;br&gt; but it might work to just use /undefined, but pack information into the undefined name itself. I know that sentence is terrible. How about an example? &lt;br&gt; &lt;p&gt; ... &lt;br&gt; dup type /integertype ne { &lt;br&gt; MUST_PASS_integer_TO_THIS_FUNC TION
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/81f4661613904b28?show_docid=81f4661613904b28</guid>
  <author>
  mijo...@yahoo.com
  (luser- -droog)
  </author>
  <pubDate>Mon, 20 May 2013 05:04:37 UT
</pubDate>
  </item>
  <item>
  <title>Throwing a custom error</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/bc7d6054c1566ecc?show_docid=bc7d6054c1566ecc</link>
  <description>
  Hi, &lt;br&gt; &lt;p&gt;In Barcode Writer in Pure PostScript (BWIPP) it is possible for the user to provide invalid input data. At present we do not provide any useful form of input validation or error reporting and we simply allow the code to trip up and bomb out in meaningless ways on invalid data. &lt;br&gt; &lt;p&gt;To provide a somewhat uniform approach to handling invalid user input I am investigating whether the PS code could raise a custom error and terminate for each circumstance (e.g. /bwipp.badCheckDigit or /bwipp.invalidCharacter, etc) that can be communicated to the user using whatever ordinary PS error handling is available in that environment.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/abc82555abd52e89/bc7d6054c1566ecc?show_docid=bc7d6054c1566ecc</guid>
  <author>
  terry.bur...@gmail.com
  (Terry Burton)
  </author>
  <pubDate>Sun, 19 May 2013 02:44:25 UT
</pubDate>
  </item>
  <item>
  <title>Re: xpost3 current challenges</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/33a0cd834c55ba59?show_docid=33a0cd834c55ba59</link>
  <description>
  ---^ should&#39;ve indented this one. There&#39;s 3 tables, but 4 &#39;variables&#39;. &lt;br&gt; &lt;p&gt;This is going to involve a bit of redesign of contexts and mfiles, as well as a cool name for the master super-duper data structure that in the darkness binds them. &lt;br&gt; &lt;p&gt;But I think I&#39;ll keep itp.c pretty much as-is, and the testing main() will for now be the entry-point to the single-process interpreter. The &amp;quot;ghostscript&amp;quot;-mode, if you will. The multiprocessing stuff really needs to be a new module. So it needs a module-name, too. Going by my pattern so far, it should be a 3-letter identifier. &amp;quot;srv&amp;quot; maybe, or ... not coming up with anything else. &amp;quot;srv&amp;quot; it is!
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/33a0cd834c55ba59?show_docid=33a0cd834c55ba59</guid>
  <author>
  mijo...@yahoo.com
  (luser- -droog)
  </author>
  <pubDate>Mon, 13 May 2013 04:49:17 UT
</pubDate>
  </item>
  <item>
  <title>Re: xpost3 current challenges</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/4f7a77abad3d4b0e?show_docid=4f7a77abad3d4b0e</link>
  <description>
  On further investigation, DPS and NeWS are quite different in their precise semantics. And DPS seems simpler, so I&#39;ll start there. &lt;br&gt; &lt;p&gt;DPS describes 3 ways of creating a new context: &lt;br&gt; &lt;p&gt;Method 1: Private Global VM, Private Local VM &lt;br&gt; &lt;p&gt;Method 2: Shared Global VM, Private Local VM &lt;br&gt; &lt;p&gt;Method 3: Shared Global VM, Share Local VM
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/4f7a77abad3d4b0e?show_docid=4f7a77abad3d4b0e</guid>
  <author>
  mijo...@yahoo.com
  (luser- -droog)
  </author>
  <pubDate>Sat, 11 May 2013 05:53:31 UT
</pubDate>
  </item>
  <item>
  <title>Re: xpost3 current challenges</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/4016072419f4660c?show_docid=4016072419f4660c</link>
  <description>
  And NeWS implements processtype objects as magic dictionaries. So maybe that&#39;s what I should be working on. Should be pretty straightforward. dicget and dicput need to recognize a special value (object type) that refers to a getter/setter struct, something like &lt;br&gt; &lt;p&gt;struct gsetter { &lt;br&gt; object (*get)(void);
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/4016072419f4660c?show_docid=4016072419f4660c</guid>
  <author>
  mijo...@yahoo.com
  (luser- -droog)
  </author>
  <pubDate>Mon, 06 May 2013 04:39:36 UT
</pubDate>
  </item>
  <item>
  <title>xpost3 current challenges</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/40241c7ce6584fae?show_docid=40241c7ce6584fae</link>
  <description>
  I&#39;ve got 2 trains going at the same time here, and kinda stalled on both. &lt;br&gt; &lt;p&gt;Track 1 is finishing up this postscript translation of the xpost2 scanner. It&#39;s running into issues with building procedures. And I&#39;ve really painted myself into a corner with lots of code and virtually no comments. I suppose the obvious next step is to print it out and re-type it (fixing the uglies as they arise).
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/b21b1ce7a8519f22/40241c7ce6584fae?show_docid=40241c7ce6584fae</guid>
  <author>
  mijo...@yahoo.com
  (luser- -droog)
  </author>
  <pubDate>Sun, 05 May 2013 04:59:02 UT
</pubDate>
  </item>
  <item>
  <title>Re: PS-viewing Browser plugin for Windows?</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/e2b5cf7456d13c1a?show_docid=e2b5cf7456d13c1a</link>
  <description>
  OK. Some web pages link to .ps files as well as to .jpg, .png, .pdf (etc.) &lt;br&gt; ones -- browsers have no trouble displaying .jpg and .pdf links -- they&#39;re &lt;br&gt; inherently capable of that -- and very little trouble with .pdf links -- &lt;br&gt; there are browser add-ons (by Adobe and by others) to deal with those --
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/e2b5cf7456d13c1a?show_docid=e2b5cf7456d13c1a</guid>
  <author>
  mpiosucb.etlll...@att.net
  (tlvp)
  </author>
  <pubDate>Fri, 03 May 2013 04:28:36 UT
</pubDate>
  </item>
  <item>
  <title>Re: PS-viewing Browser plugin for Windows?</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/dabf649ad5d3656f?show_docid=dabf649ad5d3656f</link>
  <description>
  Thanks, Luuk. Not what I thought I was after -- it&#39;s an online .ps viewer, &lt;br&gt; not a browser add-on or snap-in -- but it looks interesting all the same, &lt;br&gt; and could be a good alternative choice. Cheers, -- tlvp &lt;br&gt; -- &lt;br&gt; Avant de repondre, jeter la poubelle, SVP.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/dabf649ad5d3656f?show_docid=dabf649ad5d3656f</guid>
  <author>
  mpiosucb.etlll...@att.net
  (tlvp)
  </author>
  <pubDate>Fri, 03 May 2013 04:18:09 UT
</pubDate>
  </item>
  <item>
  <title>Re: PS-viewing Browser plugin for Windows?</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/0621eba51273edde?show_docid=0621eba51273edde</link>
  <description>
  Googleing revealed this page: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://view.samurajdata.se/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;p&gt;•The viewer software is open source, licensed under the GNU Public License. &lt;br&gt; •Version 0.3 of the software can be downloaded .....
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/0621eba51273edde?show_docid=0621eba51273edde</guid>
  <author>
  l...@invalid.lan
  (Luuk)
  </author>
  <pubDate>Thu, 02 May 2013 18:57:16 UT
</pubDate>
  </item>
  <item>
  <title>Re: PS-viewing Browser plugin for Windows?</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/80deab3d6b6592bc?show_docid=80deab3d6b6592bc</link>
  <description>
  Am Mittwoch, 1. Mai 2013 22:42:03 UTC+2 schrieb tlvp: &lt;br&gt; &lt;p&gt;More info about what the actual usage scenario looks like would be interesting. I.e., is it necessary to interpret PS on the client side or can it be done on the server? Why PS instead of PDF? &lt;br&gt; &lt;p&gt;PostScript uploaded to Google drive can be viewed in the browser.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/80deab3d6b6592bc?show_docid=80deab3d6b6592bc</guid>
  <author>
  zupf...@googlemail.com
  </author>
  <pubDate>Thu, 02 May 2013 11:23:38 UT
</pubDate>
  </item>
  <item>
  <title>Re: PS-viewing Browser plugin for Windows?</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/3d154df4e2d6965d?show_docid=3d154df4e2d6965d</link>
  <description>
  If you&#39;re gonna suggest spawning ghostscript, why not spawn ghostview &lt;br&gt; instead, and spare me converting to pdf and starting the Adobe plug-in? &lt;br&gt; The cs.wisc folks really not do that yet? But thanks; and cheers, -- tlvp &lt;br&gt; -- &lt;br&gt; Avant de repondre, jeter la poubelle, SVP.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/3d154df4e2d6965d?show_docid=3d154df4e2d6965d</guid>
  <author>
  mpiosucb.etlll...@att.net
  (tlvp)
  </author>
  <pubDate>Thu, 02 May 2013 03:21:31 UT
</pubDate>
  </item>
  <item>
  <title>Re: PS-viewing Browser plugin for Windows?</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/c521aab991fa8215?show_docid=c521aab991fa8215</link>
  <description>
  This is a write-your-own project. Convert to .pdf by spawning ghostscript, &lt;br&gt; then view the .pdf. Recent Firefox has a builtin .pdf viewer. &lt;br&gt; &lt;p&gt;--
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/c521aab991fa8215?show_docid=c521aab991fa8215</guid>
  <author>
  jreise...@comcast.net
  (John Reiser)
  </author>
  <pubDate>Thu, 02 May 2013 00:04:35 UT
</pubDate>
  </item>
  <item>
  <title>PS-viewing Browser plugin for Windows?</title>
  <link>http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/3f1aed917a6a53b3?show_docid=3f1aed917a6a53b3</link>
  <description>
  Subject line pretty much says it all: I&#39;m seeking a browser plugin (for FF, &lt;br&gt; or Safari or Opera or IE 7-8-9, under Windows (XP, Vista, 7)) to render .ps &lt;br&gt; files. Google, alas, steers me only to Linux or MacOS .ps browser services, &lt;br&gt; not Windows ones. &lt;br&gt; &lt;p&gt;Thanks for all pointers, even dead ends :-) . Cheers, -- tlvp
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.lang.postscript/browse_thread/thread/9f269e468e8135f3/3f1aed917a6a53b3?show_docid=3f1aed917a6a53b3</guid>
  <author>
  mpiosucb.etlll...@att.net
  (tlvp)
  </author>
  <pubDate>Wed, 01 May 2013 20:42:03 UT
</pubDate>
  </item>
  </channel>
</rss>
