What Scrivener does poorly (or not at all)

There’s a lot I like about Scrivener, a writer’s integrated development environment with compilation to platform specific documents. I’m not the only person who wants to like it, there are many enthusiasts online.

It’s easy to find tips and advice online, it’s harder to find a list of what doesn’t work. That’s important to know up front, before you commit to Scrivener.

This is my working list. I’ll expand it over time…

1. PDF export has no page footnotes. The footnotes become chapter endnotes instead.
2. Table creation within Scrivener is quite limited (Scrivener uses macOS text editing services).
3. Table creation in compiled output is poor or unusable. Formatting in PDF and RTF loses font information, formatting in Word .docx defaults table to Word “auto fit to contents” instead of “auto fit to window”.
4. It’s easy to get formatting drift between chapters, there’s no ready style enforcement (there is a process for redoing all formatting to a default)

Some of Scriveners’s limitations seem inherited from macOS text handling, others may be limitations of third party libraries. Scrivener could be more forthright about what works and doesn’t work, but that’s asking a lot of a small business.

Scrivener works best for writing fiction, though even there style support is a big issue (see also, below). It works less well for non-fiction — we need things like tables. If I do continue with Scrivener for my own book I’ll have to treat Word output as a forked version — with late stage editing being manually replicated in two locations. That’s not ideal, but it might be doable. The alternative, of course, is to use Word from the start [1].

- fn -

[1] At least in light use Word for Mac is now useable and the bugs are manageable. With the rental model Office 365 is also quite reasonably priced.

See also:

• The pain and suffering of Scrivener exports to Word | Laura Lis Scott - view from a fiction writer (no tables, but still needs consistent formatting).
• Automate Style Assignment During Scrivener to Word Conversion (2011) - Word for the “final” edit. A hack that uses Scrivener unique formats as a proxy for styles, then uses Word to turn these into Word styles.
• Scrivener to Word | Laura Lis Scott (2014) - Leveraging the format/style swap method.

Set Reminders.app alert sound to Constellation and you can't miss them.

I had one job. I had to put my daughter’s laundry in the dryer. Since I know I’m demented I set a Reminder. Which I never saw because I didn’t look at my phone and the tiny ding went unheard (and perhaps because Reminders sync to El Cap is unreliable).

It’s not the first time I’ve missed a Reminder. When I set one I really want to be reminded.

An alarm option for Reminders would be great but for now there’s a workaround. In Settings:Sounds:Reminder Alerts [1] choose “Constellation” ring tone. It goes on endlessly.

- fn -

[1] Same option can be found in Notifications. iOS changed settings model from a hierarchy to an acyclic graph; settings now appear in multiple places. I think this is a good thing, especially with search. Search is still odd though; if you search on Sounds you find individual Sound settings, but the Sound menu item appears with the description “Lock Sounds”. (I think this is a bug.)

Tweak to my Photos.app, Aperture workflow.

WARNING: There are at least two issues with this workflow.

1. Not all images that appear in iOS UI for “All Photos” are actually available for import into Aperture. I suspect images that have synchronized from iCloud Photo Library are stored in a different physical location from the images Aperture sees.

2. Neither Aperture nor Image Capture can delete photos from iPhone if iCloud Photo Library is active. Aperture doesn’t show an error message but fails. Image Capture doesn’t show the delete control. Turn off iCloud Photo Library to reenable delete.

———- ORIGINAL POST ——————-

With El Capitan it is possible to have Photos.app and iPhone share photos via iCloud, while Aperture owns posting to iCloud photo sharing streams. You have to fight Photos.app a bit, but it works great.

So my workflow has been to use Photos.app on OS X and iOS to cull images, then periodically export from Photos.app to Aperture. Except Photos.app original image export is broken, and has been broken since 1.0. (Exports all images, even those that are “deleted”), so this is a pain.

Finally realized there’s a much better solution. Whenever I want to move images from Photos.app to Aperture I import them from the iPhone into Aperture (iPhone set to keep full res images). Then I use Aperture post-import delete. Then they delete from Photos.app. Much neater.

See also:

• Living within iCloud Photo Library’s storage budget 6/2016
• iCloud Photo Library, Photos.app and my Aperture plan (plus Aperture Exporter)

Apple's peculiar relationship to RSS (and blogs)

Apple “Newsroom” smells like a blog, but there’s no RSS feed. I assume it uses Apple’s RSS variant and works with Apple’s News.app, but it also renders in a browser. (Historically a dull PR site, Apple is starting to use Newsroom to promote Siri.)

On the other hand, Apple has RSS Feeds. They even have an iTunes Store query tool that generates custom RSS. They don’t have them for newsroom though.

News.app and Apple News is supposed to be able to work with RSS feeds, but I can’t get it to work with Wordpress or Blogger feeds.

Apple’s half-baked approach to subscription and notification is sadly typical for them.

OS X and iOS wifi defect with iCloud keychain sharing: rejoining zombie networks.

With iCloud keychain sharing enabled both iOS and OS X seem unable to truly “forget” networks I’ve joined. I remove them using the WiFi menu or advanced preferences but they seem to keep returning. With large numbers of networks the U for locating specific networks is quite frustrating.

These unforgotten networks mean I’m constantly having to adjust what networks I join, or I join the wrong ones.

The best workaround I’ve found is to use Keychain Access from OS X to delete the wifi password for unwanted networks. That seems to propagate correctly and the UI includes search.

Modern bugs: server, client, and DRM. Also transient.

Another reason why we can’t have nice things.

My son's iPhone had access to some of our cloud media (TV) library, but not all of it. The UI looked like a mixture of age restricted on-device media, downloadable off-device media, on-device media missing normal display icons, and off-device media that wasn’t shown at all.

iTunes sync displayed odd alignments; it saw on-device media that did not show in iOS manage storage. His device requested App Store credentials multiple times, usually displaying the iOS 1 style dialogs seen when things are broken in iOS 9’s hacked together authentication frameworks.

An hour or so later things were more or less back to normal. Signing out of the App Store completely then re-authenticating might have helped. Or perhaps an old school iTunes sync or two. Or maybe an asteroid fly-by.

iOS flash style corruption? (There’s probably a reason Apple wants to retire HFS+ for something that’s Flash friendlier.) Problems with Apple’s DRM servers? Bugs in iOS? Bugs in iTunes?

Most likely all of the above. Sooner or later I’ll have to wipe and restore this phone, the iPhone equivalent of a visit to the dental hygienist. Reminds of me of Windows 95 really.

Modern bugs: emergent, complex, transient, common, and disruptive.

Beware: iPhones with mixed FairPlay app ownership may no longer backup/restore as expected

Ran into this with a friend’s devices. He was syncing his and his wife’s iPhones to iTunes under Lion. Not sure how old iTunes library was.

When his wife’s iPhone 6s had to be replaced he found he couldn’t restore from iCloud backup or from his old iTunes backup (Lion OS, I didn’t check his iTunes version). He tried to create a new iCloud backup but that removed  the old one and created a 0kb backup. I couldn’t get iCloud backup working either.

Probably relevant: they had mixed app ownership, some purchased under his Apple store ID, some under her Apple store ID.

I created a backup to a fresh user account iTunes instance on my El Cap machine (but, significantly, my machine is authorized on my App Store ID). Restore seemed to proceed — but app restore didn’t complete from the iTunes backup. Instead it slowly proceeded via iCloud then left apps in dim icon status.

I believe I got things working by signing them up to Family Sharing. Then apps downloaded from iCloud, but not from iTunes.

At the time I write this I’m still investigating media rights and have yet to attempt another iCloud backup.

I wonder if Apple quietly updated its backend DRM rules.

DRM is nasty stuff.

Update:

1. The iCloud backup problem was an unrelated bug. “The Last Backup Could Not Be Completed” bug has many causes, but sometimes it’s just the wrong error message. Instead of saying “buy more storage” (which is what I usually see) iCloud Backup gave a useless error message and quit. I excluded her 5.1GB of images and it resumed.
2. Her new phone has no media. I think I know what happened. She gets her media from a non-DRMd old school iTunes music library. If you backup, as we did, from her phone to a Library on my computer there’s a DRM conflict. Apple’s iTunes DRM is device based, not (AFAIK) user account based. So my Mac wasn’t authenticated to hold her music (maybe I could authenticate, but that’s scary). I think the music got backed up, but iTunes could’t display/handle it, so it wasn’t part of the restore. The bug here is absence of an error message, simply media free restore.