Is there any sign which would indicate that a non Scrivener document is an external file (alias) rather than an external file imported into Scrivener? Looks the same to me, but I must be missing something.
thanks in advance for your time and help
Seeing a document in the Binder means it is internal; that’s a sign that it’s internal. If it’s not in the Binder, it’s external.
But I think you mean a way to see the difference in some other way, meaning you want to see a difference in the way it’s linked or imported to a document.
If it’s a link using <$img:binderFileName> or <$img:externalURL>, it will be obvious. That’s the way I always do it, usually external, to save storage in the project and keep images out of the way when writing/editing.
If you use any of the options below, you can right-click on the image to see what it is. If you use the 2nd option, Reveal in Finder will be an option (external). If you use the 3rd option, Reveal in the Binder will be an option (internal). If using the 1st option, neither appears, because the image is directly imported into the document where it appears.
This is not true. A Research file imported as an alias will appear in the Binder.
A small arrow in the left corner of the Binder icon will indicate that it is an alias.
I was thinking of images imported or linked within a document. You’re talking about imports as a document (next screenshot), not within a document – which I’ve never considered doing. Combinations of your method and one of those I mentioned are possible too. I don’t think the OP indicated which of several import/link options is meant.
The OP described imported documents, not images.
In any case, they now have lots of information and can clarify if necessary.
2 Likes
Then I’d have to wonder what “non-Scrivener document” means.
2 Likes
Hello @drmajorbob and @kewms
My apologies to both of you for wasting your time with unclear question which I will try to better rephrase.
Consider two PDFs (PDF 1 and PDF 2) imported into Scrivener by 2 different methods
- PDF 1 is imported (as in true import, ie incorporated into Scrivener and now distinct from the original file) by drag or drop or File→ Import → Files…
- PDF 2 is imported via File→ Import→ Research Files as Aliases…
All annotations I make in the Research Files as Aliases files are reflected in the original source file. Those in the imported PDF are not.
I have 3 questions:
1- when I look at PDF 1 and 2 in Scrivener, are there any signs in the Binder and/or Editor ihat PDF 2 is the research alias and PDF 1 the imported → file (now incorporated into Scrivener) ?
2- concerning PDF 2 (research alias), is there a way to determine the path of the source PDF in my Mac, ie to retrace the source file ? Is there a keyboard shortcut or menu item ?
3- if I move the source file from one folder to another will the research alias link follow, or do I have to re-import → Research Files as Aliases ?
Sorry again and thank you
1 Like
1a. PDF 1 should have a normal red-and-white PDF icon
1b. PDF2 should have a normal red-and-white PDF icon with an overlay of an alias arrow on the lower-left corner
1c. These icon differences should be clear in the binder and in header view (if header view is enabled): View → Editor Layout → Show Header View
2a. To see where PDF 2 is, right click its icon in the binder and choose Reveal in Finder. I don’t know of a standard keyboard shortcut for this, but a user can assign their own shortcut: Create keyboard shortcuts for apps on Mac – Apple Support (UK)
3a. If you move PDF 2 to a new location, the alias should automatically update without you needing to create a new alias. I just tried this with a test PDF moving it (with Scrivener open or closed) from my desktop to my downloads folder and the alias knew where the file had been moved to.
1 Like
very intelligent and well written answer. thank you so much
for the benefit of other forum members, I took the screenshots below
1 Like
Be aware that aliases are an operating system mechanism – not under Scrivener’s control – and can be somewhat fragile on some systems. In particular, moving a project with aliased research files between systems – including to a replacement computer – has caused problems in the past. While it’s possible to repair broken aliases, it can be somewhat tedious and may involve poking around inside the project’s index files.
2 Likes