[WM] multi language support?

[Chris]

Dear Listmembers, dear Justin,

we would like to generate multilingual web pages from a single webmake file.
After playing around a while I come to know that it won't work without
extending webmake. 

Please let me know, if there have been some efforts to accomplish
this. If not maybe some people have ideas on this subject.

What has been done:
Up to now we played with the possibilities webmake offers us. The current
version defines a new content tag '<lang id="..">' which enables us to write
multilingual contents. Unfortunatley this is hard to do with EtText as it is
very sensible with newlines and so on. Inserting any kind of tags kann mess up 
the output, so we sticked to 'text/html' input. 

This was easy. The hard thing was to get different meta data for the contents.
The actual solution reads all contents from txt files with 

	<contents src="HTML" name=".../*.txt"
		metatable="meta.csv.${lang}" delimiter="|"
		listname="all_contents"
	/>

the content "lang" is set to the language identifier and for each language a
meta.csv file has to be provided. 
This limits us to have seperate projects for each language as each content can
only have on set of meta data. The content ${lang} is set at the beginning and
afterwards the main wmk file is include, which does all the work (I have to
base wmk-files, de.wmk for german, en.wmk for english). Therfore Cross
referencing between languages is not easy. Also the we would like to have all
information within one file, i.e. the contentent files should include the meta
data for all languages like having

	<lang id="de"> <wmmeta name=title value="German"></lang>
	<lang id="en"> <wmmeta name=title value="english"></lang>

at the beginning of the content files.  But webmake sticks to the first one it
encounters disregarding the <lang> tags which are only parsed on producing the
actual output (seems so). 

Right now I'm trying to figure out where to add something to the processing
steps to accomplish all this in a smooth way. The parsing and everything is
not that easy to understand from the source code. So maybe someone (Justin?)
can give me some hints on where search first.

If someone want's to have more information or the current code (which is a
mess because of all that playing around), please let me know.

Thank you.
Chris