Issue 15224 - localize tool crashes
Summary: localize tool crashes
Status: CLOSED FIXED
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: nils.fuhrmann
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-02 22:25 UTC by simonbr
Modified: 2013-08-07 15:00 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 simonbr 2003-06-02 22:25:39 UTC
In cygwin under Windows XP, using one of the examples suggested by the localize 
tool itself: 

>>>>>start of screen dump<<<<<<
Simon@max /cygdrive/c/ooo_1.1beta2_src
$ tcsh
[Simon@max ...c/ooo_1.1beta2_src]$ source winenv.set
[Simon@max ...c/ooo_1.1beta2_src]$ localize -e -i de-CH -l 01,99=35 -f MyFile

============================================================
Current settings:
============================================================
Mode:          extract
Workspace:     SRX644
Source tree:   \cygdrive\c\ooo_1.1beta2_src
Languages:     01,99=35
ISO code (99): de-CH
Filename:      MyFile
============================================================

Reading database /CYGDRIVE/C/OOO_1.1BETA2_SRC/SOLENV/CONFIG/STAND.LST ...
>>>>end of screen dump<<<<<

After this message, the localize tool crashes: "Unhandled exception in 
localize.exe(TL644MI.DLL):0xC0000005: Access violation."

The debugger locates the problem in c:\...\communi\geninfo.cxx, line 217.
I am not sure what more information would be relevant.
Comment 1 Dieter.Loeschky 2003-06-05 11:27:56 UTC
DL->NF: Would you please takeover?
Comment 2 nils.fuhrmann 2003-06-06 13:29:37 UTC
NF: I'm not sure how cygwin deals with path separators and thinks like
that. My question is if the stand.lst is available at the given
lokation and how path seperators are valid within cygwin
Comment 3 simonbr 2003-06-06 19:50:04 UTC
Yes, stand.lst is there. Also, apparently cygwin is all right with 
forward slashes, and is caps/no caps insensitive: 

[Simon@max ~]$ ls /CYGDRIVE/C/OOO_1.1BETA2_SRC/SOLENV/CONFIG/
CVS          minorpat.lst  ssrx644.ini  unlocked.flg
default.lst  ssolar.cmn    stand.lst
[Simon@max ~]$ ls /CYGDRIVE/C/OOO_1.1BETA2_SRC/SOLENV/CONFIG/STAND.LST
/CYGDRIVE/C/OOO_1.1BETA2_SRC/SOLENV/CONFIG/STAND.LST
[Simon@max ~]$
Comment 4 josef.cacek 2003-06-11 11:26:48 UTC
I have the similar problem during czech localization.
I'm working under 4NT and I get unhanced exception in transex3.exe.
It seems as stack overflow. Debuger find exception in
transex3\source\export.cxx line 588 in my case.
[if ( sTmpLine.GetChar(( USHORT )( sTmpLine.Len() - 1 )) != '\\' )]

So, I have to use transex3 project from Beta1 to build czech versions
for windows in this time.
Comment 5 simonbr 2003-08-02 14:03:51 UTC
For what it's worth, when debugging localize.exe in 
MSVC++6, "unhandled exception error in localize.exe (TL645MI.DLL): 
0xC0000005: Access Violation" occurs immediately when stepping into 
line 77 in scriter.cxx (OOo1.1RC2), in 
SourceTreeIterator::SourceTreeIterator().

Because I am not that proficient in C++ and MSVC++6 I have no idea 
how to analyze the problem further. 
I hope this provides a clue to someone who can fix the problem 
though, because it's rather inconvenient to setup a build environment 
under Linux just to get around the localize tool not working under 
Windows. 

BTW, I started MSVC++6 from a Windows command window, after setting 
the necessary environment variables, so the problem is not due to 
using cygwin. 
Comment 6 quetschke 2003-08-02 14:46:36 UTC
Hi Simon,

this issue is a duplicate of issue 16650.

The problem is that your environment variables are all set
to cygwin/posix format. localize.exe is a native w32 program
and cannot handle posix styles.
But instead of giving a file not found or illegal path or something
it just crashes.

Can you please try what I told Olivier in that other issue.
Please start:

$ guw.pl -env localize <put your switches here>

in your cygwin tcsh shell and tell us the results.
Comment 7 simonbr 2003-08-02 15:16:06 UTC
Hi Volker, 
It helps, but now I get unhandled exceptions errors for transex3.exe 
for *some* files, such as res_bmp.src. I use the arguments as 
suggested by localize.exe itself (first example). 
I have to go out now, but later I'll try if it works better in a 
Windows Command shell. 
Comment 8 quetschke 2003-08-02 15:26:52 UTC
I never tried to lolalize anything. Can you tell me your commandline
and attach your "localization file" maybe I can find something.

Is there a howto for this localization stuff?
Comment 9 simonbr 2003-08-02 20:53:17 UTC
guw.pl -env localize -e -i de-CH -l 01,99=35 -f MyFile

which are the arguments from the first example that localize.exe 
gives when called without arguments.
Comment 10 simonbr 2003-08-02 20:54:47 UTC
Note that this command should generate a localization file. 
Comment 11 intersol 2003-08-05 10:55:10 UTC
I have the same problem on XP with 4NT. 
I need a fix or an workaround ASAP.
Comment 12 quetschke 2003-08-06 19:15:10 UTC
Hi Simon,

I just tried:
$ guw.pl -env localize -e -i de-CH -l 01,99=35 -f MyFile

with my current cws_srx645_ooo11rc3 tree (checked out this morning).
(W2K, MSVC6, tcsh) and the command finished without problem.

I got a MyFile with 6874905 bytes.

P.S.: I logged all stdout/stderr of the command above and found some
mysterious lines in that logfile:

---- snip ----
CfgEx 0.9 Copyright 2000 Sun Microsystems, Inc. All Rights Reserved.
======================================================================

Processing File UI.xcu ...

===================================

Error: "Unknown language code: en" in line 70: "</value>"
Error: "Unknown language code: en" in line 105: "</value>"
Error: "Unknown language code: en" in line 140: "</value>"
Error: "Unknown language code: en" in line 175: "</value>"
Error: "Unknown language code: en" in line 210: "</value>"
Error: "Unknown language code: en" in line 245: "</value>"
Error: "Unknown language code: en" in line 280: "</value>"
Error: "Unknown language code: en" in line 317: "</value>"
Error: "Unknown language code: en" in line 352: "</value>"
Error: "Unknown language code: en" in line 387: "</value>"
Error: "Unknown language code: en" in line 422: "</value>"
Error: "Unknown language code: en" in line 457: "</value>"
Error: "Unknown language code: en" in line 492: "</value>"
Error: "Unknown language code: en" in line 527: "</value>"
Error: "Unknown language code: en" in line 562: "</value>"
Error: "Unknown language code: en" in line 597: "</value>"
Error: "Unknown language code: en" in line 632: "</value>"
Error: "Unknown language code: en" in line 667: "</value>"
Error: "Unknown language code: en" in line 702: "</value>"
Error: "Unknown language code: ks" in line 726: "</value>"
Error: "Unknown language code: en" in line 737: "</value>"
Error: "Unknown language code: en" in line 772: "</value>"
Error: "Unknown language code: en" in line 807: "</value>"
Error: "Unknown language code: en" in line 842: "</value>"
Error: "Unknown language code: en" in line 877: "</value>"
Error: "Unknown language code: en" in line 912: "</value>"
Error: "Unknown language code: en" in line 947: "</value>"
Error: "Unknown language code: en" in line 982: "</value>"

CfgEx 0.9 Copyright 2000 Sun Microsystems, Inc. All Rights Reserved.
======================================================================

Processing File Writer.xcu ...
---- snip ----

Is this worth a new issue?

Any interest in the logfile or the generated MyFile?
Comment 13 Dieter.Loeschky 2003-08-14 12:52:16 UTC
DL->NF: Could you please takeover?
Comment 14 Dieter.Loeschky 2003-08-14 13:09:37 UTC
.
Comment 15 simonbr 2003-09-10 21:43:27 UTC
Hi Nils, 

Adding "guw.pl -env" in front of the command, localize works for me 
in 1.1 RC4, both for extraction and merging. 

So as far as I'm concerned the issue can be closed. 
I did see the same error messages that Volker mentioned, it may be a 
good idea to start a separate issue for that. 
Comment 16 nils.fuhrmann 2003-10-22 06:50:05 UTC
I close this one. I will ak Ivo to take care of the "unknown iso code"
messages. He is currently dealing with the "numeric representation to
iso code" stuff and will remove the sinmply wrong items.
Comment 17 nils.fuhrmann 2003-10-22 06:53:00 UTC
Closed as discussed