This message is several days old, but I just ran into this too and
wanted to avoid having to update my host pages w/ the meta tags since
I'm only using the one locale as well.
To do this, add the following to your module's config file (.gwt.xml):
<inherits name="com.google.gwt.i18n.I18N"/>
<extend-property name="locale" values="en_US"/>
<set-property name="locale" value="en_US"/>
On Dec 2, 8:23 am, Rick Porter <
rickwpor...@gmail.com> wrote:
> I think I have solved my date/time issues by forcing alocale, but I
> would welcome suggestions for a better solution.
>
> In my module XML, I added the following line to include some
> internationalization code:
>
> <inherits name="com.google.gwt.i18n.I18N"/>
>
> I added the following line to my module XML for mylocale:
>
> <extend-property name="locale" values="en_US"/>
>
> Including thelocaleextend-property increases theGWTcompile time,
> since the compile does each browser/localecombination. This was the
> most undesireable piece of my solution since it basically doubled myGWTcompile times. I tried to set the defaultlocaleusing another bit
> of XML found athttp://
code.google.com/intl/es-AR/webtoolkit/doc/latest/DevGuideI18nL...,
> but I could not even get theGWTcompile to work when including that
> XML.
>
> The last required piece was adding the following line in my HTML file:
>
> <meta name='gwt:property' content='locale=en_US'>
>
> This gives it a defaultlocale, but I believe that it can be
> overridden with request parameters.
>
> I did test this on a couple projects, and it worked for both. However,
> I did not test with different locales. It seems that a newGWT2.1
> project has the same issues, so this is not just aGWT2.0 conversion