* Joshua Slive wrote:
> This is very nice. BUT, I think the biggest gain from PDF (and what most
> users want) comes from having one big PDF file with the entire
> documentation. There is probably a way to do that by assembling the
> smaller ones with another program.
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 ;-)
> 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 ;-)
However:
- We have to change the build system to create metafiles, that contain the
available variants (languages, pdf files). This will happen
automatically. (but the metafiles have to be checked in, otherwise the
script has no chance to check the timestamp dependencies correctly)
The perl script which maintains the metafiles could be rewritten in java,
so that we don't require perl for the build process. But again, this has
to be done by someone with java knowledge ;-)
- the metafiles have to be references anyway from within the xslt. There
are two possibilities to achieve this:
* reference the particular metafile in a attribute in the document's
rootelement (metafile="documentbasename.meta")
* inject the filename via ant into the transformation process.
the latter would be initally more easy, but has some drawbacks: we loose
the last rest of browser compatibility, since the xslt relies on an
information that's only available, if we run the transformation with ant.
Besides it requires the <foreach> task.
Conclusion: I'd prefer the first variant. It seems to be more clean
anyway.
- We have to setup the rewrite rules on daedalus. (That is independant from
the changes above.) IMHO the rewrite map file itself should go into
style/lang, thus we can maintain it via CVS (but no errors should occur
then with that file, since it may break the whole daedalus apache...)
But we have to decide, how to distribute the docs
within a release package. I'll require mod_rewrite for only viewing the
docs locally reluctantly. But currently I've no good idea how to solve
that problem.
(Note that there are some pathes to adjust in the attached ruleset)
- some minor changes in CSS and XSLT, to build in the links.
I'm going to commit the neccessary changes (I think, at 2.1 docs for now,
so that we can see, how it works, and port them back later), if the
suggestions get acknowledged.
^^^ ? ;-)
nd
--
"Die Untergeschosse der Sempergalerie bleiben w�hrenddessen aus
statistischen Gr�nden geflutet." -- Spiegel Online
# start the machine.
RewriteEngine On
RewriteMap lang2ext txt:/path/to/lang2ext.txt
#
# trailing slash...
#
RewriteCond ${lang2ext:$1} .
RewriteRule ^/docs-2.1/([^/]+)$ /docs-2.1/$1/ [R=301,L]
#
# correct nested languages.
#
RewriteCond ${lang2ext:$1} .
RewriteCond ${lang2ext:$2} .
RewriteRule ^/docs-2.1/([^/]+)/([^/]+)(/.*)?$ /docs-2.1/$2$3 [R=301,L]
#
# grab chosen language
# and fix URL.
#
RewriteCond ${lang2ext:$1} (.+)
RewriteRule ^/manual/([^/]+)(/.*) /docs-2.1$2 \
[E=CLANG:$1,E=EXT:%1,E=RFILE:/phys/path/to/docs-2.1$2]
#
# fast exit
#
RewriteCond %{ENV:EXT} .
RewriteCond %{ENV:RFILE} -f
RewriteRule ^ - [L]
#
# another trailing slash
#
RewriteCond %{ENV:EXT} .
RewriteCond %{ENV:RFILE} -d
RewriteRule ^/docs-2.1/(.*[^/])$ /docs-2.1/%{ENV:CLANG}/$1/ [R=301,L]
#
# try chosen language
#
RewriteCond %{ENV:EXT} .
RewriteCond %{ENV:RFILE} -d
RewriteRule ^ - [E=RINDEX:index.html]
RewriteCond %{ENV:EXT} .
RewriteCond %{ENV:RFILE}%{ENV:RINDEX}.%{ENV:EXT} -f
RewriteRule (.*) $1%{ENV:RINDEX}.%{ENV:EXT} [L]
# lang2ext map
de de
en en
fr fr
ja ja.jis
ko ko.euc-kr
pt-br pt-br
ru ru.koi8-r
# the End.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
