drbowen wrote on Friday, March 14, 2008:
I have found volunteers to help with translations to German, Russian, and Romanian. I was hoping to perhaps to put these into a spreadsheet with the "language constants" and forward them to Rod. Would this be OK?
Sam Bowen, MD
mborchorst wrote on Sunday, March 16, 2008:
I hope to get to need a danish translation sooner or later, so pls count me in on the spreadsheet list.
Greetings
Morten Borchorst
lemonsoftwarero wrote on Thursday, March 20, 2008:
Another proposition:
we have now more than 2500 language constants in our database. Every translated language will add another 2500. If we’ll have 7-8 languages here, the sql script will become very big (in fact it’s already big). I think one solution will be to put only the english by default, and the rest of the languages to be split in several files (with sql statements). From the administration inteface, a small function will add the required language at will.
It’s something like installing an additional module for a piece of software.
What do you think?
sunsetsystems wrote on Thursday, March 20, 2008:
I think it’s fine to have a separate SQL file for each language. Perhaps in a “languages” subdirectory within the “sql” directory.