Pushed to staging as

commit 1eed54e8ff4e371d7c4edfed34b1d54c7b159b81
Author: Werner Lemberg <[email protected]>
Date:   Wed Aug 28 20:58:34 2019 +0200

    Issue 5551/2: improve generated documentation
    
    For LilyPond commands, prepend a backslash to the command name
    (in case there isn't already a leading backslash).
    
    Don't emit @funindex and @cindex at the same time.
    
    Don't use @findex but @funindex.

commit 2165edafc50bbd7feaba80467309eed96c7dbd76
Author: Werner Lemberg <[email protected]>
Date:   Wed Aug 28 20:54:03 2019 +0200

    Issue 5551/1: better indexing support
    
    In TeX output mode we unify `@findex', `@cindex', and `@vindex'
    entries in the concept index; this is done with the `@syncodeindex'
    lines in macro `@lilyTitlePage'.  We also set
    `txiindexbackslashignore' so that `\foo' gets sorted as `foo'.
    However, the latter directive has the side effect that `\foo' and
    `foo' are treated as equal by the index sorting program.  We don't
    want that: It is important for us that entries for both `\foo' and
    `foo' appear in the unified index.
    
    For this reason, we make macro `@funindex' use `@sortas' to set a
    special sorting key, and we redefine texinfo's internal macro
    `\indexwritesortas' to swallow backslashes.  We also modify
    `@cindex' to insert another sorting key to ensure that `\foo'
    immediately comes after `foo', followed by entries like `foo bar'.
    
    (Note that HTML output is not improved by this change since the
    ancient texi2html version we have to use doesn't support `@sortas'.)
    
    Also add option `-8bit' to xe(la)tex to get real 8bit characters in
    auxiliary index files.
    
    Also emit `@vindex' entries as slanted; explain this in
    `notation.tely'.



---

** [issues:#5551] Improve generated documentation.**

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Wed Aug 28, 2019 07:04 PM UTC by Werner LEMBERG
**Last Updated:** Tue Sep 03, 2019 02:34 PM UTC
**Owner:** Werner LEMBERG


Improve generated documentation.
--------------------------------

For LilyPond commands, prepend a backslash to the command name.

Don't emit `@funindex` and `@cindex` at the same time.

Don't use `@findex` but `@funindex`.

Better indexing support.
------------------------

In TeX output mode we unify `@findex`, `@cindex`, and `@vindex`
entries in the concept index; this is done with the `@syncodeindex`
lines in macro `@lilyTitlePage`.  We also set
`txiindexbackslashignore` so that `\foo` gets sorted as 'foo'.
However, the latter directive has the side effect that `\foo` and
'foo' are treated as equal by the index sorting program.  We don't
want that: It is important for us that entries for both `\foo` and
'foo' appear in the unified index.

For this reason, we make macro `@funindex` use `@sortas` to set a
special sorting key, and we redefine texinfo's internal macro
`\indexwritesortas` to swallow backslashes.  We also modify
`@cindex` to insert another sorting key to ensure that `\foo`
immediately comes after `foo`, followed by entries like 'foo bar'.

Also add option `-8bit` to xe(la)tex to get real 8bit characters in
auxiliary index files.

http://codereview.appspot.com/573000044


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to