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

TC Haddad tchaddad at gmail.com
Mon Dec 7 13:08:40 PST 2020


Sounds good to me - users have probably translated into other languages
that we might not know about, because not everyone knows or needs to ask on
the list.

Maybe there is a place on the website where we can add a more visible call
for translations, with links to the steps, statement of terms and the
authors list?

On Mon, Dec 7, 2020 at 11:00 AM Jim Klassen <klassen.js at gmail.com> wrote:

>
>
> On 12/7/20 12:46 PM, Eli Adam wrote:
> > On Mon, Dec 7, 2020 at 10:28 AM James Klassen <klassen.js at gmail.com>
> wrote:
> >> 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?
> >>
> > Maybe we have a "Translators" section of the authors file?
> > Translators should accept the terms, although I would be fine with a
> > public acknowledgement of such in the public list archives.
> That seems reasonable.
> >> 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)?
> > I think we will get more translations if we do that overhead for
> > people.  That would also let translators focus on translation.
> > Someone mentioned a French translation too, perhaps we should reach
> > out to them as well.  The more default languages included, the more
> > welcoming to more new users.
> I very much agree.  Particularly, as long as we still have a "paper trail"
> such as public acknowledgement on the list.
> >
> >> Translations are sort of code (by implementation detail), sort of
> documentation, are mostly a statement of fact, but also could have a
> creative element.
> >>
> > Certainly a gray area, acknowledgement of the terms and a section in
> > the author file takes a conservative approach.
> That works for me.
>
> Does anyone have any comments/objections?
> >
> > Eli
> >
> >>
> >> 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
> >> _______________________________________________
> >> geomoose-psc mailing list
> >> geomoose-psc at lists.osgeo.org
> >> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
>
> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20201207/4a7ebb9b/attachment.html>


More information about the geomoose-psc mailing list