emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eric.schulte@gmx.com>
To: Zhiqiu Kong <breaddawson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Incomplete syntax highlight for C++ code
Date: Sat, 18 Feb 2012 08:21:20 -0700	[thread overview]
Message-ID: <8762f4tarv.fsf@gmx.com> (raw)
In-Reply-To: CAN8aJ9KuDeNPf2b5232muM58ct7CCTXw8uXFvy8LMeFhBu8+0g@mail.gmail.com

Hi Zhiqiu,

First, I would look at the actual text of the exported html code
example.  It likely contains css code specifying how to fontify many
elements of the code block (e.g., on my system your example exports to
the following html [1]).  You can then add css to your org-mode file
specifying what colors to use for each code class.

Also, see the `org-export-htmlize-output-type' variable.


Zhiqiu Kong <breaddawson@gmail.com> writes:

> Hi,
> I am a new org-mode user and am trying to take notes with it. As I put
> source code into my codes a lot, I love the integration with htmlize pretty
> much.  However, I found the syntax highlight on exported html file is not
> as what I see in Emacs. To be more specific, only comments and string
> literals are colored, which is shown in http://img.ly/dXTK. And here is
> what is looks like in Emacs: http://img.ly/dXU6.
> Actually, what I expected is the keywords such as int, return should at
> least be colored, which is as introduced by emacs-fu (
> http://emacs-fu.blogspot.com/2009/05/writing-and-blogging-with-org-mode.html
> ).
> I checked out the latest org-mode (Org-mode version 7.8.03
> (release_7.8.03.336.gdf0a9) ) and htmlize (for git repository), but the
> problem remains. Moreover, here is my project setting:
> (setq org-publish-project-alist
>       '(("note-org"
>          :base-directory "~/Docs/notes/org/"
>          :publishing-directory "~/Docs/notes/html/"
>  :htmlized-source t
>  :base-extension "org"
>  :sub-superscript nil
>          :recursive t
>          :publishing-function org-publish-org-to-html
>  ;; :org-export-htmlize-output-type "css"
>  :html-extension "html"
>          :auto-index t
>          :index-filename "index.org"
>          :index-title "My Notes"
>          :link-home "index.html"
>          ;; :section-numbers nil
>          :style "<link rel=\"stylesheet\"
>                 href=\"css/worg.css\"
>                 type=\"text/css\"/>")
>         ("note-static"
>          :base-directory "~/Docs/notes/org/"
>          :publishing-directory "~/Docs/notes/html/"
>          :recursive t
>          :base-extension
> "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|swf\\|zip\\|gz\\|txt\\|el"
>          :publishing-function org-publish-attachment)
>         ("My Notes"
>          :components ("note-org" "note-static")
>  :auto-sitemap t
>          :auto-index t
>          )))
> Any suggestion on how to debug and fix this problem? Or this is normal?
> Thanks a lot!!
> Thanks,
> -Zhiqiu

[1]  <pre class="src src-c++"><span style="color: #ffffff;">int</span> <span style="color: #ffc66d;">main</span>(){
  <span style="color: #6d9cbe;">std</span>::cout &lt;&lt; <span style="color: #a5c261;">"hello"</span> &lt;&lt; <span style="color: #6d9cbe;">std</span>::endl;

Eric Schulte

  reply	other threads:[~2012-02-18 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15  6:59 Incomplete syntax highlight for C++ code Zhiqiu Kong
2012-02-18 15:21 ` Eric Schulte [this message]
2012-02-19  1:47   ` Zhiqiu Kong

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:

  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=8762f4tarv.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=breaddawson@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).