On Sat, 11 Jan 2003, Andr� Malo wrote: > yep. As said before, the printer friendly pdf files were more an exercise > to become familiar with the xsl-fo stuff. My idea to assemble them to a big > one is similar to Erik's. I've just thought to transform the fo-files > first, then collect them via a script or a java task (which has to be > written by someone with java knowledge ;-) and put the names into an xml > files and run another transformation over this file, which finally feeds > fop. voila. (hopefully ;-)
Sounds good. +1 from me. > > > The available languages thing is also very nice. Can you be a little more > > specific about what changes we need to make to have that work? > > Oh, I already was (some weeks ago). Seems, the posting disappeared in the > noise ;-) I haven't been paying much attention lately. Some thoughts: 1. Having a perl script generate the metafiles is not a big deal. We don't add or change files very often, so really the perl script can just be used for the initial change and we can even do it by hand after that. 2. Having the xml docs reference the metafile is not nice, but I agree probably unavoidable. Again, it is a one-time thing for each doc, so we can live with it. 3. Once we have the metafiles, we can use some fancy xslt to generate mod_negotiation type maps. This should be a real performance and simplicity improvement. 4. Here's an idea to avoid the need for mod_rewrite, and thereby allow easier distribution: manual/file1.meta.xml manual/file1.html (generated type-map) manual/file2.meta.xml manual/file2.html (generated type-map) manual/en/file1.xml manual/en/file1.html (generated html) manual/en/file2.xml manual/en/file2.html (generated html) manual/de/file1.xml manual/de/file1.html (generated html) manual/de/file2.xml manual/de/file2.html (generated html) Now all references in the html are relative. By default, the url looks like http://example.com/manual/file1.html which hits the typemap for content-negotiation. A relative link "<a href="file2.html">" keeps you in the type-map file directory. Now file1.xml contains auto-generated links (generated by looking at file1.meta.xml) to each language specific version (<a href="../en/file1.html"> and <a href="../de/file1.html">). Once you are at the http://example.com/de/file1.html, then all (relative) links keep you under the de/ tree and no content negotiation occurs. This, of course, requires a AddType type-map .var and a RemoveType in each language sub-directory. Is this a good idea? Joshua. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
