Issue 29173 - localize has to work for single modules and files
Summary: localize has to work for single modules and files
Status: CONFIRMED
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-14 08:37 UTC by gregor.hartmann
Modified: 2013-08-07 15:00 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
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 
.