I’m pushing versions for testing private codes and i feel having this setting on by default is a waste and may take processes that shouldn’t be used when doing private versions for testing.
I feel this option should be off by default in the preferences and then you can either turn it on with the check box or also turn it on in preferences
Just a thought i had while pushing a ton of private versions for testing
@Jamie_Dale ^^^
Would be nice if it also had the persistence for the option to be per project ie new project is off ect then when you are ready you publish and turn it on in a setting then every other version will be on
Hey, thanks for the feedback.
This option is really designed for devs who don’t want to think about localization at all, with an end goal of having islands be localized by default. It’s enabled by default for that reason, and is checked by default as any build may be a publishing candidate.
The auto localization result is cached and iterative, so it only re-runs if something localization related has changed between the two builds, and only on the subset of changed strings.
If you do want to think about localization then you can turn the option off in your project settings until you’re ready to start publishing, or continue to just manually export and auto localize as you would have prior to 38.10. I realize that “disable this permanently” sounds more final than it actually is, as you can disable and enable it for your project at any point - I’ve adjusted that phrasing for 39.10.
Any manual localization data in your project is merged into the aforementioned cache when generating a build (meaning it’s used as the base localization data), so the two methods are designed to work together.
Thank you for the details explanation. It was more an observation i had when pushing testing versions. Your clarification explains it well.
