Thanks for replying. Yes, I did restart TC and I have also tested this
problem again in case I did something wrong previously; no luck.

I have created a messages.properties file in /WEB-INF/classes and
restarted TC. When I open the dialog box for the page properties the
keys are not read in from the properties file.



Will Scheidegger wrote:
> 
> I think placing it in WEB-INF/classes/ should do the trick. Did you
> restart TC afterwards?
> 
> -will
> 
> On 12.06.2009, at 12:17, Gavin Donald wrote:
> 
>>
>> I have been copying the samples example that came with Magnolia 3.6.5
>> although I am using Magnolia 4.0.1. I see that there are many cases
>> where the dialogs are i18n'ed but the only way I can see to change them
>> is to edit the jar file:
>>
>> magnolia-module-admininterface-4.0.1.jar
>>
>> For my template I am not using either a module or the Standard
>> Templating Kit but simply putting the required nodes in:
>>
>> modules => templating
>>
>> Is there a way to add a properties file with the i18n keys with the
>> method I am using? I have tried putting a messages.properties and
>> messages_en.properties file in /WEB-INF and /WEB-INF/classes but it
>> seems to be ignored. I have also looked at the manual but it hasn't shed
>> any light on this for me.
>>
>> Thanks for any assistance.
>>
>>
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <[email protected]>
>> ----------------------------------------------------------------
>>
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> 
> 
> 



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to