Issue 91642 - Localize error string
Summary: Localize error string
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: joachim.lingner
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-14 13:50 UTC by joachim.lingner
Modified: 2009-03-31 15:09 UTC (History)
1 user (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 joachim.lingner 2008-07-14 13:50:04 UTC
When there is a lock file for unopkg and one starts unopkg again then there is
the error message 
ERROR: Lock file indicates that a concurrent Office process is running!

This string should be localized.

See also  issue 88074
Comment 1 bettina.haberer 2008-07-17 16:52:22 UTC
The string has been specified as follows:
"ERROR: unopkg cannot be started. The lock file indicates it as already running.
If this does not apply, delete the lock file at:". 
The same string appears without the term "Error" at output in the warning-box.
Comment 2 joachim.lingner 2008-07-18 07:02:26 UTC
@jsk: On windows run unopkg.exe gui twice to see the message box. For the
console output run unopkg.exe gui and then unopkg.com list.
Comment 3 joachim.lingner 2008-08-12 16:07:49 UTC
Changes are documented in 
specs/www/appwide/packagemanager/unopkg_spec.sxw
Comment 4 joerg.skottke 2008-10-08 12:13:22 UTC
You said Windows, i tested Solaris ;-)
Verified.
Comment 5 lohmaier 2008-12-28 14:33:55 UTC
cws jl105 has not been properly integrated by RE/cws tooling. see comment to
issue 91204
Please check whether the fix for your issue actually made it into the master.
Comment 6 joachim.lingner 2009-01-09 12:07:40 UTC
Fixed again on cws jl111. Since we are past dead line for translation, the
message will not be localized - just English. See issue i97896, which is the
respective follow up task.
Comment 7 joachim.lingner 2009-01-09 12:10:43 UTC
see also issue 97896
Comment 8 joachim.lingner 2009-01-12 14:01:50 UTC
.
Comment 9 joachim.lingner 2009-01-12 14:11:48 UTC
.
Comment 10 joerg.skottke 2009-01-16 13:24:30 UTC
Verified, the error message now has the updated strings.
As stated in the issue above we do not have a translation yet.
Comment 11 joerg.skottke 2009-03-20 12:16:34 UTC
I set the issue to fixed but failed because - according to the test instructions
- we should get the error message when running unopkg.exe gui twice from the
console on Windows.

But there is no such error message coming up. This indicates that there is no
locking taking place (anymore).

Currently the first start of unopkg.exe gui starts the Extension Manager UI, the
second start just creates some background activity and the prompt returns
without any message. 

@JL: Please check again
Comment 12 joerg.skottke 2009-03-20 12:18:11 UTC
Reopen.
Comment 13 joachim.lingner 2009-03-31 15:09:02 UTC
@jsk: The locking does not work when the partition is compressed (Windows). I
think you submitted a different issue for this. This one is fixed.
Comment 14 joachim.lingner 2009-03-31 15:09:50 UTC
.