ST: Strange behaviour for some Metazone entries

Description

Look for instance at (sv locale, an Australian metazone):
[squo] Lord_Howe/​commonlyUsed false
[squo] Lord_Howe/​long/​daylight Lord Howe Daylight Time 1:25 PM Lord
Howe Daylight Time 13.25 GMT+11.00
[squo] Lord_Howe/​long/​generic Lord Howe Time 1:25 PM Lord Howe Time
13.25 Lord Howetid (Australien)
[squo] Lord_Howe/​long/​standard Lord Howe Standard Time 1:25 PM Lord
Howe Standard Time 13.25 GMT+10.30
[squo] Lord_Howe/​short/​daylight LHDT 1:25 PM LHDT LHDT[star] 13.25
LHDT
[squo] Lord_Howe/​short/​generic LHT 1:25 PM LHT 13.25 Lord Howetid
(Australien)
[squo] Lord_Howe/​short/​standard LHST 1:25 PM LHST LHST[star] 13.25
LHST
Items 1 to 35 of 35

1) ST prefers an empty entry over a new value (for Lord_Howe/​commonlyUsed).
2) ST prefers an empty entry over an inherited value (for
Lord_Howe/​short/​generic).

ST has similar behaviour for other metazones, this was just an example.

xpath

None

locale

None

Status

Priority

TBD

Assignee

Steven R. Loomis

Reporter

TracBot

tracReporter

Reviewer

None

Labels

Components

Fix versions

None

phase

None
Configure