 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / IDE / February 2007problems with hebrew shortcuts in setup project
Hi Everybody, I'm trying to create a setup program for a WinForms application I've written. The program is in hebrew, so I want the shortcuts created by the setup program to be in hebrew as well. However, When I change the text of the shortcuts to contain hebrew text I get a warning : WARNING: Invalid language characters in property 'Name' and when I compile and install the setup I get gibberish in the shortcut text. Is this a known problem, and is there a way to get around it? Thanks, Nadav Hello Nadav, From your description, you're building a setup package via the VS 2005 setup project. However, when adding a shortcut with hebrew text name, you get the "WARNING: Invalid language characters in property 'Name'", correct? Regarding on this problem, I've searched in the internal database and so far there hasn't any known issue on this. I've also tested on my local environment and did get the warning and when run the setup program it create a shortcut with undisplayable text. However, I've also tested some other wide char languages such as chinese, it also report such warning at design-time when you compile the program. However, at runtime, the shortcut link is displaying correctly. Therefore, I think it is possible that text in the shortcut has been encoded through the hebrew charset instead of unicode charset which cause those operating systems( which doesn't configure system locale/charset as hebrew )unable to display the text. Have you tried the setup program on some machine which has set system locale as hebrew compatible charset and also has all hebrew text required localized resources? Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. Hi Steven, The computer I tried it on has Windows XP with english GUI. The default locale is en-US, but it does have the necessary resource so I can enter text in hebrew (I compiled the setup program on the same computer I installed it on). > Have you tried the setup program on some machine which has set system > locale as hebrew compatible charset and also has all hebrew text required > localized resources? I'm not sure how to set the system locale as a hebrew charset. Nadav Hello Nadav, As for the System Locale, for windows XP and windows 2003 server, they're in the following location: Open "Control Panel---->Regional and Language options" In the Dialog, choose the "Advanced" tab, you will find a dropdownlist with the following description above it) "select a language to match the language version of the non-Unicode program you want to use" Change the selected item to "Hebrew" or any compatible one click OK to save the setting and you need to reboot the machine to make it take effect. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. Hi Steven, > As for the System Locale, for windows XP and windows 2003 server, they're > in the following location: [quoted text clipped - 6 lines] > "select a language to match the language version of the non-Unicode program > you want to use" I've checked my System locale and it was 'Hebrew'. Nadav Thanks for your reply Nadav, I've also perform some test with another setup engineer and did found that the problem is not coupled with operating system setting. Actually, we found that the problem is due to the VS setup project can not accept "hebrew" text, as in the project's "Localization" property of the setup project, it doesn't contain a "hebrew" item. Therefore, after we build the MSI package, the "hebrew" text is incorrectly converted as gibberish. So far what we can get is use the platform sdk utility to manually modify the generated MSI package and edit the text in it. VS setup project provides a subset of the windows installer sdk's features. Here, in order for Windows Installer to read the language properly, the code page of the MSI package should be set accordingly. To achieve the goal, we can use the Windows Installer Platform SDK tool Orca, here is knowlege base article introducing this tool: How to use the Orca database editor to edit Windows Installer files http://support.microsoft.com/?id=255905 And you need to follow these steps: 1. Build the Setup project. 2. Open the MSI with Orca. 3. Open the menu ¡°View¡± | ¡°Summary Information¡±. Change the ¡°Languages¡± to 1037. 4. Open the menu ¡°Tools¡± | ¡°Code Page¡±. Change the code page to 1255. 5. Go to the Shortcut table. Revise the ¡°Name¡± property for the shortcut and set it to the correct Hebrew characters. Hope this helps. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. Hi Steven, Thanks for your reply. Do you know where I can get the Orca tool? Thanks, Nadav Thanks for your quick reply Nadav, The following kb article also include the link to the installer sdk package which contains the tool: How to use the Orca database editor to edit Windows Installer files http://support.microsoft.com/?id=255905 Please feel free to let me know if it helps. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. Hi Steven, The link provided in the kb article leads to 'Windows® Server 2003 SP1 Platform SDK Web Install'. Can I install and use this on a Windows XP SP2 system? Thanks Nadav Hi Nadav, As for the SDK download linked in the kb article, it also targets windows xp system as described in the overview section as below: ===================== Overview This is no longer the most recent edition of the Platform SDK, please download the Windows Server 2003 R2 SDK - March 2006 Edition, (see related resources). The Microsoft? Windows? Software Development Kit (SDK) provides the documentation, samples, header files, libraries, and tools you need to develop applications that run on Windows. The applications you develop with this edition of the SDK can run on the x86, x64 and Itanium-based versions of Windows Server 2003 SP1, Windows XP SP2, Windows XP x64 Pro Edition, and Windows 2000. A new custom install allows you to select components you wish to install on a more granular level. This edition of the SDK replaces the previous SDKs for Windows XP SP2 and Windows Server 2003 and can be used to develop applications for those platforms. This SDK is also available as a low-cost CD. You can also order some of the legacy releases of the SDK at the site. To order a CD, click Order ============================= Therefore, you can use it directly for your XP system. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. Thanks Steven, I guess I didn't read past the title of the page. Me bad :) I'll download it and try to edit the msi and see how it goes. Thanks Nadav Hi Steven, The instructions you gave me did fix the problem! Thanks, Nadav, > Thanks Steven, > [quoted text clipped - 5 lines] > Thanks > Nadav Thanks for your followup Nadav, I'm glad that the suggestion helped you. Have a good day! Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.