On 07/12/2006, at 8:12 PM, Rafaella Braconi wrote:
yes, at the moment basically for storage and resource reasons (building full installation sets takes much longer than language packs and require much more space) we are providing full installation sets for the languages Sun is releasing StarOffice/ StarSuite into and language packs for all other languages for which the N-L Communitites provide at least 80% of GUI translation.
I didn't know that there was any difference between the languages supported in StarOffice and OpenOffice. Thankyou to both you and Ain for explaining this. Is there any reason why this difference exists? I would have thought any software project would want to release in as many languages as possible, as long as the translations were QA'd.
I am not happy at all with the distinction between Sun and non-Sun languages and I am investigating if there is a possibility to provide full installation sets at least for all those who fully localize the product (both UI and Help) .... but the storage issue seems a big one.
I can understand that. It's difficult to keep on downloading those huge files, to test the builds. :(
I promise to keep you updated on this. In the meanwhile, if you have any ideas, suggestions just let me know.
Thankyou. :)Ideally, I agree with you that all supported languages should be hosted equally. That would create one central hosting plus mirrors, rather than having different builds scattered all over. It would integrate this task, which is being repeated by different people, and could be much more effectively performed as a single task, on one schedule and set of mirrored locations. It's not efficient to have people repeating the task in different places, on different schedules. Overall, it would free up resources for the project.
Meanwhile, if there aren't currently enough resources to host all languages for all architectures, I would suggest giving priority to additional language-builds for architectures not built elsewhere. However expensive it might be in their time and overall project resources, Pavel does an excellent job of the Linux builds, and sometimes also provides Windows builds, and Maho helps us by providing for both Mac architectures. So I would suggest initially giving priority to additional languages for Solaris86 and SolarisSPARC, then Windows. I don't know what the demographics are per architecture. Another approach would be to priortize hosting by user base.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
