Re: Upgrading to current makeinfo

2020-03-16 Thread Werner LEMBERG
>> [*] Currently, HTML output is handled by an ancient version of >> `texi2html' that doesn't understand `@sortas' at all; I'm going >> to add a dummy macro replacement to fix that. As a >> consequence, the index of the HTML output will stay inferior to >> both the info and PDF v

Re: Upgrading to current makeinfo

2020-03-15 Thread Jean-Charles Malahieude
Le 14/03/2020 à 21:34, Torsten Hämmerle a écrit : Apart from the fact that it's super-inelegant, you can use raw code within your @ifhtml branch to get a real superscript even in HTML, as in: … and fastidious in matter of typing,and don't forget to add a space before the next word: @ifnothtm

Re: Upgrading to current makeinfo

2020-03-14 Thread Torsten Hämmerle
Jean-Charles Malahieude-2 wrote > Furthermore, texi2html doesn't honor French typographic rules regarding > ordinals: you can't use @sup{letter} like 1^er for 1st and I have to type > > @ifnothtml > 256@sup{e}, 512@sup{e} et 1024@sup{e} > @end ifnothtml > @ifhtml > 256e, 512e et 1024e > @end ifht

Re: Upgrading to current makeinfo

2020-03-14 Thread Jean-Charles Malahieude
Le 31/08/2019 à 21:11, Werner LEMBERG a écrit : To have both `!' and `\!' (and similar `\foo' command and `foo' property entries) in the index of the info and PDF version of the NR it is necessary to tag corresponding entries with `@sortas' directives[*] https://sourceforge.net/p/testlilyiss

Upgrading to current makeinfo

2019-08-31 Thread Werner LEMBERG
To have both `!' and `\!' (and similar `\foo' command and `foo' property entries) in the index of the info and PDF version of the NR it is necessary to tag corresponding entries with `@sortas' directives[*] https://sourceforge.net/p/testlilyissues/issues/5551/ https://sourceforge.net/p/testli