[scribus-dev] CTL and Trunk: where are we at?

[Khaled Hosny]

One issue that always bugs me is the lack of test files attached to most
issue reports, and one is expected to follow some vague instructions (or a
screen shot of some Scribus settings). This is really just making it
hard for everyone involved, and I think it should be a requirement that
the issue reports attaches a small document showing the issue (unless it
is something that can’t be captured in a document of course).

Regards,
Khaled

On Mon, Apr 25, 2016 at 11:53:45PM +0200, Craig Bradney wrote:
> the list of commits to be reviewed were:
> 
> r21114
> r21115
> r21117
> r21118
> r21123
> r21124
> r21125
> r21126
> r21128
> r21130
> r21131
> r21132
> r21135
> r21136
> r21138
> r21142
> r21144
> r21145
> r21146
> r21150
> r21155
> r21158
> r21160
> r21165
> r21168
> r21169
> r21174
> r21177
> r21188
> r21193 (bugs 13881/13948 from the list)
> r21194 (13871 from the list)
> 
> Craig
> 
> 
> > On 25 Apr 2016, at 23:52, Craig Bradney <cbradney at scribus.info> wrote:
> > 
> > I can now pretty easily build CTL nightlies… 
> > 
> > https://sourceforge.net/projects/scribus/files/scribus-svn/CTL/
> > 
> > I just uploaded a build. Note, it has NOT been tested in any way.
> > 
> > Craig
> > 
> > 
> >> On 25 Apr 2016, at 16:59, Khaled Hosny <khaledhosny at eglug.org> wrote:
> >> 
> >> AFAIK, all boxes related fixes in trunk are either picked in the CTL
> >> branch, solved in a different way, or was already solved while doing the
> >> CTL integration. The only remaining issue in this category is the
> >> performance of linked text frames which will probably be a none-issue
> >> when we introduce a general shaping cache (like many other users of
> >> HarfBuzz).
> >> 
> >> Other than that, this is the list of issues we need to fix before the
> >> code is ready to be merged:
> >> https://github.com/HOST-Oman/scribus/milestones/Complex%20text%20layout
> >> 
> >> One particularly difficult issue in this list is breaking lines inside
> >> ligatures: https://github.com/HOST-Oman/scribus/issues/144 To put it
> >> simply, I don’t have a clear idea how to fix this, yet. I know how TeX
> >> handles it (it stores both the ligated glyph and its non ligated
> >> components in its “shaping” output) but it can’t be replicated with
> >> HarfBuzz with a very big performance penalty (need to reshape the text
> >> several times with and without the ligatures and check the difference)
> >> or sacrificing layout accuracy.
> >> 
> >> Any help with the remaining issues is highly appreciated, it is only me
> >> and Fahad working on the code now in our spare time.
> >> 
> >> Regards,
> >> Khaled
> >> 
> >> On Mon, Apr 25, 2016 at 09:16:21AM -0500, Scribus User wrote:
> >>> Hi everybody,
> >>> I'm writing this email to get things straight and clear about where is CTL
> >>> in comparison to trunk these days. FYI, I'm not speaking for the Scribus
> >>> team here, just working to understand for my own perception. Thank you for
> >>> your patience.
> >>> 
> >>> Recently a github bug was open on Host-Oman repo
> >>> https://github.com/HOST-Oman/scribus/issues/147 (although we don't know if
> >>> these are the only blockers for 1.5.2 yet). Host-Oman responded that most
> >>> of these were fixed but needed testing to confirm. Also Craig recently sent
> >>> an email with revisions that Scribus Team made in Trunk in order to fix
> >>> some regressions from 'boxes' merge (Craig, where is that list BTW, could
> >>> you resend?)
> >>> 
> >>> 1. Are all these things reconciled?
> >>> 2. Are there any pending issues that need to be addressed? Lets list them.
> >>> 3. In order to get more widely tested, CTL needs to be built nightly so
> >>> that testers can confirm the Host-Oman's great progress. Can we organize a
> >>> place and methodology for this to happen? (I've tried to spearhead this but
> >>> encountered some technical problems:
> >>> https://github.com/HOST-Oman/scribus/issues/118). Any volunteers, please
> >>> make yourselves heard.
> >>> 
> >>> Thanks for all the work so far from everybody involved!
> >>> 
> >>> Cheers,
> >>> /Kunda
> >> 
> >>> _______________________________________________
> >>> scribus-dev mailing list
> >>> scribus-dev at lists.scribus.net
> >>> http://lists.scribus.net/mailman/listinfo/scribus-dev
> >> 
> >> 
> >> _______________________________________________
> >> scribus-dev mailing list
> >> scribus-dev at lists.scribus.net
> >> http://lists.scribus.net/mailman/listinfo/scribus-dev
> > 
> > 
> > _______________________________________________
> > scribus-dev mailing list
> > scribus-dev at lists.scribus.net
> > http://lists.scribus.net/mailman/listinfo/scribus-dev
> 
> 
> _______________________________________________
> scribus-dev mailing list
> scribus-dev at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus-dev