I recently realized that adding the locale files to the installer added a dependency on the gettext package in order to build the installer (inno-soft dies if the locale folder is not created).
I was curious what people thought. We currently pre-bake the man pages and store them in the patch queue to avoid forcing people to have asciidoc on their Windows machine. Should we do the same thing for translations? Pros: Easier for everyone to build installers, less dependencies Cons: The translations could easily lag the source I'm guessing the failure mode for lagging translations is just that fewer strings are translated for you at runtime, so it's not fatal. But I know that the man page patch has often been neglected for long stretches of time. -- Steve ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
