OK - thanks!
On Thu, Jul 11, 2013 at 12:53 AM, Koushik Das wrote:
> That's correct. Currently all messages are hard-coded in the Java code.
> First all these strings needs to be moved out to something like a 'resource
> file' and only then they can be localized.
>
> > -Original Message-
That's correct. Currently all messages are hard-coded in the Java code. First
all these strings needs to be moved out to something like a 'resource file' and
only then they can be localized.
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Thursda
This is the file I'm aware of:
client/WEB-INF/classes/resources/messages.properties
I can't say I understand completely how L10N works in CS, but this
properties file might be a good place for you to start.
On Tue, May 21, 2013 at 10:28 PM, Adnan Ashraf <
mohammad.adnan.ash...@gmail.com> wrote:
On Wed, May 22, 2013 at 12:28 AM, Adnan Ashraf
wrote:
> Hi,
>
> I would appreciate if anyone could point me to understand how cloudstack
> schema model accommodates the localization strings within its database
> tables. I am interested in understanding whether a central strings table is
> used or
For example, I notice we seem to hard code English strings in the text of
exceptions we throw.
I've never tried to view these exceptions while running under a language
other than English, but I somewhat doubt they are translated.
On Tue, May 21, 2013 at 10:34 PM, Mike Tutkowski <
mike.tutkow...@
