I hope these two requests don't require too much work:
Since Windows uses a "strange" charset for its batch windows, some characters appear differently if the mod is being installed on Windows or on other OSs.
So, I wanted to use different tra files, depending on the OS.
I tried using three different files called setup-win32.tra, setup-unix.tra and setup-osx.tra, and to declare them as ~setup-%WEIDU_OS%.tra~ in the LANGUAGE tag, but the variable was not evaluated, and I can't see any way to select the proper file so early (I can only load other .tra files during the installation of a component, but then it's already late).
Is it possible to enable variable evaluation there?
I don't think there will be compatibility issues; I think most variables have not been set yet, and I don't think someone would put %WEIDU_OS% in a file or folder name.
Otherwise, perhaps allowing the construct:
LANGUAGE ~[language]~
~[something]~
EVALUATE_BUFFER ~path_with_vars~
(which is not allowed yet) could be more safe?
Another feature I think could be useful either with mods which deal with huge quantities of files (and directly biff some of them), or with mods which edit saved games, would be something like AT_UNINSTALL_EARLY, which is performed before any other uninstallation action, regardless of UNINSTALL_ORDER: changing the latter would break most AT_UNINSTALL actions, whereas the former could be used together with AT_UNINSTALL to perform some actions before, and some actions after uninstallation.
Thanks in advance
PS: is it possible to update prompts.tra in the weidu archive? The file in the windows .zip archive only has strings between -1000 and -1024, whereas I've seen (in some translated mods) there are also strings -1025 to -1039 (or even more, or less?)