An argument against DicOOo is that its not "package managed files" either... you can't rpm -e a package and get rid of them. An argument against individual i18n files is that if you have an errata for OpenOffice.org, the you have to do the QA process and errata _every_ single one of the i18n packages too, which is more administrative overhead. Also, I hear that the KDE i18n stuff is special-cased inside of Anaconda, the same would have to be done for OOo if that is true (jeremy is at lunch right now). However, as the # of languages for OOo grows, I doubt people would want to download a monolithic package of all OOo langs since that would be very large. In the end, it _does_ look like individual i18n files are the best way to go, but only since the package is so large... Dan
