Issue 34658 - languagepack/RPM: empty directories and common files?
Summary: languagepack/RPM: empty directories and common files?
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: pavel
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-27 09:52 UTC by pavel
Modified: 2004-12-19 09:32 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2004-09-27 09:52:35 UTC
Hi,

today, I'm exploring language packs generated by instsetoo_native. Overall: good
work! Really.

Now for the details. I'm building with ENUS and CZECH, thus cs language pack is
generated. I unpacked it and am looking at files/directories it contains. There
are several empty directories that are also in the main packages etc:

Empty directories that are part of the main package:

./opt/openoffice1.9.55/program/addin
./opt/openoffice1.9.55/program/plugin
./opt/openoffice1.9.55/share/uno_packages/cache
./opt/openoffice1.9.55/user/Scripts
./opt/openoffice1.9.55/user/autocorr
./opt/openoffice1.9.55/user/backup
./opt/openoffice1.9.55/user/psprint/driver
./opt/openoffice1.9.55/user/psprint/fontmetric
./opt/openoffice1.9.55/user/store
./opt/openoffice1.9.55/user/temp
./opt/openoffice1.9.55/user/template
./opt/openoffice1.9.55/user/uno_packages/cache
./opt/openoffice1.9.55/user/wordbook

Czech language pack also contains psprint.conf:
./opt/openoffice1.9.55/share/psprint/psprint.conf

This file is also present in en-US package. The only difference is paper size.
But this file will conflict resulting in the case where we can't install more
than one language pack. And this file is also present in the -core package...
Comment 1 Olaf Felka 2004-09-27 09:54:39 UTC
of @ obr: please have a look.
Comment 2 pavel 2004-09-27 10:17:20 UTC
psprint.conf: It looks like someone is trying to do "localization" (paper
format) in scp2/source/ooo/file_extra_ooo.scp:

File gid_File_Extra_Fontunxpsprint
    Dir = gid_Dir_Psprint;
    TXT_FILE_BODY;
    Styles = (ARCHIVE, SETUPZIP, DONT_OVERWRITE);
    Name (en-US) = "/letter/fontunxpsprint.zip";
    Name (pt) = "fontunxpsprint.zip";
    Name (ru) = "fontunxpsprint.zip";  
    Name (el) = "fontunxpsprint.zip";

I'd personally prefer another way of configuration of the default paper format.
Do we have any other way to do that? (Shouldn't this be separated to own issue
and assigned to psprint people?) Why? The current approach means that for every
new language, we have to add line here. This is IMO unacceptable and makes it
hard to maintain. E.g. right now, we use ISO codes and we still have:

    Name (50) = "fontunxpsprint.zip";
    Name (99) = "fontunxpsprint.zip";   

there.
Comment 3 nospam4obr 2004-09-27 10:21:44 UTC
Is is on vacation for two weeks. I need to check with our printing experts.
Comment 4 christof.pintaske 2004-09-27 11:52:53 UTC
the psprint.conf/papersize thing is a known issue: "i34064 rpm language packs
conflict in psprint.conf". 
Comment 5 nospam4obr 2004-10-05 13:57:21 UTC
obr -> is: as requested by 'boss', back on your pile.
Comment 6 ingo.schmidt-rosbiegal 2004-10-11 12:31:00 UTC
This was already fixed in my cws langsupporter by removing
gid_File_Extra_Fontunxpsprint from language packs (not nice, but a fast
solution). The correct solution is in i34064. 
Therefore I set this task to "fixed".
Comment 7 ingo.schmidt-rosbiegal 2004-10-13 10:29:38 UTC
No conflicts during the language pack installation -> verified
(the correct solution is introduced by #i34064#
Comment 8 ingo.schmidt-rosbiegal 2004-12-17 10:18:47 UTC
reopen
Comment 9 ingo.schmidt-rosbiegal 2004-12-17 10:19:20 UTC
reassign
Comment 10 ingo.schmidt-rosbiegal 2004-12-17 10:21:51 UTC
is -> pjanik: There are no more conflicts in the language packs.  The empty
directories are still created (because of the CREATE flag in scp2). If this is a
problem for you, please make a new issue (probably OOo Later).
Comment 11 pavel 2004-12-19 09:32:31 UTC
OK. Verified, closing.