Deutsch English Français Italiano |
<vdevac$v20l$1@solani.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Ulrich D i e z <ud.usenetcorrespondence@web.de> Newsgroups: comp.text.tex Subject: Re: pgfplots: link to top of embedded page Date: Mon, 30 Sep 2024 21:48:31 +0200 Message-ID: <vdevac$v20l$1@solani.org> References: <vcrjpsU2ns40L1@usenet.in-ulm.de> <vd56ie$pqj6$1@solani.org> <vd69loU3b7quL1@usenet.in-ulm.de> <vd7j0j$voaf$1@solani.org> <vddr6rU3p0jqL1@usenet.in-ulm.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Date: Mon, 30 Sep 2024 19:48:28 -0000 (UTC) Injection-Info: solani.org; logging-data="1017877"; mail-complaints-to="abuse@news.solani.org" User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 Cancel-Lock: sha1:sepI4EnwxrZHIKmMMbUu7Na0wII= X-User-ID: eJwVxkkRwDAMA0BKPpUETiPV/CF0uq/thIOr0KienmDMc2imFO2q3pZ7jPB/M+zobgWQXEZ9MvkR3A== Content-Language: en-US In-Reply-To: <vddr6rU3p0jqL1@usenet.in-ulm.de> Bytes: 2421 Lines: 30 Holger Schieferdecker wrote: > Thank you very much. Now I have to decide which version I like better :-) You are welcome. > By the way, how fragile (or not fragile) is your solution? I mean, is it > likely to break with possible future changes of pdfpages or graphicx? Of > course one never knows what could change. But as far as I understand > your helper macro \HookIntoIncludegraphics I would assume it is rather > unlikely to break. I can't make any statements or predictions about what changes to the pdfpages package are planned and how they will interfere with the macro suggested by me. I also don't know what is planned for hyperref and the LaTeX kernel - for example whether the current infrastructure for cross-referencing and creating bookmarks will be retained in the middle-term or long run. However, since, when patching `\includegraphics` in the local scope, only things are used that belong to the documented official interfaces, I'm optimistic that changes under the hood on pdfpages/hyperref/the LaTeX kernel in the near future won't affect the macro suggested by me. But I would still like to say that my focus was more on a scenario where a workaround is used to get a job done in the short term, not on a permanent long-standing solution. Sincerely Ulrich