Closed GoogleCodeExporter closed 8 years ago
Investigated, and rejected. The setup is too complicated for our needs, and Im
not entirely sure I trust the reliability of the way they inject themselves
into nib loading.
Strings files + string bindings + autolayout are more reliable, and easier for
all to setup.
Original comment by dan...@growl.info
on 1 Feb 2012 at 3:30
You can still use it for strings files + strings bindings + autolayout. Then it
will give your translators a chance to see the translations before they send
them back to you. Setup for this should basically just be linking to the
framework.
We've been using this system for a long time without any problems, so the
reliability of the injection isn't a problem.
Original comment by wbyo...@fadingred.com
on 1 Feb 2012 at 3:43
We've been using iLocalize, which gives the user the same. Also, we're now
using Transifex for the handling of translations, which also has a preview.
Original comment by ch...@growl.info
on 1 Feb 2012 at 3:59
Original issue reported on code.google.com by
ch...@growl.info
on 23 Nov 2011 at 3:06