Frank Wunderlich: > is it possible to define a property for userconfig to exclude > property-files?
No currently, because of the ordering. At the stage this decision needs to be made, user properties have not been read. While the ordering could be reversed, there are other possible uses (such as an administrator setting properties in global properties which are required at user properties read time) where the current ordering may be better. > the sense is that the global-config is a versionbased config from the > maintainer and i always need to change the imports when i install a > new version, if i can set a exclude in userconfig, i see only my > wanted language-configs and the new ones. I understand the requirement but have not found a good solution. There are conflicts here between making it easy for new languages to be incorporated (I would like it to be possible to add a language by copying a file into a directory), keeping the user interface tidy without enormous lists, distributing SciTE with a large set of languages, and making it easy for users to choose and fix conflicts. > i ask because i have no locale.properties found for 1.64 to add new > strings to the version for 1.63 ;> When locale.properties does not change between releases it either means there are no new strings or I am not aware of them. When new user interface elements are contributed, they should include updates to locale.properties. Neil _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
