We used SF as a data store, because we couldn't find something appropriateBefore, I only packaged the vcs version of the tools, though today II sent you the GitHub link. Our website points to GitHub and the SourceForge
tried to package those on sourceforge.net. Unfortunately, they appear to
notably lag behind (version 0.4, 2014-03-02) and don't work for me (I
tried the current non-vcs versions of deu-eng and eng-spa).
site should mention that we have moved. Whatever you find on SourceForge is
outdated. Is there a way we can make that even more clear?
But the dictionary sources themselves on SourceForge are not outdated?
At least they are referenced from the "Detailed list", the json and the
Could you have a look at neu.freedict.org, please? This is our new draft of thePlease try this:
Thanks. I just thought all the non-vcs sources (i.e. releases) were to
be searched for on SourceForge. It would be great if, on the website,
there was a short description how to work with the release files,
information on all (or most) installation (and bulding) options.Building options are explained in the Wiki, I'm not sure how to present that on
Brilliant.Many years ago, there was a FreeDict-tools 0.4, bbut I couldn't find a 0.3
no changelog, so I decided to publish 0.1.0 officially. If this should cause
problems with packaging, I stick to 0.5, if it is more convenient.
At least in the Arch world, there existed to my knowledge never a
package for the tools. So, I personally have no problem with the versioning.
By the way, another thing I just noticed: The website by defaultErr, that is weird indeed. Another good reason to speed up the website
redirects me to /ru/. That did not happen the last time. I presume this
is not intended, in particular, it is not possible to choose English
from the list. Manually entering the /en/ URL works, though.
Description: PGP signature