Application command line (PDF)

I'm trying to launch another PDF-report by using application command line. I manage to create the report in to file but is there a way to launch it automatically "on the top" of the first report or on it's own window?
This is what I have now on the application command line:
C:\OraDS\bin\rwrun.exe c:\kkk\test userid=aki/aki@db destype=file desname=c:\temp\test.pdf desformat=pdf

The way that I'd approach this would be to run the report through a URL to the reports server rather than a direct call to rwrun.
In your command line you're telling reports to run the report to file (which it's doing correctly). If you run it via a URL then the reports server should stream the output back to the browser window, where it'll be read by Acrobat.
Hope this helps,
Danny

Similar Messages

Making bat file in Window Mobile - Oracle application command line

I have Windows mobile 6.I have installed Cre-ME+, & command line.In the command line we need to type below command & execute to load oracle Mobile Application.
Command is : \Windows\CrEme\bin\CrEme.exe -Of -classpath \Windows\CrEme\lib\AWTclasses.zip;\XONTMWA\lib\j4205328.zip oracle.apps.mwa.awt.client.StartGUI
This is working fine.
But proble is making bat/cmd file to excute this application, without type each & everytime.
I know that window mobile won't support bat/cmd file extension. But there may be any other ways.
Please tell me how can i create the bat/cmd file in windows mobile 6.
Please anybody help me out from this issue.
I am looking forward your reply.
Thanks in advance.
Regards;
Piraba
Edited by: user10702520 on Jan 6, 2012 5:06 AM

We use a third party application (AppCenter) on our Motorola devices. It's a lock down tool that can present only specific application to the user, and can auto-launch the command line (<filename.lnk> in our scenario).
-Vince

Adobe Reader 9.4.2 SIGSEGV in command-line PDF- PS conversion

NOTE: This issue was originally reported Oct. 5, 2010, against Reader 9.4.0: http://forums.adobe.com/message/3186827
The following should emit PostScript on stdout:
     acroread -toPostScript < PDF_FILE
Try doing this with Adobe Reader 9.4.2, and all you'll see is
     Segmentation fault
Adobe Reader 9.3.4 works just fine doing such PDF->PostScript conversions.
John

Forgot to mention: this is occurs on both 32-bit and 64-bit RHEL5 Linux hosts at our site.
Tail end of an strace for this issue:
24100 munmap(0xf702f000, 4096)          = 0
24100 stat64("/u/j/o/john/.adobe", {st_mode=S_IFDIR|0700, st_size=2048, ...}) = 0
24100 stat64("/u/j/o/john/.adobe/Acrobat", {st_mode=S_IFDIR|0750, st_size=2048, ...}) = 0
24100 stat64("/u/j/o/john/.adobe/Acrobat/9.0", {st_mode=S_IFDIR|0750, st_size=2048, ...}) = 0
24100 stat64("/u/j/o/john/.adobe/Acrobat/9.0/Temp", {st_mode=S_IFDIR|0750, st_size=2048, ...}) = 0
24100 open("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq", O_RDWR|O_CREAT|O_EXCL, 0600) = 4
24100 close(4)                          = 0
24100 unlink("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq") = 0
24100 open("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq", O_RDWR|O_CREAT|O_TRUNC, 0666) = 4
24100 getcwd("/tmp/acrotest"..., 1024) = 14
24100 open("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq", O_RDONLY) = 5
24100 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
24100 +++ killed by SIGSEGV +++
John

Adobe Reader 9.4.0 SIGSEGV in command-line PDF- PS conversion

The following should emit PostScript on stdout:
     acroread -toPostScript < PDF_FILE
Try doing this with Adobe Reader 9.4.0, and all you'll see is
     Segmentation fault
Adobe Reader 9.3.4 works just fine doing such PDF->PostScript conversions. Will it be another 3 months before this is fixed?
John

Forgot to mention: this is occurs on both 32-bit and 64-bit RHEL5 Linux hosts at our site.
Tail end of an strace for this issue:
24100 munmap(0xf702f000, 4096)          = 0
24100 stat64("/u/j/o/john/.adobe", {st_mode=S_IFDIR|0700, st_size=2048, ...}) = 0
24100 stat64("/u/j/o/john/.adobe/Acrobat", {st_mode=S_IFDIR|0750, st_size=2048, ...}) = 0
24100 stat64("/u/j/o/john/.adobe/Acrobat/9.0", {st_mode=S_IFDIR|0750, st_size=2048, ...}) = 0
24100 stat64("/u/j/o/john/.adobe/Acrobat/9.0/Temp", {st_mode=S_IFDIR|0750, st_size=2048, ...}) = 0
24100 open("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq", O_RDWR|O_CREAT|O_EXCL, 0600) = 4
24100 close(4)                          = 0
24100 unlink("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq") = 0
24100 open("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq", O_RDWR|O_CREAT|O_TRUNC, 0666) = 4
24100 getcwd("/tmp/acrotest"..., 1024) = 14
24100 open("/u/j/o/john/.adobe/Acrobat/9.0/Temp/AdobeTempPShUseaq", O_RDONLY) = 5
24100 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
24100 +++ killed by SIGSEGV +++
John

Simple command line pdf creation

I need to create a pdf that is simply combining graphic files in a directory.
Using VBScript I would like to be able to provide the output pdf name as well as all files to be included. I have looked but could not find an easy solution. I also could not find example code.
I am not opposed to writting C# code to create a program to do this but there must be something out there that does this already. I have Acrobat available but again no simple solution to provide the output name and input files.
Lou

Would it still be possible to use a powershell script that will open the document. would look like:
".\acrobat.exe /A "page=1=OpenActions" "location/of/pdf.pdf"
and then call an encapsulted javascript to add a premade security policy on the opened pdf? Am i just hoping for to much??
Would i be able to accomplish something similiar by using the SDK??

Remote Application Command-Line Support Is Broken In New iOS Client!!!

Folks here went around and around with Microsoft trying to get them to implement support for the "remoteapplicationcmdline:s:" RDP file setting in all of the Microsoft Remote Desktop clients. Finally, sometime around version 8.0.5 Microsoft
successfully implemented the setting (in the Mac, iOS, and Android clients). It worked flawlessly in version 8.0.6, 8.0.7, and 8.0.8, but now Microsoft has once again broken support for the setting with their latest iOS Remote Desktop client (starting with
version 8.1.0 and going forward all the way up to the current version 8.1.4 release). It's always one step forward, and two steps backwards with Microsoft. Oy!
Hey Microsoft can you please re-implement support for the "remoteapplicationcmdline:s:" setting in the new iOS client??? PRETTY PLEASE!!!

Hi,
Thanks for your feedback, i will forward your concern to the product group.
Regards.
Dharmesh Solanki
TechNet Community Support

Parsing in Weblogic/jsp doesn't work; application-mode (command-line) works

Hello-
Parsing my XML file in Weblogic/jsp doesn't work, whereas it works
in application-mode... (albeit on two different machines)
Here are the parameters:
server1:
weblogic 6.0
win2k server
jre1.3
my personal machine:
***no weblogic***
win2k server
jre1.3
When I run my code as an application (command-line style) on my machine,
parsing in my xml file works fine, and I can do a root.toString() and it
dumps out the entire xml file, as desired.
However, running my code inside weblogic (on server1) in JSP, parsing in
my file and doing a root.toString() results in the following: [dmui: null]
(where dmui is my root)
(even though i'm running it on two different machines, i'm positive its the
same code (the servers share a mapped drive)...
So, I think its probably because I'm using a different parser, as
specified by weblogic? There are no exceptions being thrown. Here's my
(abbreviated) code, which is called either command line style or in a JSP:
// Imports
import org.w3c.dom.*;
import org.w3c.dom.Document;
import javax.xml.parsers.*;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
DocumentBuilderFactory docBuilderFactory =
DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
mDocument = docBuilder.parse (inFile);
myRoot.toString()
-END
Doing a System.getProperty("javax.xml.parsers.DocumentBuilderFactory")
results in:
server1 (weblogic/jsp):
"weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
my machine (application-mode):
null
Does anyone have any ideas about how to get this work? Do I try to set it
up so that they both use the same parser? Do I change the Weblogic parser?
If so, to what? And how?
Am I even close?
Any help would be appreciated..
Thanks, Clint
"[email protected]" <[email protected]> wrote in message
news:[email protected]...
No problem, glad you got it worked out :)
~Ryan U.
Jennifer wrote in message <[email protected]>...
I completely missed setting the property(:-o), foolish mistake. That wasit. Thanks.
"j.upton" <[email protected]> wrote:
Jennifer,
Personally I would get rid of import com.sun.xml.parser.* and use xerces
which comes with WLS 6.0 now, unless like I said earlier you have a need
to
use the sun parser :) Try something like this with your code --I've put
things to watch for as comments in the code.
import javax.xml.parsers.*;
import org.xml.sax.SAXException;
import org.w3c.dom.*;
import java.io.FileInputStream;
public class BasicDOM {
public BasicDOM (String xmlFile) {
try{
FileInputStream inStream;
Document document;
/*You must specify a parser for jaxp. You can in a simple view
think
of this as being analogous to a driver used by JDBC or JNDI. If you are
using this in the context of a servlet or JSP and have set an XML
registry
with the console this happens automatically. You can also invoke it in
the
context of an application on the command line using the -D switch. */
System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
>>>
"weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
// create a document factory
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
// specify validating or non-validating parser
dbf.setValidating(true);
// obtain a factory
DocumentBuilder db = dbf.newDocumentBuilder();
// create a document from the factory
inStream = new FileInputStream(xmlFile);
document = db.parse(inStream);
}//try
catch (Exception e)
System.out.println("Unexpected exception reading document!"
+e);
System.exit (0);
}//catch
}//BasicDom
// Main Method
public static void main (String[] args) {
if (args.length < 1)
System.exit(1); file://or you can be more verbose
new BasicDOM(args[0]);
}//class
=============================================
That will give you a basic DOM you can manipulate and parse it fromthere.
BTW this code
compiled and ran on WLS 6.0 under Windows 2000.
Let me know if this helped or you still are having trouble.
~Ryan U.
"Jennifer" <[email protected]> wrote in message
news:[email protected]...
Actually I included com.sun.xml.parser.* as one last febble attempt toget
it working.
And as for source code, I included the code. If I just put that oneline
of code
in, including the imports, it fails giving me an error listed above inthe
subject
line. Here is the code again:
package examples.xml.http;
import javax.xml.parsers.*;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.w3c.dom.*;
import java.util.*;
import java.net.*;
import org.xml.sax.*;
import java.io.*;
public class BasicDOM {
static Document document;
public BasicDOM (String xmlFile) {
try {
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
} catch (FactoryConfigurationError e){
System.err.println(e.getException());
e.printStackTrace();
// Main Method
public static void main (String[] args) {
BasicDOM basicDOM = new BasicDOM (args[0]);

Hi, Rob
Does it work in WL9.2?
It seems I do it exactly as the explained at http://edocs.bea.com/wls/docs81/programming/classloading.html - and it fails :o(.
I try to run my app.ear with WL9.2 There are 2 components in it: webapp and mdb. The webapp/WEB-INF contains weblogic.xml:
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
Mdb is expected to run in the same mode, i.e. to prefer the webapp/WEB-INF/*.jar over the parent Weblogic classloader. To do so I add the weblogic-application.xml to the app.ear!/META-INF:
<weblogic-application>
<classloader-structure>
<module-ref>

<module-uri>webapp</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>mdb.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
Now, when classloader-structure specified, both webabb and mdb prefer the weblogic root loader as if prefer-web-inf-classes not defined at all.

MDT 2013 - Concatenate command lines in an application?

Total noob to MDT. Have a few years experience with SCCM. My ongoing project is to create bootable media (DVD's only, no USB allowed...) to rebuild seats not attached to our network.
I know one can concatenate command lines in SCCM task sequence steps... wondering if I can do so in applications too?
Example:
Create application BlahBlah
Dir structure is:
\BlahBlah
\BlahBlah\A
\BlahBlah\B
The application will point to \BlahBlah as the source dir
In the application command line, will this command work?
"xcopy .\A\*.* c:\temp\BlahBlahA /E /Y & xcopy .\B\*.* c:\temp\BlahBlahB /E /Y"
TIA,
Lang

It depends on what your working directory is set to
But I'd recommend using a script to handle installing applications, copying files, etc. You can then do far more advanced functions with the ability to log as well.
For instance here's a script I wrote to install Firefox and copy over configuration files. It's one script that handles both x86 and x64 architectures.
<job id="Install-MozillaFirefox">
<script language="VBScript" src="..\..\scripts\ZTIUtility.vbs"/>
<script language="VBScript">
'// Purpose: Used to install Flash Player
'// Usage: cscript Install-MozillaFirefox.wsf [/debug:true]
'// Version: 1.0 - September 29, 2014
'// Version: 1.1 - February 6, 2015 - Corrected architecture detection
'// Global constant and variable declarations
Option Explicit
Dim iRetVal
'// End declarations
'// Main routine
On Error Resume Next
iRetVal = ZTIProcess
ProcessResults iRetVal
On Error Goto 0
'// Function: ZTIProcess()
'// Input: None
'// Return: Success - 0
'// Failure - non-zero
'// Purpose: Perform main ZTI processing
Function ZTIProcess()
oLogging.CreateEntry "Install-MozillaFirefox: Starting Mozilla Firefox installation", LogTypeInfo
' Disable Zone Checks
oEnv("SEE_MASK_NOZONECHECKS") = 1
' Install Mozilla Firefox
iRetVal = oUtility.RunWithHeartbeat(oUtility.ScriptDir & "\Installer\Setup.exe -ms")
if (iRetVal = 0) or (iRetVal = 3010) then
ZTIProcess = Success
Else
ZTIProcess = Failure
oLogging.CreateEntry "Install-MozillaFirefox: Error installing Application Plugin. Check the log " & oUtility.LocalRootPath & "\SMSOSD\OSDLOGS\Install-MozillaFirefox-Plugin-App.log", LogTypeWarning
End If
' Configure Mozilla Firefox
If oEnvironment.Item("Architecture") = "X86" then
oLogging.CreateEntry oUtility.ScriptName & ": Configuring for 32bit OS", LogTypeInfo
oFSO.CopyFile oUtility.ScriptDir & "\Installer\override.ini", oENV("ProgramFiles") & "\Mozilla Firefox\", True
oFSO.CopyFile oUtility.ScriptDir & "\Installer\mozilla.cfg", oENV("ProgramFiles") & "\Mozilla Firefox\", True
oFSO.CopyFile oUtility.ScriptDir & "\Installer\local-settings.js", oENV("ProgramFiles") & "\Mozilla Firefox\Defaults\Pref\", True
Else
oLogging.CreateEntry oUtility.ScriptName & ": Configuring for 64bit OS", LogTypeInfo
oFSO.CopyFile oUtility.ScriptDir & "\Installer\override.ini", oENV("ProgramFiles(x86)") & "\Mozilla Firefox\", True
oFSO.CopyFile oUtility.ScriptDir & "\Installer\mozilla.cfg", oENV("ProgramFiles(x86)") & "\Mozilla Firefox\", True
oFSO.CopyFile oUtility.ScriptDir & "\Installer\local-settings.js", oENV("ProgramFiles(x86)") & "\Mozilla Firefox\Defaults\Pref\", True
End If
' Enable Zone Checks
oEnv.Remove("SEE_MASK_NOZONECHECKS")
oLogging.CreateEntry "Install-MozillaFirefox: Return code from command = " & iRetVal, LogTypeInfo
oLogging.CreateEntry "Install-MozillaFirefox: Finished Mozilla Firefox installation", LogTypeInfo
End Function
</script>
</job>
You can then use variables. Your code to copy files could be something like
oFSO.CopyFile oUtility.ScriptDir & "\A\*.*", oENV("SystemDrive") & "\temp\BlahBlahA", True
oFSO.CopyFile oUtility.ScriptDir & "\B\*.*", oENV("SystemDrive") & "\temp\BlahBlahB", True
If this post is helpful please vote it as Helpful or click Mark for answer.

File name as command line option for multiple VM processes

"-Xloggc:/tmp/gc.log" is the option I'd like to set, but every process will log to that file and even if we don't experience any concurrency issues the data still isn't useful because I can't tell which process did what.
The island files are cleverly named to include their process number, can I do similar for command line options or will I be restricted to a single JVM?

Online help (as of LabVIEW 7.0?), Index, Command Line, User-defined arguments - It will show you the following:
You also can pass LabVIEW-defined or user-defined arguments when you launch LabVIEW from the command line. To pass user-defined arguments in the command line, enter two hyphens (--) surrounded by spaces before the set of user-defined arguments. LabVIEW does not use any arguments after the two hyphens to launch labview.exe. LabVIEW passes the arguments after the two hyphens to the block diagram of the VI you launch. Use the Application:Command Line Arguments property to read the user-defined command-line arguments passed when LabVIEW launches.
For example, to launch mycool.vi and pass user-defined arguments, use the following command:
c:\labview\la
bview.exe c:\coolapp\mycool.vi -- 1000 sine
On the block diagram of the mycool.vi, use the Application:Command Line Arguments property to read the 1000 and sine arguments you passed and handle the values.
Enjoy,
Roy

Labview is using stale command line arguments

I've created a vi to test passing command line arguments to Labview. I've attached it below. All it does is display the 1st and 2nd arguments. Also in VI Properties in the Execution category, it's set to 'Run when opened'.
In the command prompt I'm entering: "C:\Program Files (x86)\National Instruments\LabVIEW 2014\LabVIEW.exe" "C:\Users\command_line_arguments.vi" -- a b
This works - the vi launches, and displays a and b. However, if I run it again from the command prompt with -- a c as the arguments, it still displays a b. Only if I exit the vi, and quit LabVIEW (so that LabVIEW.exe stops running) then launch it again from the command line does it display a c.
So for some reason Application:Command Line Arguments is using stale data, and ignoring the new arguments. Is this a bug, or am I using it in the wrong way? Thanks.
Attachments:
command_line_arguments.vi ‏8 KB

lv_manchester wrote:
So for some reason Application:Command Line Arguments is using stale data, and ignoring the new arguments. Is this a bug, or am I using it in the wrong way? Thanks.
That's normal behavior, the command line arguments are always the ones with which LabVIEW was first started. I think most single-instance applications work this way, although it's not something I've ever tested. Attempting to run LabVIEW again will just bring the already-running application to the front.

How to run labview exe with command line

I would like to launch a labview exe with a command line.
I would like to get advice how to launch the Labview exe with giving values to the control parameters?
You can view the example where x,y are the controls
Solved!
Go to Solution.
Attachments:
exe.png ‏65 KB

There is a much more detailed guide here, which I reference below:
1. First you will enable it in the settings:
1. Open the properties for the application's build specification
2. Navigate to the Advanced category
3. Check the Pass all command line arguments to application box
To pass the command line arguments to the application and access them in your code follow the same steps as for LabVIEW 7.x.
2. Then you will use two hypens (--) to pass command line arguments to the VI.
When you launch LabVIEW or a stand-alone executable from the command line, you can pass user-defined arguments to the application. User-defined arguments start after two hyphens (– –) surrounded by spaces in the command line. For example, the following command line entry will launch LabVIEW 7.1 and open test.vi from the root of C:\ and pass 2 arguments, 1000 and sine:
"C:\Program Files\National Instruments\LabVIEW 7.1\LabVIEW.exe" "C:\test.vi" –– 1000 sine
You can also pass a command line argument directly to an EXE without launching LabVIEW, as long as the machine has the appropriate Run-Time Engine and necessary drivers. For example, if test.vi was built into an executable, it could be called as follows:
"<build directory>\test.exe" –– 1000 sine
3. Lastly, you will use a property node to wire them to your controls:
LabVIEW passes the arguments from the command line to the block diagram of the VI or EXE you launch. You can reference the arguments in the block diagram by using the Application:Command Line Arguments selection in a property node, as shown below.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!

Launched from a windows command line

If my labview app is run remotely from a windows command line, is there any way to tell programmatically from a variable somewhere that it was launched by another app and not by the operator manually launching the app itself ?

Hello id,
If you have control over the application that's invoking your exe through the command line, I'd suggest using a simple custom argument that is passed to the application per this KnowledgeBase:
KnowledgeBase 1CNFGHFI: Passing Command Line Arguments to a LabVIEW Executable
http://digital.ni.com/public.nsf/allkb/17C3AD70493CE0208625666A00763364
You would then use the App.Args property (Application:Command Line Arguments Property) to check for your "this launched from the command line via this other application" argument, whatever it might be. I would suggest that you should only need to check for *any* arguments, if they're present then you know it's been launched via the command line. The argument could just be the name of the calling application. If you're unable to insert arguments via the invoking application, you could also use a one-line batch file that's installed with the target EXE to do the same thing (you'd run the batch file instead of the executable from the invoking application).
Determining where an application was invoked from without sending it that information explicitly is another, trickier problem- there are plenty of discussions on stackexchange and elsewhere detailing possible solutions, but if the invoked application (your EXE) isn't owned by the command prompt process I'm not sure it's possible. There are a few mentions of checking environment variables that the command prompt usually sets to see if they've been configured, but I have no experience with this.
Best Regards,
Tom L.

We are trying to implement a process so that any document that needs to be printed through our Java application will be printed as PDF using Adobe Reader. For which, We created and execute the below command line to call Adobe Reader and print the PDF on a

We are trying to implement a process so that any document that needs to be printed through our Java application will be printed as PDF using Adobe Reader. For which, We created and execute the below command line to call Adobe Reader and print the PDF on a printer."C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe" /T "\\<Application Server>\Report\<TEST.PDF>" "<Printer Name>". Current Situation: The above command line parameter when executed is working as expected in a User's Workspace. When executed in a command line on the Application Server is working as expected. But, the same is not working while executing it from Deployed environment.Software being used: 1. Adobe 11.0 enterprise version. 2. Webshpere Application Server 8.5.5.2. Please let us know if there is a way to enable trace logs in Adobe Reader to further diagnose this issue.

This is the Acrobat.com forum. Your question will have a much better chance being addressed in the Acrobat SDK forum.

How do I open a PDF to a specific page via the command line?

Several questions about opening PDFs from the Mac OS X command line:
1) How do I use the "open" command to open a PDF to a specific page? (I know I can open a document via: open doc_name.pdf)
2) How do I use the "open" command to pass multiple arguments (page no, zoom scale, view mode, etc...) to open a PDF file in a specific manner?
3) Does Preview handle the same parameters as Acrobat Reader? If not, what are the differences in options?
I've spent hours searching for this answer and have come up dry. I've downloaded Adobe's "PDF Open Parameters" document -- it lists all of the parameters I need, however I can't get any of them to work from the command line.
My goal: Open a PDF from the command line to a specific page. At first glance, I thought this would be simple to do and find -- however, after a lot of searching I haven't found an example on how to do it.
Anyone have any experience doing this, and care to share?
Much appreciated! ---> Kelsey

I don't know of any way to do what you want using the 'open' command. It can probably be done with Applescript, which you could call from a shell script. The Preview application doesn't seem to be scriptable. I don't use Acrobat, so I can't tell you anything about that. Looking through the dictionaries of the apps I do have, it seems that Skim (another PDF viewer) has an AS 'page' class. Below are a couple of links that may get you started. Look for more specific guidance in Applescript forums.
http://sourceforge.net/apps/mediawiki/skim-app/index.php?title=AppleScript
http://links.tedpavlic.com/shell_scripts/skim

Apply Quartz filter to a PDF from command line

Hello
I'm trying to apply a quartz filter to a PDF document via the command line. I know it's possible with Python and there's a script at /Developer/Examples/Quartz/Python/filter-pdf.py that does just that. The problem with this is that the script is Python 2.3 and my OS X 10.5.8 is running Python 2.5 - so I'm getting the error message:
+<Error>: The function `CGPDFDocumentGetMediaBox' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance. Please use `CGPDFPageGetBoxRect' instead.+
I don't know Pyton but I checked the file and I grep'ed the Developer folder to see if I can find where CGPDFDocumentGetMediaBox is being used, but no matter what I changed, I didn't manage to get the script working.
So I guess my question is one of the following:
How can I update the developer example to a new, functioning version?
or how do I get rid of the deprecated functions that script is using?
or is there any other way to apply a quartz filter to a PDF via the command line? (I've read that SIPS is able to accomplish this, but I couldn't find out how..)
Thank you for any help!
Cheers

There a quartz filter printer hidden in OS X which makes applying a quartz filter to a PDF file on the command line a piece of cake. This is the syntax:
+/System/Library/Printers/Libraries/./quartzfilter inputfile filterpath outputfile+
So if I wanted to convert big.pdf to small.pdf it would go like this:$
+/System/Library/Printers/Libraries/quartzfilter big.pdf /System/Library/Filters/Reduce\ File\ Size.qfilter small.pdf+
The "Reduce File Size" filter isn't that great though when it comes to reducing the file size for printing. Jerome Colas wrote a nice article about quartz filters though: http://discussions.apple.com/thread.jspa?messageID=6109445&tstart=0
You can also create your own with the ColorSync utility in Mac OS X. A Quartz filter is nothing but an XML, so you could also generate one on the fly if necessary.
Resource: http://macscripter.net/viewtopic.php?id=25916

Application command line (PDF)

Similar Messages

Maybe you are looking for