Issue 8092 - localize does not extract
Summary: localize does not extract
Status: CLOSED FIXED
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: 643
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: nils.fuhrmann
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-06 20:03 UTC by pavel
Modified: 2003-01-07 10:08 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 pavel 2002-10-06 20:03:16 UTC
I'm trying to build SRX643_OO for Czech language but I can not get
localize to extract all strings:

oo@mirka:~/Build/oo_SRX643_OO_src> localize -e -i cs-CZ -l 01,99=01 -f /tmp/q.txt

=======================================================
Current settings:
=======================================================
Mode:          extract
Workspace:     SRC643
Source tree:   /home/oo/Build/oo_SRX643_OO_src
Languages:     01,99=01
ISO code (99): cs-CZ
Filename:      /tmp/q.txt
=======================================================

Reading database /home/oo/Build/oo_SRX643_OO_src/solenv/config/stand.lst ...
Creating virtual directory tree ...
pDirectory->GetSubDirectories() is false


The last string was added by me to srciter.cxx to the function

void SourceTreeIterator::ExecuteDirectory( SourceDirectory *pDirectory )
{
	if ( bInExecute ) {
		OnExecuteDirectory( pDirectory->GetFullPath());
	  if ( pDirectory->GetSubDirectories()) {
	    for ( ULONG i=0;i < pDirectory->GetSubDirectories()->Count();i++ )
	      ExecuteDirectory(( SourceDirectory * )
			       pDirectory->GetSubDirectories()->GetObject( i ));
	  } else
	    fprintf(stderr, "pDirectory->GetSubDirectories() is false\n");
	}
}

I'm able to merge all strings from the GSI file to the sources as I was doing
with 1.0.1.
Comment 1 Dieter.Loeschky 2002-10-09 10:11:43 UTC
DL->NF: Could you please takeover?
Comment 2 nils.fuhrmann 2002-10-23 07:14:38 UTC
For me it simply looks like the workspace set in environment is not
available in the stand.ls7 (solver/config/stand.lst).
If localize is not able to locate the workspace in the stand.lst it
internally sets the count of modules to be analysed to zero =>
GetSubDirectories() returns 0.

Solution: Please check if the stand.lst contains the workspace set in
environment (in the current case SRC643). If not, set up a valid
environment and localize should work. Potentially you have to checkout
a valid stand.lst.
Comment 3 pavel 2002-10-23 08:59:59 UTC
Yes. I use 643 developers build (regularly updated to tag SRX643_OO
from CVS). The file solenv/config/stand.lst contains those environments:

oo@oo:~/tr/oo_SRX643_OO_src/solenv/config> grep ^S stand.lst 
SRC638
SRC641
SRX642

I tried to synch ro HEAD and even there is no SRX643:

oo@oo:~/tr/oo_SRX643_OO_src/solenv/config> grep ^S stand.lst 
SRC641
SRX642
SRC654 
SRC655 

Where can I found the correct definition of SRX643?  I tried to
"workaround" it by renaming SRX642 to SRX643 and it started doing
something. So having correct definition of SRX643 will solve this
problem, IMHO.
Comment 4 rt 2002-11-01 08:59:38 UTC
Hi Pavel,

I just added SRX643 to stand.lst (HEAD), please update. OTH,
differences between SRX642 and SRX643 are small indeed, so your
workaround should not be too bad.

Rüdiger
Comment 5 pavel 2002-11-01 12:17:31 UTC
I still do not see SRX643 there:

oo@oo:~/tr/oo_OO643C_src/solenv/config> cvs -z9 diff -u -r HEAD
stand.lst|grep SRX643
oo@oo:~/tr/oo_OO643C_src/solenv/config>

Can you please send it to my via e-mail?
Comment 6 pavel 2002-11-02 09:16:26 UTC
Kevin have just commited it to public CVS.
So we can close this. Thank you for solving it.
Comment 7 nils.fuhrmann 2003-01-07 09:47:40 UTC
Closed now
Comment 8 hans_werner67 2003-01-07 10:08:28 UTC
-