🚀 go-pugleaf

In article <970314121459.M0100353@earth.cias.osakafu-u.ac.jp>,
okamoto@earth.cias.osakafu-u.ac.jp (Kenji Okamoto) wrote:

>In the article <aa0b921-1403970940090001@133.109.74.51> of newsgroup
>comp.sys.mac.apps,fj.life.in-japan,sci.lang.japan
>aa0b921@giken.kobelco.co.jp.NOSPAM wrote
>
>  | In article <970313171729.M0114427@earth.cias.osakafu-u.ac.jp>, 
>  | okamoto@earth.cias.osakafu-u.ac.jp (Kenji Okamoto) wrote:
>  | 
>  | >He wrote a English text on Japanese version of Word6, and sent it to
>  | >Stanford where someone read it by English version of Word (don't know
>  | >the version number).
>  | 
>  | The problems we've had occur when trying to read text written by an 
>  | English version of Word (versions up to and including 6.0, don't know the 
>  | minor version number) of both Windows & Mac, on a Japanese version. Text 
>  | submitted on a disk for a joint paper with our US subsidiary was garbled 
>  | by any Japanese Word version.
>
>He has read the edited by a researcher of Stanford, which means he could
>read a Word text written by English version.   It's also worthy to add
>another case that he wrote English on Word-J and sent it to China where
>nobody could read it.  This is the observation when I said minor release 
>number maybe be the difference between them.  I don't know more details
>because I'm not a Word user, but LaTeX user.  :-)

Most problems I've encountered and heard are also in the E->J direction. My
understanding of the J->E direction is that while the port always fails on
Macs, sometimes you can pull it off in Windows but even so must be sure to
do a "Save as..." right away to make sure you don't lose the data.

You're sure they were not trading .rtf files? This is the only way I've
managed to port Word files reliably. (I'll bet it would work for the
Chinese version too. Worth a try.)

Could it possibly have anything to do with file content?



Regards,
Tod McAvoy
mctod@gol.com