allow translations for time zones in drop down menu in time.sh by carrying a short jsObj.property in the quoted text for the menu options. The field is split, parsed & evaluated as a javascript object, yielding the value.

commons.js: parseTimezones() - add a bit of i18n/L10n flexibility by checking the value of TiZ (which carries the new zone strings). If null (localized), behave as before. If there are properties, split on the space & eval the split value. Then reassemble the string.

time.sh: pass the TiZ object to parseTimezones
time.js: declare the TiZ object (which will be null in L10n firmware)

English-EN & Spanish-ES: add the new translations. For Spanish, I figured the natives would rather see their country (España) listed rather than Poland.

localize.py: support localizing this new type of expression

-----------------------
this was far&away better than the first try using the awk 2 file method relying on this heinous time.sh code:

	echo "var timezoneLines = new Array();"
	lng=$(uci -q get gargoyle.global.language)
	[ -n $lng ] && {
		tstr="./i18n/$lng/timezones_strings.txt"
		[ ! -e "$tstr" ] && tstr="./data/timezones_strings.txt"
		awk -F $'\t' -v TZ="$tstr" 'BEGIN { while ( getline < TZ > 0 ) { f1_i++; f1[f1_i] = $2; } } { printf "%s %s\t\t%s\t\t%s\n", substr($1,1,10), substr(f1[NR],2), $2, $4 } ' ./data/timezones_base.txt | awk '{gsub(/"/, "\\\""); print "timezoneLines.push(\""$0"\");"}'
} || awk '{gsub(/"/, "\\\""); print "timezoneLines.push(\""$0"\");"}' ./data/timezones.txt
	echo "var timezoneData = parseTimezones(timezoneLines);"
merge i18n timezone handling improvements from bashfulbladder
i18n/Polish: add timezone translations
Remove Thumbs.db
timezone names russian translation
Merge remote-tracking branch 'wildrat/master'
allow timezone translations to be used in more than 1 page (i18n)

firstboot.i18n.sh: add /www/time.js to gargoyle_header_footer pages required (holds the timeStr object needed when the Language-LG/time.js page is loaded) + the Language-LG/time.js for timezone definitions.

common.js: now hold the timezone definitions; more than 1 page uses timezones (firstboot & time), so this saves carrying the object thru to the common.js parseTimezones function

Note: ordinary/localized firstboot.sh doesn't require the added /www/time.js page because localized timezone translations are carried within the /www/data/timezones.txt document