Issue 29173

Summary:	localize has to work for single modules and files
Product:	Internationalization	Reporter:	gregor.hartmann
Component:	code	Assignee:	AOO issues mailing list <issues>
Status:	CONFIRMED ---	QA Contact:
Severity:	Trivial
Priority:	P3	CC:	issues
Version:	OOo 1.1.2
Target Milestone:	---
Hardware:	All
OS:	All
Issue Type:	FEATURE	Latest Confirmation in:	---
Developer Difficulty:	---

Description gregor.hartmann 2004-05-14 08:37:50 UTC

It should be possible to use localize on one or more modules and even on single
files similar to the CWS tools.

It is not bearable to use a different tool for each filetype with cryptic
parameters to call. Espechially since the names of the tools have to be guessed
for the different filetypes.

Comment 1 ivo.hinkelmann 2004-10-13 15:52:51 UTC

Ever tried:
fgrep ^mymodule sdffile > sdf_mymodule ; localize -m -l all -f sdf_mymodule ; rm
sdf_mymodule 
;)

Comment 2 gregor.hartmann 2004-10-14 15:10:14 UTC

but extracting is the part I would like to see. And not like this:

localize -e -l all -f sdffile2 ; grep ^mymodule sdffile2 > sdf_mymodule ; rm
sdffile2

but directly to save time.

Comment 3 ivo.hinkelmann 2004-12-21 15:01:54 UTC

as discussed target -> OOo Later

Comment 4 ivo.hinkelmann 2011-01-31 16:28:22 UTC