+ Reply to Thread
Results 1 to 2 of 2

Thread: Localizing include scripts

  1. #1
    Unregistered Guest

    Default Localizing include scripts

    Include scripts like the VC++ 2008 redistributable, or MSI 3.1 don't seem to have the same functionality when you open them in Developer edition. So to localize these, is the following the best practice?

    If %CURLNG% Equals "1031" Then
    Display Message Box "Something in German"
    ElseIf %CURLNG% Equals "1041" Then
    Display Message Box "Something in Japanese"
    Else
    Display Message Box "Something in English"
    End

  2. #2
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Localizing include scripts

    Hello,

    %CURLNG% always holds the GetSystemDefaultLangID() Windows API return value. This function returns the language identifier for the system locale. Your code snipped should work fine.

    Friedrich

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •