Re: documentation: unreadable html tables
On Mon, Oct 26, 2009 at 07:18:54AM -0700, -Eluze wrote: > > Graham Percival-3 wrote: > > The languages involved are perl, texinfo, and html. In > > particular, the documentation is written in texinfo; a perl script > > (called texi2html) interprets the texinfo files, and outputs html. > > > i have some experience with html; texinfo and perl are fully new to me! > furthermore i am working on windows - hope this is not a problem!? Working on windows will be no problem. > > The first step is to reproduce the problem in a small example. > > Try making a tiny texinfo file, which contains the same kind of > > table as in pitches.itely. I think it's a @multitable, but I'm > > not 100% certain. > > i will need to know where i can download this file from! Please see the Contributor's Guide, particularly the section about windows git. > altogether i think it will take me some time to get familiar with these new > components and surroundings! > if anybody could advise a practical tutorial both for texinfo and perl this > could help a lot. You don't need a lot of texinfo; a seven-line file should be fine for your testing. As for perl, there are many tutorials on the internet devoted to it. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation: unreadable html tables
Graham Percival-3 wrote: > > The languages involved are perl, texinfo, and html. In > particular, the documentation is written in texinfo; a perl script > (called texi2html) interprets the texinfo files, and outputs html. > i have some experience with html; texinfo and perl are fully new to me! furthermore i am working on windows - hope this is not a problem!? > The first step is to reproduce the problem in a small example. > Try making a tiny texinfo file, which contains the same kind of > table as in pitches.itely. I think it's a @multitable, but I'm > not 100% certain. > i will need to know where i can download this file from! > > Verify that running texi2html 1.82 on your tiny texinfo file > produces the bad output. Then have a look at the output and see > what exactly you want to change -- is it just removing the > tags? Would it look better if there was some attribute > being set? etc. > > Then you need to figure out how to get texi2html to produce the > output you want to see. As it happens, texi2html is relatively > easy to extend (it's in perl, you can replace any of its built-in > fuctions easily, etc). We *could* just add a special "overriding" > function to our texi2html init script, but in this case I'd > recommend getting your fix integrated into texi2html itself. This > won't help us with 1.82, but when texi2html 1.84 comes out, it'll > have the fix. > > > I really hope that you'll take this up; we could really use > somebody who's familiar with texi2html. We have a few problems > with our texi2html init scripts, and there's other parts of those > scripts that work well, but I think other texi2html users could > benefit from (like the sectioning-by-numbers), so it would be nice > if we could send a patch for this upstream. > altogether i think it will take me some time to get familiar with these new components and surroundings! if anybody could advise a practical tutorial both for texinfo and perl this could help a lot. > If you're not familiar with perl... well, it's not as easy to > learn as python, but I'd still say that it's on the "easy" side of > programming languages. It's much easier than scheme! :) > > Cheers, > - Graham > cheers -Eluze -- View this message in context: http://www.nabble.com/documentation%3A-unreadable-html-tables-tp26037552p26060704.html Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation: unreadable html tables
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Sonntag, 25. Oktober 2009 15:59:45 schrieb Graham Percival: > The languages involved are perl, texinfo, and html. In > particular, the documentation is written in texinfo; a perl script > (called texi2html) interprets the texinfo files, and outputs html. > > The first step is to reproduce the problem in a small example. > Try making a tiny texinfo file, which contains the same kind of > table as in pitches.itely. I think it's a @multitable, but I'm > not 100% certain. Yes it is. > Verify that running texi2html 1.82 on your tiny texinfo file > produces the bad output. FWIW, I was unable to produce the bad output with a small @multitable testcase using texi2html 1.81 and with 1.83... Maybe I'm missing some global settings (or it is caused by our .init script ?) There was a problem with multitables inside a @quotation enviroment ( was wrapped around the contents of each cell), but that was fixed a while agot by Patrice in texi2html. Cheers, Reinhold - -- - -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFK5JtWTqjEwhXvPN0RAk4mAJ93+AgJFuYKR7zS3KszVVl/9JNpkgCfUW1z XGAhwrQjbtfLAc2tghX8rik= =VY8r -END PGP SIGNATURE- ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation: unreadable html tables
The languages involved are perl, texinfo, and html. In particular, the documentation is written in texinfo; a perl script (called texi2html) interprets the texinfo files, and outputs html. The first step is to reproduce the problem in a small example. Try making a tiny texinfo file, which contains the same kind of table as in pitches.itely. I think it's a @multitable, but I'm not 100% certain. Verify that running texi2html 1.82 on your tiny texinfo file produces the bad output. Then have a look at the output and see what exactly you want to change -- is it just removing the tags? Would it look better if there was some attribute being set? etc. Then you need to figure out how to get texi2html to produce the output you want to see. As it happens, texi2html is relatively easy to extend (it's in perl, you can replace any of its built-in fuctions easily, etc). We *could* just add a special "overriding" function to our texi2html init script, but in this case I'd recommend getting your fix integrated into texi2html itself. This won't help us with 1.82, but when texi2html 1.84 comes out, it'll have the fix. I really hope that you'll take this up; we could really use somebody who's familiar with texi2html. We have a few problems with our texi2html init scripts, and there's other parts of those scripts that work well, but I think other texi2html users could benefit from (like the sectioning-by-numbers), so it would be nice if we could send a patch for this upstream. If you're not familiar with perl... well, it's not as easy to learn as python, but I'd still say that it's on the "easy" side of programming languages. It's much easier than scheme! :) Cheers, - Graham On Sat, Oct 24, 2009 at 01:43:41PM -0700, -Eluze wrote: > > no idea if i have enough skills in any of the languages involved (i do not > even know which they are!) > > but if you'd take the risk i would try! pls let me know how to proceed! > > > > Graham Percival-3 wrote: > > > > Unfortunately, I don't think anybody is available to look into > > this. If you could start working on a patch to fix this issue, > > we'd be happy to help you work on this. > > > > Cheers, > > - Graham > > > > On Sat, Oct 24, 2009 at 02:49:54AM -0700, -Eluze wrote: > >> > >> imo tables in the documentation are hardly readable because they > >> > >> - are wasting a lot of space so that you have to sroll around to try to > >> get > >> an overview of the table > >> - have no borders so that your eyes have to try to reconstruct columns > >> - have columns of different widths even if the contents are comparable > >> > >> i am not sure if it is - partially - a problem of my browser (i am using > >> opera) or if it could be improved by more appropriate settings or styles. > >> > >> i had a short look at the source of the table > >> http://lilypond.org/doc/v2.13/Documentation/music-glossary/Pitch-names#Pitch-names > >> pitch names and noticed that and is placed around the content > >> of > >> each cell which might cause the waste of vertical space. this table has > >> only > >> 20 real rows (without the header) but needs scrolling over more than 2 > >> pages > >> on my display. > >> > >> it would be nice if such tables could be rendered in a more compact way - > >> thanks! > >> -- > >> View this message in context: > >> http://www.nabble.com/documentation%3A-unreadable-html-tables-tp26037552p26037552.html > >> Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. > >> > >> > >> > >> ___ > >> lilypond-devel mailing list > >> lilypond-devel@gnu.org > >> http://lists.gnu.org/mailman/listinfo/lilypond-devel > > > > > > ___ > > lilypond-devel mailing list > > lilypond-devel@gnu.org > > http://lists.gnu.org/mailman/listinfo/lilypond-devel > > > > > > -- > View this message in context: > http://www.nabble.com/documentation%3A-unreadable-html-tables-tp26037552p26042896.html > Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. > > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation: unreadable html tables
no idea if i have enough skills in any of the languages involved (i do not even know which they are!) but if you'd take the risk i would try! pls let me know how to proceed! Graham Percival-3 wrote: > > Unfortunately, I don't think anybody is available to look into > this. If you could start working on a patch to fix this issue, > we'd be happy to help you work on this. > > Cheers, > - Graham > > On Sat, Oct 24, 2009 at 02:49:54AM -0700, -Eluze wrote: >> >> imo tables in the documentation are hardly readable because they >> >> - are wasting a lot of space so that you have to sroll around to try to >> get >> an overview of the table >> - have no borders so that your eyes have to try to reconstruct columns >> - have columns of different widths even if the contents are comparable >> >> i am not sure if it is - partially - a problem of my browser (i am using >> opera) or if it could be improved by more appropriate settings or styles. >> >> i had a short look at the source of the table >> http://lilypond.org/doc/v2.13/Documentation/music-glossary/Pitch-names#Pitch-names >> pitch names and noticed that and is placed around the content >> of >> each cell which might cause the waste of vertical space. this table has >> only >> 20 real rows (without the header) but needs scrolling over more than 2 >> pages >> on my display. >> >> it would be nice if such tables could be rendered in a more compact way - >> thanks! >> -- >> View this message in context: >> http://www.nabble.com/documentation%3A-unreadable-html-tables-tp26037552p26037552.html >> Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. >> >> >> >> ___ >> lilypond-devel mailing list >> lilypond-devel@gnu.org >> http://lists.gnu.org/mailman/listinfo/lilypond-devel > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel > > -- View this message in context: http://www.nabble.com/documentation%3A-unreadable-html-tables-tp26037552p26042896.html Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: documentation: unreadable html tables
Unfortunately, I don't think anybody is available to look into this. If you could start working on a patch to fix this issue, we'd be happy to help you work on this. Cheers, - Graham On Sat, Oct 24, 2009 at 02:49:54AM -0700, -Eluze wrote: > > imo tables in the documentation are hardly readable because they > > - are wasting a lot of space so that you have to sroll around to try to get > an overview of the table > - have no borders so that your eyes have to try to reconstruct columns > - have columns of different widths even if the contents are comparable > > i am not sure if it is - partially - a problem of my browser (i am using > opera) or if it could be improved by more appropriate settings or styles. > > i had a short look at the source of the table > http://lilypond.org/doc/v2.13/Documentation/music-glossary/Pitch-names#Pitch-names > pitch names and noticed that and is placed around the content of > each cell which might cause the waste of vertical space. this table has only > 20 real rows (without the header) but needs scrolling over more than 2 pages > on my display. > > it would be nice if such tables could be rendered in a more compact way - > thanks! > -- > View this message in context: > http://www.nabble.com/documentation%3A-unreadable-html-tables-tp26037552p26037552.html > Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. > > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
documentation: unreadable html tables
imo tables in the documentation are hardly readable because they - are wasting a lot of space so that you have to sroll around to try to get an overview of the table - have no borders so that your eyes have to try to reconstruct columns - have columns of different widths even if the contents are comparable i am not sure if it is - partially - a problem of my browser (i am using opera) or if it could be improved by more appropriate settings or styles. i had a short look at the source of the table http://lilypond.org/doc/v2.13/Documentation/music-glossary/Pitch-names#Pitch-names pitch names and noticed that and is placed around the content of each cell which might cause the waste of vertical space. this table has only 20 real rows (without the header) but needs scrolling over more than 2 pages on my display. it would be nice if such tables could be rendered in a more compact way - thanks! -- View this message in context: http://www.nabble.com/documentation%3A-unreadable-html-tables-tp26037552p26037552.html Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
