Hard Time Adding Properties File To A Module In CSIDE Project

Hello,

I'm working on a new module and willing to use a .properties file in order to point some strings into it.

What I did is created in the srcmodule section a new file and gave it a ".propeties" extension. Then I selected a string and presset Ctrl + T in order to open the Xlate dialog and to choose my propertie file. Unfortunatelty I can't find the my prop file in the search section which eventually disables me from adding strings into this file.

I tried moving the .properties file into the staging folder in the OTHOME folder it seems helped but only 1 file is shown later on in the Xlate search section. I have 2 .properties file, but only one can be found.

What am I missing, doing wrong? Tried to follow up the guide in the CSIDE Plugin for Eclipse section but without any luck. Can anyone assist me?

Thank you.

Find more posts tagged with

Comments

Dave Carpeneto

Hiya - this is known behavior with the current release of CSIDE. The xlate functionality only operates on deployed properties files, not on the ones in your project.

There's a few tickets open to get this behavior changed. Until these are released (hopefully soon) : what you'll need to do is manually keep the properties files synchronized (a common process here is to deploy your module with a .properties file, use CSIDE to update the file via the xlate functionality, then manually copy the file over from OTHOME to their project before building their module).

Dave Carpeneto

Regarding your second concern (only one property file seems to get read in): can you confirm that the language that the property file is for is enabled?

To do this: point your browser to the "Configure Languages" ( func=admin.configurelanguage ) admin page & confirm that the languages relating to your proprty file(s) are enabled.

Should this not resolve (or if this was already done): please open a ticket with support, mentioning this thread & passing in the log files covered in https://knowledge.opentext.com/go/KB12497600 .

Ignore the above comment. After looking further into this: CSIDE only reads in property files for the default locale. I've opened up a ticket to see what can be done to change this behavior. For now you'll need to chage the default locale if you want the built-in locale functionality to work in CSIDE.