Csound Csound-dev Csound-tekno Search About

[Cs-dev] TOC Rendering problem in frames version of manual

Date2013-10-12 02:21
FromForrest Cahoon
Subject[Cs-dev] TOC Rendering problem in frames version of manual
AttachmentsNone  None  
When I look at the frames version of the manual at http://www.csounds.com/manual/html/indexframes.html in Iceweasel (debian version of Firefox), the contents on the left hand side have a rendering problem: at dumpk4, the opcodes are no longer links, and no longer on separate lines -- an error which persists to the end of the opcode section.

I looked at the contents of contents.html and I found that Iceweasel was getting confused by the tag <font size="2"/> on every opcode line.  It didn't like <font size="2" /> either, but when I tried <font size="2"></font> the table of contents rendered correctly.

Of course, those tags could simply be removed instead, since they don't do anything.

I know this is done in the docbook xsl, but I haven't gone so far as to look at that -- I'm hoping someone who knows about this stuff can just tweak one line.

Forrest


Date2013-10-12 02:29
FromAndres Cabrera
SubjectRe: [Cs-dev] TOC Rendering problem in frames version of manual
AttachmentsNone  None  
Hi,

I recently fixed this in git, but the fixed version hasn't been uploaded. If anyone gives me details of how to upload, I can do it.

Cheers,
Andrés


On Fri, Oct 11, 2013 at 6:21 PM, Forrest Cahoon <forrest.cahoon@gmail.com> wrote:
When I look at the frames version of the manual at http://www.csounds.com/manual/html/indexframes.html in Iceweasel (debian version of Firefox), the contents on the left hand side have a rendering problem: at dumpk4, the opcodes are no longer links, and no longer on separate lines -- an error which persists to the end of the opcode section.

I looked at the contents of contents.html and I found that Iceweasel was getting confused by the tag <font size="2"/> on every opcode line.  It didn't like <font size="2" /> either, but when I tried <font size="2"></font> the table of contents rendered correctly.

Of course, those tags could simply be removed instead, since they don't do anything.

I know this is done in the docbook xsl, but I haven't gone so far as to look at that -- I'm hoping someone who knows about this stuff can just tweak one line.

Forrest


------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel