| |
| |
On 10/27/20 4:46 PM Manolo wrote:
I propose to fix a limitation of our PostScript support where only latin
characters can be output in vectorial form to PostScript. Non-latin scripts
are output in bitmap form.
That is relevant for the X11 platform where FLTK printing uses PostScript.
[That is not important under Windows and macOS because printing
fully supports all of unicode in vectorial form there.]
OK, sounds good.
The solution I propose is to use cairo's PostScript surface, and to
activate that
by "configure --enable-pango" or CMake's OPTION_USE_PANGO.
Hmm, as I read this, this means that building FLTK with Pango and
(optional) print support will additionally require Cairo (libpangocairo,
IIRC). Is this true?
I think this would be a (kinda) regression that should be avoided. Note
that I disabled libpangocairo on my Linux system (by editing
CMake/options.cmake in a non-standard way, see below) for testing and
this broke the compilation.
Maybe my test failed because it was faulty, but anyway, this needs
clarification. TIA.
I attach, as an example, the PostScript output for test/editor and
misc/lorem_ipsum.txt
containing all sorts of scripts.
Awesome!
It's all at
https://github.com/ManoloFLTK/fltk.git
in branch pango-ps
Checked out, built, but not yet tested...
Please, vote about my proposal to commit that to FLTK 1.4.
Thanks.
Need some testing and, before I vote, I'd like to see the question above
answered. I wouldn't like to have a dependency on Cairo for builds that
don't need it (for instance, using only latin scripts).
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/b70d658b-965d-2ce4-0e28-c7c555b45e98%40online.de.
[ Direct Link to Message ] | |
|
| |
