On 08/11/2023 16:37, Ihor Radchenko wrote:
Max Nikulin writes:
It would be nice to have a LaTeX package that redefines \label to
generated \hypertarget from its argument.
Can't we simply generate a pair of \label + \hypertarget when generating
.tex files in ox-latex? This way, we can make
On 08/11/2023 15:02, David Masterson wrote:
Max Nikulin writes:
On 07/11/2023 19:36, Ihor Radchenko wrote:
If \href{file.pdf#anchor} can work, we should indeed use it when
publishing org->pdf.
It would be nice to have a LaTeX package that redefines \label to
generated \hypertarget from its
Max Nikulin writes:
>> If \href{file.pdf#anchor} can work, we should indeed use it when
>> publishing org->pdf.
>
> It would be nice to have a LaTeX package that redefines \label to
> generated \hypertarget from its argument.
Can't we simply generate a pair of \label + \hypertarget when
Max Nikulin writes:
> On 07/11/2023 19:36, Ihor Radchenko wrote:
>> If \href{file.pdf#anchor} can work, we should indeed use it when
>> publishing org->pdf.
>
> It would be nice to have a LaTeX package that redefines \label to
> generated \hypertarget from its argument.
This would make it easy
On 07/11/2023 19:36, Ihor Radchenko wrote:
Max Nikulin writes:
Cross-links between files work.
This is interesting. I am wondering if it is document (it should...).
file:///usr/share/doc/texlive-doc/latex/hyperref/hyperref-doc.pdf#section.6
or
Max Nikulin writes:
> I just have tried
>
> file-a.tex:
>
> \documentclass{article}
> \usepackage{hyperref}
> \begin{document}
> A 1
>
> \href{file-b.pdf#b-2}{b-2 in file b}
> \newpage
> \section{Section in A}
> \hypertarget{a-2}{}A 2
> \end{document}
>
> file-b.tex:
>
> \documentclass{article}
On 06/11/2023 16:37, Ihor Radchenko wrote:
David Masterson writes:
[[file:test.pdf::#anchor][Another document]]
-> \href{test.pdf\#anchor}{Another document}
AFAIK, this kind of URL cannot be opened except when opening pdf in
browser.
What else is there? PDFviewer? What is the
David Masterson writes:
>>> [[file:test.pdf::#anchor][Another document]]
>>>-> \href{test.pdf\#anchor}{Another document}
>>
>> AFAIK, this kind of URL cannot be opened except when opening pdf in
>> browser.
>
> What else is there? PDFviewer? What is the standard for Latex?
Yes, PDFviewer.
Ihor Radchenko writes:
> Max Nikulin writes:
>
>> Human-readable link targets are susceptible to collisions. So ox-latex
>> should support links to particular locations in the specified files,
>> either an Org one or inside external PDF files. Code from ox-html should
>> be adapted for
Max Nikulin writes:
> Human-readable link targets are susceptible to collisions. So ox-latex
> should support links to particular locations in the specified files,
> either an Org one or inside external PDF files. Code from ox-html should
> be adapted for ox-latex.
>
>
On 04/11/2023 04:55, Samuel Wales wrote:
[[file:contacts.org::#custom_id][My
text]] made me think of the need for global custom id in addition to a
file-specific one like this.
Taking into account that there is another active thread on user-global
links, I am not going to discuss that feature
[again, the specific implementation or syntax isn't the issue for me
here, just hte ability to have global custom id in addition to
existing .org local custom id]
[in case not obvious, i used org-link-minor-mode to implement the
equivalent of global custom id's, including non-org. i'd say, like,
";; mypackage-whatever-parsing-thingie". that is a kludge if we can
do it right with an oref-concept-ish org minor mode, but it was hugely
useful.]
to throw a cat among the pigeons, [[file:contacts.org::#custom_id][My
text]] made me think of the need for global custom id in addition to a
file-specific one like this. idk what a good ui for it would be given
all the options we have considered over the years and recently. just
thought to bring
On 03/11/2023 13:29, David Masterson wrote:
the generated LaTeX href looks like
\href{contacts.tex}{My text}
which looks wrong.
Search part definitely should be retained.
I have realized that in the LaTeX world inter-document cross-linking
works differently. With the xr-hyper package,
Max Nikulin writes:
> On 02/11/2023 09:11, David Masterson wrote:
>> If I understand what you mean by "anchor", does Org create an anchor in
>> exporting to Latex when it sees a CUSTOM_ID property in an item? Then,
>> would the search in the hyperlink reference the anchor? Your examples
>>
On 02/11/2023 09:11, David Masterson wrote:
If I understand what you mean by "anchor", does Org create an anchor in
exporting to Latex when it sees a CUSTOM_ID property in an item? Then,
would the search in the hyperlink reference the anchor? Your examples
weren't precise enough for me to
Max Nikulin writes:
> On 01/11/2023 11:24, David Masterson wrote:
>> In the Org Mode documentation, I see how hyperlinks are handled in HTML
>> export and how images are handled in Latex export, but is there a clear
>> description of how hyperlinks are handled across export engines
>>
On 01/11/2023 11:24, David Masterson wrote:
In the Org Mode documentation, I see how hyperlinks are handled in HTML
export and how images are handled in Latex export, but is there a clear
description of how hyperlinks are handled across export engines
(particularly the standard ones)?
Only the
In the Org Mode documentation, I see how hyperlinks are handled in HTML
export and how images are handled in Latex export, but is there a clear
description of how hyperlinks are handled across export engines
(particularly the standard ones)? I see that the PDF viewer is seeing
file links from
20 matches
Mail list logo
