Changes between Version 2 and Version 3 of maestro/Translation
- Timestamp:
- 12/08/09 14:39:02 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
maestro/Translation
v2 v3 9 9 * Microsoft .Net Framework 2.0 [http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5 Download] (Should be installed) 10 10 * Microsoft .Net 2.0 SDK [http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-c96d69c35dec Download] (Included in Visual Studio 2005 or newer) 11 * A Subversion client, TortoiseSVN is fine for Windows [ /http://tortoisesvn.net/downloads Download]11 * A Subversion client, TortoiseSVN is fine for Windows [http://tortoisesvn.net/downloads Download] 12 12 13 13 All the mentioned files should install and run just fine under Wine, except TortoiseSVN. … … 130 130 All the files that are missing a "neutral" resx file (those with only a `*`.en-US.resx file) must be edited with a text editor. They all start with a lot of boilerplate system code, and then multiple entries of the form: 131 131 {{{ 132 <data name=" TimeParseError" xml:space="preserve">133 <value>Unable to parse "{0}" into a time offset: {1}</value>132 <data name="OpenFileError" xml:space="preserve"> 133 <value>Unable to open "{0}", error message: {1}</value> 134 134 </data> 135 135 }}} … … 137 137 The "name" attribute is a system key, and may not be changed. 138 138 The text between the {{{<value>}}} and {{{</value>}}} is the one that needs translating. 139 The special items {0} and{1} are placeholders for some text that Maestro will insert. It should be fairly obvious what the fields will be substituted with, but if in doubt, ask on the [http://mapguide.osgeo.org/user.html MapGuide-Users mail list].139 The special items !{0} and !{1} are placeholders for some text that Maestro will insert. It should be fairly obvious what the fields will be substituted with, but if in doubt, ask on the [http://mapguide.osgeo.org/user.html MapGuide-Users mail list]. 140 140 141 141 == Building and testing the dll's ==