July 2015

[aoloe]

will be published end of june 2015

topics:

• release of 1.5.0
  • explaining a bit what it means, what are 1.5.0, 1.5.1, trunk...
  • announce that we will present the new features
  • what will for sure be done until 1.6.0 (PP)
  • who should/could use 1.5.x and what are the dangers
• announce scribusCTL by andreas vox and arabic support
• http://bugs.scribus.net/view.php?id=12920 (Scribus should ensure fonts are either embeded or outlined)
• announce the inofficial ScribusAPI

add a graph with statistics about scribus?

• commits per week / day
• bug opened / fixed
• posts in the ML, forum, G+, twitter

[luzpaz]

I propose to write about my perspective of moving from an outside-in perspective on using Scribus to an inside-out perspective. What perceptual changes I've moved through seeing what it takes to follow closely the evolution of an enormous and complex open source project.

[aoloe]

after having fixed (for the first time) a broken .sla, i'm in the mood of describing how to do it :-)

roscoeeather reported a corrupted .sla in the (private) bug #13123.

A computer crash left him with a truncated .sla. having a look at it with a test editor shows that the last line has been truncated:

        <PAGEOBJECT OwnPage="6" PTYPE="4" XPOS="1261.46491562126"  
YPOS="3941.42606929134" WIDTH="149.005888" HEIGHT="40.2356" RADRECT="0" FRTYPE="0"  
CLIPEDIT="0" PWIDTH="1" PCOLOR="None" PCOLOR2="None" TXTFILL="New Color"  
COLUMNS="1" COLGAP="0" NAMEDLST="" SHADE="100" SHADE2="100" GRTYP="0" ROT="0"  
PLINEART="1" PLINEEND="0" PLINEJOIN="0" LOCALSCX="1" LOCALSCY="1" LOCALX="0"  
LOCALY="0" PICART="1" PLTSHOW="0" BASEOF="0" textPathType="0" textPathFlipped="0"  
FLIPPEDH="0" FLIPPEDV="0" IFONT="Old Standard TT Regular" SCALETYPE="1" RATIO="1"  
PRINTABLE="1" ANNOTATION="0" ANNAME="" TEXTFLOWMODE="0" TEXTFLOW="0"  
TEXTFLOW2="0" TEXTFLOW3="0" AUTOTEXT="0" EXTRA="0" TEXTRA="0" BEXTRA="0"  
REXTRA="0" FLOP="0" PFILE="" PFILE2="" PFILE3="" PRFILE="" EPROF="" IRENDER="1"  
EMBEDDED="1" LOCK="0" LOCKR="0" REVERS="0" TransValue="0" TransValueS="0"  
TransBlend="0" TransBlendS="0" isTableItem="0" TopLine="0" LeftLine="0" RightLine="0"  
BottomLine="0" isGroupControl="0" NUMDASH="0" DASHS="" DASHOFF="0" NUMPO="16"  
POCOOR="0 0 0 0 149.006 0 149.006 0 149.006 0 149.006 0 149.006 40.2356 149.006 40.2356  
149.006 40.2356 149.006 40.2356 0 40.2356 0 40.2356 0 40.2356 0 40.2356 0 0 0 0 " NUMCO="16"  
COCOOR="0 0 0 0 149.006 0 149.006 0 149.006 0 149.006 0 149.006 40.2356 149.006 40.2356  
149.006 40.2356 149.006 40.2356 0 40.2356 0 40.2356 0 40.2356 0 4^@^@^@^@^@^@

with many more ^@ following that. ^@ being the null character.

I have to suppose that the file has been truncated at that point. how to rescule the 10 MB of xml tags before that?

The first step, is to remove the incomplete tag. That was easy.
But not enough. If you know just a little bit about XML, you know that it's very likely that there was one or more open tag for the document and maybe the page. Sadly, the file being so huge, it's not possible to find out the orphaned item.

Let's try with an XML validator, then!
On my Linux computer I've tried the first result suggested by my internet search: xmllint (from the libxml2-tools package).
Runing it against the broken .sla file gives the following result:

$ xmllint Document-2\ \(1\).sla 
Document-2 (1).sla:27533: parser error : Premature end of data in tag DOCUMENT line 3

^
Document-2 (1).sla:27533: parser error : Premature end of data in tag SCRIBUSUTF8NEW line 2

That looks useful!
The first try is the good one: I just had to add

</DOCUMENT>
</SCRIBUSUTF8NEW>

Et voilà: we've lost what comes after the truncating point, but we can restore the first 10 MB of data.

[aoloe]

anke's tutorial on guides?
http://www.scribus-user.de/forum/viewtopic.php?f=6&t=136

[aoloe]

what about presenting the new icons? is it possible to make a short interview with the author?

[aoloe]

presenting the goals and roadmap for the new scripter (and ask for comments)

[aoloe]

vertical align in a text frame

• only works if the frames are not linked
• only for simple cases (which ones)
  it's a temporary implementation
• One work-around could be to unlink the frames (with text splitting, don't remember what the option is called) and then vertically align each frame