View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0014916||Scribus||Import / Export||public||2017-07-18 18:15||2017-07-23 13:06|
|Platform||OS||Windows 10 - 64 bit||OS Version||1703|
|Target Version||Fixed in Version|
|Summary||0014916: Imported *.odt file not imported correctly and Story Editor does not maintain accurate Scribus styles that are selected.|
|Description||Importing a *.odt file does bring the file in with much of the formatting intact. However, some of the text is not imported correctly.|
In addition, once in the story editor, when a style is selected from the style menu in upper right corner, the style is not applied accurately.
Also, I note that F3 does not work in this version: Scribus 1.5.3 - Build ID: C--T-*-C1.14.6-Windows-64bit; Using Ghostscript version 9.20. This seems to be because both the Style Editor and the Text Properties are assigned to F3?
|Steps To Reproduce||1) Import attached file, Scribus test.odt into attached Scribus test.sla file.|
2) The file is imported with much of the formatting maintained (italics, bold) bus some is lost. For example, the "Abstract" should be in Arial font as well as "Key words". The citation below "Key words" does appear partially in Arial but the italicized words "British Columbia Birds" are in Times New Roman.
3) When I go to reformat what isn't properly formatted I use the Story Editor and the style menu in the upper right corner as that is the only one that will reformat a change in text without losing the other formatting (e.g., italics, bold; see old issue 0012800). Changing the style in the left column of the Story Editor or using the Text Properties will cause italics and bold to be lost.
4) In the Story Editor, The "Abstract" and "Key words" are showing as TNR Bold 10 pt. with the style "abstract", the style used in the odt file. When the abstract is highlighted and the style is changed to "Abstract" (upper case "A") at the top of the Scribus style menu (upper right corner), the font stays in TNR (should change to Arial as that's the font in the Scribus style for "Abstract") but the font size does change to 9 pt., which is correct. So Arial is somehow not picked up.
5) When the citation below "Key words" is changed to the "Citation" style, sometimes it remains as TNR 10 pt. and occasionally it does change to Arial 9 pt. In any case, it should be Arial 8 pt.
6) Update Text Frame and Exit.
7) The "Abstract" and "Key words" are still in TNR, although in Text properties it shows the Scribus paragraph style as "Abstract" which is Arial font.
8) the citation below "Key words" is in Arial 9 pt but should be Arial 8 pt, according to the Scribus style. Also, the italicized "British Columbia Birds" is still in TNR, not Arial.
|Additional Information||When importing an *.odt file, all the formatting in the file should be brought into Scribus correctly which over the production of a journal issue saves countless hours of reformatting. |
Also, it would be nice to have the choice of bringing the *.odt file's styles into the Scribus Style Manager OR NOT. The Style manager quickly fills with numerous styles as different writers use different styles on their computers, making use of the Style manager quite cumbersome.
Scribus test.sla (70,417 bytes)
Scribus test.odt (29,807 bytes)
||I committed a first fix which fix cases where imported text was using a wrong font. I will try to provide new snapshots with that fix this week-end.|
New snapshots now available:
|2017-07-18 18:15||nkdawe2||New Issue|
|2017-07-18 18:15||nkdawe2||File Added: Scribus test.sla|
|2017-07-18 18:15||nkdawe2||File Added: Scribus test.odt|
|2017-07-18 18:15||nkdawe2||Tag Attached: import|
|2017-07-18 18:15||nkdawe2||Tag Attached: styles|
|2017-07-21 11:16||jghali||Note Added: 0044194|
|2017-07-23 13:06||jghali||Note Added: 0044202|