At 19:25 -0500 UTC, on 2007-01-31, TNHarris wrote: > On Sat, 27 Jan 2007 17:27:05 +0100, "Sander Tekelenburg" > <tekelenb@xxxxxxxxxx> said: >> Wouldn't it be practical to follow Apache's convention of adding the >> 2-letter code to the end of the file name? >> page1.txt.en >> page1.txt.de >> page1.txt.fr >> > > If only for certain broken operating systems that rely on the filename > to tell them what the content type of the file is. Yes, that's a problem. > I think using metadata to create a relationship between pages is the > most sensible. I agree that would probably be nicer. > [...] ~~LANG:es:translation~~ gives the > name of the translated page. If I understand cortrectly what you mean, that would require the translator to edit every other language version of the page. You might not want to let them; you might not want to have to keep track of it al manually; you might not want to have to update already existing pages (thus changing their history; thus affecting RSS feeds, etc.) just because a translation was added, becasue after all, the original didn;t in fact change. It would be nicer if there were some way that Dokuwiki itself automatically 'sees', by their mere existence, that different translations of the a page exist. Some sort of "istranslationof" parameter perhaps? Similarly, I'd think when you run a miltilingual Dokuwiki, you'd want to be able to move pages around in one language, and have all other languages synchronized automatically. You'd quickly get a mess if you'd have to manually sync things in several languages. If only because the person doing that may not know all those languages. That's why I thought of the simple Apache approach -- easy to just move entire directories around. But I agree that a more subtle approach could be nicer. -- Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/> -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist