From: Martin H. <mar...@si...> - 2013-05-24 13:49:37
|
Dear All, Announcing a new release of Graphite2, downloadable from the normal culprits: http://projects.palaso.org/attachments/download/378/graphite2-1.2.2.tgz http://sourceforge.net/projects/silgraphite/files/graphite2/graphite2-1.2.2.tgz/download Here is the relevant section of the Changelog: . Add support for passKeySlot (makes Charis 2x faster) up to 32 passes . Add telemetry output to json if enabled in build GRAPHITE2_TELEMETRY . Shrink font memory footprint particularly in the fsm . Add -S to comparerenderer . Bug fixes: . Fix shift.x being reversed for rtl text . Fix faulty fallback justification . Fix bad cmap handling . Support compiling on old Solaris where bidi attributes clash with register names . Follow the crowd in using Windows.h The most exciting of these is the first where we have made a change to the compiler that means that a suitably compiled font has an attribute that for each pass has a bit. If the bit is set, then this particular glyph does not force the pass to be run. Thus if all the glyphs in a run do not require a pass to be run, the pass can and is skipped. This can radically speed up things like pure lowerascii shaping. A key bug fix is that shift.x was working the wrong way round in rtl fonts. This has been fixed in this release. Yours, Martin |
From: Shriramana S. <sa...@gm...> - 2013-05-24 16:12:19
|
Hello Martin and thanks for this update. I'd like to know what's with the windows.h thing. Why was it necessary and I hope it need not concern me who am on Linux. Sent from my Android phone |
From: Martin H. <mar...@si...> - 2013-05-24 16:23:28
|
Dear Shriramana, > I'd like to know what's with the windows.h thing. Why was it necessary and > I hope it need not concern me who am on Linux. It won't affect linux builds for obvious reasons (windows.h doesn't get used on linux). The reason is to do with mingw builds. Basically, while the filename is one, everyone uses the wrong name and it gets sorted out. We were doing the right thing and it was causing problems. In short, this should make things better not worse and it's what all other projects of this kind do, so we are merely following the crowd. Yours, Martin |
From: Jonathan K. <jfk...@go...> - 2013-05-24 18:03:46
Attachments:
clang-direct
|
On 24/5/13 21:49, Martin Hosken wrote: > Dear All, > > Announcing a new release of Graphite2, downloadable from the normal culprits: > Thanks, Martin! One small thing I happened to notice when building it standalone (i.e. using Graphite's CMake build system) was that it refused to build the "direct" machine and fell back to "call" instead. This happens because on my system the clang compiler is found under the name /usr/bin/c++. It's a symlink to clang++, but the fact that it is found first under the c++ name means that the check at CMakeLists.txt:54, which looks at CMAKE_BASE_NAME, fails to detect it as clang++. Would it be reasonable to change this to check CMAKE_CXX_COMPILER_ID instead of CMAKE_BASE_NAME, as per the attached patch? For my system (OS X with standard Apple tools), at least, this correctly detects clang and happily builds the "direct" machine. (This isn't an issue for our build within Mozilla, as we don't use the CMake system. But for anyone building Graphite by itself on OS X, at least, it may be helpful.) JK |