making html pages for an easier updatable site

Since more eyeballs make bugs popup easier than only two,
I am trying to use user generated html pages for a local,
more quickly updated, site.

Doing

make

creates a html pages & update images links but...in a way that (IMHO) is
not really smart.One example is better than a thouthands words...
Essentially, for italian and english, the output of the command is:

html/en
html/it

these two dirs contains all the html code with one image simlink that points
to ../../xml/en/images and ../../xml/it/images respectively.

so we have:

html/en
html/itxml/en/imagesxml/it/images

This is all ok but...in xml/en/images (and similarly in xml/it/images) there
are _not_ images but _absolute_ simbolic links to

for example:

xml/it/images/dialogs/scale-image.png

points to

-> /home/marco/svn-gnome/gimp-help-2/trunk/images/it/dialogs/scale-image.png
this makes copying this stuff to a site not so fast...

Q: is it possible to substitute all absolute links with relative one or
(alternatively) making only one absolute reference (that is easier to
modify) and all other references relative to this one?

Yes, this was just the easiest way to create these links - because I
didn't know the command to convert absolute links to relative links.
(It seems there is no such command.)

Q: is it possible to substitute all absolute links with relative one

Yes, of course. For instance, we can write a little shell/Perl/Python
script to make relative links or (better) to do all the
find-image-and-make-link stuff (try 'make -n xml/it/images' to see
these commands).

or (alternatively) making only one absolute reference (that is easier
to modify) and all other references relative to this one?

No, we "copy" the image files in xml/it/images from two different
sources: the English (language-independent) images or the localized
images. So IMO we had to use three absolute references (to images/C,
images/common, images/LANG)...

Yes, this was just the easiest way to create these links - because I
didn't know the command to convert absolute links to relative links.
(It seems there is no such command.)

apt-get install symlinksman symlinks

Q: is it possible to substitute all absolute links with relative one

Yes, of course. For instance, we can write a little shell/Perl/Python
script to make relative links or (better) to do all the
find-image-and-make-link stuff (try 'make -n xml/it/images' to see
these commands).

ok I'm working on it, please wait...

or (alternatively) making only one absolute reference (that is easier
to modify) and all other references relative to this one?

No, we "copy" the image files in xml/it/images from two different
sources: the English (language-independent) images or the localized
images. So IMO we had to use three absolute references (to images/C,
images/common, images/LANG)...

Yes, of course. For instance, we can write a little
shell/Perl/Python script to make relative links or (better) to do
all thefind-image-and-make-link stuff (try 'make -n xml/it/images' to see
these commands).

ok I'm working on it, please wait...

Don't write a script based on "symlinks"!

I've written a little Perl script, which uses the File:.Spec module and
should be portable.

making html pages for an easier updatable site

On Wed, Mar 25, 2009 at 02:02:23PM +0100, Ulf-D. Ehlert wrote:

Yes, of course. For instance, we can write a little
shell/Perl/Python script to make relative links or (better) to do
all thefind-image-and-make-link stuff (try 'make -n xml/it/images' to see
these commands).

ok I'm working on it, please wait...

Don't write a script based on "symlinks"!

I've written a little Perl script, which uses the File:.Spec module and
should be portable.

making html pages for an easier updatable site

(if it isn't too simple we could add it to the tools dir or insert it
in the makefile)

The (autotools generated) Makefile contains some dist* targets, and
there is also the old (disabled) install target ("install-data-local")
in Makefile.am. I didn't check them, but it may be that they are meant
to build the html packages...

If that's true, you should consider making these install routines work
with the new build system rather than (or in addition to) adding this
script.