Zibi Braniecki [:zbraniecki][:gandalf] Reporter
	Description • 11 years ago

Branding files aren't correctly picked up

	Staś Małolepszy :stas
	Comment 1 • 11 years ago

This bug results in errors like the following ones

/home/stas/moz/b2g/gaia/shared/locales/branding/unofficial/branding.ar.properties could not be found.
/home/stas/moz/b2g/gaia/shared/locales/branding/unofficial/branding.ar.properties could not be found.

	Axel Hecht [:Pike]
	Comment 2 • 11 years ago

Can you be more precise on what this bug is about?

I'm asking because we're not exposing official branding to l10n, but we do expose unofficial.

	Staś Małolepszy :stas
	Comment 3 • 11 years ago

The key lines in the patch are:

+                # copy official branding from en-US, not from source
+                copy_official_branding(target_dirname, filename, locale)
+                # localization files can only modify unofficial branding, 
+                # amend the path accordingly
+                target_dirname = os.path.join(target_dirname, 'unofficial')

Currently, we read all English files (say, settings.properties and branding.properties) and then overwrite the English translations in the gL10nData dict with another language, but this another language's branding files are not in shared/.

So everything works as expected for official branding, because we do want en-US there, but it doesn't work for unofficial.

Also, if we ever switch the way we compose the translations dictionary (e.g. in L20n each locale is stored separately), we'll run into 404 errors.

	BMO Automation
	Comment 4 • 7 years ago

Firefox OS is not being worked on