On Wed, Feb 23, 2011 at 2:10 AM, NopMap wrote:
> Just to explain the situation: I am running an (unmodified) P2, but I have
> built a custom map_feature file from scratch. Of course it would be good to
> translate both.
I wonder how this would best work? Maybe we could have auxiliary
map_features
Is there a way to attach custom resource files to this process which match
the custom map_features?
bye
Nop
--
View this message in context:
http://gis.638310.n2.nabble.com/Potlatch-dev-i18n-using-babelFx-tp6040153p6048659.html
Sent from the Potlatch mailing list archive at
On Mon, Feb 21, 2011 at 12:30 PM, NopMap wrote:
>
> Hi!
>
> It's great to hear that there is an internationalization module being done,
> even if it is still a little fragile.
>
> Doing the application is rather straightforward work, I guess, but what
> about the map features? It'll probably be a
xt:
http://gis.638310.n2.nabble.com/Potlatch-dev-i18n-using-babelFx-tp6040153p6048524.html
Sent from the Potlatch mailing list archive at Nabble.com.
___
Potlatch-dev mailing list
Potlatch-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/potlatch-dev
Following on from a discussion last year[1] I've started work on
internationalisation of p2 using the babelFx[2] i18n framework. This
lets use keep the internationalisation separate from the rest of the
development, rather than covering the code in standard flex
resourceManager calls. It's the same
