[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#835162: marked as done (How to link to an external URL with # (hash) sign?)



Your message dated Wed, 24 Aug 2016 00:43:20 +0900
with message-id <20160823154320.GO19152@logic.at>
and subject line Re: Bug#835162: How to link to an external URL with # (hash) sign?
has caused the Debian Bug report #835162,
regarding How to link to an external URL with # (hash) sign?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
835162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835162
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-base
Version: 2016.20160805-1
Tags: upstream

Before this bug gets lost in infinity, here is a quick report.

There is an issue in between doxygen generated LaTeX code and hyperref
package (as shipped in Debian at least), where one cannot use a # sign
in a URL even if the documentation states it is supposed to work.

Based solely on the documention (and the original doxygen bug), I
believe the bug is indeed in texlive-latex-base, see for more ref:

https://bugzilla.gnome.org/show_bug.cgi?id=769977

Let me copy/paste some keywords for reference:

[...]
    ! Illegal parameter number in definition of \Hy@tempa.
    <to be read again>
                       p
    l.153 ...ageref{classgdcm_1_1ImageRegionReader}}{}

    ?
[...]

--- End Message ---
--- Begin Message ---
> Fill free to close this as wontfix, since it does not impact building
> src:gdcm anymore.

I closed it.

BTW, please see the comment of David on the github issue. He
responded:
> I doubt this has changed for years (no time to check the records today sorry)
> usual problems with "making characters safe" is that it fails if used after
> they are already tokenized.
>
> This works, and doxygen could presumably generate equivalent code
> 
> \documentclass{article}
> \usepackage{hyperref}
> \edef\safehash{\string#}
> \begin{document}
>
> \contentsline{section}{note: \href{http://a.b.c/d\safehash EEE}{link} }{}{}
> 
> \end{document}

This is what doxygen should create in one way or another ;-)

All the best

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13    fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

--- End Message ---

Reply to: