https://bugs.documentfoundation.org/show_bug.cgi?id=62846
--- Comment #40 from [email protected] --- @Laslzo in that case may I beg you to try to get the warnings count as close to 0 as you can. If there are any that you find particularly difficulty, please feel free to contact me. In addition, rules of the kind: x > y / a _ b run much faster that a x b > a y b in addition the engine will look backwards for the a and will start processing at the b for the next rule. You can still use ^ if you want to reprocess your results: x > y / a ^ _ b notice that you can do multiple replacements in complex contexts: x y z > u v w / a _ b _ c _ d if you are just setting attributes then: x > @x{attr=3} / a _=x b or x > @2{attr=3} / a _ b the less work you can get your font to do the faster it will run. Another trick is to split big passes into smaller ones with pass constraints. E.g. how about all those \ replacement rules going in their own pass with a pass constraint saying: don't do this pass if the feature isn't enabled. That'll make the font smaller and faster. There are other speed up tricks that you can do. But let's start with these simple ones first. Happy hacking. You may also like graide as a good test and development environment. Look for it on graphite.sil.org -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
