(In reply to comment #7)
> Good stuff, Andreas (only a quick glance taken). The only thing that is
> probably missing is a parse method for the intermediate format.
Right. I'll have to adapt AreaTreeParser.setTraits() as well, since the external-link Trait is no longer a simple String.
> I guess if the Acrobat plug-in does not handle the "NewWindow" flag properly,
> there's not much we can do. It probably needs to be considered a bug in Adobe's
A bug or a missing feature, indeed. It is also not possible, AFAICT, to open a different destination in the same document in a new window. Still, if I interpret correctly, this is the expected behavior for show-destination="new", no matter whether the destination is internal or external.
> I'm not sure that behaviour is a bug. Undesirable maybe. My understanding is
> that Adobe Reader plugin uses the option "Display PDF in Browser" under
> Edit\Preferences menu (Internet Tab) to decide whether to open a separate
> window for PDF links or not.
Not exactly. The above option controls whether the plugin is used altogether if you enter a PDF address in the browser's address bar or click a hyperlink targeting a PDF. If you disable it, then Adobe Reader or Acrobat is always used standalone to view PDFs. There is another option that also relates to the /NewWindow flag. On the General Tab, I have the possibility to disable "Open cross-document links in the same window". This determines what happens if no explicit value for the /NewWindow flag is specified. Only, this option does not influence the behavior in the plugin; only relevant for standalone mode.