From mboxrd@z Thu Jan  1 00:00:00 1970
From: David O'Toole <dto@gnu.org>
Subject: Re: org-publish v1.71
Date: Sat, 10 Jun 2006 11:44:20 -0400
Message-ID: <m31wtxdnhn.fsf@gnu.org>
References: <m3verbfm00.fsf@gnu.org>
	<9bcdfad70606090216h681184ear2d271d7321817861@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Fp5dX-0000c9-Lz
	for emacs-orgmode@gnu.org; Sat, 10 Jun 2006 11:44:31 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Fp5dU-0000Xb-37
	for emacs-orgmode@gnu.org; Sat, 10 Jun 2006 11:44:31 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Fp5dT-0000XT-Vq
	for emacs-orgmode@gnu.org; Sat, 10 Jun 2006 11:44:28 -0400
Received: from [66.249.82.199] (helo=wx-out-0102.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fp5lm-000087-Fk
	for emacs-orgmode@gnu.org; Sat, 10 Jun 2006 11:53:02 -0400
Received: by wx-out-0102.google.com with SMTP id s19so727920wxc
	for <emacs-orgmode@gnu.org>; Sat, 10 Jun 2006 08:44:24 -0700 (PDT)
In-Reply-To: <9bcdfad70606090216h681184ear2d271d7321817861@mail.gmail.com>
	(Chris wallace's message of "Fri, 9 Jun 2006 09:16:42 +0000")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Chris wallace <crassshed@gmail.com>
Cc: emacs-orgmode@gnu.org


Tranforming the filenames/paths during publishing is a nontrivial
problem. This would require changes to both org-publish and org
itself. One way of solving it would be to pass an association list
mapping input filenames to output filenames, this would let you bypass
the normal :publishing-directory setting and set things on a per-file
basis. 

Carsten, what do you think? 

"Chris wallace" <crassshed@gmail.com> writes:

> On 08/06/06, David O'Toole <dto@gnu.org> wrote:
>>
>>
>> Bugfix release. Should now allow absolute filenames in the :include
>> directive.
>>
>>
> Thanks.  It works.  Just one more request, so I can use this with my files
> spread across many directories.
>
> When I have
>
> (setq org-publish-project-alist
>      (list
>       '("bright" . (:base-directory "~/bright"
>             :base-extension "org"
>             :include ("/home/chris/bright/chr5/cng/Readme.org"
> "/home/chris/bright/chr5/phase2/Readme.org")
>             :publishing-directory "~/public_html/org"))))
>
> The two Readme.org files both get published as
> ~/public_html/org/Readme.org.  I would really like them to be
> ~/public_html/org/chr5_cng_Readme.html and
> ~/public_html/org/chr5_phase2_Readme.org.  Ie with the directory relative to
> :base-directory included in the file name.  Is this possible?
>
> My working situation is that under project bright, important directories
> have a Readme.org file containing notes relating to that sub-directory.
> It's handy for writing the notes for the filename to always be Readme.org,
> but less handy for publishing so that my colleagues can see where I'm up to.
>
> Thanks, Chris.

-- 
David O'Toole -- Independent Consultant
dto@gnu.org