From: Carsten Dominik <carsten.dominik@gmail.com>
To: Water Lin <WaterLin@ymail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Three questions about publishing webpages
Date: Tue, 10 Nov 2009 10:23:10 +0100 [thread overview]
Message-ID: <719D36E5-2883-467B-A27F-B77B1092E82E@gmail.com> (raw)
In-Reply-To: <83bpjax6c2.fsf@ymail.com>
On Nov 10, 2009, at 7:05 AM, Water Lin wrote:
>
> Here comes three more questions about publishing webpages about org
> mode:
>
> 1. After publishing webpages with command M-x org-publish-current-
> file,
> the org file will be closed by Emacs. I always use M-x
> org-publish-current-file to check if the output is good, so I still
> want
> to edit the org file. What can I do if I don't want that Emacs
> closes my
> org file after publishing webpages with M-x org-publish-current-file.
I cannot reproduce this. Org tries to remove buffer that are visited
just for publishing, but it tries to keep those which are already
present.
>
> 2. I have some characters other than English in my org files. But org
> publishes org file to webpages as coding ISO-8859-1. So Firefox can't
> show the characters correctly. How can I let org publish files as
> UTF-8?
Hmm.
Have you set org-export-html-coding-system? This will overrule
the automatic charset setting which is derived from the value
of `buffer-file-coding-system' in your Emacs buffer.
>
> 3. I set #+link_home: and #+link_up: , but nothing happened when I
> publish the org file to webpages. There is no up or home link on my
> pages. Is it necessary to introduce links in my org file? Or what
> else I
> need to set in org?
Nothing. When I do set them, they show up in the upper right
corner of the page.
Do you have a recent version of Org-mode???
- Carsten
prev parent reply other threads:[~2009-11-10 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 6:05 Three questions about publishing webpages Water Lin
2009-11-10 9:23 ` Carsten Dominik [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=719D36E5-2883-467B-A27F-B77B1092E82E@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=WaterLin@ymail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.