From: Sebastian Rose <sebastian_rose@gmx.de>
To: emacs-orgmode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Enhancement request : publish page limits
Date: Wed, 22 Oct 2008 19:55:49 +0200 [thread overview]
Message-ID: <87hc74pl96.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <87ljwgpm2w.fsf@kassiopeya.MSHEIMNETZ> (Sebastian Rose's message of "Wed, 22 Oct 2008 19:37:59 +0200")
Richard,
there is a tutorial at org/worg:
http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php
which shows how I handle the HTML export here. It's shorter to read,
than the old org-info documentation, and covers a nice way to handle
recursive exporting of entire directory trees and glue them together
by org-info.js.
I like this example most, currently, since it shows how `i TAB' is
handled with fixed-toc:
http://orgmode.org/worg/org-faq.php
Regards,
Sebastian
> Sebastian Rose <sebastian_rose@gmx.de> writes:
>> Patch to fix this in doc/org.texi (pulled an hour ago).
>>
>>
>> diff --git a/doc/org.texi b/doc/org.texi
>> index 0ae852e..b2ce486 100644
>> --- a/doc/org.texi
>> +++ b/doc/org.texi
>> @@ -7688,7 +7688,7 @@ as well, press @kbd{?} for an overview of the available keys). The second
>> view type is a @emph{folding} view much like Org provides it inside Emacs.
>> The script is available at @url{http://orgmode.org/org-info.js} and you can
>> find the documentation for it at
>> -@url{http://orgmode.org/worg/code/org-info-js/org-info.js.html}. We are
>> +@url{http://orgmode.org/worg/code/org-info-js/index.html}. We are
>> serving the script from our site, but if you use it a lot, you might not want
>> to be dependent on @url{orgmode.org} and prefer to install a local copy on
>> your own web server.
>>
>>
>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>> Hi,
>>>
>>> Do you have an example?
>>>
>>> The link
>>>
>>> http://orgmode.org/worg/code/org-info-js/org-info.js.html
>>>
>>> mentioned in the info file is dead.
>>>
>>> r.
>>>
>>>
>>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>>
>>>> org-info.js ;-)
>>>>
>>>> ???
>>>>
>>>> Make the de facto standard for viewing text in the internet !!!
>>>>
>>>> :-D
>>>>
>>>>
>>>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>>>> I didn't spot anything in the manual, but it would be nice if publish
>>>>> automatically split large published org files into multiple html files
>>>>> based on a "num entries per page" setting. This would then effectively
>>>>> work as a handy blogging client IMO (ok no replies etc). Clearly it
>>>>> would need to render a navigation widget too. (page 1,2,4,5 .. next 5 )
>>>>> etc. Does anyone have something like this or suggestions along the same
>>>>> path?
--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.: +49 (0)511 - 36 58 472
Fax: +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http: www.emma-stil.de
prev parent reply other threads:[~2008-10-22 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 16:36 Enhancement request : publish page limits Richard Riley
2008-10-22 16:19 ` Sebastian Rose
[not found] ` <w9k5c0oa73.fsf@development.richardriley.net>
2008-10-22 17:11 ` Sebastian Rose
2008-10-22 17:16 ` Sebastian Rose
[not found] ` <87ljwgpm2w.fsf@kassiopeya.MSHEIMNETZ>
2008-10-22 17:55 ` Sebastian Rose [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=87hc74pl96.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--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).