> In this case reply articles would be the closest match to your needs. A
> more generic linking style would probably require an extarnal linking
> table, which has pros and cons. I'll try to work out a concept for 2.0.
> Input very welcome.
Well I won't dare comment on the external linking issue but I might add my
input in the form of our business need. I'm looking at moving every site in
the company I work for (we are a publicly listed company in Australia with 6
subsidiary companies all over the world) to Midgard. One thing we do want
to have is a massivee content tree that is developed by certain people (such
as the product managers in Australia) and other people in offices in other
locations (such as our sales manager in America that speaks Spanish)
translate the content into other languages which can then be available to
all the sites meaning that Spanish translated content could be used not only
on our American website but also on the European etc.
Functionality such as an ability to use language specific graphics (I
suppose BLOB support will cover this?) and something that, should an article
have not been translated then say the English version would get served up
(perhaps with an apology before you hit the link - see francais.curling.ca).
I'm sure I'll over other thoughts later but it's always nice to see some of
the things people want out of a product before you sit down to code.
Nick Rohrlach
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
