Re: Texinfo indexing
Jean-Charles Malahieude writes: > Le 14/06/2016 à 10:47, David Kastrup a écrit : >>> >>> Huh, I have to try. I just remember that we likely are still using >>> texi2html for our web page generation, and I have no idea how _that_ >>> does the indexing. If we can only create better sorted indices for PDF >>> and/or Info, that would be sort of a let-down. >> >> A cursory glance would suggest that the following commands are entered >> both with and without backslash via @funindex: >> >> \accepts >> [...] >> > > This one appears only once, labeled "\accepts" with notation.pdf. Documentation/de/notation/changing-defaults.itely:@funindex \accepts Documentation/de/notation/changing-defaults.itely:@funindex accepts Documentation/de/notation/changing-defaults.itely:@funindex \accepts Documentation/de/notation/changing-defaults.itely:@funindex accepts Documentation/de/notation/changing-defaults.itely:@funindex \accepts Documentation/es/notation/changing-defaults.itely:@funindex \accepts Documentation/es/notation/changing-defaults.itely:@funindex accepts Documentation/es/notation/changing-defaults.itely:@funindex \accepts Documentation/es/notation/changing-defaults.itely:@funindex \accepts Documentation/fr/notation/changing-defaults.itely:@funindex \accepts Documentation/fr/notation/changing-defaults.itely:@funindex accepts Documentation/fr/notation/changing-defaults.itely:@funindex \accepts Documentation/fr/notation/changing-defaults.itely:@funindex \accepts Documentation/it/notation/changing-defaults.itely:@funindex \accepts Documentation/it/notation/changing-defaults.itely:@funindex accepts Documentation/it/notation/changing-defaults.itely:@funindex \accepts Documentation/it/notation/changing-defaults.itely:@funindex \accepts Documentation/ja/notation/changing-defaults.itely:@funindex \accepts Documentation/ja/notation/changing-defaults.itely:@funindex accepts Documentation/ja/notation/changing-defaults.itely:@funindex \accepts Documentation/ja/notation/changing-defaults.itely:@funindex \accepts Documentation/notation/changing-defaults.itely:@funindex \accepts Documentation/notation/changing-defaults.itely:@funindex accepts Documentation/notation/changing-defaults.itely:@funindex \accepts Documentation/notation/changing-defaults.itely:@funindex \accepts > Even more, there is only one target (so to say only one place where > both versions are mentioned) for "accepts" vs 3 targets when > @set txiindexbackslashignore > is specified in common-macros.itexi. > > BTW this make a 6 pages less volume. > > If texi2any follows the same rule, it would be the same, I guess for > the HTML version. For the moment I'm still stuck withe the same errors > and unable to dig further in the switch from texi2html that, sooner or > later, will disappear from distros. Sigh. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Texinfo indexing
Le 14/06/2016 à 10:47, David Kastrup a écrit : Huh, I have to try. I just remember that we likely are still using texi2html for our web page generation, and I have no idea how _that_ does the indexing. If we can only create better sorted indices for PDF and/or Info, that would be sort of a let-down. A cursory glance would suggest that the following commands are entered both with and without backslash via @funindex: \accepts [...] This one appears only once, labeled "\accepts" with notation.pdf. Even more, there is only one target (so to say only one place where both versions are mentioned) for "accepts" vs 3 targets when @set txiindexbackslashignore is specified in common-macros.itexi. BTW this make a 6 pages less volume. If texi2any follows the same rule, it would be the same, I guess for the HTML version. For the moment I'm still stuck withe the same errors and unable to dig further in the switch from texi2html that, sooner or later, will disappear from distros. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
musicxml2ly: AttributeError: PartGroupInfo instance has no attribute 'set_part_information'
Hello list, I get this traceback trying to convert the Reunion demo score from MuseScore: musicxml2ly: Reading MusicXML from Reunion.xml ... musicxml2ly: Converting to LilyPond expressions... musicxml2ly: Converting to LilyPond expressions... musicxml2ly: Converting to LilyPond expressions... musicxml2ly: Converting to LilyPond expressions... musicxml2ly: Converting to LilyPond expressions... musicxml2ly: Converting to LilyPond expressions... Traceback (most recent call last): File "/usr/bin/musicxml2ly", line 2986, in main() File "/usr/bin/musicxml2ly", line 2981, in main voices = convert (filename, options) File "/usr/bin/musicxml2ly", line 2896, in convert update_score_setup (score, part_list, voices) File "/usr/bin/musicxml2ly", line 2794, in update_score_setup score_structure.set_part_information (part_id, staves_info) File "/usr/share/lilypond/2.19.43/python/musicexp.py", line 1941, in set_part_information self.contents.set_part_information (part_id, staves_info) File "/usr/share/lilypond/2.19.43/python/musicexp.py", line 1780, in set_part_information c.set_part_information (part_name, staves_info) AttributeError: PartGroupInfo instance has no attribute 'set_part_information' The MusicXML file is available here: https://musescore.com/marcsabatella/reunion I haven't been able to reproduce this myself with a smaller score, but Reunion works if I remove these lines: brace That bit seems to be redundant anyway in this case according to the MusicXML specification, although it doesn't seem to be wrong either. If I add a stub set_staff_information method to PartGroupInfo it also works but I get this warning instead: musicxml2ly: warning: Unprocessed PartGroupInfo <__main__.PartGroupInfo instance at ...> encountered Maybe this is a bug in the score, or in MuseScore's MusicXML exporter? Even so, musicxml2ly could perhaps handle faulty scores more gracefully than a traceback or obscure warning. It doesn't look like a bug in the XML to me, though. I ran it against the schema and it only complained about something unrelated: The 'dynamics' attribute is invalid - The value '-1.11' is invalid according to its datatype 'non-negative-decimal' - The MinInclusive constraint failed. (which in deed seems to be an error and probably a bug in MuseScore.) Cheers, Dag ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly: AttributeError: PartGroupInfo instance has no attribute 'set_part_information'
Sorry, I utterly failed to mention that I'm on LilyPond 2.19.43. Tested both with the binaries from the website and the Fedora 23 package. On Tue, Jun 14, 2016 at 7:11 PM, Dag Odenhall wrote: > Hello list, > > I get this traceback trying to convert the Reunion demo score from > MuseScore: > > musicxml2ly: Reading MusicXML from Reunion.xml ... > musicxml2ly: Converting to LilyPond expressions... > musicxml2ly: Converting to LilyPond expressions... > musicxml2ly: Converting to LilyPond expressions... > musicxml2ly: Converting to LilyPond expressions... > musicxml2ly: Converting to LilyPond expressions... > musicxml2ly: Converting to LilyPond expressions... > Traceback (most recent call last): > File "/usr/bin/musicxml2ly", line 2986, in > main() > File "/usr/bin/musicxml2ly", line 2981, in main > voices = convert (filename, options) > File "/usr/bin/musicxml2ly", line 2896, in convert > update_score_setup (score, part_list, voices) > File "/usr/bin/musicxml2ly", line 2794, in update_score_setup > score_structure.set_part_information (part_id, staves_info) > File "/usr/share/lilypond/2.19.43/python/musicexp.py", line 1941, in > set_part_information > self.contents.set_part_information (part_id, staves_info) > File "/usr/share/lilypond/2.19.43/python/musicexp.py", line 1780, in > set_part_information > c.set_part_information (part_name, staves_info) > AttributeError: PartGroupInfo instance has no attribute > 'set_part_information' > > The MusicXML file is available here: > https://musescore.com/marcsabatella/reunion > > I haven't been able to reproduce this myself with a smaller score, but > Reunion works if I remove these lines: > > > brace > > > That bit seems to be redundant anyway in this case according to the > MusicXML specification, although it doesn't seem to be wrong either. > > If I add a stub set_staff_information method to PartGroupInfo it also > works but I get this warning instead: > > musicxml2ly: warning: Unprocessed PartGroupInfo <__main__.PartGroupInfo > instance at ...> encountered > > Maybe this is a bug in the score, or in MuseScore's MusicXML exporter? > Even so, musicxml2ly could perhaps handle faulty scores more gracefully > than a traceback or obscure warning. It doesn't look like a bug in the XML > to me, though. I ran it against the schema and it only complained about > something unrelated: > > The 'dynamics' attribute is invalid - The value '-1.11' is invalid > according to its datatype 'non-negative-decimal' - The MinInclusive > constraint failed. > > (which in deed seems to be an error and probably a bug in MuseScore.) > > Cheers, > Dag > ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Texinfo indexing
On 13/06/16 12:00, David Kastrup wrote:
In my current Texinfo manual I read:
For the printed output, you may specify an explicit sort key for an
index entry using '@sortas' immediately following the index command.
For example: '@findex @sortas{\} \ @r{(literal \ in @code{@@math})'
sorts the index entry this produces under backslash.
To reduce the quantity of sort keys you need to provide explicitly,
you may choose to ignore certain characters in index entries for the
purposes of sorting. The characters that you can currently choose to
ignore are '\', '-', '<' and '@', which are ignored by giving as an
argument to the '@set' command, respectively, 'txiindexbackslashignore',
'txiindexhyphenignore', 'txiindexlessthanignore' and
'txiindexatsignignore'. For example, specifying '@set
txiindexbackslashignore' causes the '\mathopsup' entry in the index for
this manual to be sorted as if it were 'mathopsup', so that it appears
among the other entries beginning 'M'.
Now obviously this might _finally_ make it possible for us to clean up
indexing and have entries like \tweak sorted under "t" while the index
entry properly is '\tweak'.
I don't know to what degree the HTML index would be affected. This
would require a reasonably recent version of Texinfo and/or texinfo.tex.
I believe that Gub is still stuck at version 4.something because of
efficiency considerations (Texinfo 4 is written in C rather than Perl
and thus faster). This indexing issue, however, might well be a
reasonable incentive to bite the bullet and move to a current Texinfo
version.
Thoughts?
I assume you are meaning this?
https://sourceforge.net/p/testlilyissues/issues/855/
and I think we are using Texi2html.
James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Texinfo indexing
David Kastrup writes: > "Phil Holmes" writes: > >> "Werner LEMBERG" wrote in message >> news:20160614.060033.1990219825710207668...@gnu.org... >>> This indexing issue, however, might well be a reasonable incentive to bite the bullet and move to a current Texinfo version. Thoughts? >>> >>> I support your suggestion. >>> >> >> +1 > > Huh, I have to try. I just remember that we likely are still using > texi2html for our web page generation, and I have no idea how _that_ > does the indexing. If we can only create better sorted indices for PDF > and/or Info, that would be sort of a let-down. A cursory glance would suggest that the following commands are entered both with and without backslash via @funindex: \accepts \acciaccatura \addChordShape \addInstrumentDefinition \addlyrics \addQuote \aeolian \afterGrace \aikenHeads \aikenHeadsMinor \alias \arpeggio \arpeggioArrowDown \arpeggioArrowUp \arpeggioBracket \arpeggioNormal \arpeggioParenthesis \arpeggioParenthesisDashed \arrow-head \ascendens \auctum \autoBeamOff \autoBeamOn \autochange \balloonGrobText \balloonLengthOff \balloonLengthOn \balloonText \bar \barNumberCheck \beamExceptions \bendAfter \bold \book \box \bracket \breathe \breve \cadenzaOff \cadenzaOn \caesura \cavum \center-align \center-column \change \chordmode \circle \clef \column \combine \compressFullBarRests \compressMMRests \consists \context \cr \cresc \crescHairpin \crescTextCresc \cueClef \cueDuring \cueDuringWithClef \decr \decresc \defaultTimeSignature \defineBarLine \deminutum \denies \descendens \dim \dimHairpin \dimTextDecr \dimTextDecresc \dimTextDim \displayLilyMusic \displayMusic \divisioMaior \divisioMaxima \divisioMinima \dorian \dotsDown \dotsNeutral \dotsUp \draw-circle \draw-line \drummode \dynamic \dynamicDown \dynamicNeutral \dynamicUp \easyHeadsOff \easyHeadsOn \epsfile \espressivo \expandFullBarRests \f \featherDurations \fermataMarkup \ff \fff \ \f \filled-box \fill-line \finalis \finger \fixed \fontsize \fp \fret-diagram \fret-diagram-terse \fret-diagram-verbose \funkHeads \funkHeadsMinor \general-align \glissando \grace \halign \harmonic \hbracket \header \hideKeySignature \hideNotes \hideStaffSwitch \huge \improvisationOff \improvisationOn \incipit \inclinatum \instrumentSwitch \inversion \ionian \italic \justified-lines \justify \keepWithTag \key \killCues \laissezVibrer \large \larger \layout \left-align \linea \locrian \longa \lower \lydian \lyricmode \lyricsto \magnify \magnifyMusic \major \makeClusters \mark \markLengthOff \markLengthOn \markup \markuplist \maxima \mergeDifferentlyDottedOff \mergeDifferentlyDottedOn \mergeDifferentlyHeadedOff \mergeDifferentlyHeadedOn \mf \midi \minor \mixolydian \modalInversion \modalTranspose \mp \musicglyph \name \new \noBeam \normalsize \normal-size-super \null \numericTimeSignature \octaveCheck \omit \once \oneVoice \oriscus \ottava \override \overrideProperty \overrideTimeSignatureSettings \p \pad-around \pad-markup \pad-to-box \pad-x \parallelMusic \parenthesize \partcombine \partcombineApart \partcombineAutomatic \partcombineChords \partcombineSoloI \partcombineSoloII \partcombineUnisono \partial \phrasingSlurDashed \phrasingSlurDashPattern \phrasingSlurDotted \phrasingSlurDown \phrasingSlurHalfDashed \phrasingSlurHalfSolid \phrasingSlurNeutral \phrasingSlurSolid \phrasingSlurUp \phrygian \pitchedTrill \postscript \powerChords \pp \ppp \ \p \predefinedFretboardsOff \predefinedFretboardsOn \quilisma \quoteDuring \raise \relative \remove \RemoveEmptyStaves \removeWithTag \repeatTie \rest \retrograde \revert \revertTimeSignatureSettings \rfz \right-align \rightHandFinger \rounded-box \sacredHarpHeads \sacredHarpHeadsMinor \scaleDurations \score \set \sf \sff \sfz \shiftOff \shiftOn \shiftOnn \shiftOnnn \showKeySignature \showStaffSwitch \single \skip \slurDashed \slurDashPattern \slurDotted \slurDown \slurHalfDashed \slurHalfSolid \slurNeutral \slurSolid \slurUp \small \smaller \sostenutoOff \sostenutoOn \southernHarmonyHeads \southernHarmonyHeadsMinor \sp \spp \startGroup \startStaff \startTextSpan \startTrillSpan \stemDown \stemNeutral \stemUp \stopGroup \stopStaff \stopTextSpan \stopTrillSpan \storePredefinedDiagram \stringTuning \stringTunings \stropha \sub \super \sustainOff \sustainOn \tabFullNotation \tag \taor \teeny \tempo \textLengthOff \textLengthOn \textSpannerDown \textSpannerNeutral \textSpannerUp \thumb \tieDashed \tieDotted \tieDown \tieNeutral \tieSolid \tieUp \time \times \tiny \translate \translate-scaled \transpose \transposedCueDuring \transposition \treCorde \triangle \trill \tuplet \tupletDown \tupletNeutral \tupletUp \tweak \type \unaCorda \underline \unHideNotes \unset \virga \virgula \voiceFour \voiceOne \voiceThree \voiceTwo \walkerHeads \walkerHeadsMinor \with \with-color \wordwrap \wordwrap-lines -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-l
Re: Texinfo indexing
"Phil Holmes" writes: > "Werner LEMBERG" wrote in message > news:20160614.060033.1990219825710207668...@gnu.org... >> >>> This indexing issue, however, might well be a reasonable incentive >>> to bite the bullet and move to a current Texinfo version. >>> >>> Thoughts? >> >> I support your suggestion. >> > > +1 Huh, I have to try. I just remember that we likely are still using texi2html for our web page generation, and I have no idea how _that_ does the indexing. If we can only create better sorted indices for PDF and/or Info, that would be sort of a let-down. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Texinfo indexing
"Werner LEMBERG" wrote in message news:20160614.060033.1990219825710207668...@gnu.org... This indexing issue, however, might well be a reasonable incentive to bite the bullet and move to a current Texinfo version. Thoughts? I support your suggestion. Werner +1 -- Phil Holmes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
