MakeIndex, Nomenclature, Glossaries and Acronyms ⇒ See also command without page number

[Jongomez]

Hello,
When using the comand |seealso for index definition, as this:

Code: Select all

\index{Sistemas compuestos!|seealso Entrelazamiento}

, the compilation gives me as output:

Sistemas compuestos, véase también
Etrelazamiento110

Question: I don't want the page number (110 in this case) to appear.
What can I do to prevent this page number from appearing?

Miscellaneous: Why appears the word "Etrelazamiento" instead of Entrelazamiento, as is written in tha coding?

Thank you so much for your help

[Jongomez]

véase también = see also

[Jongomez]

problem solved, coding:

Code: Select all

\index{Sistemas compuestos!|seealso {Entrelazamiento}}

(name inside brackets.

The only question that remains is that it appears at the beginnig of the entry list instead of appearing at the end(see below in red colour

Sistemas compuestos,
véase también Entrelazamiento
estados mixtos y puros, 106, 110
estados producto, 86–88
observables en, 93–95
producto tensorial, 79–82, 86, 87
representación, 79–81, 85, 86, 93
véase también Entrelazamiento

[Jongomez]

Hi Stephan,
By the way, could you revise this minor problem:
* how can I do to let appear "seealso" at the end of the list?

Thank you,
Jon

[Stefan Kottwitz]

Hi Jon,

I could try to figure it out based on a compilable example. I know it takes time to post a minimal working example for a problem, but imagine how to create a working solution without code.

Stefan

[Jongomez]

Thanks so much. I'll see what I can do. Apart from that, could it be practical to give you accessto my Overleaf projects?

Jon

[Stefan Kottwitz]

My main task is helping with LaTeX while keeping the forum here alive, so I don't go to other sites but I try my best here on LaTeX.org. An Overleaf link may help in a specific situation where it's impossible to post a working code example here, but see it this way: it's a discussion forum here where later also people come in via Google searching for index or font issues and if they only see Overleaf links they don't learn from it or understand a solution.

Threads here start with a well-described problem and end with a working solution so Google users can find it and solve their challenges, too. And if not, they found us here, and post their own question.

Stefan

[Jongomez]

I understand your position and work. Thanks for your precise explanation.
I'll see whether I can prepare some workable code.
Best regards,
Jon