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

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

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 24, 2009, 08:29 UTC
Message-ID
<49C899E1.6060809@drmicha.warpmail.net>
In-Reply-To
<94a0d4530903231721i2a2a6fc1yf54d4303283ec415@mail.gmail.com>
Felipe Contreras venit, vidit, dixit 24.03.2009 01:21:
Show 30 quoted lines
> On Mon, Mar 23, 2009 at 5:20 PM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> Felipe Contreras venit, vidit, dixit 23.03.2009 11:31:
>>> On Mon, Mar 23, 2009 at 8:42 AM, Jeff King <peff@peff.net> wrote:
>>>> On Sun, Mar 22, 2009 at 08:05:15PM +0200, Felipe Contreras wrote:
>>>>
>>>>>  tt.literal, code.literal {
>>>>>    color: navy;
>>>>> +  font-size: 1em;
>>>>> +}
>>>>
>>>> Isn't 1em already the default size? Or are you trying to override some
>>>> other size specification elsewhere? It's hard to tell what the goal is
>>>> because your commit message merely says "improve".
>>>
>>> That's correct.
>>>
>>> The problem is that when the user has a different size for the
>>> sans-serif and monospace fonts it looks horrible when they are on the
>>> same paragraph. I thought 1em did the trick, but you are right, it
>>> doesn't.
>>>
>>> It looks like the only way to fix this is to set absolute sizes.
>>>
>>
>> Also, it seems that everything which is not black is blue, except for
>> terms, which are green and slanted. I don't think that looks nice
>> together. How about slanted blue?
> 
> What's wrong with having 2 colors?

I don't mind having 2, they just don't look good together over here, on my screen and to my eyes...

Right now we have "plain old asciidoc look" which doesn't look that old after all. You pointed out a deficiency, and I'm all for fixing it. I just think that introducing new colors is something that may require a ground up rethinking of the theme being used: make it informative but unobtrusive. Also, I'm against over-emphasizing: use slanted or a specific color, but not both. Unless one color means emphasizing and slanted means file, for example.

Michael
Previous: Felipe ContrerasNext: Felipe Contreras
Message 17 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.