git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH 2/8] docbook: improve css style

From
Jeff King <peff@peff.net>
Date
Mar 24, 2009, 08:42 UTC
Message-ID
<20090324084236.GC660@coredump.intra.peff.net>
In-Reply-To
<94a0d4530903231720r620e44fu90dd77a3231bd4d1@mail.gmail.com>
On Tue, Mar 24, 2009 at 02:20:13AM +0200, Felipe Contreras wrote:
> I've updated the CSS. Can you take a look again?
> 
> I changed the font-size to normal, except for the code chunks. Also, I

Well, it looks better to me, in that the body text isn't small and scrunched. The code chunks are, of course, noticeably smaller. I really don't see what you're trying to accomplish with that. Are you trying to make it fit into browsers where we are somehow wrapping in the code chunks?

> changed the font of the in-paragrah code tags to sans-serif, that's
> the most sane way I can think to fix the problem with different
> font-size configured for monospace font.

Hrm. I'm not sure that is particularly sane. You have the style for a <tt> tag rendering as a sans-serif font. But the _definition_ of tt is to render as a monospace font.

As it happens, there are no <tt> tags at all in the document, so that change is irrelevant (and I wonder if we should ditch the tt.literal specifier entirely). But I tend to think that <code> tags generally follow the same principle. Looking over the document, I didn't find anything that looked broken by it (at least in Firefox using my set of fonts). But it just seems counterintuitive.

If you are unsatisfied with the size of the text in <code> blocks, can't you set some variant of an em (e.g., 1.1em)?

Looking at all of these <code> examples did make me notice one thing: there are some special characters used that are probably counterintuitive. For instance, "--not" is rendered with a single long dash instead of two short dashes. A code snippet has a right-arrow character instead of "->". I assume this is asciidoc trying to be clever, but I haven't looked into it.

-Peff
Previous: Felipe ContrerasNext: Jeff King
Message 23 of 40 in “user-manual: style improvements”
  1. 0/8 user-manual: style improvementsFelipe Contreras, Mar 22, 2009
  2. 1/8 user-manual: remove some git-foo usageFelipe Contreras, Mar 22, 2009
  3. 2/8 docbook: improve css styleFelipe Contreras, Mar 22, 2009
  4. 3/8 docbook: radical style changeFelipe Contreras, Mar 22, 2009
  5. Jeff KingMar 23, 2009
  6. Felipe ContrerasMar 23, 2009
  7. Jeff KingMar 23, 2009
  8. Felipe ContrerasMar 23, 2009
  9. Michael J GruberMar 23, 2009
  10. Felipe ContrerasMar 24, 2009
  11. Junio C HamanoMar 24, 2009
  12. Felipe ContrerasMar 24, 2009
  13. Jeff KingMar 24, 2009
  14. Felipe ContrerasMar 24, 2009
  15. Jeff KingMar 24, 2009
  16. Felipe ContrerasMar 24, 2009
  17. Michael J GruberMar 24, 2009
  18. Felipe ContrerasMar 24, 2009
  19. Jeff KingMar 24, 2009
  20. Michael J GruberMar 24, 2009
  21. Felipe ContrerasMar 24, 2009
  22. Felipe ContrerasMar 24, 2009
  23. Jeff KingMar 24, 2009
  24. Jeff KingMar 23, 2009
  25. Felipe ContrerasMar 23, 2009
  26. 5/8 user-manual: use 'fast-forward' instead of 'fast forward'Felipe Contreras, Mar 22, 2009
  27. 6/8 user-manual: use SHA-1 instead of SHA1 or sha1Felipe Contreras, Mar 22, 2009
  28. 7/8 user-manual: add global config sectionFelipe Contreras, Mar 22, 2009
  29. 8/8 user-manual: simplify the user configurationFelipe Contreras, Mar 22, 2009
  30. Wincent ColaiutaMar 22, 2009
  31. Felipe ContrerasMar 22, 2009
  32. Junio C HamanoMar 23, 2009
  33. Felipe ContrerasMar 23, 2009
  34. Wincent ColaiutaMar 23, 2009
  35. Felipe ContrerasMar 23, 2009
  36. Wincent ColaiutaMar 23, 2009
  37. Felipe ContrerasMar 24, 2009
  38. J. Bruce FieldsMar 24, 2009
  39. Felipe ContrerasMar 24, 2009
  40. J. Bruce FieldsMar 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.