Merge pull request #6 from khaledhosny/typos
Combine the two if’s
Update changelog
Fix webpage URL
Typo
Make writing outlines with Cairo actually work
Release 5.0 and new development website
Hello your ticket was moved to the new issue tracker: https://github.com/eugmes/fntsample/issues/5 Please subscribe there if you'd like to be notified about changes.
Add option to render missing glyphs with FreeSerif
Do not hardcode Blocks.txt into the program
Hi, in the new release (5.0) it is now possible to specify an alternate blocks file using --blocks-file option. This should help in your use case. The release is available from github: https://github.com/eugmes/fntsample/releases/tag/release%2F5.0
Improve errors handling when reading Unicode blocks at runtime
Remove configure.ac
Add new options to the manpage and update the website link
Scan unicode_blocks.c for translatable strings
Add support for reading Unicode blocks file at runtime
Add README
Update the website link
Add screenshot
Update message catalogs
Don't pass --verbose to xgettext
Update Ukrainian translation
Update changelog
Fix directory change in Travis config
Update Ukrainian translation
Revert "Depend on pango >= 1.37 and remove conditional compilation"
Compile with -Werror on Travis-CI
Add Travis CI config file
Build everything using CMake
Add fntsample --help for testing and install it into temporary directory
Fix compiler warning when cairo with outlines support is not available
Depend on pango >= 1.37 and remove conditional compilation
Link fntsample executable with math library
Make autoreconf install needed files
Fix passing options to make in Travis config
Use Pango for drawing glyph cells
This is commited
Add an option to use add PDF outlines with Cairo
Commited, thanks
Update message catalogs
Fix warning
Merge pull request #2 from khaledhosny/pango-cairo
Add an option to use Pango for drawing glyph cells
Add an option for writing outlines directly
I can make it an option and send a GitHub pull request. For my fonts the difference between using Freetype and Pango is the difference between not showing glyphs at all and showing them correctly. The dotted cirrcle is a feature for me as well (though it can be disable by putting a space before the marks), as it makes combining from non-compining marks clear and make it easy to see if the mark applies above or below the base.
Hi, sorry for late reply. I had time to test your patch, and for me result does not always look better than without it. Cairo adds circles for combining marks that look bad with DejaVu Sans for example. Also with DejaVu Sans some (historic) characters in Cyrillic range look off-center. I'll probably make this layout selectable as command line option for now. BTW I've created a repo on Github where I plan to move the development of this project: https://github.com/eugmes/fntsample
This seems to have been introduced in 1.37.0 from May 2015 (judging by git log).
Here is an updated version of the patch to check for Pango version explicitely.
It was introduced in Pango 1.37, released in May 2015 (based on the git tag).
Add an option to use add PDF outlines with Cairo
Do not hardcode Blocks.txt into the program
Add option to render missing glyphs with FreeSerif
Thanks for the patch. I'll incorporate it when I'll have slightly more time to test...
Use Pango for drawing glyph cells
Thanks for your report. Both bugs are fixed now in version 4.1.
Problems finding libiconv
Update ChangeLog
Detect iconv and add LIBICONV to LDADD
Detect support for -Wl,--as-needed in configure
Set version to 4.1
I also wanted to add something unrelated. I had to remove -Wl,--as-needed from LDFLAGS...
Problems finding libiconv
Thanks!
Update change log
Prepare to release 4.0
Fix broken handling of font names
I've commited your patch. Additionally I extended buffer for UTF-8 decoding and fixed...
Fix broken handling of font names
Update gettext version in Makefile.in.in
Extend buffer size for UTF-16 to UTF-8 conversion
Update translation files
I don’t think a font will work on Windows without the MS platform names, and it will...
Thanks for your report. I agree that current font name handling is a bug. I have...
Add an option to not embed the font files
That's fixed in commit ab679c6feb26f90c405e1072872a9d1ddd15e8c5. Thanks.
Add a --no-embed option
Fix broken handling of font names
Add an option to not embed the font files