Hi,
Here is what I have done;
1. I have built a project that supports a range of DataFields
2. I have set up product specific resource directories to adjust the things that need to be adjusted for each product - settings, properties, strings, JsonData
3. I have built various monkey.jungle, manifest.xml and batch script files to export the entire range of products with the correct manifest identifiers and resources
AND IT ALL WORKS!
I now want to be able to localise it and... well... Here is my problem;
If it was a simple project, I would simply create "resources-fre" and add French as a supported language.
But it is not a simple project!
project.manifest = manifest.xml ##################### # SINGLE SPORT base.resourcePath = $(base.resourcePath);customise-singlesport;customise-singlesportA #base.resourcePath = $(base.resourcePath);customise-singlesport;customise-singlesportB #base.resourcePath = $(base.resourcePath);customise-singlesport;customise-singlesportC ##################### # MULTI SPORT #base.resourcePath = $(base.resourcePath);customise-multisport ############### # Add settings at the end base.resourcePath = $(base.resourcePath);suffix-settings-resource
Based on the jungle above, I need to be able to specify a resources-fre for each of my customisations as the strings involved are unique to each project and I am running _WAY_ too close on memory to allow surplus in my projects!
What I need to know is how does the compiler detect language specific resources?
EG: If I simply created the product specific localisations in :
customise-singlesportA-fre
customise-singlesportB-fre
customise-singlesportC-fre
customise-multisport-fre
If I include those in monkey.jungle, will they overwrite / conflict with the other resources or will the compiler recognise them as product specific localisations?
What is the correct way for me to reference localisations explicitly? (Assuming this is even possible?)
