On Mon, 2006-01-23 at 16:33 +0000, Neil Williams wrote: > OK. I've got gettext working with PHP to translate a single website using as > many PO files as we can create.
Awesome. > It means yet more restructuring of the htdocs and running some scripts to > create and update the PO files, much as we do with 'make pot' in trunk. > > I think svn should simply be a copy of the final website, including binary > translation .mo files in real locations. I'll create some bash scripts to > site in htdocs/ to help create, update and merge the translations. If we're going to "bake" the site via some script "compilation" step, then can we get away from using PHP entirely? :) > I'll have to restructure the top level directories as well because we don't > need these locale directories (the LC_MESSAGES ones) exposed via apache so it > will mean adjusting some Apache settings to map the root directory of the > website to a directory *beneath* htdocs. e.g. where the virtual host maps a > DocumentRoot of htdocs, it will need to be modified to map htdocs/www Also, does it then make sense to structure the files so that we can configure Apache can do language content-negotiation? <http://httpd.apache.org/docs/2.0/content-negotiation.html> It would basically mean a different structure; one like: htdocs/www/index.html.en htdocs/www/index.html.de htdocs/www/index.html.[...] htdocs/www/features.html.{en,de,...} > To protect the .svn directories below www/, this snippet should be added to > the virtual host config: > <Directory /opt/svn/htdocs/www/*/.svn> > Order Deny,Allow > deny from all > </Directory> I suppose this, or maybe using `svn export` so the .svn files aren't even created? -- ...jsled http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
