Ticket #367 (Fixed)Mon Dec 02 16:05:06 UTC 2013
Internationalisation bug: !Configure doesn't use a configure plugin Message<n> file
| Reported by: | Dick Tanis (1648) | Severity: | Normal |
| Part: | RISC OS: Application | Release: | |
| Milestone: | Status | Fixed |
Details by Dick Tanis (1648):
The !Configure application in !Boot only uses the text from !<pluginname>.Messages. This means that other language files like Messages7, Messages34 etc are not used for the text under the icons in the main configuration window when their Territory is configured. Also the text from the window ‘About this plugin’ is only read from !<pluginname>.Messages.
Changelog:
Modified by Dick Tanis (1648) Tue, December 03 2013 - 13:09:18 GMT
- Summary changed from Internationalisation bug: !Configure doesn't use a configure plugin Messages
file to Internationalisation bug: !Configure and configure plug-ins don't use the Messagesfile
Also the configure plug-ins which use Toolbox for their resources don’t use the Messages<territory number> file.
Modified by Dick Tanis (1648) Tue, December 03 2013 - 14:20:02 GMT
- Summary changed from Internationalisation bug: !Configure and configure plug-ins don't use the Messages
file to Internationalisation bug: !Configure doesn't use a configure plugin Messagefile
Changed ticket bug almost back to it’s original title. The configure plug-ins are working correctly. Read page 15 of the toolbox manual and found out that Toolbox searches for Message<n> and not Messages<n>. The problem still remains that !Configure doesn’t use the Message<n> file when it searches for the plug-ins.
Modified by Sprow (202) Sat, December 07 2013 - 09:30:22 GMT
- Status changed from Open to Fixed
Fixed in Main-2_10.
