Web: Bolder links in Manuals page

[Trevor Daniels]

Hi Graham

I've just pushed a fix for another TODO in web/manuals.itexi

@c TODO: do we want these links to be in larger text / bold ? 
CSS.


The fix makes the links bold, and they certainly look better, IMO,
but the fix is very messy due to the the way @spanClass has been
implemented - it generates  ..  tags if newlines appear in
certain places.  I've indicated where newlines have to be avoided
in the itexi file.

I'm not very happy with the fix, but it works and removes another
item in critical issue 958.  Sorting it out properly would take me
more time than is justified, even if I could.

I said earlier


The remaining TODOs and FIXMEs are fairly
straightforward, I think.


I should have known by now that nothing in LP is straightforward,
especially something you in particular left as a TODO ;)

One more to go in 958...

Trevor




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Web: Bolder links in Manuals page

[Graham Percival]

On Sat, Aug 07, 2010 at 06:54:25PM +0100, Trevor Daniels wrote:
> Hi Graham
>
> I've just pushed a fix for another TODO in web/manuals.itexi
>
>> @c TODO: do we want these links to be in larger text / bold ? CSS.

Woah there -- that's a question, not a command!  I was wondering if
the css should contain something like
a href {
  font-weight: bold;
}
, not suggesting that the single manuals.html page contain bolder
links than any other page!

> I'm not very happy with the fix, but it works and removes another
> item in critical issue 958.

I think I generally used the following interpretations:
FIXME: must be resolved before 2.14.
@help: must be resolved, and can be done by a frog.
TODO: would be nice to do.

Also, note that 958 actually says "if it's a build issue, add it
to the tracker".


The overall intent of 958 was to examine all of those commends in
web, and remove the comments by either writing text, reading
oldweb+revising new web, or by adding stuff to the tracker.

> Sorting it out properly would take me
> more time than is justified, even if I could.

I'm sorry that my poor communication made you work on a weird
solution... I don't know if we want to keep the @spanClass stuff
on that page.

Sorry,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel