[geomoose-psc] [Geomoose-users] Add a language to GeoMoose

[James Klassen]

Moving this to the PSC list for a procedural question:

How should we apply the contribution guidelines to translation
contributions?  In other words, when do translators need to accept the
terms and be listed in the AUTHORS file?

Our current practice is to have people submit a PR adding themselves to the
AUTHORS file.

Does this model for code (and docs?) fit for translators (who may be less
comfortable working with git and submitting a PR than the typical code
contributor)?

Translations are sort of code (by implementation detail), sort of
documentation, are mostly a statement of fact, but also could have a
creative element.



On Mon, Dec 7, 2020, 08:29 Eli Adam <eadam at co.lincoln.or.us> wrote:

> Hi Flavio,
>
> Adding additional languages is great!  Can you open a Github issue
> with it.json here, https://github.com/geomoose/gm3/issues?
>
> It looks like placement of the language file has come up before,
> https://github.com/geomoose/gm3/issues/544
>
> And maybe we should actively call for additional translations there too!
>
> Best regards, Eli
>
> On Sun, Nov 29, 2020 at 11:43 PM flavio rigolon
> <flavio.rigolon at gmail.com> wrote:
> >
> > Hi all,
> >  I'm using GeoMoose 3.6.2 and I've added my own "it.json" (italian
> language).
> > The default languages are stored in
> > "/srv/geomoose/gm3-example/htdocs/geomoose/src/gm3/lang/" but
> > following the instruction [1] is implied but not explicitly said that
> > we have to copy the. json file in the "home" directory (i.e.
> > "/srv/geomoose/gm3-example/htdocs/desktop"). So, in my case I've set
> > the "app.js" file like this:
> >
> > ------------------------------------------
> > var app = new gm3.Application({
> > mapserver_url: CONFIG.mapserver_url,
> > mapfile_root: CONFIG.mapfile_root,
> > map: {
> > scaleLine: {
> > enabled: true,
> > //    units: 'imperial'
> > units: 'metric'
> > }
> > },
> > lang: {
> > it: './it.json',
> > },
> > });
> > ------------------------------------------
> >
> > and it works fine.
> > Is it the case of edit the page [1] to explicitly point where the
> > .json file must be? (I think there is also a trivial typo error in the
> > page title: "...langauge" should be "...language").
> > I've translated the .json file in italian; do you think it could be
> > share to give a base point for other italian users like the es.json
> > one for spanish?
> >
> > my 2 cents
> > best regards
> > flavio
> >
> > [1] https://geomoose.github.io/gm3/howto/add-a-language.html
> >
> > --
> > /"\  ASCII Ribbon Campaign
> > \ /  Respect for low technology.
> >  X  Keep e-mail messages readable by any computer system.
> > / \  Keep it ASCII.
> > _______________________________________________
> > Geomoose-users mailing list
> > Geomoose-users at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/geomoose-users
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20201207/8d24670d/attachment.html>