Giuseppe Castagno wrote:
mm..., and if the PDF filter could export font clever-wise? I mean,
using the same font the user provided for the control, if that exist in
the OOo document, or using some kind of font fall back, for example the
same provided by the display rendering? I think there is some kind of
fall back in the display rendering code of OOo, ain't it?
You can only set one font in the PDF widget appearance stream. The
fallback would have to be done by the reader app; and even if that were
possible (possibly CID fonts can do that), rendering some glyphs with
one font and other glyphs with another font will just end up looking
like crap (as it does when OOo's font fallback needs to replace single
glyphs in a font).
However currently we do not have a solution for locales outside
WinAnsiEncoding at all. I think at least for eastern fonts we will not
come around using a system font not contained in the PDF file (we cannot
download a font containing 10000 glyphs for chinese for example, such a
font would alone have some 40 MB or so).
May be make this behavior selectable instead of enabling the user to
fiddle with fonts.
Actually the user can fiddle with fonts in OOo already :-) He can select
the font a form control uses; the originaly issue was that that font
does not appear in the created PDF file.
Just some idle thoughts :-).
It's not a trivial matter really, any thoughts are welcome.
Kind regards, pl
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
