Takeshi Posted March 2, 2006 Posted March 2, 2006 Under GET LANG section in HFSLIP_60220.cmd:IF "!Localization!"=="Chinese(PRC)" SET LG=CNIF "!Localization!"=="Chinese(PRC)" SET LNG=CHTrem IF "!Localization!"=="Chinese(Taiwan)" SET LG=CHT ?????????????IF "!Localization!"=="Chinese(Taiwan)" SET LNG=CHTAccording to the expanded folder of windowsupdateagent20-x86.exe, shouldn't Chinese(PRC) be SET LG=zhcnandChinese(Taiwan) be SET LG=zhtw?The EULA in those folders are correct for the respective languages.And what's the purpose of SET LNG?
Tomcat76 Posted March 2, 2006 Posted March 2, 2006 The Chinese part needs some improvement. The problem is that the Microsoft documents are conflicting themselves so HFSLIP depends on user input for that.Try the latest version (60302). I made some changes to the localization section.
Takeshi Posted March 3, 2006 Author Posted March 3, 2006 Fine.In reply to your pm query about prodspec.ini, the relevant entries areWindows 2000 Simplified Chinese version:Localization=Chinese(PRC)Windows XP (Taiwanese version and Hong Kong version, both Traditional Chinese):Localization=Traditional Chinese
Tomcat76 Posted March 3, 2006 Posted March 3, 2006 You just confirmed my assumption on the difference between "Simplified" and "Traditional". Thanks-- Your post has been very helpful. "Chinese(PRC)" should be fine in the current version of HFSLIP but I'll update it tomorrow to add support for "Traditional Chinese".
tommyp Posted March 4, 2006 Posted March 4, 2006 Tomcat to the rescue! Do you think that microsoft ate their leaded paint chips this morning?
Takeshi Posted March 4, 2006 Author Posted March 4, 2006 Thanks you're welcome. IF "!LG!"=="" ECHO You have run run the WindowsUpdateAgent20 manually after installationDo you mean: You have to run...Would you mind explaining the purpose of SET LNG? I can't find any more reference to this env variable outside the GET LANG section.
Tomcat76 Posted March 4, 2006 Posted March 4, 2006 It's already fixed for the version that'll be released tomorrow. I noticed it while rearranging the entire Localization section. Thanks anyway for reporting it."LNG" is not really used for the moment. Could be in the future...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now