<div dir="ltr"><div>For visibility, the link to the "Add a Language Page" should probably be a direct link sub bullet in the index:</div><div><br></div><div><a href="https://geomoose.github.io/gm3/">https://geomoose.github.io/gm3/</a></div><div><br></div><div>Under the main "how to contribute to Geomoose" bullet. <br></div><div><br></div><div>As an aside - I'm not sure where things stand with reorganizing the docs, but starting next week I should have some availability to help with this task if you think I can help,</div><div><br></div><div>T<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 8, 2020 at 9:44 AM Jim Klassen <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On 12/7/20 3:18 PM, Eli Adam wrote:<br>
> On Mon, Dec 7, 2020 at 1:08 PM TC Haddad <<a href="mailto:tchaddad@gmail.com" target="_blank">tchaddad@gmail.com</a>> wrote:<br>
>><br>
>> 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.<br>
>><br>
>> 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?<br>
>><br>
> What do you think of here,<br>
> <a href="https://geomoose.github.io/gm3/howto/add-a-language.html" rel="noreferrer" target="_blank">https://geomoose.github.io/gm3/howto/add-a-language.html</a> assuming that<br>
> most people will start there to add their translation? Hmm, that page<br>
> is not in the index which makes it pretty low visibility. I guess we<br>
> are in the process of addressing some of our documentation indexing.<br>
That makes sense to me (or the equivalent place after the docs re-organization).<br>
><br>
>> On Mon, Dec 7, 2020 at 11:00 AM Jim Klassen <<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>> wrote:<br>
>>><br>
>>><br>
>>> On 12/7/20 12:46 PM, Eli Adam wrote:<br>
>>>> On Mon, Dec 7, 2020 at 10:28 AM James Klassen <<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>> wrote:<br>
>>>>> Moving this to the PSC list for a procedural question:<br>
>>>>><br>
>>>>> 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?<br>
>>>>><br>
>>>> Maybe we have a "Translators" section of the authors file?<br>
>>>> Translators should accept the terms, although I would be fine with a<br>
>>>> public acknowledgement of such in the public list archives.<br>
>>> That seems reasonable.<br>
>>>>> Our current practice is to have people submit a PR adding themselves to the AUTHORS file.<br>
>>>>><br>
>>>>> 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)?<br>
>>>> I think we will get more translations if we do that overhead for<br>
>>>> people. That would also let translators focus on translation.<br>
>>>> Someone mentioned a French translation too, perhaps we should reach<br>
>>>> out to them as well. The more default languages included, the more<br>
>>>> welcoming to more new users.<br>
>>> I very much agree. Particularly, as long as we still have a "paper trail" such as public acknowledgement on the list.<br>
>>>>> Translations are sort of code (by implementation detail), sort of documentation, are mostly a statement of fact, but also could have a creative element.<br>
>>>>><br>
>>>> Certainly a gray area, acknowledgement of the terms and a section in<br>
>>>> the author file takes a conservative approach.<br>
>>> That works for me.<br>
>>><br>
>>> Does anyone have any comments/objections?<br>
>>>> Eli<br>
>>>><br>
>>>>> On Mon, Dec 7, 2020, 08:29 Eli Adam <<a href="mailto:eadam@co.lincoln.or.us" target="_blank">eadam@co.lincoln.or.us</a>> wrote:<br>
>>>>>> Hi Flavio,<br>
>>>>>><br>
>>>>>> Adding additional languages is great! Can you open a Github issue<br>
>>>>>> with it.json here, <a href="https://github.com/geomoose/gm3/issues" rel="noreferrer" target="_blank">https://github.com/geomoose/gm3/issues</a>?<br>
>>>>>><br>
>>>>>> It looks like placement of the language file has come up before,<br>
>>>>>> <a href="https://github.com/geomoose/gm3/issues/544" rel="noreferrer" target="_blank">https://github.com/geomoose/gm3/issues/544</a><br>
>>>>>><br>
>>>>>> And maybe we should actively call for additional translations there too!<br>
>>>>>><br>
>>>>>> Best regards, Eli<br>
>>>>>><br>
>>>>>> On Sun, Nov 29, 2020 at 11:43 PM flavio rigolon<br>
>>>>>> <<a href="mailto:flavio.rigolon@gmail.com" target="_blank">flavio.rigolon@gmail.com</a>> wrote:<br>
>>>>>>> Hi all,<br>
>>>>>>> I'm using GeoMoose 3.6.2 and I've added my own "it.json" (italian language).<br>
>>>>>>> The default languages are stored in<br>
>>>>>>> "/srv/geomoose/gm3-example/htdocs/geomoose/src/gm3/lang/" but<br>
>>>>>>> following the instruction [1] is implied but not explicitly said that<br>
>>>>>>> we have to copy the. json file in the "home" directory (i.e.<br>
>>>>>>> "/srv/geomoose/gm3-example/htdocs/desktop"). So, in my case I've set<br>
>>>>>>> the "app.js" file like this:<br>
>>>>>>><br>
>>>>>>> ------------------------------------------<br>
>>>>>>> var app = new gm3.Application({<br>
>>>>>>> mapserver_url: CONFIG.mapserver_url,<br>
>>>>>>> mapfile_root: CONFIG.mapfile_root,<br>
>>>>>>> map: {<br>
>>>>>>> scaleLine: {<br>
>>>>>>> enabled: true,<br>
>>>>>>> // units: 'imperial'<br>
>>>>>>> units: 'metric'<br>
>>>>>>> }<br>
>>>>>>> },<br>
>>>>>>> lang: {<br>
>>>>>>> it: './it.json',<br>
>>>>>>> },<br>
>>>>>>> });<br>
>>>>>>> ------------------------------------------<br>
>>>>>>><br>
>>>>>>> and it works fine.<br>
>>>>>>> Is it the case of edit the page [1] to explicitly point where the<br>
>>>>>>> .json file must be? (I think there is also a trivial typo error in the<br>
>>>>>>> page title: "...langauge" should be "...language").<br>
>>>>>>> I've translated the .json file in italian; do you think it could be<br>
>>>>>>> share to give a base point for other italian users like the es.json<br>
>>>>>>> one for spanish?<br>
>>>>>>><br>
>>>>>>> my 2 cents<br>
>>>>>>> best regards<br>
>>>>>>> flavio<br>
>>>>>>><br>
>>>>>>> [1] <a href="https://geomoose.github.io/gm3/howto/add-a-language.html" rel="noreferrer" target="_blank">https://geomoose.github.io/gm3/howto/add-a-language.html</a><br>
>>>>>>><br>
>>>>>>> --<br>
>>>>>>> /"\ ASCII Ribbon Campaign<br>
>>>>>>> \ / Respect for low technology.<br>
>>>>>>> X Keep e-mail messages readable by any computer system.<br>
>>>>>>> / \ Keep it ASCII.<br>
>>>>>>> _______________________________________________<br>
>>>>>>> Geomoose-users mailing list<br>
>>>>>>> <a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
>>>>>>> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
>>>>>> _______________________________________________<br>
>>>>>> Geomoose-users mailing list<br>
>>>>>> <a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
>>>>>> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
>>>>> _______________________________________________<br>
>>>>> geomoose-psc mailing list<br>
>>>>> <a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
>>>>> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
>>> _______________________________________________<br>
>>> geomoose-psc mailing list<br>
>>> <a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
>> _______________________________________________<br>
>> geomoose-psc mailing list<br>
>> <a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
>> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
<br>
</blockquote></div>