You're right about CSS selectors; the simple fix for this without re-
generating any source, is just to instruct the browser to not double
up on the indentation when it sees a ul nested in a blockquote. Hey
wait, the problem is already fixed. Looks great today. The lists
too; thanks for the
Hi,
There are some sphinx system messages on:
http://www.sqlalchemy.org/docs/sphinxtest/intro.html
Reference Documentation¶
*
System Message: WARNING/2
(/home/classic/dev/sphinx/doc/build/intro.rst)
undefined label: datamapping – if you don't give a link
caption
The searching is a bit weird.
If I search for Adjacency I get no results. If I search for adjacency
(all lower case) I get results, the first of which has an upper-cased
Adjacency.
Otherwise they look nice and I'm sure will look nicer-yet as time goes on!
--
Jon
well we have no control over any of thatI don't know that Sphinx
search uses case insensitivity for full text searches.
On Dec 5, 2008, at 11:53 AM, Jon Nelson wrote:
The searching is a bit weird.
If I search for Adjacency I get no results. If I search for adjacency
(all lower case)
Mike,
Gaetan's right -- I just viewed the site a day after you (Mike) said
that the li issue had been fixed, but they're still too widely
spaced for sure. There are several conflicting (well ok, inheriting/
overriding) settings of line-height across the various css files, and
it does not appear
Forgot to add that I can't see much reason for links to be given a
line-height that would be any different from the text that surrounds
them -- at least not on the TOC page. That's why I felt free to scrap
the 'a' rule and put the 'li li' in the same spot. If the 'a' rule is
necessary for other
Oh yeah, and in Main Documentation (at least) you have some ul
class=simple lists nested inside of blockquote elements, which is
resulting in some of your lists being much farther indented than
others, without a good visual reason why. Seems like the difference
could be eliminated.
I sent new
Here are the suggestions that come to mind:
- You should either get rid of, or (preferably) expand/replace the
current top-level table of contents. As it is currently, there is
only one useful link in there (API reference) and the table of
contents block waste way too much space for just one
On Dec 4, 2008, at 4:21 AM, Gaetan de Menten wrote:
Here are the suggestions that come to mind:
- You should either get rid of, or (preferably) expand/replace the
current top-level table of contents. As it is currently, there is
only one useful link in there (API reference) and the table
I've made all of these changes up on the site. The li issue was a
pixel-based padding already so I just reduced that.
On Dec 4, 2008, at 9:25 AM, Michael Bayer wrote:
On Dec 4, 2008, at 4:21 AM, Gaetan de Menten wrote:
Here are the suggestions that come to mind:
- You should either
10 matches
Mail list logo
