Hi Jim > Question 1: > I would like to be able to offer my OpenOffice.org ISO to customers in the > UK. what does it take to "localize" it?
There would be two options - you could use the en_GB build (yes, it does exist), but it has not been QAed at this time, so you'd only have the RC available. Alternatively, include the en_GB langpack, and write an install script to install it after the main installation has completed. > I assume that what is available > from the US FTP mirrors is workable. I have only a guess that the only > thing that is needed is a dictionary, and I don't know how I would install > that with any generic wraparound installer like NSIS. The language pack not only installs an English English dictionary, but also localises the menus and help (at least, that's how I understand it to work). As for a wrapper, it would be simple enough to do a simple script (or a batch file), using any of the scripting languages available (Java, Ruby, Python etc.) which would simply call the installer, then when that has finished it would install the langpack. I'd probably do it in a DOS batch file, since that's what I'm most familiar with, and it is adequate for the job. > > Issue: > by the way, the OpenOffice.org installer when executed with ExecWait via > NSIS does not wait. it must be exiting and firing off another process or > child process, because the next program in the software suite's installer > (executed with ExecWait) executes immediately. that shouldn't be. maybe I > should file a bug report. > ExecWait waits until the process is done before going on to the next line > of installer script. Something is circumventing this. Don't ask me, I'm not familiar with this.... > > Question 2: > I thought we were supposed to be writing wraparound installers for this and > to display a certain disclaimer text " These binaries (installable > software) are in development. > They may not be fully stable and should be used with caution. > We make no claims about them. > " to be community distributors? at least that's what it used to be. have > the rules changed? I haven't heard of that one. IIRC, such a disclaimer is in the license which is displayed during installation. > > > > > Jim Michaels > [email protected](main) > http://JesusnJim.com (my site) > ________________________________ > http://DoLifeComputers.JesusnJim.com > (Do Life Computers group site which I lead) > > > while (stone != rolling) moss++; > --- > Computer memory/disk size measurements: > [KB KiB] [MB MiB] [GB GiB] [TB TiB] > [10^3B=1000B=1KB][10^6B=1000000B=1MB][10^9B=1000000000B=1GB][10^12B=1000000 > 000000B=1TB] > [2^10B=1024B=1KiB][2^20B=1048576B=1MiB][2^30B=1073741824B=1GiB][2^40B=1099 > 511627776B=1TiB] Note: disk size is measured in MB, GB, or TB, not in MiB, > GiB, or TiB. computer memory (RAM) is measured in MiB and GiB. --- > Robot dog food: Cables n' Bits > --- > adress=seg<<4+ofs; (ambiguity - a double-minded compiler is unstable in > all its ways) biosdsk2.h:733: warning: suggest parentheses around '+' > inside '<<' --- > I'm balding on top (:-] > --- > > ---------------------------------------------------------------------- > -- Alex Fisher Co-Lead, CD-ROM Project OpenOffice.org Marketing Community Contact Australia/New Zealand http://distribution.openoffice.org/cdrom/
signature.asc
Description: This is a digitally signed message part.
