Issue 20537 - Move strings from scp to officecfg for better language pack support
Summary: Move strings from scp to officecfg for better language pack support
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: joerg.barfurth
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-01 09:45 UTC by mkretzschmar
Modified: 2004-07-14 12:45 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description mkretzschmar 2003-10-01 09:45:02 UTC
In language pack scenarios (e.g. Ximian, Debian, ... packages) the menus for New
and Wizard are not correctly translated.

http://installation.openoffice.org/servlets/ReadMsg?msgId=627719&listName=dev

outlines possible solutions. A patch that adds the strings to officecfg is at

http://ooo.ximian.com/patches/OOO_1_1/gui-menu-new-wizard-translations.diff

It was created by some ad-hoc hackery. Strings for languages where I didn't know
the encoding were dropped. Is there a standard way to extract the strings in
UTF-8 from setup (.lng files) and merge them in .xcu files?

The mail says the strings can stay in scp, but that's of course duplication.
Would you accept a patch that moves those strings completely to officecfg?
Comment 1 Olaf Felka 2003-10-01 09:55:05 UTC
of -> mh: Please have a look.
Comment 2 chris 2003-10-20 15:25:02 UTC
confirming issue
Comment 3 Martin Hollmichel 2003-10-23 10:26:40 UTC
reassigned.
Comment 4 joerg.barfurth 2003-10-24 10:51:29 UTC
Both the installation process and the menu configuration will be
changed greatly for 2.0. I will keep an eye on these changes,
particularly as they relate to configuration, to ensure that they will
properly support creation of language packs.

The changes that have to be done for this will also include proper
migration of the menu texts.

I can use this task as a reminder for this. This would mean setting
the target to 2.0.

For the 1.1 codeline things are more difficult. I don't know the
effect of migrating these strings from scp to officecfg on translation
databases and gsi files. The change might also create problems for
'patch' upgrades (as opposed to full reinstalls). I am sure that this
is not desired for the StarOffice 7 codeline and will create
unnecessary extra work for OOo 1.1.x as well. 

Thus any solution for 1.1 would probably involve:
- Keeping the duplicate entries in scp and officecfg
- Allow to select either one using a build-time flag

The patch that is provided is still far from being feasible:

- Of course all existing languages must be migrated properly. 

For this it will be necessary to write a program/script that extracts
the strings from the scp files and converts them to UTF-8. The mapping
from language codes to text encodings that is used in setup/scp can be
found in some 'lang2textenc' (or similar) function in the tools module
(you can find this in LXR, starting from ~
SiConfigurationItem::Execute (setup2/source/agenda/action.cxx)).

- To keep the ability to use 'custom setup' (which is why the stuff is
in scp in the first place), these settings need special handling in
officecfg: The data for the res/<language>/... files needs to be 
generated, but the corresponding data/... files should not contain the
corresponding branch. 

To achieve this, a special attribute (or 'op' value) needs to be
introduced into the officecfg source xcu files and the
officecfg/util/alllang.xsl script needs to implement this new mode of
splitting up the files. To achieve configurability, a new parameter
for the script must be introduced.

- Makefiles in scp and officecfg, as well as config_office/configure
need to be changed to support that build-time option.

Because the given patch is more a sketch of a solution rather than a
usable patch, I changed the issue type to ENHANCEMENT for now.

I will not be able to do this myself for 1.1 although I am willing to
review any patch -> flagging as 'needhelp'

Please provide feedback whether you need this for 1.1.x and whether
you can help getting this done (properly). If that is not the case I
will change the target to 2.0 as explained above.

Comment 5 joerg.barfurth 2003-12-15 14:10:16 UTC
Will be done for 2.0
Comment 6 joerg.barfurth 2004-06-14 09:31:44 UTC
Implemented for OOo 2.0 as part of feature #25937# in CWS scp2officecfg.
Comment 7 joerg.barfurth 2004-06-14 09:45:05 UTC
Source code/build issue: marking as verified
Comment 8 joerg.barfurth 2004-07-14 12:45:24 UTC
Now available on MWS: closing
Comment 9 joerg.barfurth 2004-07-14 12:45:46 UTC
.