Reply to thread

Message

<blockquote data-quote="davidf" data-source="post: 686922" data-attributes="member: 19484">Albert,I can think of tons of things to do with them - if there is a valid source of data.&nbsp; The strings_&lt;lang&gt;.xml are currently the only reliable source of data.&nbsp; Take for instance the code from WeatherDotComCatcher:[code]&nbsp; &nbsp; &nbsp; &nbsp; ILocalization localization = ServiceRegistration.Get&lt;ILocalization&gt;();&nbsp; &nbsp; &nbsp; &nbsp; // handle only mappings of different spellings&nbsp; &nbsp; &nbsp; &nbsp; if (string.Compare(tokenSplit, &quot;T-Storms&quot;, true) == 0 || string.Compare(tokenSplit, &quot;T-Storm&quot;, true) == 0)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; localizedWord = localization.ToString(&quot;[Weather.TStorm]&quot;);&nbsp; &nbsp; &nbsp; &nbsp; else if (string.Compare(tokenSplit, &quot;Cloudy&quot;, true) == 0)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; localizedWord = localization.ToString(&quot;[Weather.Clouds]&quot;);&nbsp; &nbsp; &nbsp; &nbsp; else if (string.Compare(tokenSplit, &quot;Shower&quot;, true) == 0 ||&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; string.Compare(tokenSplit, &quot;T-Showers&quot;, true) == 0)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; localizedWord = localization.ToString(&quot;[Weather.Showers]&quot;);&nbsp; &nbsp; &nbsp; &nbsp; else if (string.Compare(tokenSplit, &quot;Isolated&quot;, true) == 0)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; localizedWord = localization.ToString(&quot;[Weather.Scattered]&quot;);&nbsp; &nbsp; &nbsp; &nbsp; else if (string.Compare(tokenSplit, &quot;Gale&quot;, true) == 0 ||&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; string.Compare(tokenSplit, &quot;Tempest&quot;, true) == 0)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; localizedWord = localization.ToString(&quot;[Weather.Storm]&quot;);&nbsp; &nbsp; &nbsp; &nbsp; else &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; // for all other tokens do a direct lookup&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; localizedWord = localization.ToString(&quot;[Weather.&quot;+tokenSplit+&quot;]&quot;);&nbsp; &nbsp; &nbsp; &nbsp; localizedLine.AppendFormat(&quot;{0} &quot;, localizedWord ?? tokenSplit); //if not found, let fallback&nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; return localizedLine.ToString();[/code]with all the code inspection in the world there is no way to determine that [Weather.DewPoint] is valid (or invalid for that matter).&nbsp; One way to get around this is to make the use of localized strings explicit:[LocalizedString(&quot;Weather.DewPoint&quot;)] or similar somewhere in the code (or more likely assembly) where it can be examined and compared against the strings_&lt;lang&gt;.xml files to determine if any are missing or extra.&nbsp; Similarly [ImportedLocalizedString(&quot;Media.MusicMenuItem&quot;)] could be used to declare uses of imported strings.So far we have achieved a chore for devs, so to make it work a carrot (or two) is needed.&nbsp; 1.&nbsp; Carrot (and stick): A tool to run (after compilation?) which will prompt on new and missing strings and test for the existence of imported strings.2.&nbsp; Another tool to manage translations/editing of existing files (this is pretty close to what's there).&nbsp; It would need the functionality of the tool in 1 to be complete rounded solution.Without a second source of data most of the really useful functionality is not possible or it would have disproportionate time needed spent (and wouldn't every be accurate as can be seen).Achieving a second source of data to make string management work correctly needs a change - it simply cannot work with only one data source.&nbsp; My preference would be a method which can be used on assemblies rather than on code - as sometimes code will not be easily available.Skin files are a slightly different proposition and would more easily be parsed.Opinions/alternatives welcome <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />David</blockquote>

[QUOTE="davidf, post: 686922, member: 19484"] Albert, I can think of tons of things to do with them - if there is a valid source of data. The strings_<lang>.xml are currently the only reliable source of data. Take for instance the code from WeatherDotComCatcher: [code] ILocalization localization = ServiceRegistration.Get<ILocalization>(); // handle only mappings of different spellings if (string.Compare(tokenSplit, "T-Storms", true) == 0 || string.Compare(tokenSplit, "T-Storm", true) == 0) localizedWord = localization.ToString("[Weather.TStorm]"); else if (string.Compare(tokenSplit, "Cloudy", true) == 0) localizedWord = localization.ToString("[Weather.Clouds]"); else if (string.Compare(tokenSplit, "Shower", true) == 0 || string.Compare(tokenSplit, "T-Showers", true) == 0) localizedWord = localization.ToString("[Weather.Showers]"); else if (string.Compare(tokenSplit, "Isolated", true) == 0) localizedWord = localization.ToString("[Weather.Scattered]"); else if (string.Compare(tokenSplit, "Gale", true) == 0 || string.Compare(tokenSplit, "Tempest", true) == 0) localizedWord = localization.ToString("[Weather.Storm]"); else // for all other tokens do a direct lookup localizedWord = localization.ToString("[Weather."+tokenSplit+"]"); localizedLine.AppendFormat("{0} ", localizedWord ?? tokenSplit); //if not found, let fallback } return localizedLine.ToString(); [/code] with all the code inspection in the world there is no way to determine that [Weather.DewPoint] is valid (or invalid for that matter). One way to get around this is to make the use of localized strings explicit: [LocalizedString("Weather.DewPoint")] or similar somewhere in the code (or more likely assembly) where it can be examined and compared against the strings_<lang>.xml files to determine if any are missing or extra. Similarly [ImportedLocalizedString("Media.MusicMenuItem")] could be used to declare uses of imported strings. So far we have achieved a chore for devs, so to make it work a carrot (or two) is needed. 1. Carrot (and stick): A tool to run (after compilation?) which will prompt on new and missing strings and test for the existence of imported strings. 2. Another tool to manage translations/editing of existing files (this is pretty close to what's there). It would need the functionality of the tool in 1 to be complete rounded solution. Without a second source of data most of the really useful functionality is not possible or it would have disproportionate time needed spent (and wouldn't every be accurate as can be seen). Achieving a second source of data to make string management work correctly needs a change - it simply cannot work with only one data source. My preference would be a method which can be used on assemblies rather than on code - as sometimes code will not be easily available. Skin files are a slightly different proposition and would more easily be parsed. Opinions/alternatives welcome :D David [/QUOTE]

Verification