We already discussed that the JS functions defined by scripts are not included. Therefor my suggested trick had nothing to do with ePub, it was about invoking menu actions from within JS. As you now bring up InDesign Server: IDS has no UI and therefor no menu actions, so you either keep it just as license and let InDesign Desktop do the work, or it is really time to file a support case, especially as you're still targeting to CS3! Now getting off topic: In the OMV you only see the object model equivalent to the VersionedScriptElementInfo resources that describe your (and all the others) script providers. If in that resource you use the kCoreScriptManagerBoss, your script provider will work in all languages. If it does not show, your plugin might not be recognized by IDS - maybe you forgot to enable IDS in the plugin info? If I had to implement something similar to your method, I'd change at least these points: the method should be parentend by the addressed spread rather than the application words within method and property names should be lowercase (except acronyms) and separated by spaces. ScriptInfo will reformat (capitalize) those according to language specific rules. If you really have a native implementation backing that export as epub functionality, I'd forget about script providers and turn the export into a true export provider. Otherwise it does not make sense to run a script that invokes a plugin that invokes another script, just do it from the top level script. Dirk
... View more