emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: bva@alexanderonline.org
Cc: raman@users.sf.net, emacs-orgmode@gnu.org
Subject: Re: Emacs-orgmode Digest, Vol 26, Issue 34
Date: Sun, 13 Apr 2008 21:08:45 +0200	[thread overview]
Message-ID: <8C52B62C-D1B7-48AF-A106-BD97259C356F@science.uva.nl> (raw)
In-Reply-To: <0F5CB3CE-98B7-4242-A07E-12539846FA5C@alexanderonline.org>

Hi Ben,

thanks for this.

- Carsten

On Apr 13, 2008, at 7:04 PM, bva@alexanderonline.org wrote:

> Hi Carsten,
>
> I thought I'd jump in with my 2 pennies:
>
> http:foo.html is a bad habit because (just perhaps) the HTML file  
> isn't accessed by http, and then the internal links break.  So if  
> the generated HTML documents are stored locally (I fantasize that  
> someday my PSP will be able to do this) and accessed using a file://  
> link, the HTML spec requires the browser to ditch the protocol and  
> use the specified one, which won't work if my PSP is offline.
>
> -Ben
>
> On 2008-04-13 Sun, at 17:54:33 +0200, Carsten Dominik <dominik@science.uva.nl 
> > wrote:
>>
>> Date: Sun, 13 Apr 2008 17:54:33 +0200
>> From: Carsten Dominik <dominik@science.uva.nl>
>> Subject: Re: [Orgmode] export to html and relative links:
>> To: raman@users.sf.net
>> Cc: emacs-orgmode@gnu.org
>> Message-ID: <D929E8AD-0CAF-4263-81E5-13D28C023EE2@science.uva.nl>
>> Content-Type: text/plain; charset=US-ASCII; format=flowed
>>
>>
>> On Apr 13, 2008, at 5:33 PM, T. V. Raman wrote:
>>
>>> I've not tried http:foo.html -- but I suggest doing that to
>>> author a relative URL is a bad idea.
>>
>> Can you explain why you think that this is a bad idea?
>> Educate me!  What is wrong with writing http:foo.html ??????
>>
>> - Carsten
>>
>

      reply	other threads:[~2008-04-13 19:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 17:04 Emacs-orgmode Digest, Vol 26, Issue 34 bva
2008-04-13 19:08 ` 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

  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=8C52B62C-D1B7-48AF-A106-BD97259C356F@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=bva@alexanderonline.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=raman@users.sf.net \
    /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).