emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Cc: rick@calicojack.co.uk
Subject: Re: Blorg problems
Date: Tue, 17 Jul 2007 01:42:06 +0200	[thread overview]
Message-ID: <87vecjc3w1.fsf@bzg.ath.cx> (raw)
In-Reply-To: <469BAA55.4050009@calicojack.co.uk> (Rick Moynihan's message of "Mon\, 16 Jul 2007 18\:26\:45 +0100")

Hi Rick,

Rick Moynihan <rick@calicojack.co.uk> writes:

> Firstly it appears that my paragraphs don't render as such 

I cannot reproduce this. Can you send me the whole .org file?

> - The time of the post is always rendered something like +00 00 and
> not 12:43 This isn't a big problem as I've just disabled it with the
> format string)

I've seen this before, it will be fixed in the next release.

> - It's not clear how to render images in the output, i.e. with a <img
> src="..."/>.

For now [[file:myimage.jpg][file:myimage.jpg]] in the org file should
end up in this :

<img alt="file:myimage.jpg" src="images/myimage.jpg">

You're asked for the creation of the "images/" directory where blorg
will store the image and then a relative link is created pointing to
this image.

Hope this helps.

> - The format of Echoes appears to be fixed, yet I'd like to use them
> to generate a different order as I'd like to include the following
> HTML snippet (forgive me I can't remember the names of the includable
> properties):

I'll try to make blorg-echo-list more customizable, perhaps by allowing
to set the formatting string manually. Not sure how this can be done
right now.

> It would also be great if somebody could create an example blorg.org
> file which demonstrated all the org markup in a test-blog.

Sure.

> In the future I'd also like a mechanism for exporting code blocks into
> the html (ideally with emacs syntax highlighting). It would be great
> if the org-mode colon syntax could be used to do this, e.g:
> 
> : public int randomNumber() {
> :    return 3;  //guaranteed random number (was a fair dice roll) (xkcd)
> : }

In this example, you are using org-mode's verbatim environment (starting
with the character ":") to insert code - that means that this code won't
be highlighted according to its syntax, it will use the org-table face
instead.

I guess we need to have some information about the syntax of the code
(enclosed in such a verbatim environnement) before we can highlight it.

What about a #+BEGIN_ELISP / #+END_ELISP around the verbatim paragraph,
so that we can guess the relevant mode and call htmlize efficiently?

Carsten: working on org-export-latex.el made me think it might be useful
to have all these options :

#+BEGIN/END_HTML  : only exported in HTML format
#+BEGIN/END_LaTeX : only exported in LaTeX format
#+BEGIN/END_ELISP : call some elisp funcs before exporting this part

> I seem to remember having some other small problems and ideas about
> the whole thing, which if I remember I'll post here. Anyway, if I can
> get the paragraphs and image export working, I should be able to start
> blorging.

Please give me your org file and all information concerning those two
problems.

> Also does anyone know of any blogs online using blorg?

Yes, i know, i should use it myself :)

Cheers,

-- 
Bastien

      reply	other threads:[~2007-07-16 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 17:26 Blorg problems Rick Moynihan
2007-07-16 23:42 ` Bastien [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

  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=87vecjc3w1.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=rick@calicojack.co.uk \
    /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).