Issue 6261 - localized builds won't install
Summary: localized builds won't install
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Windows 2000
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact: issues@installation
URL:
Keywords:
: 6262 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-07-03 13:31 UTC by Unknown
Modified: 2013-08-07 15:26 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-07-03 13:32:46 UTC 
All non-english builds won't install. Installation process aborts at 
the point when the file type select menu should appear and reports 
an 'application error'. 

This only happens when setup.exe is started outside the build environment 
(from freshly opened shell or file browser). Installation does work when 
the winenv.bat file has been executed before.
Comment 1 Olaf Felka 2002-07-03 13:38:56 UTC 
*** Issue 6262 has been marked as a duplicate of this issue. ***
Comment 2 Martin Hollmichel 2002-07-03 13:56:18 UTC 
some resource files cannnot be found. if you reset STAR_RESOURCEPATH
in build environment you should have the same error.
but I also forgot the solution.
Comment 3 Unknown 2002-07-03 14:09:27 UTC 
well, what do you suggest me to do (since you re-assign the issue 
to me?? I'm a bit clueless, and how can re-assigning to me help?
Comment 4 Unknown 2002-07-03 16:56:32 UTC 
I don't understand how this issue is handled. It goes back to me, 
but if I knew how to solve it I wouldn't have filed it in the 
first place. Then I don't understand the 'target milestone' change 
to 'next build' (the entry is not well defined). Does this mean 
that you want to drop windows localised builds for the 1.0.1 
release? I don't believe that.
Comment 5 Martin Hollmichel 2002-07-04 12:47:36 UTC 
does it only occur on the windows platform ?

are the same set of resource files for english and non english installed?
Comment 6 Unknown 2002-07-04 13:39:00 UTC 
only windows is affected. The error occurs when the menu for 
MS file type selection should pop up (which explains why only 
windows is affected). 

I compared the resourcefiles between solaris and windows, and 

reg4msdoc64101.res

appears additionally for windows. Seems right. 

I see the same resource files for windows/english and windows/french. 

Full list: 

jvm64133.res
reg4msdoc64133.res
set64133.res
svs64133.res
svt64133.res
tplx64133.res
uui64133.res
vcl64133.res

(and the corresponding ones in english). 

So, there is nothing in linux or windows/english which is missing 
in windows/french...
Comment 7 Unknown 2002-07-05 10:41:49 UTC 
No new status? 

I've added a french installation set on blossom (maybe should have 
done this earlier)
Comment 8 Martin Hollmichel 2002-07-08 12:58:32 UTC 
reassigned to lla
Comment 9 lars.langhans 2002-07-08 13:16:31 UTC 
Problem is, that we search to a set_pp1*.res which we don't found in a
normal build, by this, we set the default language to
LANGUAGE_KOREAN_JOHAB or something equal. 
In a src641 setup2/source/ui/main.cxx 1.67.4.13 this is fixed
in an openoffice1.0.1 setup2/source/ui/main.cx 1.67.2.2 not.
Comment 10 Martin Hollmichel 2002-07-08 14:11:16 UTC 
now joined to OOO_STABLE_1
Comment 11 Martin Hollmichel 2004-02-17 08:54:54 UTC 
verified.
Comment 12 Martin Hollmichel 2004-02-17 09:03:08 UTC 
close issue.