apertium
todo.txt-cli
Our great sponsors
apertium | todo.txt-cli | |
---|---|---|
5 | 55 | |
84 | 5,471 | |
- | 1.0% | |
5.6 | 2.9 | |
9 days ago | 2 months ago | |
C++ | Shell | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
apertium
-
Ask HN: Tell us about your project that's not done yet but you want feedback on
This is very cool, looking forward to it! I've been doing the same thing with Spanish Wikipedia articles for a while, using a few lines of Bash + Regex. I was using Apertium for it. https://apertium.org/ It's definitely worse than most ML-based solutions, but it works reliably and fast; you can run it entirely offline. With Spanish translations, the main problem I was facing is lack of vocabulary, so I created https://github.com/phil294/apertium-eng-spa-wiktionary which about doubles the amount of recognized words, albeit with wonky grammar.
-
Show HN: Unlimited machine translation API for $200 / Month
I used to keep track of the state of machine translation some years back.
I think the way you measure the success of an automated translation is edit distance, i.e. how many manual edits you need to make to a translated text before you reach some acceptable state. I suppose it's somewhat subjective, but it is possible to construct a benchmark and allow for multiple correct results.
The best resources I knew back then were:
VISL's CG-3 self-reported a competitively low edit distance compared to Google Translate: https://visl.sdu.dk/constraint_grammar.html -- the abstraction unfortunately requires a rather deep knowledge of any one particular language's grammar. It is a convincing argument that in order to beat Google Translate, you want less fuzzy machine learning and more structural analysis. But you also need a PhD in computational linguistics and deep knowledge of each language.
Apertium has an open-source pipeline: https://apertium.org/ -- seems to be much more like an open-source approach with a quality similar to Google Translate (although I don't know if it's better or worse; probably slightly worse in most cases, and with a slightly lower coverage).
-
Translating several languages into CV Creole
For context, I have been contributing CV Creole data to Unicode's CLDR and MediaWiki for a number of years now, but both are mostly manual work. I once considered setting up an Apertium language pair between CV Creole and Portuguese, given the grammatical similarities, but never got around to it.
-
"Lingva" Google Translate but without the tracking
Lingva is awesome. Also don't forget to check out LibreTranslate and Apertium. They are open source. Apertium can even translate web pages (you need to enter the URL).
-
How I installed Apertium on CentOS 7
#!/bin/bash set -x mkdir -p apertium-src && \ mkdir -p $MTDIR cd apertium-src && \ wget http://ftp.tsukuba.wide.ad.jp/software/gcc/releases/gcc-8.5.0/gcc-8.5.0.tar.gz -O - \ | gzip -dc \ | tar -xf - && \ cd gcc-8.5.0 && \ ./configure --prefix=$MTDIR --disable-multilib && \ make -j $(nproc) && \ make install && \ cd .. || exit 1 cd apertium-src && \ wget https://github.com/unicode-org/icu/releases/download/release-69-1/icu4c-69_1-src.tgz -O - \ | gzip -dc \ | tar -xf - \ && cd icu/source \ && CC=gcc CXX=g++ ./configure --prefix=$MTDIR \ && CC=gcc CXX=g++ make -j $(nproc) \ && CC=gcc CXX=g++ make install \ && cd ../.. \ || exit 1 cd apertium-src && \ svn checkout http://beta.visl.sdu.dk/svn/visl/tools/vislcg3/trunk vislcg3 && \ cd vislcg3 && ./get-boost.sh \ && ./cmake.sh -DCMAKE_INSTALL_PREFIX=$MTDIR \ -DICU_INCLUDE_DIR=$MTDIR/include \ -DICU_LIBRARY=$MTDIR/lib/libicuuc.so \ -DICU_IO_LIBRARY=$MTDIR/lib/libicuio.so \ -DICU_I18N_LIBRARY=$MTDIR/lib/libicui18n.so \ && make -j$(nproc) && \ make install && cd .. || exit 1 cd apertium-src && \ git clone https://github.com/apertium/lttoolbox && \ cd lttoolbox && ./autogen.sh --prefix=$MTDIR && make -j $(nproc) && make install && cd ../.. || exit 1 cd apertium-src && \ git clone https://github.com/apertium/apertium && \ cd apertium && ./autogen.sh --prefix=$MTDIR && make -j $(nproc) && make install && cd ../.. || exit 1 cd apertium-src && \ git clone https://github.com/apertium/apertium-lex-tools && \ cd apertium-lex-tools && ./autogen.sh --prefix=$MTDIR && make -j $(nproc) && make install && cd ../.. || exit 1 cd apertium-src && \ git clone https://github.com/apertium/apertium-tha && \ cd apertium-tha && ./autogen.sh --prefix=$MTDIR && make && make install && cd ../.. || exit 1 cd apertium-src && \ git clone https://github.com/apertium/apertium-tha-eng && \ cd apertium-tha-eng && ./autogen.sh --prefix=$MTDIR && make && make install && cd .. && \ cd .. || exit 1
todo.txt-cli
-
Ask HN: What products other than Obsidian share the file over app philosophy?
FSNotes for macOS and iOS is one I used for a little while.
https://fsnot.es/
todo.txt is another thing that comes to mind.
http://todotxt.org/
And of course pretty much all of *nix.
-
My productivity app is a never-ending .txt file
Since at least 2012 I've also been using a text file format from http://todotxt.org/ and more recently I wrote a program that takes a crontab-like list to pre-generate entries on a daily, by-day-name (every Sunday for example), and I also pull in a list of holidays from gov.uk, so they are also populated.
[^1]: (https://github.com/blacksmithgu/obsidian-dataview)
- Why I Like Obsidian
-
Ask HN: Tell us about your project that's not done yet but you want feedback on
It's a web app implementing the todo.txt format (see http://todotxt.org/). It's an exercise to learn frontend currently, I doubt I could successfully monetize it. Would appreciate any feedback!
-
Looking for a note taking app with inline tags.
That format is really similar to todo.txt format, worth taking a look at http://todotxt.org/ (which in turn has application links).
-
Using Acme with Inferno's Shell as a pkm tool
For todo and schedule I use todo.txt (http://todotxt.org/) a plain file managed by scripts which build agenda and plumber to keep track of unique keys.
-
Looking for PC and mobile "to do list" software
The ToDo.Txt format makes it easy to use across devices/software, but this is really limited to ToDos.
-
Yet another To Do manager written in BASH. Simple and colorful.
Here’s the todo.sh features for those interested. There are several addons for it as well: https://github.com/todotxt/todo.txt-cli
-
TaskTXT The Todo List for Hackers
Good idea, something similar to todotxt.org. But no 1) iPhone app 2) you need to sigh up and keep your notes at developers servers 3) subscriptions?! come on!
-
Wish to start cli apps development
There are a couple different routes you can go down. If your goal is to learn CLI stuff, it's hard to beat using shell-scripting for a simple app like a todo manager. Storing them in a plain-text file, a little sed/grep/awk and you're well on your way. For inspiration & hints, you might check out https://todotxt.org However, you can rapidly hit performance issues and limitations on available tooling if you stick to just POSIX tools.
What are some alternatives?
lingva-translate - Alternative front-end for Google Translate
taskpaper.vim - This package contains a syntax file and a file-type plugin for the simple format used by the TaskPaper application.
icu - The home of the ICU project source code.
taskwarrior - Taskwarrior - Command line Task Management
LibreTranslate - Free and Open Source Machine Translation API. Self-hosted, offline capable and easy to setup.
org-caldav - Caldav sync for Emacs orgmode
apertium-tha-eng - Apertium translation pair for Thai and English
MarvinAPI - API documentation for the Amazing Marvin productivity tool
lttoolbox - Finite state compiler, processor and helper tools used by apertium
github-orgmode-tests - This is a test project where you can explore how github interprets Org-mode files
feature-express
vimwiki - Personal Wiki for Vim