Issue 112394 - extend localizaion and build process to .properties files
Summary: extend localizaion and build process to .properties files
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: hjs
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks: 100845
  Show dependency tree
 
Reported: 2010-06-14 18:14 UTC by hjs
Modified: 2017-05-20 10:24 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description hjs 2010-06-14 18:14:07 UTC
the current L10N process doesn't allow direct processing of .property resource
files. this task is about integrating that format as yet another resource type
into the common L10n process.
Comment 1 hjs 2010-06-14 18:26:51 UTC
sample makefile snippet to get localized .properties files:

------
L10NPROPERTYFILES:=$(CLASS)/$(PACKAGE)/myfile.properties
------

or

------
L10NPROPERTYFILES:=$(CLASS)/$(PACKAGE)/myfile_en_US.properties
------

source language .properties files are expected to reside in the current
directory. currently the only supported destination is $(CLASS)/$(PACKAGE) -
which seems to be sufficient for all found use cases.

for the processing makefile check out solenv/inc/tg_propmerge.mk
Comment 2 hjs 2010-06-14 18:32:29 UTC
.
Comment 3 hjs 2010-06-15 12:48:29 UTC
correction: must be CLASSDIR instead of just CLASS

------
L10NPROPERTYFILES:=$(CLASSDIR)/$(PACKAGE)/myfile.properties
------

or

------
L10NPROPERTYFILES:=$(CLASSDIR)/$(PACKAGE)/myfile_en_US.properties
------
Comment 4 ivo.hinkelmann 2010-06-15 15:22:30 UTC
works fine