View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008606 | Scribus | General | public | 2009-11-28 17:14 | 2010-01-02 23:39 |
Reporter | sliou | Assigned To | jghali | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | AMD 64 | OS | Mandriva Linux | OS Version | 2010.0 64-bit |
Product Version | 1.3.5 | ||||
Fixed in Version | 1.3.6svn | ||||
Summary | 0008606: Informative message when opening file fails | ||||
Description | I have a couple of files created with 1.3.3.12. They open with 1.3.5.1, but after saving I can no longer reopen them. This happens regardless of whether I modify the file or not. When I try to reopen, I see some disk activity and nothing happens. | ||||
Steps To Reproduce | Open old_file.sla save it as new_file.sla exit scribus open scribus try to open file new_file.sla nothing happens | ||||
Additional Information | This is the same issue as 0007605, which is now closed. I report it again because I am able to supply the files that cause the problem. | ||||
Tags | No tags attached. | ||||
Patch | |||||
2009-11-28 17:14
|
|
|
OK, great, problem solved: it turns out the color names were messed up. Still, this is a bug with scribus and should be fixed. I attach the hand-edited file which opens ok; I have removed four non-ascii symbols from the color names. |
2009-11-28 17:34
|
|
|
The root of the problem is the 133x document itself. It contains already corrupted color names : the character sequence �� representing null characters in color names is illegal. How did you manage to create such color name in 133x??? 1.3.5.1 happens to open that doc, but that's only by chance as the qt component used for loading 133x document is very forgiving vs malformed xml. There is nothing to be fixed in 1.3.5.1 in your case, only in 133x. |
|
Hm, I respectfully disagree with that :) Regardles of which component causes the problem, some feedback should be given to the user when a file cannot be opened. I agree that this is a "nicety" rather than a core feature, but I still believe it is essential for a normal user experience. |
|
i believe that you get a warning when opening a 1.3.3.x file with 1.3.5.1 that it wont open with older versions anymore. |
|
Yes, you get a warning for that. The problem I described (please read previous posts) arises when you save the file and then you try to reopen it with THE SAME version (1.3.5.1). |
|
Some informative message have been added when parsing file fails. Cannot do anything more as the 133x document is the root of the problem. |
Date Modified | Username | Field | Change |
---|---|---|---|
2009-11-28 17:14 | sliou | New Issue | |
2009-11-28 17:14 | sliou | File Added: files_7605.tar.gz | |
2009-11-28 17:34 | sliou | Note Added: 0022892 | |
2009-11-28 17:34 | sliou | File Added: new_file_cor.sla.gz | |
2009-11-28 19:10 | jghali | Note Added: 0022893 | |
2009-11-28 19:13 | jghali | Note Edited: 0022893 | |
2009-11-29 15:47 | sliou | Note Added: 0022894 | |
2009-12-05 05:37 | farid | Note Added: 0022911 | |
2009-12-09 04:36 | sliou | Note Added: 0022930 | |
2009-12-17 23:31 | jghali | Summary | Unable to reopen files created with older versions after saving => Informative message when opening file fails |
2009-12-17 23:32 | jghali | Note Added: 0022982 | |
2009-12-17 23:32 | jghali | Status | new => resolved |
2009-12-17 23:32 | jghali | Fixed in Version | => 1.3.6svn |
2009-12-17 23:32 | jghali | Resolution | open => fixed |
2009-12-17 23:32 | jghali | Assigned To | => jghali |
2010-01-02 23:39 | cbradney | Status | resolved => closed |