Re: Exporting Hyperlinks ?

[Samuel Wales]

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 it up.

one thing i dislike is having to specify a file name in #+include or
links.  too brittle for my taste.  you change the file name and the
inclusion [transclusion package also?] or link is broken.  i'm ok with
org id most of the time but suepect global human-readable would be
really really useful.

imo huge value here.  in fact, i think we should allow human-readable
id's [/and/ org id's] in non-org files, such as .el.

oref seems to do this, but is not part of org and does not use org id
db yet, and some might or might not want a different syntax [no
opinion].

good concept.  as something similar, i found myself using
org-link-minor mode all the time for linking together, in comments,
parts of .el files, such as comments with distant code or code in
another file, or format statements with something that parses them but
is for whatever reason not nearby them.  and i also linked org with
.el so that org would do org things.  it made tses and links
clickable.  id markers [not implemented] would be even better as they
would allow instar and outstar formations and unbreakable bidir links
and tours/cycles and arbitrary graphs if those turn out to be desired.
if desired and not too complex, it could even hook up with the org
link insertion and editing mechanism in principle.

i did look at hyperbole both old and new, and found almost nothing
that i needed there.  just personal experience.

also, given especially the org-id stuff and other org aspects, i
actually think this kind of thing should NOT be a
separately-maintained package like oref, but should be a minor mode
that is part of the org-maintained codebase.  we do already have at
least one org minor mode for operating on non-org files.

of course, maintainers would have to be on board with it being part of
org-maintained code.  i just think org should branch out to this minor
mode.


On 11/3/23, Max Nikulin <manikulin@gmail.com> wrote:
> 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, labels from another
> document may be used directly or with a prefix:
> https://texfaq.org/FAQ-extref
> It may be implemented for Org random labels.
>
> However I would strongly prefer PDF files having stable anchors based on
> CUSTOM_ID, not ones derived from section, figure, etc. counters. I am
> unsure if there is a package that allows to get such anchors out of the
> box.
>
> When I looked into the code for link targets resolution in the context
> of ox-html, I found it rather complicated.
>
>> I use publish for LaTex (org-latex-publish-to-pdf)
>
> Depending on your requirements, it might be possible to export to HTML
> files and then print them to PDF as a workaround. Chromium supports
> headless printing, so it should be scriptable. However to improve
> quality of formatting almost certainly heavy customization of CSS.
>
> I have realized that Chomium scrolls to proper position in PDF when it
> opens a file URI with #anchor part, but it does not update tab address
> bar when an internal link is clicked and it does not react when URL is
> edited to change #anchor part.
>
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com