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
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
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...
mus
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:
>
> mu
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{@@ma
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.
Tho
"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 sugges
"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