Hi >> Have you a list of all codepages that scite supports? > This is in the documentation. i thought, that are only samples of the mostly used codepages. i want to include codepages to yasc so i need to know all the codepages, not only a part of them.
>> is it possible to change the definition of the imports? >> i write yasc so it doesn't change the global-config, but in the user-config >> i have no chance to manipulate the imports to decreasing the amount of >> properties to include. if the imports defined like the example below, i can >> change them in the user-config: >> imports=asm,au3,conf,cpp,css,html,lua,others,pascal,perl,ps,sql,vb > This is not possible as the global properties are read before the > user properties. You can import into user properties. The import > statement reads a file relative to the current file. is it possible to define a property for userconfig to exclude property-files? 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. the path can be used from globalconfig only the name of the lexer must be compared... >> are there any strings that must be translated and when yes, where do i found >> these strings in scite (length=>fully displayed?)? > All translated strings are listed in locale.properties. In SciTE > they exist in many places as literals and in resource files. i ask because i have no locale.properties found for 1.64 to add new strings to the version for 1.63 ;> Greets Frank mailto:[EMAIL PROTECTED] _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
