To expand on Matthew a bit...
It is an extraordinarily Windows-centric view, that we should try to do
something _for one user_ during software installation _for the machine_.
Let the application figure out user-specific stuff when the user runs it.
In Linux, Xiphos (or BibleTime, or anything els
> I believe that anything that uses the NSIS installer can do this. I think
> this is the case for BibleCS and BibleDesktop. The trick is to only use the
> NSIS provided, stock messages. Note: this only applies to installation on
> Windows.
I believe that David is talking about setting the *app
On Sat, Feb 19, 2011 at 2:55 PM, DM Smith wrote:
> I believe that anything that uses the NSIS installer can do this. I think
> this is the case for BibleCS and BibleDesktop. The trick is to only use the
> NSIS provided, stock messages. Note: this only applies to installation on
> Windows.
>
> B
I believe that anything that uses the NSIS installer can do this. I think this
is the case for BibleCS and BibleDesktop. The trick is to only use the NSIS
provided, stock messages. Note: this only applies to installation on Windows.
BibleDesktop, by default, will use the user's locale in determi
A good topic for consideration is to lessen the reliance on knowing the
English language for those front-ends that already have support for changing
locale.
I've come across several applications (unrelated to Bible software) in which
the installation process gives the user the opportunity to choo
