I received a short Word document from work today and opened it in NWE 2.7 which used Abiconvert to format the document. I noticed loads of error messages in the console log, a short sample:
(process:4028): libgsf:msole-CRITICAL **: file gsf-infile-msole.c: line 109 (ole_get_block): assertion `block < ole->info->max_block' failed
2007-03-30 11:09:29.852 abiconvert[4028] ASSERT m_pItems.getItemCount() > 0 raised at src/text/fmt/xp/fl_AutoNum.cpp:833
2007-03-30 11:09:29.858 abiconvert[4028] ASSERT pns raised at src/wp/impexp/xp/ie_exp_RTF.cpp:2272
2007-03-30 11:09:29.858 abiconvert[4028] ASSERT pStyle raised at src/wp/impexp/xp/ie_exp_RTF_listenerWriteDoc.cpp:1392
2007-03-30 11:09:29.859 abiconvert[4028] ASSERT pns raised at src/wp/impexp/xp/ie_exp_RTF.cpp:2272
Is this anything to be worried about?
The document appeared to be translated all right.
Geoff
Abiconvert errors
- GeoffRoynon
- Posts: 48
- Joined: 2004-04-26 10:20:33
- Location: Oxford, UK
Abiconvert errors
Geoff Roynon
Mac Studio, MacOS X 14.0 Sonoma
NW Pro 3.3
Mac Studio, MacOS X 14.0 Sonoma
NW Pro 3.3
Re: Abiconvert errors
If it was a word .doc, why on earth was Abiconvert involved ... NWE will read .docs directly ... or was it originally written in AbiWord rather than word?GeoffRoynon wrote:I received a short Word document from work today and opened it in NWE 2.7 which used Abiconvert to format the document. I noticed loads of error messages in the console log, a short sample:
(process:4028): libgsf:msole-CRITICAL **: file gsf-infile-msole.c: line 109 (ole_get_block): assertion `block < ole->info->max_block' failed
2007-03-30 11:09:29.852 abiconvert[4028] ASSERT m_pItems.getItemCount() > 0 raised at src/text/fmt/xp/fl_AutoNum.cpp:833
2007-03-30 11:09:29.858 abiconvert[4028] ASSERT pns raised at src/wp/impexp/xp/ie_exp_RTF.cpp:2272
2007-03-30 11:09:29.858 abiconvert[4028] ASSERT pStyle raised at src/wp/impexp/xp/ie_exp_RTF_listenerWriteDoc.cpp:1392
2007-03-30 11:09:29.859 abiconvert[4028] ASSERT pns raised at src/wp/impexp/xp/ie_exp_RTF.cpp:2272
Is this anything to be worried about?
The document appeared to be translated all right.
Geoff
To my mind, if it was translated alright, you could read it, edit if necessary and save it out, there's not a problem ... there only is if you become aware that something is missing or if it misbehaves.
Mark
Martin, that's really interesting ... though of no particular importance to me, as long as they convert OK. But tell me, does TextEdit also use Abiconvert? I thought NWE and TextEdit used the same engines.martin wrote:We use Abiconvert to handle translation of ".doc" files. Don't let the warnings concern you- as long as your document looks fine, there's no problem.
Mark
- martin
- Official Nisus Person
- Posts: 5228
- Joined: 2002-07-11 17:14:10
- Location: San Diego, CA
- Contact:
TextEdit does not use Abiconvert, as Apple has their own ".doc" file importer. When we say that we use the text engine that Apple provides we are generally referring to the layout engine, eg: the code that handles the placement and display of text. Of course we have modified that engine for our needs, but the core is provided by OSX.