- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -3,29 +3,29 @@
 
 For LilyPond commands, prepend a backslash to the command name.
 
-Don't emit @funindex and @cindex at the same time.
+Don't emit `@funindex` and `@cindex` at the same time.
 
-Don't use @findex but @funindex.
+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.
+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
+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'.
+`\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
+Also add option `-8bit` to xe(la)tex to get real 8bit characters in
 auxiliary index files.
 
 http://codereview.appspot.com/573000044

~~~~

- **Needs**:  -->  



---

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

**Status:** Started
**Created:** Wed Aug 28, 2019 07:04 PM UTC by Werner LEMBERG
**Last Updated:** Wed Aug 28, 2019 07:04 PM UTC
**Owner:** nobody


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