<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi Jorge,
<div class=""><br class="">
</div>
<div class="">Thank you for trying out Glossarist! </div>
<div class=""><br class="">
</div>
<div class="">Actually the OSGeo glossary repository needs to be updated to suit the latest version of Glossarist — which we are going to do so today. The current repo is using an older data schema. The unexpected diffs are due to this reason.</div>
<div class=""><br class="">
</div>
<div class="">In order to submit change requests, you will need write access to the repository. Should the group discuss about it?</div>
<div class=""><br class="">
</div>
<div class="">Now to the questions:</div>
<div class="">
<blockquote type="cite" class="">2) To change something, I must start a change request and make my<br class="">
changes, right?<br class="">
</blockquote>
<br class="">
</div>
<div class="">Yes, you’re right. A change request can contain multiple changes.</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">3) Afterwards, in my local<br class="">
~/.config/Electron/glossarist-database/change-requests I have the<br class="">
changes from my change request.<br class="">
</blockquote>
</div>
<div class=""><br class="">
</div>
<div class="">Correct. The git “upstream” remote is a deprecated artifact, it will be removed in the next version of Glossarist.</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">4) Question: If I want to contribute to the OSGeo terminology, what<br class="">
should I do next?<br class="">
<br class="">
Should I push my changes from the command line or there is some button<br class="">
on Glossarist to submit the change request?<br class="">
</blockquote>
<div class=""><br class="">
</div>
Glossarist has the Review pane where you can “Propose” a CR, after which you can “Sync” (top left of window) — it will upload the CR.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">In this case, since you don’t have direct write access, you could:</div>
<div class="">1. First, work on your fork of the repository — i.e. fork <a href="https://github.com/geolexica/osgeo-glossary" class="">
https://github.com/geolexica/osgeo-glossary</a> , and make that your new remote in Glossarist.</div>
<div class="">2. Create a CR in your own fork</div>
<div class="">3. Make a Pull Request to submit your CR to the master branch of <a href="https://github.com/geolexica/osgeo-glossary" class="">
https://github.com/geolexica/osgeo-glossary</a></div>
<div class="">4. Whoever has access to merge can bring in your CR to master and review/approve the CR.</div>
<div class=""><br class="">
</div>
<div class="">Would you mind waiting until tomorrow for the new version of Glossarist (due tonight) and the upgrade of the data repo schema?</div>
<div class=""><br class="">
</div>
<div class="">Thanks!</div>
<div class=""><br class="">
</div>
<div class="">Ron</div>
<div class=""><br class="">
</div>
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
_____________________________________<br class="">
<br class="">
Ronald Tse<br class="">
Ribose Inc.<br class="">
<br class="">
+=========================================================+<br class="">
This message may contain confidential and/or privileged<br class="">
information. If you are not the addressee or authorized to<br class="">
receive this for the addressee, you must not use, copy,<br class="">
disclose or take any action based on this message or any<br class="">
information herein. If you have received this message in<br class="">
error, please advise the sender immediately by reply e-mail<br class="">
and delete this message. Thank you for your cooperation.<br class="">
+=========================================================+</div>
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Jul 7, 2020, at 5:03 PM, Jorge Gustavo Rocha <<a href="mailto:jgr@osgeopt.pt" class="">jgr@osgeopt.pt</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi all,<br class="">
<br class="">
I've clone the Glossarist desktop tool repo and started to use it. It<br class="">
work pretty well on my Ubuntu. Thanks for those working on it.<br class="">
<br class="">
I would like to understand the workflow behind it and how can we use it<br class="">
in OSGeo.<br class="">
<br class="">
1) I've started Glossarist, identified my self with my Github account. I<br class="">
can browse existent entries and the application is working smoothly. Great!<br class="">
<br class="">
2) To change something, I must start a change request and make my<br class="">
changes, right?<br class="">
<br class="">
3) Afterwards, in my local<br class="">
~/.config/Electron/glossarist-database/change-requests I have the<br class="">
changes from my change request.<br class="">
<br class="">
The folder ~/.config/Electron/glossarist-database is under git control<br class="">
(setup done by Glossarist).<br class="">
<br class="">
The remote repos are:<br class="">
<br class="">
jgr@zoe:~/.config/Electron/glossarist-database$ git remote -v<br class="">
origin<span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/geolexica/osgeo-glossary" class="">https://github.com/geolexica/osgeo-glossary</a> (fetch)<br class="">
origin<span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/geolexica/osgeo-glossary" class="">https://github.com/geolexica/osgeo-glossary</a> (push)<br class="">
upstream<span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/ISO-TC211/geolexica-database" class="">https://github.com/ISO-TC211/geolexica-database</a> (fetch)<br class="">
upstream<span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/ISO-TC211/geolexica-database" class="">https://github.com/ISO-TC211/geolexica-database</a> (push)<br class="">
<br class="">
4) Question: If I want to contribute to the OSGeo terminology, what<br class="">
should I do next?<br class="">
<br class="">
Should I push my changes from the command line or there is some button<br class="">
on Glossarist to submit the change request?<br class="">
<br class="">
Note: All local files were rewritten and git reports changes in all<br class="">
terms. I didn't expect such changes. As far as I can understand, git<br class="">
should report only changes in `change-requests` folder, right?<br class="">
<br class="">
My local --stats are:<br class="">
<br class="">
jgr@zoe:~/.config/Electron/glossarist-database$ git diff --stat --cached<br class="">
origin/master | head -10<br class="">
change-requests/7a5c63.yaml | 37 +++++++++++++<br class="">
change-requests/bd20b0.yaml | 61 ++++++++++++++++++++++<br class="">
concepts/concept-1.yaml | 30 +++++++++--<br class="">
concepts/concept-10.yaml | 30 +++++++++--<br class="">
concepts/concept-100.yaml | 30 +++++++++--<br class="">
concepts/concept-101.yaml | 30 +++++++++--<br class="">
concepts/concept-102.yaml | 30 +++++++++--<br class="">
concepts/concept-103.yaml | 30 +++++++++--<br class="">
concepts/concept-104.yaml | 30 +++++++++--<br class="">
concepts/concept-105.yaml | 30 +++++++++--<br class="">
<br class="">
Unexpected changes (for me!) are like this one:<br class="">
<br class="">
jgr@zoe:~/.config/Electron/glossarist-database$ git diff --cached<br class="">
origin/master concepts/concept-10.yaml<br class="">
diff --git a/concepts/concept-10.yaml b/concepts/concept-10.yaml<br class="">
index 0c68c10..54ae114 100644<br class="">
--- a/concepts/concept-10.yaml<br class="">
+++ b/concepts/concept-10.yaml<br class="">
@@ -1,4 +1,3 @@<br class="">
----<br class="">
term: AM/FM<br class="">
termid: 10<br class="">
eng:<br class="">
@@ -8,8 +7,29 @@ eng:<br class="">
notes: []<br class="">
examples: []<br class="">
authoritative_source:<br class="">
- link: <a href="https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf" class="">
https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf</a><br class="">
+ link:<br class="">
'<a href="https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf" class="">https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf</a>'<br class="">
terms:<br class="">
- - type: expression<br class="">
- designation: AM/FM<br class="">
- normative_status:<br class="">
+ - type: expression<br class="">
+ designation: AM/FM<br class="">
+ normative_status: null<br class="">
+ _revisions:<br class="">
+ current: 0c7724<br class="">
+ tree:<br class="">
+ 0c7724:<br class="">
+ object:<br class="">
+ id: 10<br class="">
+ definition: Automated Mapping/Facilities Management<br class="">
+ language_code: eng<br class="">
+ notes: []<br class="">
+ examples: []<br class="">
+ authoritative_source:<br class="">
+ link:<br class="">
'<a href="https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf" class="">https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf</a>'<br class="">
+ terms:<br class="">
+ - type: expression<br class="">
+ designation: AM/FM<br class="">
+ normative_status: null<br class="">
+ parents: []<br class="">
+ timeCreated: 2020-07-06T21:28:14.660Z<br class="">
+ author:<br class="">
+ name: Glossarist bot<br class="">
+ <a href="mailto:glossarist@ribose.com" class="">email: glossarist@ribose.com</a><br class="">
<br class="">
Sorry for this newbie question.<br class="">
<br class="">
But soon as I understand the workflow, I can write a short tutorial<br class="">
about how to use Glossarist to maintain and improve OSGeo terminology.<br class="">
<br class="">
Regards,<br class="">
<br class="">
Jorge<br class="">
<br class="">
<br class="">
On 04/07/20 13:47, Richard Duivenvoorde wrote:<br class="">
<blockquote type="cite" class="">Nice Nice!!!<br class="">
<br class="">
And good to lift this to an higher (OSGeo) plan!!<br class="">
<br class="">
Go go! :-)<br class="">
<br class="">
Regards,<br class="">
<br class="">
Richard Duivenvoorde<br class="">
<br class="">
(bcc to our dutch translation master)<br class="">
<br class="">
On 7/4/20 11:01 AM, Jorge Gustavo Rocha wrote:<br class="">
<blockquote type="cite" class="">Hi Ron,<br class="">
<br class="">
Thank you for the update.<br class="">
<br class="">
I've looked in the current <a href="https://osgeodev.geolexica.org" class="">https://osgeodev.geolexica.org</a> and on yours<br class="">
Glossarist desktop tool. Looks like very promising.<br class="">
<br class="">
OSGeo and QGIS in particular would benefit from such a well defined<br class="">
glossary.<br class="">
<br class="">
I'll be watching the project. I'll try to contribute with build<br class="">
instructions for Linux :-)<br class="">
<br class="">
Best regards,<br class="">
<br class="">
Jorge<br class="">
<br class="">
On 04/07/20 04:56, Ronald Tse wrote:<br class="">
<blockquote type="cite" class="">Hi Jorge,<br class="">
<br class="">
Thank you for spreading the news!<br class="">
<br class="">
The current development site with loaded terms is located here:<br class="">
<a href="https://osgeodev.geolexica.org" class="">https://osgeodev.geolexica.org</a><br class="">
<br class="">
I believe the group is still waiting for some confirmation on<br class="">
terminology across OSGeo. As you can see on the site, a number of<br class="">
conflicting definitions exist and the group would need some effort to<br class="">
discuss and attempt to settle these — since they are used across<br class="">
different OSGeo projects.<br class="">
<br class="">
Geolexica has also been working with ISO/TC 211 on their latest efforts<br class="">
in translating the 5th edition of the TC 211 Multi-Lingual Glossary of<br class="">
Terms (MLGT). There is now have a desktop application for managing<br class="">
translations through change requests, all based off a git repository on<br class="">
GitHub:<br class="">
https://www.glossarist.org<br class="">
<br class="">
I agree that more love is needed to the lexicon group to move things ahead!<br class="">
<br class="">
Kind regards,<br class="">
Ron<br class="">
<br class="">
_____________________________________<br class="">
<br class="">
Ronald Tse<br class="">
Ribose Inc.<br class="">
<br class="">
+=========================================================+<br class="">
This message may contain confidential and/or privileged<br class="">
information. If you are not the addressee or authorized to<br class="">
receive this for the addressee, you must not use, copy,<br class="">
disclose or take any action based on this message or any<br class="">
information herein. If you have received this message in<br class="">
error, please advise the sender immediately by reply e-mail<br class="">
and delete this message. Thank you for your cooperation.<br class="">
+=========================================================+<br class="">
<br class="">
<blockquote type="cite" class="">On Jul 4, 2020, at 6:23 AM, Jorge Gustavo Rocha <jgr@di.uminho.pt<br class="">
<mailto:jgr@di.uminho.pt>> wrote:<br class="">
<br class="">
Hi Ian, hi all,<br class="">
<br class="">
There are people trying to run an OSGeo "Interest group" on<br class="">
"Terminology", to be transversal to all OSGeo projects.<br class="">
<br class="">
They created a proof of concept, called "geolexica", available at:<br class="">
<br class="">
https://osgeo.geolexica.org/concepts/<br class="">
<br class="">
Sources on: https://github.com/geolexica/osgeo.geolexica.org<br class="">
<br class="">
It would be awesome if we were able to fill the translation for the<br class="">
different languages associated with the English concept, right on the<br class="">
origin.<br class="">
<br class="">
As far I as know (I'm cc to lexica group), this project needs some<br class="">
additional "love" to go on.<br class="">
<br class="">
Maybe Cameron (in cc) or someone else can make an update on the lexicon<br class="">
activities/plans.<br class="">
<br class="">
Regards,<br class="">
<br class="">
Jorge<br class="">
<br class="">
On 30/06/20 10:57, Ian Turton wrote:<br class="">
<blockquote type="cite" class=""><br class="">
<br class="">
On Tue, 30 Jun 2020 at 10:40, Bo Victor Thomsen<br class="">
<bo.victor.thomsen@gmail.com <mailto:bo.victor.thomsen@gmail.com>> wrote:<br class="">
<br class="">
Dear developers:<br class="">
<br class="">
As a former translator of the Danish version of QGIS I have a few -<br class="">
very personal, perhaps a bit caustic - comments:<br class="">
<br class="">
* Create a group or list of highly technical GIS related terms<br class="">
that is *not* to be translated. There is a lot of GIS terms that<br class="">
is English in origin, but haven't a well defined local<br class="">
translation. (With some hilarious results if they are<br class="">
translated). Not all translators is well versed in every aspect<br class="">
of GIS. <br class="">
<br class="">
<br class="">
<br class="">
Is this something that OSGEO can help to oversee and/or maintain as I<br class="">
suspect that this list would be useful across many projects.<br class="">
<br class="">
Ian <br class="">
<br class="">
-- <br class="">
Ian Turton<br class="">
<br class="">
_______________________________________________<br class="">
QGIS-Developer mailing list<br class="">
QGIS-Developer@lists.osgeo.org<br class="">
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">
<br class="">
</blockquote>
<br class="">
J. Gustavo<br class="">
-- <br class="">
Jorge Gustavo Rocha<br class="">
Departamento de Informática<br class="">
Universidade do Minho<br class="">
4710-057 Braga<br class="">
Gabinete 3.29 (Piso 3)<br class="">
Tel: +351 253604480<br class="">
Fax: +351 253604471<br class="">
Móvel: +351 910333888<br class="">
skype: nabocudnosor<br class="">
_______________________________________________<br class="">
Lexicon mailing list<br class="">
Lexicon@lists.osgeo.org<br class="">
https://lists.osgeo.org/mailman/listinfo/lexicon<br class="">
</blockquote>
<br class="">
</blockquote>
<br class="">
J. Gustavo<br class="">
<br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
Lexicon mailing list<br class="">
<a href="mailto:Lexicon@lists.osgeo.org" class="">Lexicon@lists.osgeo.org</a><br class="">
https://lists.osgeo.org/mailman/listinfo/lexicon<br class="">
<br class="">
</blockquote>
<br class="">
-- <br class="">
OSGeo Portugal<br class="">
NIF: 509588190<br class="">
<a href="mailto:geral@osgeopt.pt" class="">email: geral@osgeopt.pt</a><br class="">
https://www.osgeopt.pt/<br class="">
<br class="">
Próximo evento: SASIG 2017, 20 a 22 de novembro, Porto<br class="">
Mais informações: http://osgeopt.pt/sasig2017/<br class="">
_______________________________________________<br class="">
Lexicon mailing list<br class="">
Lexicon@lists.osgeo.org<br class="">
https://lists.osgeo.org/mailman/listinfo/lexicon<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>