Oh boy … (update)

The migration to Subversion apparently did have some cost attached to it. Just found out that for whatever reason the resource scripts have been garbled. Hmpf …

Update: Actually the culprit must have been one of the editors used two/three years back, according to the history. It only affected those languages with real diacritic characters (e.g. Polish) and completely different alphabet (Cyrillic/Russian) that could not be fit into the 1252 ANSI code page (the default on my system). This website from Microsoft really helped to find the correct matched for each code page. Hoefully the UTF8 version of the resource scripts is now correct. Parsing the strings inside string tables was pretty straightforward, but the PITA will be the controls in dialogs (which also need to be extracted). Just to explain briefly what I am going to do: all the resource DLLs will be replaced by a text file (most likely XML, as the saving of reports is another good reason to use an XML library already). This will allow anyone with basic understanding of computers to contribute translations (or pieces thereof) without having to know the (slightly convoluted) syntax of resource scripts (.rc files).

// Oliver

This entry was posted in Translation, Uncategorized. Bookmark the permalink.

11 Responses to Oh boy … (update)

  1. It would be really nice to have some Windows Explorer integration, via context-menu with an option “Scan with WinDirStat” or alike on drives and folders.

  2. TesserId says:

    Context menu can be manually created from explorer using Tools->Folder Options->File Types. For both “Drive” and “File Folder”, click the “Advanced…” button. In the “Edit File Type” dialog, click “New…”. Enter a description under “Action”, like “Scan with WinDirStat”. Under “Application to use perform action”, enter the full path to WinDirStat, which you can browse for or copy from a WinDirStat shortcut (typically: “C:\Program Files\WinDirStat\windirstat.exe”).

  3. TesserId says:

    Sorry, please ignore my last suggestion.

    There’s a Windows annoyance that rears its ugly head when attempting to add context menu items for folders and drives. There is a workaround for it, but it’s too complicated to add here (though I will post it on request, it is for advanced power users).

  4. SKMorton says:

    I’ve been using v1.1.2.80 (unicode) as a portable app. Though it’;s really come in handy, a print feature would be great!

  5. Brad says:

    TesserID!

    I’d really like to know how to add this to context menu for folders and drives

  6. Brad says:

    I got it to add to the context menu for folders by adding the following registry key:

    HKCR\Directory\shell\WinDirStat\command
    @=”C:\Program Files (x86)\WinDirStat\WinDirStat.exe” “%1”

    Not sure how to get it to show up on drives yet…

  7. Mark Huessy says:

    Brad: any luck with drives yet?
    Your directory key works wonderfully (modified to match my actual paths).

  8. Adrian says:

    @Brad

    Thanks mate, that was all I needed, much appreciated.

  9. Ted says:

    The following will enable scanning a drive as well as a folder with WinDirStat, just paste into Notepad, save it with whatever name you want adding “.reg” at the end, then run it:

    Windows Registry Editor Version 5.00
    [HKEY_CLASSES_ROOT\Directory\shell\windirstat]
    @="WinDirStat Here"
    [HKEY_CLASSES_ROOT\Directory\shell\windirstat\command]
    @="\"C:\\Program Files (x86)\\WinDirStat\\windirstat.exe\" \"%1\""
    [HKEY_CLASSES_ROOT\Drive\shell\windirstat]
    @="WinDirStat Here"
    [HKEY_CLASSES_ROOT\Drive\shell\windirstat\command]
    @="\"C:\\Program Files (x86)\\WinDirStat\\windirstat.exe\" \"%1\""

    Make sure to change both instances of C:\\Program Files (x86)\\WinDirStat\\windirstat.exe if WinDirStat is installed in a different location.

  10. Concerned Citizen says:

    Ted’s script is great and works perfectly for me with only one exception, when the context menu is used to launch WinDirStat my system drive (C:), it points the program to C:\Windows\System32 for some reason.

  11. Ethan T says:

    To fix integration with drives, modify the end of the command for the Drive entry ONLY from:

    \”%1\””

    to:

    \”%1\\\””

    Note the extra two backslashes. That turns “c:” into “c:\” so that it opens the root directory of the drive rather than the current directory of that drive.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.