Article # 616, added by Geoworks, historical record
| first |
previous |
index |
next |
last |
The proper usage of @localize and monikers.
The big things that would aid the localization process are: - @localize instructions on almost every string, especially all of the non product-specific system geodes. - Get rid of any unused strings in the system, so it's clear to localizers that they don't have to be changed. - Change any UI, in both system and app geodes, so that definitions like: @object GenTriggerClass Foo = { GI_visMoniker = "Bar"; } is instead: @visMoniker BarMoniker = "Bar"; @object GenTriggerClass Foo = { GI_visMoniker = @BarMoniker; } The second version is more clear to the localizer, and more importantly, ResEdit can track it when chunks move around from one build to the next, and knows not to throw up its hands. Apparently this is a supreme headache for localizers.