glossterm VS logseq

I saw a few posts discuss using the Wiktionary dump directly vs. the freeDictionary API, which is difficult to do because the raw wiki text isn't immediately usable. I actually created and open sourced a project several years ago that I never publicized that lexes and parses the Wiktionary dump:

https://github.com/vthommeret/glossterm

Specifically it can understand and execute 21 different wiki text templates (e.g. "cog", "borrow", "gloss", "prefix", "qualifier”), e.g. {{inh|es|la|gelātus}}:

https://github.com/vthommeret/glossterm/tree/master/lib/tpl

And eventually parse it into this structure, which has a list of all definitions (distinguished into nouns, adjectives, verbs, adverbs, etc...), etymology, links, and descendants for a given word:

https://github.com/vthommeret/glossterm/blob/master/lib/gt/p...

Further parts of the pipeline turned different relationships into edges that I could stick into a graph database and do certain graph queries. This allowed me to do certain queries like find French, Spanish, and English words that share a Latin root.

I ended up parallelizing this specific query using Apache Beam and then dumping the results into Firestore so they could be queried via a web app. Here's an example for the Spanish word: helado

https://cognate.app/words/es/helado

Under the "Cognates" section, it knows that it comes from the Latin root "gelatus" from which English has borrowed the word "gelato".

I originally started this project when I was learning Spanish. If you just look up the definition of helado (ice cream) it doesn't necessarily help you learn it. But I found that if I could relate it to languages I already knew (e.g. English and French), it was easier to remember. In this case helado is related to gelato, but you won't find that in e.g. Google Translate or SpanishDict.

Ultimately, I found that while the Wiktionary data is amazing, it’s also a bit of a quagmire for finding cognates. I would miss certain etymologies where you had to follow a descendant tree 2 or 3 levels deep. Or a definition would just mention a word it was related to. But if I expanded the query to include these instances, then it significantly increased the amount of non-cognates that showed up in the results.

So I created a useful set of tools (which I never wrote about until now), but I realized the end result of a web UI that showed the relationships between words would require a significant investment in data quality that likely wasn’t possible without changing Wiktionary itself / community investment.

Logseq support via our Logseq Plugin

Sorry, but _what exactly_ «it seems to do» from your point of view?

My «second brain» now is almost 300Mb of text, pictures, sound files, PDF and other stuff. As I already mentioned, it contains tables, mathematical formulae, sheet music, cross-references, code samples, UML diagrams and graphs in Graphviz format. It is versioned, indexed by local search engine, analyzed by AI assistant and shared between many computers and mobile devices. And (last but not least) it works: it allows me to solve my tasks way more faster than with the assistant of external, non-personalized tools (like ChatGPT, StackExchange or Google).

I know no tools for all this tasks except org-mode. Well, maybe Evernote in the 2010-s was something similar — but with less features, with more bugs and with worse interface.

Personal note-taking _is_ a complex task per se (well, at least for someone like typical HN visitor). I've seen many note-taking tools, that were ridiculously featureless, stupid and inconvenient because they were _not_ complex enough.

> Sure if one wants to do emacs-gardening it is fine.

1)You can use org-mode outside Emacs. See for example Logseq (https://logseq.com/), organice (https://organice.200ok.ch/) or EasyOrg.

2)Org-mode works in Emacs out of the box, you don't need any «emacs-gardening» to use org-mode.

3)The term «Emacs-gardening» itself sound a bit like hate-speech for me. The complexity of Emacs customization is overrated, mostly due to opinions of people who never used Emacs or used it in the previous millennium.

Obsidian is great.

For those looking for an open source alternative (or don't want to pay the Obsidian fees for professional usage) check out Logseq: https://logseq.com/

For an opensource alternative to Obsidian checkout Logseq (1). I spent a while thinking obsidian was opensource out of my own ignorance and was disappointed when I learned it was not.

1: https://logseq.com/

I use logseq to keep journal of my daily work.

While Emacs and Org mode can certainly be used for this (and, when they can't, you can always inject little python/js scripts in your emacs config to take care of specific things), I'd also recommend you take a look at Logseq.