Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-issues@incubator.apache.org
From: bugzilla@apache.org
To: ooo-issues@incubator.apache.org
Subject: DO NOT REPLY [Bug 62843] Ability to use JavaScript in pdf-forms
Date: Sun, 27 Nov 2011 21:33:24 +0000
Message-ID: <bug-62843-248469-IRpNu5OeZh@https.issues.apache.org/ooo/>
In-Reply-To: <bug-62843-248469@https.issues.apache.org/ooo/>
References: <bug-62843-248469@https.issues.apache.org/ooo/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/ooo/show_bug.cgi?id=62843

orcmid <orcmid@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |orcmid@apache.org

--- Comment #8 from orcmid <orcmid@apache.org> 2011-11-27 21:33:24 UTC ---
Well, both links in the original issue report are now obsolete.

There are ISO Standards for PDF and it would be interesting to know what
provision for scripting exists in those.

But a larger problem is, if the ODT can't be scripted in the way desired, how
would such scripting be conveyed into an exported PDF?  And then what would it
take to translate it into the exported PDF from however it is accomplished in
the ODT.

So it applies to both scripting framework, where and how scripting happens in
ODTs, ODSs, and ODPs, and then how to map that into their PDF exports.

There are probably some security, authentication, and safety considerations in
all of this too.

@argoon: It seems not so active.  The classification as P3 trivial is a
mystery.

-- 
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.