Re: The name of the pdfmark mark

[Michael Piotrowski]

Ludovic Courtès <address@hidden> writes:

> @ExternalLink, @FixedWidthRule, etc. can all be used in a Lout document
> regardless of which output backend is being used.  Why would it be
> different for @DocInfo?  If @DocInfo makes sense only in the PS backend,
> then its definition would just include something like:
>
>   @BackEnd @Case {
>     PostScript @Yield { ... }
>     else @Yield @Null
>   }

I agree.  But in addition to that, there may be some backend-specific
things.  For example, in my own extended report setup I have:

    # PDF options
    # Possible values for @PDFInitialPageMode:
    # UseNone, UseOutlines, UseThumbs, FullScreen
    named @PDFInitialPageMode           { UseNone               }
    named @PDFInitialPage               { 1                     }
    named @PDFSubject                   {                       }
    named @PDFKeywords                  {                       }
    named @PDFCreationDate              { UseDateLine           }
    named @PDFModDate                   { UseDateLine           }
    # Predefined values for @PDFInitialView:
    # FitFullPage = /Fit, FitWidth = /FitH 900, NoChange = /XYZ null null null
    named @PDFInitialView               { NoChange }

Now, @PDFSubject, @PDFKeywords, @PDFCreationDate, and @PDFModDate
should really be @DocInfo (or something like that).  However, the
@PDFInitial* symbols--or rather their possible values--are really
PDF-specific.

-- 
Michael Piotrowski, M.A.                               <address@hidden>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt>