>>>>> "Alejandro" == Alejandro Aguilar Sierra <[EMAIL PROTECTED]> writes:
Alejandro> Hello, It seems that freetype 1.2 is quite stable now. For
Alejandro> wordprocessing pourposes, using our own font server is very
Alejandro> convenient. We have discussed the reasons so I'll just
Alejandro> remember you some of them:
Yes, the only thing which is missing is their high-level library,
which is planned for 2.0.
Alejandro> I think it's important that we start to discuss how to add
Alejandro> this support. IMO it's even more important than the
Alejandro> bundled scripting language support, at least for 1.1.
Yes, we should start discussing that, indeed.
Alejandro> Of course this should be in some way encapsulated in the
Alejandro> painter (lyxfont is just the code of the font). We could
Alejandro> support transparently both TT and T1 fonts and still
Alejandro> support fonts from the X server. Maybe we could left the T1
Alejandro> support to the X server.
- we should make sure that plain X fonts are still supported.
- we don't need to support T1 since the rasterizer in type1lib is the
same broken rasterizer that X has. It is slow and ugly, whereas
freetype is fast and exact.
- we could maybe bundle a part of freetype (only the source of the
lib) with LyX, since the codebase is small.
- A stupid question: would it be feasible/difficult to use PK fonts
directly? This would be a very good solution LaTeX-wise.
JMarc
