From: Erik V. <eri...@hc...> - 2006-07-16 19:51:17
|
> Ok... I think I'm more or less done with moving all of the localizable > strings out to LocalisedText.properties. Any particular strategy behind using the different key format styles (e.g. LayTile and LAY_TRACK)? > I've also included some helpful text about the conventions used in the > file to further help anybody interested in translating. There is an easier and IMO far better way to format strings that contain variable values: MessageFormat. I have implemented this in LocalText.getText as a new signature getText (key, Object[]), where the 2nd arg is an array of objects (typically Strings). I have included one example on line 121 of LocalisedText.properties, which is used in ORPanel line 802. In addition: - fixed bug 1519026 (Canceling train purchase does not abort purchase). This was true for buying from another company, in the price request popup. - implemented request 1517709 (Deactivate train button), this applies to train buying if the company has no room for more trains. - fixed a few more bugs around train buying. Erik. |