Sonny Software

Here, FWIW is a JavaScript for Automation version which aims for a little more flexibility by:

1. Allowing you to specify the target field name at the top of the script,
2. deciding how many zeros are needed at the start (target width) by looking for the highest digit count seen in the data,
3 ...

The trick is to load the scripting library in Script Editor:

File > Open Dictionary... > Bookends

and change the language selector at the top from AppleScript to JavaScript.

Searching for format you will then see:

format PublicationItem or list of PublicationItem : The publication item(s ...

From Delicious Library 3 we can export a default XML file

File > Export To > Another Application > XML

The script below can convert:
an .xml file exported from DL3
to a .bex file (json content, importable to Bookends)


At the Bookends end, the menu path is:

File > Import References > From ...

This is what I did in the end (JavaScript for Automation)

(Probably a niche use case, so I haven't generalised it for others with file-choosing dialogs etc,
but certainly could, if anyone else might find that useful)

(() => {
"use strict";

const main = () => {
const
fpDL3xml = "~/Desktop ...

Before I draft a script to write out Bookends JSON from DL3 plists,
is there a better route that I have missed ?

(Delicious Library 3 doesn't seem to export BibTeX, which was a previous route)

Your Ver 14 announcement mentions (but doesn't, as far as I can see, specify) a new bundle id.

Could you confirm to us what it is ?

Some firewall software panics when it sees such a change, and it would be helpful to have confirmation somewhere of what the correct bundle id should now be.

Not sure if this is any faster (I would personally tend to do this in JS, which makes some of these things a bit easier and faster), but here FWIW is a variant approach in AppleScript:

use AppleScript version "2.4" -- Yosemite (10.10) or later
use scripting additions

-- Rob Trew @2020

on run ...

It works great! I am currently experimenting with it. Unfortunately, the Script Editor is not a very good IDE and the documentation for JXA is still abysmal. Feels quite immature as a technology. But holds great promise.

For an IDE, I tend to use Atom (free, excellent), with the Script and JS ...

With a couple of JavaScript helper functions – evalOSA and eventCode :

// evalOSA :: String -> String -> IO String
function evalOSA(strLang, strCode) {

var oScript = ($.OSAScript || (
ObjC.import('OSAKit'),
$.OSAScript))
.alloc.initWithSourceLanguage(
strCode, $.OSALanguage.languageForName ...