strubinsky
Instructor
Hello,
we have a tool that is similar to Adobe CUE and allows files to be stored versioned.
That we don't use CUE is not my decision but politics, so I have to live with it.
My problem is that -for whatever reason- inDesign DOES NOT allow graphics to be included as an URL like " Paste doesn't do it, relink via http copies the graphics and points then to the local copy as <img href="file://localdrive/localdir/thePic.jpg"
Well, that is exactly what I and our people DON't want. If we change a logo, a pic, all instances pointing to that pic should display from now on the new logo.
I can 'make' a web service that would respond to an http request with the retrieved image. webDav does it automatically and CUE does it too.
Why -for heavans sake- does inDesign castrate the <href..> tag to exclusively local or network drives and forbids uniform resource identifiers (URI) and uniform resource locators (URL's) since the underlying operating system by default supports it.
After having ranted enough I have to accept, that there are things in life you can't change (or is there a way???) like the artificial limits in inDesign (I know that the graphics needs to be embedded for publication) and the political decision not to use CUE.
My question is now:
Can I convince inDesign to accept a url-
- via scripting
- via api's as a plugin
It can obviously be done since I found several server applications that do exactly what I need, but they are for and associated with tools/databases that are not 'the chosen ones' of my organization.
I am certain that a solution would profit quite a few of us, since it makes a lot of sense to point from several docs to one graphics so that a change of that graphic would be reflected in all referring documents and as technology progresses, some orgs want versioning which is why a simple filename won't do it.
Any hints, ideas, wisdom, tricks, pats on my burdened shoulder??
Thank you in advance
guenter strubinsky
we have a tool that is similar to Adobe CUE and allows files to be stored versioned.
That we don't use CUE is not my decision but politics, so I have to live with it.
My problem is that -for whatever reason- inDesign DOES NOT allow graphics to be included as an URL like " Paste doesn't do it, relink via http copies the graphics and points then to the local copy as <img href="file://localdrive/localdir/thePic.jpg"
Well, that is exactly what I and our people DON't want. If we change a logo, a pic, all instances pointing to that pic should display from now on the new logo.
I can 'make' a web service that would respond to an http request with the retrieved image. webDav does it automatically and CUE does it too.
Why -for heavans sake- does inDesign castrate the <href..> tag to exclusively local or network drives and forbids uniform resource identifiers (URI) and uniform resource locators (URL's) since the underlying operating system by default supports it.
After having ranted enough I have to accept, that there are things in life you can't change (or is there a way???) like the artificial limits in inDesign (I know that the graphics needs to be embedded for publication) and the political decision not to use CUE.
My question is now:
Can I convince inDesign to accept a url-
- via scripting
- via api's as a plugin
It can obviously be done since I found several server applications that do exactly what I need, but they are for and associated with tools/databases that are not 'the chosen ones' of my organization.
I am certain that a solution would profit quite a few of us, since it makes a lot of sense to point from several docs to one graphics so that a change of that graphic would be reflected in all referring documents and as technology progresses, some orgs want versioning which is why a simple filename won't do it.
Any hints, ideas, wisdom, tricks, pats on my burdened shoulder??
Thank you in advance
guenter strubinsky
