Support.Bible is a public forum that connects users of Bible translation software, so that they can help one another find solutions and discover new ways of working together. We welcome users of all Bible translation software systems to discover how they can help one another take God's Word to the world.
Search existing questions first — if you don't find what you need, create a free account to ask your own.
I tried to mark this as a bug report, but that’s not an option. This is a long-standing multifaceted bug that I’ve mentioned before.
Can you confirm this?
~Matthew_Lee SIL Cameroon
I’m fairly certain that was fixed in the 7.6 installer.
I think this was fixed for 7.6 as well.
Also note that we have a completely new installer for 8.0 so there should be fewer issues going forward (or completely new issues ).
The problem, of course…is that 7.6 is a non-recommended/beta version of Paratext, so the 32-bit fix should have been back-ported to the stable Paratext 7.5 some time in the past year that we were supposed to use it.
Back-porting changes is not free. It costs developer time and we have to weigh that cost with the fact that most people have a 64bit OS so they are not having problems and it’s not actually keeping people from getting their job done.
In other words, I’m sorry to say it wasn’t deemed worthwhile to back-port the change.
I think I also reported a while ago that Paratext 7.5 creates and installs to a Program Files (x86) folder on 32-bit Windows. If I remember correctly, it also gives Read-Write access to Everyone, so it’s a security issue too. The Paratext program could become infected with a virus.
).
