I'm very frequently in this situation:
A multi-language website where most of the content is generated through tables and is somehow language agnostic. Sometimes editors would like to add "custom" content to the "base" content automatically generated from tables... sometimes they don't.
So a "node" end up in a nearly language agnostic part and a custom strongly dependent language part.
Now I'd like to be able to have the nodes for each language generated automatically at least for the "language agnostic" part and let people add the custom language dependent part if they wish/have time etc...
This looks so near to what views and cck could do... but not exactly what I need.
What I end up doing is simply create an interface to add rows to the language agnostic table/content, a new content type that just refer to a row of this table then create a view-like function to list all the row in the table.
The view-like, "current language sensitive", function provide 2 kind of links: to nodes when people had created translated special content and to simpler page that just show the details of the table.
This somehow is replicating the CCK/View system.
Another approach would be to just create "empty" nodes for each row inserted and then people could edit the nodes adding their custom language dependent content at a later time...
Are there any other alternative approaches?