Techwriter 8.90/RISC OS 5.20
Chris Hall (132) 3554 posts |
Techwriter fails to open a docx file with the error message ‘Could not open file XXX/docx because JPEG format is not supported by this version of the SpriteExtend module.’ It works fine in 5.16 |
Trevor Johnson (329) 1645 posts |
Has SpriteExtend been changed recently? It doesn’t look like it, but perhaps I’m looking in the wrong place. |
Raik (463) 2059 posts |
No problems with TW 9.00 and RISC OS 5.20 on xM. I try my docx with a jpeg inside. |
Chris Hall (132) 3554 posts |
It may be the particular document, other docs were fine. |
Raik (463) 2059 posts |
Try this if you want. |
Chris Hall (132) 3554 posts |
More complicated. In 5.16 and with TechWriter 8.90 on my Iyonix:
So I can load doc (AE6) and docx (A7E) files (so long as TechWriter is running or I load a docx file first). Before upgrading to 5.20 I did not get this problem. The app !Writer+ in Apps (now broken by a change in !Boot for 520 which loads a ‘bugfixed’ Shared C Library) was previously harmless. Going back to the old version of !Boot, I find !Writer+ works fine under 5.16. Now I am quite puzzled. In 5.20 after start up the system variables above are the same. However opening a docx file with an image (which worked in 5.16) fails with a ‘this version of SpriteExtend can’t handle the JPEG’. The version of SpriteExtend is 1.21 (19-Jan-2010) under 5.16 and 1.51 (10-Aug-2013) under 5.20. Therefore something has been broken in SpriteExtend? Perhaps under the new terminology this is also a ‘bugfix’? List of modules under 5.16 compared between old Boot and new Boot:
So if I was following the ROOL upgrade checklist for 520 I would stop after trying the new !Boot directory under 5.16 and say ‘cannot proceed further – the update to the Shared C Library does not work correctly with !Writer+’. So anyone who has upgraded to 520 on the Iyonix has not followed the instructions.
|
Chris Hall (132) 3554 posts |
Has SpriteExtend been changed recently? Yes. From the version number, there have been 30 changes since 2010. However the JPEG problem was evident in RISC OS 5.18 (SpriteExtend 1.47 (03-Oct-2011)) so the problem is between versions 1.21 and 1.47. That was (probably) one of the reasons I stuck with 5.16 on the Iyonix rather than go to 5.18. |
nemo (145) 2529 posts |
BTW. I haven’t looked but I was, how can I put this, “rather disappointed” when ROL added code to SpriteExtend to ignore any ‘next’ sprite offset that was negative. I do hope no such barbarism has been committed on this version. Note that not only was the restriction not originally present in the OS_SpriteOp interface, it was only imposed on those commands implemented inside SpriteExtend, and no others. It was… irritating. |
Chris Gransden (337) 1202 posts |
JPEGs with interlacing set give the not supported error from the current version of SpriteExtend. |
Steve Pampling (1551) 8155 posts |
Chris H. Any of your problem apps require ABCLib? |
Chris Hall (132) 3554 posts |
Any of your problem apps require ABCLib? I don’t think so… v4.15 is downloadable from Paul Vigays module database links … but I had 4.15 in my 5.16 boot so I’ll put that in the new boot. Shouldn’t the 520 HardDisc4 be updated to have the later ABCLib? |
Raik (463) 2059 posts |
I have found two test version from TW (8.91) and EW (8.84) in my E-Mail archive. Martin send this to try it on my ARMini Prototype. |
Chris Gransden (337) 1202 posts |
Both Techwriter and EasiWriter are working as they are supposed to. |
Raik (463) 2059 posts |
That’s why I have my test file online. See above. I do not know Chris Halls files. Possible that he has a special problem. This is also the reason why I pointed out that the docx-files are Zip-files and so you can open and edit it individually. Some errors come from an unpredictable direction. |
Chris Hall (132) 3554 posts |
The image file |
Raik (463) 2059 posts |
First short test on my Pandora: !DPIngscan (Imagemaster) und !Variations can handle the jpeg. |
Chris Gransden (337) 1202 posts |
Your example jpeg also has interlace set so that confirms the problem. I’ve raised ticket #349. It’s an enhancement request to add support for JPEGs with interlace to SpriteExtend.
It looks like resaving the JPEG must be removing the interlace. That’s why it then subsequently loads. |
Chris Hall (132) 3554 posts |
It’s an enhancement request to add support for JPEGs with interlace to SpriteExtend. To add it back in, you mean. It was OK in an earlier version. Many thanks for raising the bug item. |