Jacek Furmankiewicz

In Part 1 of this article (PBDJ, Vol. 9, issue 4) we discussed creating resource DLLs using the open-source LCC-WIN32 C compiler, maintaining string phrases in its IDE, and utilizing the compiled resource DLLs in our PowerBuilder application. Although that provides the basic technical foundation for internationalizing an application, it still doesn't cover many of the real-life issues that come up during the internationalization process, which is what we'll cover in Part 2. Clarity of Code One thing that became obvious early on is that using only resource IDs without indicating to the programmer what sort of text they refer to quickly makes it very unreadable. Imagine opening a window in PowerBuilder and instead of seeing labels on the command buttons, text boxes, etc., ... (more)

Internationalizing PowerBuilder Applications with Resource DLLs

Expanding into other language markets presents an ample challenge for any PowerBuilder shop. In my case, we were faced with internationalizing our existing sales audit application into French (we're based in Quebec, where French versions of applications are required by law), as well as UK English (there are enough differences in retail terminology between North America and England to mak... (more)

Deploying PowerBuilder Applications Using NSIS

A common question we see in the newsgroups is "Where do I get the free version of InstallShield," or something along those lines. The truth is that deploying PowerBuilder applications is so easy (in most cases) that a full-blown, large commercial tool like InstallShield is overkill (especially when coupled with a behemoth of complexity such as Windows Installer). Unbeknownst to many, ther... (more)

Internationalizing PowerBuilder Applications with Resource DLLs Part 2

In Part 1 of this article (PBDJ, Vol. 9, issue 4) we discussed creating resource DLLs using the open-source LCC-WIN32 C compiler, maintaining string phrases in its IDE, and utilizing the compiled resource DLLs in our PowerBuilder application. Although that provides the basic technical foundation for internationalizing an application, it still doesn't cover many of the real-life issues th... (more)

Internationalizing PowerBuilder Applications with Resource DLLs

Expanding into other language markets presents an ample challenge for any PowerBuilder shop. In my case, we were faced with internationalizing our existing sales audit application into French (we're based in Quebec, where French versions of applications are required by law), as well as UK English (there are enough differences in retail terminology between North America and England to mak... (more)