Muke Tever wrote:
Ray Saintonge <saintonge(a)telus.net> wrote:
I agree.
As I have said ... probably many times now, 99% of Wiktionary
articles are stubs.
If you want stubs look at the Ido Wiktionary. 8-)
I hit special:randompage once on en: and io: and got:
http://en.wiktionary.org/wiki/Benignant
http://io.wiktionary.org/wiki/Seenessel
Not much difference there, except that en: has a part of
speech and io: has a language index category...
nl: doesn't fare much better, returning
http://nl.wiktionary.org/wiki/yei
which manages language, category, part of speech, and definition...
But the word is spelled entirely wrong (according to
[1] and en: it should probably be ေရ, though since Google
search ignores Burmese text [!!] I can't really confirm that)
If such a thing happens in a little Wiktionary, only a very few will
notice it. If it happens in UW, chances are a lot better somebody who
knows what is wrong about it, will see it, since all our eyeballs will
be focused on one version of the data. And then it can be fixed once and
for all. If something gets fixed now in one Wiktionary, it is very well
possible it is still entered wrongly in many others.
Will the UW have any way to note that information was
added by a
non-native speaker?
IMO the more effort put in (can't really say it was _duplicated_, as
outside of very specialized technical terms and the communalized SAE
semantics, just because something translates an English word doesn't
mean it's the best translation of the French, Greek, or Chinese word
that also translates the English..., and at the very least that has
to be checked), the more chances we have to find discrepancies and
make a better dictionary by checking them against each other.
The problem of the translations is a very real one and it's not going to
be easy to solve it. That doesn't mean we should just give up though. It
means we should look for a viable solution. Words across different
languages can be linked to each other. For each language pair a link is
needed. This would solve the problem nicely. It's not how I set up my
implementation (my implementation is not what is being used for UW, so
it's pretty irrelevant), but maybe it's a good way to do things in UW.
Jo