New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xrefitem doesn't handle hyphen in key (Origin: bugzilla #626508) #3896

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component doxywizard for ---
Reported in version 1.7.1 on platform Other
Assigned to: Dimitri van Heesch

On 2010-08-10 08:47:34 +0000, sbutler@planer.co.uk wrote:

ALIAS set to "test{1}=@xrefitem test\1 "Test notes \1" "Test notes \1" \n"

Have a page block containing two tests

/**
@page changelog_sb Change Log SJB.

@test{SBUR-87YKDP}

  • stuff here
  • more stuff

@test{SBUR-883CV7}

  • and the next test
  • and more

@note

  • comments.
    */

If the first argument to the @test has the hyphen in the text the keys for both tests get treated the same, so although the alias should make the xrefitem keys, testSBUR-87YKDP and testSBUR-883CV7 only one entry gets made; the first one. If the source is changed to @test{SBUR87YKDP} and @test{SBUR883CV7} the documentation works correctly.

I assume that the - in the key is causing SBUR-87YKDP and SBUR-883CV7 to be treated the same.

On 2010-08-14 18:42:02 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-10-09 08:19:38 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.2. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

@doxygen doxygen added the doxywizard label Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment