Re: The PhDMediaManager class.
| From: | Christian Weiske | Date: | Wed, 11 Feb 2009 13:52:30 +0000 |
| Subject: | Re: The PhDMediaManager class. | ||
| References: | 1 2 3 4 5 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969380139@lists.php.net to get a copy of this message | ||
Hi Richard!
> >> OK. But this class is breaking the links. They all now have an MD5
> >> hash in the html/php output and are not copied to the correct location
> >> (actually not copied at all).
> >
> > They are not copied because they are referenced wrongly now in the
> > manual itself. Their fileref needs to be relative to the manual.xml location.
>
> Aha! Just for those at the back (ahem), that means whereas it is currently ...
> figures/imagick.hello_world.png
> this would become
> en/reference/imagick/figures/hello_world.png
Exactly.
> Especially if a translator needs to change the image (say it contains
> words or whatever), they would also "translate" the fileref to ...
> lang-x/reference/imagick/figures/hello_world.png
Yep.
> There are just over 40 images at the moment. I'll test this out and
> make the necessary changes.
> OOI. Is there a reason to add an md5 hash to the filename?
Images are located everywhere in the file structure which I did not want to replicate in the
compiled manual. Instead, I chose to have only one single directory (images/) in which all image
files reside, independent of their location in the docbook sources/phpdoc cvs. So that hash is the
md5 of the file path in cvs, guranteeing uniqueness in the final images/ folder.
--
Regards/Mit freundlichen Grüßen
Christian Weiske