<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">This sounds fine. Looking forward to it!</div><br class=""><div><blockquote type="cite" class=""><div class="">On 21 Jan 2016, at 06:16, Dawood al-badi <<a href="mailto:dawood.albadi@gmail.com" class="">dawood.albadi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="rtl" class=""><div style="text-align:left" class="">As Mr Fahad explain, for now we just implementing boxes tree method for storing glyphs but this is the difficult part in our work because it require major changes in scribus. I think this part known by all of you because it not related to CTL so, I will complete this part completely before I move to CTL and I will integrate it with the updated SVN version. After that, I will send patch with this implementation for you for further testing. Then, integrating harfbuzz and freebidi will be straight forward for me or for any one interested in CTL because it will not need much and complex coding as box implementation required. What do you think about that solution ??<br class=""><br class=""><br class=""></div><div dir="ltr" style="text-align:left" class="">regards<br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote"><div dir="ltr" class="">2016-01-20 22:49 GMT+04:00 Fahad Al-Saidi <span dir="ltr" class=""><<a href="mailto:fahad.alsaidi@gmail.com" target="_blank" class="">fahad.alsaidi@gmail.com</a>></span>:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Jan 20, 2016 at 10:27 PM, Craig Bradney <<a href="mailto:cbradney@scribus.info" class="">cbradney@scribus.info</a>> wrote:<br class="">
> We should be able to set some basic timers on the layout code for a frame of<br class="">
> Latin text, and then run the same tests with Latin text with the CTL code in<br class="">
> place. Then run similar tests for CTL texts. IIRC Andreas had some QTimers<br class="">
> in the layout code already.<br class="">
<br class="">
</span>Great to know that.<br class="">
<span class=""><br class="">
> For the initial import we would want to see little to no change for Latin<br class="">
> texts at a minimum.<br class="">
><br class="">
<br class="">
</span>As Andreas planned [1], the first stage , which is " Implement a<br class="">
box-oriented layout mechanism", has no thing to do with CTL text.<br class="">
Right now, all the work done is to support Latin text. You can see<br class="">
some screenshots & video of the current status of Boxes layout<br class="">
implementation here: <a href="https://github.com/andreas-vox/ScribusCTL/pull/18" rel="noreferrer" target="_blank" class="">https://github.com/andreas-vox/ScribusCTL/pull/18</a><br class="">
we want first to make sure that there is no regression in processing<br class="">
Latin text, then we can move to add CTL support.<br class="">
<br class="">
[1] <a href="https://github.com/andreas-vox/ScribusCTL/issues/3#issuecomment-128344149" rel="noreferrer" target="_blank" class="">https://github.com/andreas-vox/ScribusCTL/issues/3#issuecomment-128344149</a><br class="">
<div class="HOEnZb"><div class="h5"><br class="">
_______________________________________________<br class="">
scribus-dev mailing list<br class="">
<a href="mailto:scribus-dev@lists.scribus.net" class="">scribus-dev@lists.scribus.net</a><br class="">
<a href="http://lists.scribus.net/mailman/listinfo/scribus-dev" rel="noreferrer" target="_blank" class="">http://lists.scribus.net/mailman/listinfo/scribus-dev</a><br class="">
</div></div></blockquote></div><br class=""></div>
_______________________________________________<br class="">scribus-dev mailing list<br class=""><a href="mailto:scribus-dev@lists.scribus.net" class="">scribus-dev@lists.scribus.net</a><br class="">http://lists.scribus.net/mailman/listinfo/scribus-dev<br class=""></div></blockquote></div><br class=""></body></html>