A question on Japanese patents

Leland Ness (lness@dgsys.com)
Thu, 11 Feb 1999 21:15:02 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01BE5603.96B6B700
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is a question for Alan, although I thought the response might be =
interesting to all the group, so I am posting it here.

Now that my hopes of being able to machine-translate the Japanese =
patents that I need have been dashed, I have begun looking again at PAJ. =
In many of the abstracts I look at the abstract itself is =
unintelligible. The words are English, but the sentences (when such =
exist) often make no sense at all. I have spoken to several others who =
have encountered the same problem.

What causes this? Is it:

(a) the original (Japanese) abstracts are ambiguous
(b) the MT program the JPO uses is so abysmal
(c) the translation from Japanese to English is so complex that any MT =
program will yield the same result.
(d) some problem I haven't thought of

Thanks

Lee Ness

------=_NextPart_000_0006_01BE5603.96B6B700
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

This is a question for Alan, = although I thought=20 the response might be interesting to all the group, so I am posting it=20 here.
 
Now that my hopes of being able to=20 machine-translate the Japanese patents that I need have been dashed, I = have=20 begun looking again at PAJ.  In many of the abstracts I look at the = abstract itself is unintelligible.  The words are English, but the=20 sentences (when such exist) often make no sense at all.  I have = spoken to=20 several others who have encountered the same problem.
 
What causes this?  Is = it:
 
(a) the original (Japanese) = abstracts are=20 ambiguous
(b) the MT program the JPO uses is = so=20 abysmal
(c) the translation from Japanese to = English is=20 so complex that any MT program will yield the same result.
(d) some = problem I haven't=20 thought of
 
Thanks
 
Lee Ness
------=_NextPart_000_0006_01BE5603.96B6B700--