Mantis Issue Tracking for Scribus
· Hosting provided by Anduin.net / Øverby Consulting ·

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0011420ScribusImport / Exportpublic2013-02-13 20:312014-10-11 17:32
ReporterJLuc 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version1.5.0svn 
Target VersionFixed in Version 
Summary0011420: 1.5 style management during page import
Description1.4 tried to cleverly manage styles during a page import - but code was not finished and functionnality was buggy. 1.5 is different but does not better at it.

Uploaded pageimport.sla is a document featuring 3 paragraph :

- A paragraph with pure "default par style" being defined as CYAN ARIAL UPPERCASE. When imported it keeps being "default par style" but the definition is not imported and so the look is correct.

- A paragraph with "default par style" and some local inline character formating (not using style definitions) : this is perfectly imported.
This paragraph includes also a bit of text styled with a named char style : "UserCharStyle". This part of text cannot be read once imported : all letters appear as big squares. + The named style has not been created in the importing document. There must be some big mismatch in the styles defintion and uses.

- A paragraph with a pure user defined paragraph style : UserParStyle, that does not formerly exists in the importing document. It includes both character properties : color, font, effects and paragraphe properties : lineheights.
Strangely, the paragraph looks partly well : color , lineheight, font and font size are ok but "uppercase" text effect has been lost.

- At first it looks like the imported styles have not been created in the document since they dont appear in the style window, but its only a display refresh issue because 2 newly created styles appear sooner or later in the style dialog : a new "default paragraph style" (that make 2 styles with same name; that's a problem) and the imported "UserParStyle".
The defined and used character style has not been imported at all.

- When looking more closely at the UserParStyle, it looks like
1) some of its properties have been copied truthfully (font, lineheight...)
2) some of its properties have been totally ignored (uppercase)
3) for the color of the font, its more complex. At first it appears to NOT have been copied into the style definition, but into the text itself, as inline formatting. But then later on, after some operations, it seems to appears that the style definition sometime changes itself to reflect the original style value.

That's a big lot of important issues that make the functionnality rather hazardous to use.
Additional InformationWhen testing you'll notice that the import does not position the imported content at its right place : that's 0011411

If some dev is willing to solve this issue i'm willing to study and propose specifications for the various possible cases.
Tagsstyles
Patch
Attached Files? file icon pageimport.sla [^] (26,698 bytes) 2013-02-13 20:32
png file icon originating.png [^] (202,730 bytes) 2013-02-13 20:34


png file icon once imported.png [^] (185,960 bytes) 2013-02-13 20:34

- Relationships

-  Notes
(0029837)
JLuc (updater)
2013-02-13 21:02

2nd paragraph should read

- A paragraph with pure "default par style" being defined as CYAN ARIAL UPPERCASE. When imported it keeps being "default par style" but the definition is not imported and so the look is NOT correct.
(0030133)
JLuc (updater)
2013-05-07 21:56

At the end of a magazine creation session, requiring quite a few page-import actions (and maybe a couple of style-import actions too), the SLA is crippled with lots of "Copy of Suchstyle" and "Copy of Copy of Suchstyle". There even is a "Copie de Suchstyle (2)" which is its french counterpart. The "(2)" there is quite mysterious since there is no "Copie de Suchstyle" at all without the (2).

After researching in the SLA it appears that these "Copy of" styles are not used at all. So AFAIAC it's possible to delete them and it's quite easy to do so in editing the SLA with a text editor. Better would be not to create them, and even better would be to handle styles correctly during page or style imports.
(0030244)
JLuc (updater)
2013-06-05 17:43
edited on: 2013-06-06 07:08

Right now another experience :

I import various document using the same styles at the end of a document : the styles are not duplicated in the resulting merged document and everything looks allmost fine.
(But then, since no new style is created, a layout problem would have occured, in case the styles had had the same name but a different definition ???)

However, there seem to be a problem with interline space : when it has been changed localy, that change is not reported in the imported pages (the style default value used).
Importing another document's pages rises another issue : some characters become "bad glyph" squares...


- Issue History
Date Modified Username Field Change
2013-02-13 20:31 JLuc New Issue
2013-02-13 20:32 JLuc File Added: pageimport.sla
2013-02-13 20:34 JLuc File Added: originating.png
2013-02-13 20:34 JLuc File Added: once imported.png
2013-02-13 21:02 JLuc Note Added: 0029837
2013-05-07 21:56 JLuc Note Added: 0030133
2013-06-05 17:43 JLuc Note Added: 0030244
2013-06-06 07:07 JLuc Note Edited: 0030244 View Revisions
2013-06-06 07:08 JLuc Note Edited: 0030244 View Revisions
2014-03-23 11:11 JLuc Tag Attached: foundation
2014-03-23 11:11 JLuc Tag Attached: style
2014-10-09 01:21 Kunda Tag Attached: styles
2014-10-09 01:22 Kunda Tag Detached: style
2014-10-11 17:32 Kunda Tag Detached: foundation



Copyright © 2000 - 2014 MantisBT Team
Powered by Mantis Bugtracker