Re: [edict-jmdict] <xref> tags without a destination or with too many destinations

[Jim Breen <jimbreen@*********>]

Just started to catch up on this thread, and there is a flurry of emails.

2010/10/30 Stuart McGraw <smcg4191@frii.com>:
> On 10/28/2010 08:26 PM, Jim Breen wrote:

>> I'm working through the rest of the 18, and they should be cleaned up in
>> a day or two.
>
> Jim, for reference you can get a list of all the unresolved
> references at any time by running:
>
>  ./xresolv.py  -nkv -d jmdict
>
> This will list the xrefs that it
> - Can resolve (run again without the -n and -k options and it
>  will generate "real" xrefs for the resolvable ones.)
> - Can't resolve because it couldn't find any matching entries
> - Can't resolved because there are multiple matching entries.

Thanks.

I was going to use it to make a page for the interest of others, but I see
it also sweeps in rejected entries, for which things like unresolved or
multiple xrefs are a waste of time pursuing.

I'm plugging away at the multiple targets. The fix is to use the ent_seq
as the target.

Cheers

Jim


-- 
Jim Breen
Adjunct Snr Research Fellow, Clayton School of IT, Monash University
Vice-president: Hawthorn Rowing Club, Treasurer: Japanese Studies Centre
Graduate student: Language Technology Group, University of Melbourne