View Issue Details

IDProjectCategoryView StatusLast Update
0003531ScribusImport / Exportpublic2008-03-20 10:12
Reporteralexandre Assigned Tojghali  
Status closedResolutionfixed 
Platformi386OSWindows XP ProfessionalOS VersionSP1
Product Version1.3.3 
Target Version1.3.5Fixed in Version1.3.5svn 
Summary0003531: ODT files whose names contain special/unicode characters cannot be imported on Windows
DescriptionScribus doesn't import ODT files.
Steps To Reproduce1. Create new document: 200 pages, automatic text frames, 2 columns.
2. Select text frame.
3. Open context menu and choose "Append text".
4. Choose ODT file (tested on a 230 Kbyte large .odt).
5. In import settengs all checkbox on, except "don't ask again".
6. Click OK.
7. Scribus does nothing - no sign of importing (no progress bar, no usual visual artefacts, same amount of used RAM ), text frame is still editable, movable etc.

I have report from a Linux user that on the same operation with a 300 Kbyte large file Scribus eats 100% of CPU time (as reported in other Mantis entry).

Here at work I have a Celeron 1,3 with 512 Mbyte RAM, it handles large ODT files in fine, just FYI.
TagsNo tags attached.


child of 0003621 assignedTsoots [OBSOLETE] Metabug: COSS text importer update 
child of 0005693 closedplinnell 1.3.5 bug collection (prior to roadmap) 



2006-12-05 19:27

administrator   ~0013784

I strongly suspect this issue is related to special characters in path name and gzopen behavior on windows.


2006-12-05 20:47

administrator   ~0013786

libxml2 xmlSAXParseFile() seems to have some problems also with special characters on windows


2006-12-06 00:31

administrator   ~0013788

Last edited: 2006-12-06 01:05

in fact libxm2 expect filenames to be utf8 encoded on winnt based systems, have committed a patch which make things work better, gzopen/unzOpen problems are always here tho


2007-01-19 22:16

administrator   ~0014890

I have committed patch in 134cvs which add unicode functions supports on Windows to FileUnzip class. Tests shows that files which could not be opened due to unicode chars in their names now can. Have to deal with the gzOpen stuff now


2008-03-17 19:19

administrator   ~0019211


Issue History

Date Modified Username Field Change
2006-03-29 13:24 alexandre New Issue
2006-03-30 00:52 Tsoots Status new => assigned
2006-03-30 00:52 Tsoots Assigned To => Tsoots
2006-04-10 21:56 Tsoots Relationship added child of 0003621
2006-12-05 19:27 jghali Note Added: 0013784
2006-12-05 20:47 jghali Note Added: 0013786
2006-12-06 00:31 jghali Note Added: 0013788
2006-12-06 01:05 jghali Note Edited: 0013788
2007-01-19 22:16 jghali Note Added: 0014890
2008-03-17 19:19 jghali Assigned To Tsoots => jghali
2008-03-17 19:19 jghali Status assigned => resolved
2008-03-17 19:19 jghali Fixed in Version => 1.3.5svn
2008-03-17 19:19 jghali Resolution open => fixed
2008-03-17 19:19 jghali Note Added: 0019211
2008-03-17 19:23 jghali Summary ODT import doesn't work => ODT files whose names contain special/unicode characters cannot be imported
2008-03-17 19:28 jghali Summary ODT files whose names contain special/unicode characters cannot be imported => ODT files whose names contain special/unicode characters cannot be imported on Windows
2008-03-17 21:52 christoph_s Target Version => 1.3.5
2008-03-19 19:05 christoph_s Relationship added child of 0005693
2008-03-20 10:12 jghali Status resolved => closed