7.0491 R and Report; Chinese Char Sets; WinWord (2/90)

Elaine Brennan (EDITORS@BROWNVM.BITNET)
Wed, 16 Feb 1994 23:52:36 EST

Humanist Discussion Group, Vol. 7, No. 0491. Wednesday, 16 Feb 1994.


(1) Date: 16 Feb 94 08:00:19 EST (25 lines)
From: Otmar.K.E.Foelsche@Dartmouth.EDU (Otmar K. E. Foelsche)
Subject: Re: 7.0484 Qs: Scanner/Printer; OCR; ACH Newsletter (3/52)

(2) Date: Wed, 16 Feb 1994 15:34:13 +0000 (CUT) (65 lines)
From: Maurizio Lana <lana@rs950.cisi.unito.it>
Subject: experience with WinWord 2.0 and a big file of text and images

(1) --------------------------------------------------------------------
Date: 16 Feb 94 08:00:19 EST
From: Otmar.K.E.Foelsche@Dartmouth.EDU (Otmar K. E. Foelsche)
Subject: Re: 7.0484 Qs: Scanner/Printer; OCR; ACH Newsletter (3/52)

--- You wrote:
Date: 14 Feb 94 16:05:18 GMT
From: johnstonj@attmail.com (James Johnston )
Subject: Re: 7.0455 Qs: Unicode; KLEIO; Long Names; Quote Query; MLA Online;

A colleague of mine is searching for a company that can do OCR on Chinese
characters . . . word has it that there is a firm in Germany that has such
a product . . . alas, no information on who, where, etc. Anyone?

Also, WordPerfect Corporation has just released a Chinese version of their
word processor -- unfortunately, no on in Orem seems to know where they got
their version of the Chinese character set . . . it was apparently purchased
in Taiwan. Does anyone know who is selling a Windows version of Chinese
characters?
--- end of quoted material ---

I saw a Chinese Windows version together with a Microsoft Word version
recently (apparentlyboth still in beta). The experts here (at Dartmouth) tell
me that it is still rather primitive compared to running NISUS with both
traditional and simplified Chinese plus the cihui dictionary on the
Macintosh.
(2) --------------------------------------------------------------81----
Date: Wed, 16 Feb 1994 15:34:13 +0000 (CUT)
From: Maurizio Lana <lana@rs950.cisi.unito.it>
Subject: experience with WinWord 2.0 and a big file of text and images

This is a report about my recent experience: I think it can be useful for=

others.

Notes on use of Winword 2.0 with large text file (1,2M)

I publish these notes to share my experience with others about a subject
not quite known. As I worked with an italian version of Winword, I'll
indicate which menu choice is used.

My file contained text and images. Six images were produced including
(master menu, fourth choice "Inserisci oggetto") a MSDraw object, two were
Paintbrush objects. The file wasn't splitted into smaller files, as
Microsoft advices, because I had a number of internal references (made
using fields "rif" and "pagrif").

After the file had grown up, I got an error "The file is too big to be
saved" (the last save had written a 2M file, even if I hadn't doubled its
dimension adding so much stuff). I splitted it recursively in two parts,
one of which always gave the error message "The file is too big...". I
ended up discovering that the error was given by the Paintbrush images: I
erased them, reimported them from the files where they were saved as .bmp,
and all went right.

After some days I got another time the error message "The file is too big
to be saved" (now the last saved file was 2.9M; still I hadn't put into so
much text or images).

The problem were always the .bmp images *and* the option "allow quick
save". The .bmp images added about 600K (the .bmp files alone were instead
80K each) when included; and after saving two or three times the files, I
always ended with that error.

(I must use a Paintbrush image because I needed an area filled in color).

For the images growing from 160 to 600K I avoided the problem this way:
for each one of the .bmp images
I opened a new Winword file;
included the .bmp alone;
saved the file as a Winword doc;
opened Word 5 for Macintosh;
imported into Word for Mac the doc containing the bitmap;
without doing anything saved it as a Word for Windows 2.0 doc;
included into my big doc that file saved from Mac;
and - voila=E0 - the big doc was about 170K bigger, as expected.

For the (probably) faulty "save file" command I deactivated the option
"allow quick save": after being saved two or three times the file was
*smaller*, the backup save and normal save were *faster*, and I got no
more error messages about the file dimensions.

Conclusions:
big text files are a viable solution, if you need them;
beware of "quick save" option with big text files;
beware of Paintbrush objects.


Maurizio Lana - CISI - Universita' di Torino
lana@rs950.cisi.unito.it fax: 39-11-8990458