Re: [REQUEST] Internationalization - Adding multiple languages
exactly - that's the problem that plagues content publishing groups everywhere, including my job.
what we do here is have a separate globalization content publishing team. when we have an update to the documentation, a bug is opened for that team and then we usually make a totally separate release of the documentation in that language. we aren't web-based so clearly it's a little different, but i'm bringing this point up so people understand that doing this sort of a thing isn't as easy as just getting a few people to do it once. there has to be a plan in place for making sure we have the staff to do the content, a solid update system, etc; as once we start doing it, we have to keep maintaining it.
hence the need for a solid business reason to do this :) we'll see!