Internationalization in Acrobat GUI

Hi,
I have a question regarding internationalization in Acrobat GUI. I'm writing a plugin that needs to display a few dialog boxes (currently using AVAlert functions), and will also have something added to the top menu bar. All these things will have to be translated to a few other languages in the near future. So my question is, is there anything in Acrobat SDK to help "translate" the GUI messages? I.e., something that will automatically know the locale, and will generate the right messages specified for that locale. I know InDesign have something like the PMString, and I also found some language resource files with the Acrobat plugins, but is there anything from Acrobat SDK?
Thanks!
William So

You can find the locale used by Acrobat. That's about as much help as
you get.
Aandi Inston

Similar Messages

Acrobat X: SDI vs. MDI

I'd like to coninue this thread, because I believe it's important:
Acrobat and Acrobat Reader are strongly missing the MDI feature.
Probably the biggest share of "common" users will only open a single document at a time. But there are others around that sometimes have more than one single document open and who don't want to get their screen cluttered up with Acrobat documents.
From the thread above there's a Hyperlink to the Acrobat blog, justifying why MDI has been removed from the Acrobat GUI.
I believe the reasons given in there are wrong:
Feature Parity with Macintosh was desired. As stated before, the Mac OS does not have this option. While I will be the first to admit that feature parity is not 100% between Windows and Macintosh, it is a goal that we aim for.
As written at the top of the blog, "MDI is not applicable on the Mac OS." So this is simply a system feature not available to Mac OS but to Windows. Parity in regard to system environment can never be achieved. Otherwise, Acrobat would have to strip keyboard support, because smartphones like the IPhone lack the presence of a keyboard.
Utilizing MDI is quite transparent to the software when being programmed properly. The client area to draw into won't be different. And the Mac OS will simply display like an MDI environment with just one document in it.
In version 8, we made SDI the default in the viewing mode. Making SDI default, but still providing MDI in version 8 was done to start the deprecation of MDI.
This is no reason at all. It's just a description of a decision you made.
Microsoft advised that to work as good as possible on Vista, applications should avoid MDI.
MDI is currently still available in any document centric Microsoft application. And it's available in any current document centric Adobe software - except for Acrobat.
WPF is commonly used as the successor of MDI, yet multiple-document GUIs are fully supported in Windows.
Acrobat and Adobe Reader’s new UI modes would not work with MDI. Form editing mode, portfolio mode, and portfolio preview mode all wanted a complete refresh of the UI. MDI mode always left a bit of the UI skin under the care of an MDI main frame, so there would have had been no way for those UI modes to re-skin that part of the UI if MDI mode was left in place.
Perfoming these modes in MDI, WPF or any other multi-document environment would just have been a matter of good program design. Nothing more.
And again, if Mac OS does not support MDI, it's still possible to abstract the display concept to address SDI/MDI differences transparently in the Acrobat application. Microsoft Office even demonstrates how this is done: In all the MS Office applications there is an option to switch between MDI/SDI ("Show in Task bar").
A cost compelling reason was that MDI and SDI mode essentially became another view mode in which all work flows had to be tested. This increases the cost of testing the product and the cost of fixing bugs. Often a fix to a bug in one view mode would cause adverse reactions in the other view mode. The decision to support only one view mode on Windows was made to simplify this. Furthermore, more time spent in this area could mean less time spent developing and fixing bugs in other areas.
That's true, alright. - But automated testing tools also decrease the cost of testing. And as far as I know, testers do not develop software. That's the developers' task. So performing more testing in this area does not result into spending less time for developing. This is particularly true once the framework had been established to deal with MDI/SDI transparently.
I strongly suggest to return to MDI. The implementation classes should still be available from Acrobat 8. Perhaps they'd need a redo in order to support a better, transparent program design.

Acrobat was never a part of Creative Suite, it was merely included in the collections. The CS applications were developed by a different unit within Adobe to the 'enterprise' applications like Acrobat and LiveCycle. The creative business unit developed their own interface system (OWL) but it wasn't adopted by the other teams as it was specifically designed for one type of user, who worked on multi-screen hardware with highly customized desktops and took the time to really learn the software in depth.
The same is true of the consumer programs (Lightroom, etc.) - their target users have different hardware and skill levels, and their UIs reflects that. A Lightroom user doesn't need workspaces, and by discounting that the UI is free to implement something that makes more sense to photographers. In the OWL UI, you tend to have multiple information streams presented to the user in different panels, rather like an aircraft cockpit. The user is doing something with one tool, but can pull information from other panels as required. If they're editing text they need to see the swatches and styles panels. In Acrobat however, the workflow is single-task-based. You pick a tool, do something with it, then pick another tool. While you're editing a watermark there's no reason you would want to see the ink manager dialog or the XMP metadata.
Of course I see the logic in having a tabbed interface, but for everyone it pleases there'll be someone who begrudges the space taken up by the tabs on their netbook screen, or the fact they can't drag one file onto a second monitor. Adobe would have to keep both interface options so you could switch between them, and that pretty much doubles the workload on every release.
I'm not saying that going forward there's no chance of a tabbed interface ever appearing in the Acrobat Family, but with respect the target users tend to get lost when the UI reinvents itself. Acrobat is just a tool like the photocopier for most people, they aren't going to spend weeks learning it as they would with Photoshop. Open>Redact>Save>Email, all day every day. Adobe's target customers (big enterprises) see any change, even one that "improves" the UI, as a nightmare of retraining and reduced productivity.
BendersonMath wrote:
Actually, let me say something about homogeny of user experience. It seems like a fairly reasonable approach to this challenge is to come up with a UI that is intuitive based on knowledge users can be assumed to have from other UIs they can be assumed to be using. Acrobat's approach seems to be to come up with its own UI that is not only completely unlike the major OSes, but also unlike everything else Adobe does. Dividing Acrobat from Windows, Mac, etc. — sure, that's only fair. But why divorce it from the rest of its own sister products? The results have been strange.

How to enable forms extenstion for adobe reader using Acrobat SDK?

Adobe acrobat GUI tool enables PDF forms designers to extend the use of Adobe Reader and allow the end user to save the PDF form locally using the Reader.
Is it possible to do the same kind of fuctionality at run time on the server using Acrobat SDK?.
We are creating several PDF Form on the server, is there any way we can use Acrobat SDK to enable form's extenstions programatically on the server after the PDF is created.
If Yes How? any code example?

Not using the Acrobat SDK, no.
However, Adobe sells the LiveCycle Reader Extensions Server that can be
used on a server for exactly this purpose.

Problem: Blättern im Acrobat Viewer für Java

Hallo,
ich benutze den Pdf-Viewer mit der Java-Version 1.3.1 . Mein Problem ist, dass ich beim Seitenwechsel über eigene JButton's [fac.viewer.execMenuItem(ViewerCommand.NextPage_K)] immer eine ClassCastException erhalte, obwohl das Blättern über die mitgelieferte Menüleiste funktioniert.
java.lang.ClassCastException: com.adobe.acrobat.BeanClientTransactionExecutionContext
at com.adobe.acrobat.gui.PVNavigationVerb.invoke(PVNavigation.java:257)
at com.adobe.acrobat.gui.CommandRegistry.executeCommand(CommandRegistry.java:77)
at com.adobe.acrobat.Viewer.execMenuItem(Viewer.java:754)
at fsdb.AdobePanel.cmdNext_actionPerformed(AdobePanel.java:322)
at fsdb.AdobePanel$2.actionPerformed(AdobePanel.java:439)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1450)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1504)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:378)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:250)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:216)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
at java.awt.Component.processMouseEvent(Component.java:3715)
Würde mich freuen wenn Ihr mir weiterhelfen könnt.
Danke Björn

Hallo Björn,
habe auch das Anliegen PDF-Dateien im Applet oder JavaApp anzuzeigen.
Vielleicht gibst Du mir ein paar Tips. Kann Dir bei Deinem Problem leider noch nicht helfen.
-Woher hast Du die Klassen (JAR-File) von Adobe und wie aktuell sind diese?
-Gibt es vielleicht direkt Beans für Java?
-Wie sieht die Performance aus beim Aufruf von PDF-Files.
Danke Frank

How to Query search panel internationalization in ADF.

Hi,
I am using JDeveloper Studio 11.1.1.2.0 and weblogic server 10.3.2.My Requirement is Internationalization.I did Internationalization(Arabic) In GUI level Its coming
but Problem is in Query search panel(VO level) i want to change Internationalization ,but it is not comming.I have configured faces-config.xml.but not comming in Query search panel.
In VO level ,i have change in Control Hints, As a label Tex---> #{UIServiceMessage['_U0627_U0644_U0646_U0638_U0627']} but still same text msg is comming.
So plz help me how to Query search panel internationalization in ADF.
Thanks&Regards
Anup

hi
check this
http://andrejusb.blogspot.in/2008/02/list-of-values-component-in-search-and.html
Regards

XML format for Acrobat JavaScript

Hi,
This is my first posting to any Adobe forum, so please bear with me...
I'm interested in the XML format for Acrobat JavaScript. I'll be using an external editor (UltraEdit). When I do (in Acrobat 8) Advanced-->Document Processing-->Edit All JavaScripts, UltraEdit starts off with this:
//-----------------Do not edit the XML tags--------------------
Interesting, but not very useful. If I look at some existing PDF files containing JavaScript, I see things like:
//-----------------Do not edit the XML tags--------------------
//<Document-Level>
//<ACRO_source>DocOpen</ACRO_source>
//<ACRO_script>
/*********** belongs to: Document-Level:DocOpen ***********/
OK, this is better. In fact, if I look at enough existing PDF files containing JavaScript, I could probably figure out the XML format by myself, including the XML format of tags like <Page-Actions>, <AcroForm>, etc. However, it would be far easier to get the specification of the JavaScript XML format -- for example, what is the format of the text following the "belongs to:" string within the various types of XML tags?
I *presume* this is documented somewhere but I couldn't find it. If someone has the Acrobat JavaScript XML format specification, it would be greatly appreciated.
Thanks.
Dave
P.S. Another possible approach would be to create JavaScripts myself using Advanced-->Document Processing-->Document JavaScripts, and then see what XML is created based on the code I enter into the GUI, e.g. form code, functions, etc. This also seems somewhat inefficient, presuming again that the JavaScript XML format is already documented.

Thanks for the additional information.
I played with JavaScript some more, using my preferred editor, UltraEdit, which I attached to Acrobat. I thought I would be able to take a JavaScript program from one PDF file (source file) and do a copy & paste into another PDF file (destination file). While I can do the paste (again, via UltraEdit) into the destination file and can do an UltraEdit Save, when I go back into UltraEdit via Advanced --> Document Processing --> Edit All JavaScripts, the JavaScript I pasted from the source file to the destination file isn't there in the destination file.
From this, I concluded that I'll need to create the Document-level JavaScript and the form field Javascripts (e.g. a JavaScript triggered by a "Mouse Down" in a button) via the Acrobat GUI's. Acrobat doesn't seem to like it if I bypass the GUIs and just attempt to paste the code directly into the PDF file via an editor. By not using the GUI and just doing the cut & paste as I did, I'm probably missing some part of the code setup/creation process that Acrobat needs to know about.
This is why I originally asked about the syntax for the pseudo-XML, thinking I could just copy the pseudo-XML/JavaScript code from one PDF file to another, and then modify the code to reflect the needs of the destination PDF. Now I understand the need you mentioned to use the Acrobat GUIs to set up the initial XML/JavaScript structure.
Once I have the XML structure set up in the destination file (e.g. a JavaScript triggered by a "Mouse Down" in a button), I can obviously copy code snippets into that <AcroForm> sections, I just can't *create* the original "Mouse Down" <AcroForm> sections via the editor.
Another approach I could follow would be to make a copy of the original source file and change the name of the copy to the desired destination file name, and then start modifying the code in the new (destination) file -- presuming that's the easiest path to get the desired functionality created. This way, I wouldn't have to manually (via the Acrobat GUI) create all of the <Document-Level> and <AcroForm> sections.
Thanks for your (and others') help, let me know if I'm missing anything.
Dave

Problems when using javascript in jsp

hello, i am implementing a program to upload files.
a user can upload either a pdf or a latex file.
so for example if the user uploads a pdf file the form action should be
"uploadPDF.jsp" and if it is a latex file the action is "uploadlatex.jsp"
currently when the user uploads the pdf file IT WORKS and does the action correctly but it does not do it for the other file (latex file) gives
some long jasper exceptions pls help
*************here is the code*******************
<SCRIPT LANGUAGE="JavaScript">
var extArray = new Array(".pdf", ".tex", ".txt");
function LimitAttach(form, file) {
allowSubmit = false;
if (!file) return;
while (file.indexOf("\\") != -1)
file = file.slice(file.indexOf("\\") + 1);
ext = file.slice(file.indexOf(".")).toLowerCase();
for (var i = 0; i < extArray.length; i++) {
if (ext = "pdf"){
document.forms[0].action.value = "uploadPDF.jsp";
allowSubmit = true;
break;
if (allowSubmit) form.submit();
else
alert("Please only upload files that end in types: "
+ (extArray.join(" ")) + "\nPlease select a new "
+ "file to upload and submit again.");
</script>
</HEAD>
and below is the form
<form action="" name="upform"enctype="multipart/form-data">
<input type="file" name="PDFfilename" size="50"><br>
<input type="hidden" name="todo" value="upload">
<input type="submit" name="Submit" value="Upload" onclick="LimitAttach(this.form, this.form.PDFfilename.value)">
</form>
thanks,
moh

when uploading this latex file in a different jsp file and form it works fine
however in the above form it does not...........here is the exception errors:
org.apache.jasper.JasperException: This file appears to be damaged and cannot be repaired. This may not actually be a PDF file.
     org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
root cause
javax.servlet.ServletException: This file appears to be damaged and cannot be repaired. This may not actually be a PDF file.
     org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:858)
     org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:791)
     org.apache.jsp.uploadPDF_jsp._jspService(uploadPDF_jsp.java:209)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
root cause
com.adobe.acrobat.pdfobjstore.CantRebuildXRefException: This file appears to be damaged and cannot be repaired. This may not actually be a PDF file.
     com.adobe.acrobat.pdfobjstore.XRefTableRebuilder.buildTrailerDict(XRefTableRebuilder.java:141)
     com.adobe.acrobat.pdfobjstore.XRefTableRebuilder.rebuildXRefTable(XRefTableRebuilder.java:121)
     com.adobe.acrobat.pdfobjstore.XRefTableRebuilder.<init>(XRefTableRebuilder.java:46)
     com.adobe.acrobat.pdfobjstore.XRefTable.<init>(XRefTable.java:44)
     com.adobe.acrobat.pdfobjstore.XRefTable.<init>(XRefTable.java:64)
     com.adobe.acrobat.pdfobjstore.PDFObjMap.compute(PDFObjMap.java:122)
     com.adobe.pe.notify.VValue.handleRequest(VValue.java:172)
     com.adobe.acrobat.pdfobjstore.PDFObjMap.getTrailerDictRef(PDFObjMap.java:49)
     com.adobe.acrobat.pdfobjstore.VTrailerDict.computeReference(PDFObjStore.java:552)
     com.adobe.acrobat.pdfobjstore.VPDFReference.compute(VPDFReference.java:150)
     com.adobe.pe.notify.VValue.handleRequest(VValue.java:172)
     com.adobe.acrobat.pdfobjstore.VPDFReference.pdfReferenceValue(VPDFReference.java:161)
     com.adobe.acrobat.pdfobjstore.security.VEncryptionMethod.computeString(SecurityHandler.java:208)
     com.adobe.pe.vtypes.VString.compute(VString.java:55)
     com.adobe.pe.notify.VValue.handleRequest(VValue.java:172)
     com.adobe.pe.vtypes.VString.stringValue(VString.java:126)
     com.adobe.acrobat.pdfobjstore.security.VPDFObjStorePerms.computePDFObjStorePerms(VPDFObjStorePerms.java:41)
     com.adobe.acrobat.pdfobjstore.security.VPDFObjStorePerms.compute(VPDFObjStorePerms.java:54)
     com.adobe.pe.notify.VValue.handleRequest(VValue.java:172)
     com.adobe.acrobat.pdfobjstore.security.VPDFObjStorePerms.peObjStorePermsValue(VPDFObjStorePerms.java:32)
     com.adobe.acrobat.gui.AcroViewContext.setByteArraySource(AcroViewContext.java:587)
     com.adobe.acrobat.Viewer$3.buildChanges(Viewer.java:907)
     com.adobe.pe.notify.Transactor.commit(Transactor.java:70)
     com.adobe.acrobat.Viewer.setByteArraySource(Viewer.java:911)
     com.adobe.acrobat.Viewer.setDocumentByteArray(Viewer.java:948)
     com.adobe.acrobat.Viewer.setDocumentInputStream(Viewer.java:971)
     org.apache.jsp.uploadPDF_jsp._jspService(uploadPDF_jsp.java:106)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
on the first line it says that the file may be corrupted but it is fine and works, thanks
moh

Launching Adobe Viewer from a Swing application

How do I launch Adobe Viewer (or Reader) from my Swing application. I have a help menu item that needs to open the viewer with the PDF help manual. Since the application is cross-platform, do I need different versions of Adobe with my install package? Thanks for any help.

Thanks. I tried the adobe bean and it seems to work fine until I select the "Print" icon. It crashes the Viewer and my application as well. I get the following:
Any suggestions?
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0xff2c614c
Function name=realloc
Library=/lib/libc.so.1
Current Java thread:
at sun.awt.motif.MTextFieldPeer.create(Native Method)
at sun.awt.motif.MComponentPeer.init(MComponentPeer.java:169)
at sun.awt.motif.MComponentPeer.<init>(MComponentPeer.java:179)
at sun.awt.motif.MTextFieldPeer.<init>(MTextFieldPeer.java:68)
at sun.awt.motif.MToolkit.createTextField(MToolkit.java:85)
at java.awt.TextField.addNotify(TextField.java:194)
at java.awt.Container.addNotify(Container.java:1579)
at java.awt.Panel.addNotify(Panel.java:74)
at java.awt.Container.addNotify(Container.java:1579)
at java.awt.Window.addNotify(Window.java:349)
at java.awt.Dialog.addNotify(Dialog.java:247)
at java.awt.Window.pack(Window.java:367)
at com.adobe.acrobat.gui.PDFPrint$PageRangeDialog.<init>(PDFPrint.java:144)
at com.adobe.acrobat.gui.PDFPrint.<init>(PDFPrint.java:18)
at com.adobe.acrobat.gui.PrintUI.printPages(PrintUI.java:183)
at com.adobe.acrobat.gui.PrintUIVerb$PrintTransactor.printFileWithUI(PrintUI.java:591)
at com.adobe.acrobat.gui.PrintUIVerb$PrintTransactor.buildChanges(PrintUI.java:556)
at com.adobe.pe.notify.Transactor.commit(Transactor.java:44)
at com.adobe.pe.awt.UIVerb$1.buildChanges(UIVerb.java:151)
at com.adobe.pe.notify.Transactor.commit(Transactor.java:70)
at com.adobe.pe.awt.UIVerb.invoke(UIVerb.java:51)
at com.adobe.pe.awt.ToolBar.mouseReleased(ToolBar.java:419)
at java.awt.Component.processMouseEvent(Component.java:3715)
at java.awt.Component.processEvent(Component.java:3544)
at java.awt.Component.dispatchEventImpl(Component.java:2593)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2451)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:2216)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2125)
at java.awt.Container.dispatchEventImpl(Container.java:1200)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
Dynamic libraries:
0x10000 /shared/j2sdk1_3_1/bin/../bin/sparc/native_threads/java
0xff360000 /lib/libthread.so.1
0xff3a0000 /lib/libdl.so.1
0xff280000 /lib/libc.so.1
0xff260000 /usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1
0xfe480000 /local/j2sdk1_3_1/jre/lib/sparc/client/libjvm.so
0xff210000 /lib/libCrun.so.1
0xff1f0000 /lib/libsocket.so.1
0xff100000 /lib/libnsl.so.1
0xff1c0000 /lib/libm.so.1
0xff240000 /lib/libw.so.1
0xff0e0000 /lib/libmp.so.2
0xff0a0000 /local/j2sdk1_3_1/jre/lib/sparc/native_threads/libhpi.so
0xff070000 /local/j2sdk1_3_1/jre/lib/sparc/libverify.so
0xff030000 /local/j2sdk1_3_1/jre/lib/sparc/libjava.so
0xfe450000 /local/j2sdk1_3_1/jre/lib/sparc/libzip.so
0xfd060000 /local/j2sdk1_3_1/jre/lib/sparc/libawt.so
0xf4880000 /local/j2sdk1_3_1/jre/lib/sparc/motif21/libmawt.so
0xfd010000 /shared/j2sdk1_3_1/bin/../jre/lib/sparc/libmlib_image.so
0xf4600000 /lib/libXm.so.4
0xf4580000 /lib/libXt.so.4
0xfafd0000 /lib/libXext.so.0
0xfafa0000 /usr/openwin/lib/libXtst.so.1
0xf4480000 /lib/libX11.so.4
0xfac60000 /lib/libSM.so.6
0xfac30000 /lib/libICE.so.6
0xf4380000 /local/j2sdk1_3_1/jre/lib/sparc/libfontmanager.so
0xf4ba0000 /usr/openwin/lib/libdps.so.5
0xf4860000 /shared/j2sdk1_3_1/bin/../jre/lib/sparc/libsunwjdga.so
0xf4830000 /usr/openwin/lib/libdga.so.1
0xf4560000 /shared/j2sdk1_3_1/bin/../jre/lib/sparc/libxinerama.so

Toolbar button doesn't work

Acobat Pro 7.10, WinXp, sp. 2.
My Acrobat GUI isn't in English, so I will try to explain.
In the toolbar "Files" the search button with the binoculars graphic doesn't work. When clicking it nothing happens and Acrobat stops to work.
The toolbar "Search", the one with the text field, works OK.

Hi
i am having the same problem.when i click on last page buttom it ll shows some parameters are missing.can any body help me??????

PDF Display INSIDE a SWING app.

Is there a way to display PDF inside a JPanel (or whatever ;-) ? I know Adobe made a Bean but no support was added since two years (if i am right). PDFGo could be a solution but it seems slow and not really nice...
Other solutions ?
Anyone has already done such thing ?
Thanks.
Phil

Hi,
we are using the bean in an 1.3.1 environment and it works pretty well...
you can see how we implemented it by looking into the code a bit...Don't worry about the maintainer class..its just part of our gui framework.
Regards.,
rookie_no2
package de.fiscus.sfs.akte;
import com.adobe.acrobat.*;
import com.adobe.acrobat.gui.*;
import de.fiscus.sfs.akte.internal.AkteHelpset;
import java.awt.event.WindowAdapter;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.awt.event.ActionEvent;
import java.awt.event.FocusListener;
import java.awt.event.FocusEvent;
import java.awt.*;
import java.io.StringWriter;
import java.io.PrintWriter;
import java.util.*;
import javax.swing.*;
import de.fiscus.mw.bnof.*;
import de.fiscus.mw.transfer.*;
import de.fiscus.sfs.druck.druckauftrag.TODruckAuftrag;
* Diese Form realisiert die Anzeige eines einzelnen Aktenelementes in einer Nur-Lese-Ansicht.
* Dazu zeigt die Form die PDF-Viewer-Bean, deren Inhalt durch ein an den Viewer �bergebenes
* Byte-Array bestimmt wird, an.
* <p>
* @version %version: 7 %
* @see BNOForm
public class AkteneintragPDFForm extends AkteneintragBNOForm implements ViewerCommand{
Viewer ivViewer = null;
// Komponenten, die vom JBuilder erzeugt wurden
BorderLayout borderLayout1 = new BorderLayout();
BorderLayout borderLayout2 = new BorderLayout();
JPanel jPanel1 = new JPanel();
JPanel jPanelButtonBar = new JPanel();
GridBagLayout gridBagLayout1 = new GridBagLayout();
GridLayout gridLayout1 = new GridLayout();
/** Konstruktor. Initialisiert die Form. Es wird lediglich die Methode
   * <code>jbInit</code> gerufen, um die grafische Repr�sentation der Form zu
   * erzeugen.
   * @see jbInit
public AkteneintragPDFForm() {
    try {
      jbInit();
    catch(Exception e) {
      e.printStackTrace();
/** Definiert die grafische Repr�sentation der Form.
   * @return void
   * @exception Exception : technischer Fehler aufgetreten
private void jbInit() throws Exception {
    this.setComponentName("Druckvorschau"+AkteHelpset.cvARBEITS_BESTANDSANZEIGE);
    //Funktionalit�t der pdf-Bean
    try{
      ivViewer = new Viewer();
      //Setzen der Skalierung auf die Breite des Frames
      ivViewer.setProperty("Default_Zoom_Type","FitWidth");
      //Abschalten der gesamten Shortcut-Funktionalit�t
      Properties prop = CommandRegistry.getKeymaps();
      prop.clear();
      //Einschalten bestimmter Shortcut-Funkionalit�ten
      prop.putAll(getAllowedShortcuts());
      //Nicht ben�tigte Commands abschalten
      CommandRegistry.setDisallowedCommands(getDisallowedCommands());
    catch (Exception e) {
      e.printStackTrace();
    this.setMaintainer(new AkteneintragPDFForm.FormMaintainer(ivViewer));
    this.setPreferredSize(new Dimension(700, 600));
    this.setLayout(borderLayout1);
    this.add(ivViewer, borderLayout1.CENTER);
    jPanelButtonBar.setLayout(borderLayout2);
    jPanelButtonBar.add(getButtonBar(), borderLayout2.EAST);
    //this.add(this.getButtonBar(), borderLayout1.SOUTH);
    this.add(jPanelButtonBar, borderLayout1.SOUTH);
    Die nicht ben�tigten Commands (ViewerCommand) werden hier in einem String-Array zusammengefa�t und zur�ckgegeben
    @return String [] gesammelte Commands
private String [] getDisallowedCommands () {
    return new String [] {PageOnly_K, Thumbnails_K, ShowBookmarks_K, HideBookmarks_K, ToggleBookmarks_K,
                          Window_K, Open_K, OpenURL_K, Close_K, GeneralPrefs_K, About_K, Reload_K, Find_K,
                          FindAgain_K, DocInfo_K, ListBindings_K, PrintSetup_K, FirstPage_K,
                          PrevPage_K, NextPage_K, LastPage_K, PageUp_K, PageDown_K, LineUp_K, LineDown_K,
                          SinglePage_K, OneColumn_K, TwoColumn_K, TwoColumnLeft_K, TwoColumnRight_K,
                          ActualSize_K, FitPage_K, FitVisible_K, FitWidth_K, FitVisibleWidth_K, FitHeight_K,
                          FitVisibleHeight_K, FitVisibleHeight_K, FullScreen_K, ToFullScreen_K, FromFullScreen_K,
                          ToggleFullScreen_K, OpenHelpFile_K, OpenLicenseFile_K, EditUndo_K, EditDelete_K,
                          EditCopy_K, EditCut_K, EditPaste_K, EditSelectAll_K, Print_K};
    Erlaubte Shortcuts werden hier in einer Properties zur�ckgegeben. Die existierenden Commands sind
    durch den Aufruf CommandRegistry.getKeymaps() ersichtlich.
    @return Properties gesammelte Shortcuts
private Properties getAllowedShortcuts () {
    Properties prop = new Properties();
    prop.put("Page_Down", "PageDown");
    prop.put("Page_Up", "PageUp");
    return prop;
public Viewer getPDFViewer () {
    return ivViewer;
* INNER CLASS - FormMaintainer --- Beginn                                   *
public class FormMaintainer extends AkteneintragBNOFormMaintainer {
    private Viewer ivViewer = null;
    public FormMaintainer (Viewer ivViewer) {
      this.ivViewer = ivViewer;
     * F�gt den Inhalt des �bergebenen Byte-Arrays in den Viewer ein.
     * @param byte [] Byte-Array mit dem Inhalt des darzustellenden pdf-Files
    public void setPdfContent (byte [] bArray) {
      try{
        ivViewer.setDocumentByteArray(bArray);
      catch (Exception e) {
        e.printStackTrace();
     * CALLBACK: Diese Methode wird vom BNOFramework nach der Initialisierung
     * der Form gerufen. Diese Implementierung initialisiert die Toolbar der
     * Form. Anschlie�end wird die Methode <code>refresh</code> gerufen, um
     * die Form neu darzustellen.
     * @return void
     * @see refresh
    protected void handleSetup() {
      super.handleSetup();
      refresh();
     * �berschreibt die Methode der Superklasse. Sorgt daf�r, da� bei einem Klick auf den
     * Schlie�en-Button die pdf-Bean ordnungsgem�� beendet wird.
     * @param ActionEvent e
    protected void handleCancel (ActionEvent e){
      ivViewer.deactivate();
      super.handleCancel(e);
     * �berschreibt die Methode in der Superklasse. Dient dazu, den Event f�r einen vorhandenen
     * Drucken-Button in der AkteneintragPDFForm entsprechend zu behandeln
     * @param e ActionEvent, das das ausgel�ste Ereignis enth�lt
     * @exception Exception
    protected void handleActionPerformed (ActionEvent e) throws java.lang.Exception {
      if (e.getActionCommand().equals(BNOActionEvent.cvPRINT)){
        //ALT:
        //ivViewer.execMenuItem(ViewerCommand.Print_K);
        BNOFormMaintainer bnoFM = this.getParentMaintainer();
        final AkteneintragBearbeiten ab = (AkteneintragBearbeiten)this.getDataSource();
        final TODokumentDruckInfo toDruckInfo = ab.getDruckInformation();
        TOAkteneintrag toAE = null;
        //Abfangen der Exception notwendig. Tritt auf, wenn eine Druckvorschau vorhanden ist,
        //der Akteneintrag gel�scht wird und versucht wird, auf der ge�ffnetten Druckvorschau
        //diesen gel�schten Akteneintrag zu drucken
        try{
          toAE = ab.getAkteneintrag();
        catch (AkteException ae){
          throw new AkteException (true, "AkteneintragNotFoundException", new Object [] {"M�glicherweise wurde der Akteneintrag gel�scht"});
        final TOAkteneintrag selectedTO = toAE;
        AkteneintragDruckDialogForm form = new AkteneintragDruckDialogForm(ab.provideDienstpostenBefragen());
        BNODataAccessor data = new BNODataAccessor("", "") {
          public Object handleGetData () throws de.fiscus.mw.util.FiscusException, java.rmi.RemoteException {
            return toDruckInfo;
          public void handleSetData (Object o) throws de.fiscus.mw.util.FiscusException, java.rmi.RemoteException {
            TODokumentDruckInfo toDruckInfo = (TODokumentDruckInfo)o;
            ab.printDokument(toDruckInfo);
            if (selectedTO.getStatus()==(AkteneintragStatus.IM_BESTAND.getValue())){
              ab.printDokumentImBestand(toDruckInfo);
            else {
              ab.printDokumentPreview(toDruckInfo);
        //form.setButtonBar(AkteneintragBNOForm.cvDRUCKVORSCHAU_OK_ABBRECHEN);
        form.setButtonBar(AkteneintragBNOForm.cvOK_ABBRECHEN);
        BNOOpenWindowParameters owp = BNOOpenWindowParameters.createForSecondaryWindow(form, data, this, null, true);
        BNOWindow w = BNOFactory.createWindow(owp);
      else super.handleActionPerformed(e);
    * Initialisiert die Maintainerhierarchie richtungsm��ig von den
    * �bergeordneten Maintainern zu den untergeordneten Maintainern.
    public void reInitialize() {
      super.reInitialize();
      refresh();
    /** Diese Methode wird verwendet, um die Form neu darzustellen. Dazu wird die
     * zuvor erzeugte Viewer-Bean aktiviert, soda� sie dargestellt werden kann.
     * @return void
    public void refresh() {
      try{
        ivViewer.activate();
      catch (Exception e) {
        e.printStackTrace();
* INNER CLASS - FormMaintainer --- Ende                                     *
}

How to call GUI/Dialog in Acrobat sdk Plugin

How to call GUI/Dialog in Acrobat sdk Plugin using VC++ here is my code
ACCB1 void ACCB2 MyPluginCommand(void *clientData)
HMODULE hAppInst = GetModuleHandle(NULL);
DialogBox(hAppInst, MAKEINTRESOURCE(IDD_DIALOG1), NULL, NULL);
HWND hWnd = ::CreateDialog(hAppInst, MAKEINTRESOURCE(IDD_DIALOG1), NULL, DlgProc);
::ShowWindow(hWnd, SW_SHOW);

You can, with care, use Windows API calls in a plug-in. But you have to understand the process of loading resources. In particular, the calls you use try to load resources that belong to the main executable, which is Acrobat.exe. Plug-ins have their own instance handle, which is conveniently stored in gHINSTANCE.
In certain cases, especially modeless dialogs, there may be extra calls to make things work properly.
You do need to know how to use the Windows API, and your sample lines seem confused, unless you intended to first display a modal dialog then open the same dialog as modeless. That's something for another forum,

What GUI environment/toolkit is used by Acrobat programmers?

I have a GUI application that resembles Acrobat at first glance, to the point that people have suggested that it should have been developed as a set of plugins. Upon closer examination, however, one realizes that the similarity is only skin deep. To begin with, the files handled are not even PDF, they are TIFF files. I also have a palette that looks like Photoshop's.
In any event, I *really* like the look and feel of Acrobat, specially the floating and docking toolbars. I would like to request recommendations about any toolkit (commercial or otherwise, or perhaps Windows already provides all I need?) that allows me to exhibit such cool and professional looking behavior.
If there is a better newsgroup(s) to post this, I am glad to hear about them.
Thanks,
-RFH
ps: I hope Adobe won't sue me. :-)
pps: "Imitation is the sincerest form of flattery".

Adobe uses it's own internally developed libraries.

Configure Acrobat Reader tool buttons when Reader is started inside SAP GUI

Hi,
we have deployed some registry keys in "HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\AVGerneral\cToolbars" to show some tool buttons in Acrobat Reader. This works fine when starting Acrobat Reader as standalone application.
But in SAP GUI the Acrobat Reader starts with default tool buttons.
Is there a chance to configure the Acrobat Reader tool buttons when the Reader is started inside a SAP GUI session?
thanks
Albert

These are the settings in the registry to show/hide tools in the Adobe Reader 9 toolbar.
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\AVGeneral\cToolbars\cBasicTools\cInternalButtons]
"a0"="Select"
"a1"="Hand"
"a2"="Zoomin"
"a3"="ZoomDrag"
"a4"="endBasicToolsGroup"
"a5"="ZoomViewOut"
"a6"="ZoomViewIn"
"a7"="ZoomTo"
"a8"="Zoom100"
"a9"="FitWidth"
"a10"="FitPage"
"a11"="endZoomTypeGroup"
"a12"="PanAndZoom"
"a13"="Loupe"
"a14"="SelectGraphics"
"a15"="endZoomToolsGroup"
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\AVGeneral\cToolbars\cCommenting\cStamp]
"bInternalExpanded"=dword:00000001
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\AVGeneral\cToolbars\cFile\cInternalButtons]
"a1"="Print"
"a2"="Save"
"a3"="SaveFileAs"
"a4"="FindDialog"
"a5"="endDialogGroup"
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\AVGeneral\cToolbars\cPageDisplay\cInternalButtons]
"a0"="endLayoutZoomTypeGroup"
"a1"="Fullscreen"
"a2"="endPageLayoutViewGroup"
"a3"="RotateCCW"
"a4"="RotateCW"
"a5"="Wireframe"
When starting Adobe Reader standalone this works fine.
But starting Adobe Reader from a SAP GUI Session (for example in transaction CV03N) the default tools will be shown.
Is there a chance to configure the Acrobat Reader tool buttons when the Reader is started inside a SAP GUI session?
thanks
Albert

Adobe Acrobat 8 Plug-in GUI issues in Mac OS 10.4.11 using XCode 2.5

I am trying to port my plug-in to Acrobat 8. I have been maintaining this plug-in from Acrobat 5 on both PC and Mac. I am now having some trouble with the UI components of the Plug-in on the Mac. I can load and debug my plug-in on Acrobat 8, however my toolbar does not show up. Also, the modal dialog box that needs to launch does not. I am having trouble locating an example, or some documentation.
For the Toolbar button, I am using the following code from the Stamper example.
void *GetStamperToolButtonIcon(void)
#ifdef MAC_PLATFORM
extern CFBundleRef gPluginBundle;
AVIconDataRec iconData;
// Find a resource in the plugin bundle by name and type.
CFURLRef pingURL = CFBundleCopyResourceURL( gPluginBundle,
CFSTR("StamperIcon"),
CFSTR("png"),
NULL );
ASFile asf = NULL;
ASPathName aspn = ASFileSysCreatePathName (NULL,ASAtomFromString("CFURLRef"),
pingURL, NULL);
ASFileSysOpenFile(NULL, aspn, ASFILE_READ, &asf);
ASUns32 dataSize = ASFileGetEOF(asf);
ASUns8 *data = (ASUns8 *)ASmalloc(dataSize + 1);
ASFileRead(asf, (char *)data, dataSize);
ASFileClose(asf);
iconData.dataStm = ASMemStmRdOpen((char *)data, dataSize);
iconData.eColorFormat = kAVIconColor;
return AVAppCreateIconBundle6(kAVIconPNG, &iconData, 1);
#elif WIN_PLATFORM
return(AVCursor)LoadBitmap(gHINSTANCE, MAKEINTRESOURCE(IDB_BITMAP1));
#endif
This works for the stamper, and correctly displays the Stamper Icon in the toolbar, but when I try to create a new PNG file with the same name, the button no longer works. Also, if I try to change the name of the PNG file to "MyTool.png" and then the reference from CFSTR("StamperIcon") to CFSTR("MyTool") the button no longer works. Does anyone have any insight? In my research, I have come across SafeGetResource, and using the resource chain, however, I can not get this to work either.
The Modal Dialog I am trying to display is in a RSRC file, and it does not launch when I call sADMDialog->Modal() like it does in Acrobat 7, 6, and 5. Are there any Mac examples of plug-ins that use ADM, or platform specific Modal Dialog Boxes?
I have read the SDK documentation, but I can not find any code samples.
Any help would be greatly appreciated,
Thank You,
Austin

As of now I am unable to link up the objective c cocoa code when I build the plug-in. I can compile but not link. The error I get is below. Note that is that there is a -framework Carbon flag, but no -framework Cocoa flag. I have modified the Stamper example plug-in provided with the SDK and I can not find how to tweak the project settings to use the cocoa framework. If I can not figure out this linking problem, I will create a small project demonstrating the issues I am having and I will post it.
Ld "/Applications/Adobe/Acrobat 8 SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac/BuildResults/obj/MacShoomTool8/MacSh oomTool8_debug/MacShoomTool8.build/Default/MacShoomTool8_debug.build/Objects-normal/i386/M acShoomTool8" normal i386
cd "/Applications/Adobe/Acrobat 8 SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac"
/Developer/usr/bin/g++-4.0 -o /Applications/Adobe/Acrobat\ 8\ SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac/BuildResults/obj/MacShoomTool8/MacSh oomTool8_debug/MacShoomTool8.build/Default/MacShoomTool8_debug.build/Objects-normal/i386/M acShoomTool8 -L/Applications/Adobe/Acrobat\ 8\ SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac/BuildResults/obj/MacShoomTool8/MacSh oomTool8_debug/Default -F/Applications/Adobe/Acrobat\ 8\ SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac/BuildResults/obj/MacShoomTool8/MacSh oomTool8_debug/Default -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Cocoa.framework -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Cocoa.framework/Headers -F. -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Cocoa.framework/Versions/A -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Cocoa.framework/Versions/Curr ent -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Cocoa.framework/Versions/A/He aders -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Cocoa.framework/Versions/Curr ent/Headers -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks -filelist /Applications/Adobe/Acrobat\ 8\ SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac/BuildResults/obj/MacShoomTool8/MacSh oomTool8_debug/MacShoomTool8.build/Default/MacShoomTool8_debug.build/Objects-normal/i386/M acShoomTool8.LinkFileList -framework Carbon -framework ApplicationServices -arch i386 -exported_symbols_list Symbols.exp -Wl,-Y,1455 -bundle -mmacosx-version-min=10.3 -Wl,-dead_strip -isysroot /Developer/SDKs/MacOSX10.4u.sdk
/Developer/usr/bin/../libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
_objc_msgSend
.objc_class_name_NSObject
/Applications/Adobe/Acrobat 8 SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac/BuildResults/obj/MacShoomTool8/MacSh oomTool8_debug/MacShoomTool8.build/Default/MacShoomTool8_debug.build/Objects-normal/i386/S hoomToolUI.o reference to undefined _objc_msgSend
/Applications/Adobe/Acrobat 8 SDK/Version2/PluginSupport/Samples/MacShoomTool8/mac/BuildResults/obj/MacShoomTool8/MacSh oomTool8_debug/MacShoomTool8.build/Default/MacShoomTool8_debug.build/Objects-normal/i386/S hoomToolController.o reference to undefined .objc_class_name_NSObject
collect2: ld returned 1 exit status

Editing Form Fields inside Acrobat? (after using LiveCycle Designer)

Adobe Acrobat 9 Pro Extended == Acrobat
LiveCycle Designer ES 8.2 == LiveCycle Designer
=========================================
Say I downloaded a new PDF from the interwebs.
I want to add some forms fields so I go to Forms ==> Add or Edit Fields... (inside Acrobat)
Now Acrobat will detect possible places where to add the form fields. I make changes etc. Then I am satisfied with my form fields.
Now say I want to remove a particular object from the PDF, lets take an image as an example.
So I fire up LiveCycle Designer; File ==> New ==> Import a PDF document ==> Create an Interactive Form with a Flowable Layout.
I remove that pesky little object.
In LiveCycle Designer, I save the file as PDF.
I open up Acrobat. I realize I need to make some more changes to some of the Form Fields.
But now instead of "Add or Edit Fields..." option I get "Edit Form in Designer..."
I hate the GUI of LiveCycle Designer --- I had rather edit the form fields from inside Acrobat, as it is easy and fast to change multiple form fields in a few clicks.

Thank you Niall for the above response; Your response gave me an idea which allowed me to remove that line by zooming in to 200%
You know Acrobat detects Form Fields for you.
But many times it makes mistakes, for example in the screenshot below it made the boxes that came with the PDF as text fields instead of check boxes.
The thing is rather than me delete the (form) fields it detected, and start over by making new check boxes, I will not be able to place my new check box in exact locations as Acrobat has done.
When I imported the fields that Acrobat made into LC (by saving the PDF in Acrobat and then opening it with LC) I get option to change the Object Type from Text Field to Check Box when I right click the object.
Is there a similar way to change the Object Type from Text Field to Check Box inside Acrobat? Any suggestions?
===========
I would really like to do it inside Acrobat because then if I have to make some minor changes to some field properties, all my hard work which I did by filling the fields gets deleted, as I am forced to use LC. The text I add to the fields don't get deleted when I edit the field properties inside Acrobat. I don't know why LC decides to delete all the text which is filled out in the form fields even though the PDF is saved in Acrobat before being imported into LC?
Here is the above PDF file with the text boxes:
http://www.mediafire.com/?lnn32jm5am5
Again thanks for all your guidance so far.

Internationalization in Acrobat GUI

Similar Messages

Maybe you are looking for