On 27 Oct 2020, at 19:09, Albrecht Schlosser wrote:
> 
> 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’m (generally) in favour of this mechanism, though I take Albrecht’s point that adding a dependency on Cairo may not be ideal... The output looks good, and the additional print support it brings is useful.


Is there some scheme whereby we get the current behaviour for builds *with* print support but *without* Cairo, and this improved behaviour for builds with both print support and Cairo enabled?

How complex is that?



-- 
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/3299E66F-C949-4E59-BA78-B727F39CB166%40gmail.com.