|
|
On Wed, 28 Oct 2020 at 07:23, Manolo <manolo.gouy@gmail.com> wrote:
>
> - If OPTION_USE_PANGO is not activated, the usual PostScript driver remains in the code which
> gives full printing support, except it draws non-Latin characters in bitmap form.
>
Ah - I had missed that...
I think that mostly addresses my concerns then, as we will fall back
to the "legacy" behaviour if pango is not enabled...
On Linux, I pretty much always have pango enabled in 1.4 builds
anyway, so I had not really grasped that was what would happen.
So, a user that builds *without* pango enabled will get the "legacy"
postscript support, and no new dependency is introduced.
A user who builds *with* pango enabled will get the improved
postscript support, and potentially added dependency on libs that can
be assumed to be present if pango is present.
Is that a reasonable statement?
If so then I am in favour of this enhancement.
--
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/CAGFM6dYaS1HuaQ01Op99zsBw1SW3qOEAgnDE%2BeXkCNDDVXxAzQ%40mail.gmail.com.
[ Direct Link to Message ] | |
|
| |