emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Colors for pre elem. on orgmode.org
Date: Mon, 16 Nov 2009 14:15:43 +0100	[thread overview]
Message-ID: <87hbsur4ow.fsf@gmx.de> (raw)
In-Reply-To: <28BB9C80-9659-4551-AF90-F0F5D15906A2@gmail.com> (Carsten Dominik's message of "Mon, 16 Nov 2009 14:04:30 +0100")

Carsten Dominik <carsten.dominik@gmail.com> writes:
> Hi Sebastian,
>
> can you point to a page where you think the stuff is badly readable?
>
> - Carsten

Yes - sorry.

http://orgmode.org/worg/org-contrib/org-protocol.php#open-source-rewritten-urls



  Sebsatian



>
> On Nov 15, 2009, at 8:08 PM, Sebastian Rose wrote:
>
>> Hi,
>>
>>
>> the colors on orgmode.org are made from an Emacs setup with a dark
>> background.
>>
>> Because of the light background on the Web, code examples with syntax
>> highlighting are hard to read. I even avoid #+BEGIN_SRC and use
>> #+BEGIN_EXAMPLE instead.
>>
>>
>> I played a little locally, and found, that the following simple change
>> makes highlighted source code readable. Just put this in an exported
>> HTML file, just before the `</head>' tag and keep the original styles in
>> place, to see the results:
>>
>>
>> <style type="text/css">
>> pre {
>>    background-color:#333333;
>>    color:white;
>> }
>> </pre>
>>
>> These are just the changed values.
>>
>>
>>
>> Unfortunately, this changes the appearance significantly. Dark
>> background for all code.
>>
>>
>>
>> As an alternative, we could change all foreground colors, in that we
>> keep the tint, but reduce the brightness of each. That way we would keep
>> the appearance and have readable code. I've changed the background to be
>> slightly lighter. Just put this in an exported HTML file, just before
>> the `</head>' tag and keep the original styles in place, to see the
>> results:
>>
>>
>> <style type="text/css">
>>
>> pre {
>>    /* only the changed values for <pre> again */
>>    background-color:#fafafa;
>>
>>    /* Use bigger font? courier is soo small on my system: */
>>    font-size:110%;
>> }
>>
>>
>> .org-string   { color:#BC2020; }
>> .org-builtin  { color:#5C2659; }
>> .org-keyword  { color:#5C128A; }
>> .org-doc      { color:#754C4C; }
>> .org-constant { color:#385D5E; }
>>
>> .org-variable-name { color:#805F11; }
>> .org-function-name { color:#0000CC; }
>>
>> </style>
>>
>>
>>
>> What do you think?
>>
>> How is the font-size of code on Windows and MAC (Safari)?
>>
>>
>>
>>  Sebastian
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> - Carsten
>
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sebastian  Rose      Fachinformatiker / Anwendungsentwicklung
Viktoriastr. 22      Entwicklung von Anwendungen mit freien Werkzeugen
30451  Hannover      und Bibliotheken.

0173  83 93 417      sebastian_rose@gmx.de         s.rose@emma-stil.de
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  reply	other threads:[~2009-11-16 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 19:08 Colors for pre elem. on orgmode.org Sebastian Rose
2009-11-16 13:04 ` Carsten Dominik
2009-11-16 13:15   ` Sebastian Rose [this message]
2009-11-16 13:17     ` Greg Newman
2009-11-16 16:43       ` Sebastian Rose
2009-11-16 22:33         ` Rick Moynihan
2009-11-17 17:31           ` Eric S Fraga
2009-11-17 18:17             ` Sebastian Rose
2009-11-17 19:03               ` Eric S Fraga
2009-11-17 19:16                 ` Rick Moynihan
2009-11-16 15:56     ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hbsur4ow.fsf@gmx.de \
    --to=sebastian_rose@gmx.de \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).